FLOSS Project Planets

DrupalCon News: Wednesday Keynote with Joe Shindelar

Planet Drupal - Fri, 2017-08-11 16:59

We're looking forward to  our community keynote in Vienna, and here's why.

Joe Shindelar is a developer, artist, and snowboarding enthusiast who has been building Drupal sites and participating in Drupal core development since 2006. Joe is also very active in the Drupal issue queues where he has helped to develop and improve Drupal's image handling and manipulation features, contextual links, and various other bits and pieces.

Categories: FLOSS Project Planets

François Dion: Readings in Visualization

Planet Python - Fri, 2017-08-11 16:29
"Ex-Libris" part V: Visualization
Part 5 of my "ex-libris" of a Data Scientist is now available. This one is about visualization.
Starting from a historical perspective, particularly of statistical visualization, and covering a few classic must have books, the article then goes on to cover graphic design, cartography, information architecture and design and concludes with many recent books on information visualization (specific Python and R books to create these were listed in part IV of this series). In all, about 66 books on the subject.
Just follow the link to the LinkedIn post to go directly to it:
"ex-libris of a data scientist, part V

From Jacques Bertin’s Semiology of Graphics
"Le plus court croquis m'en dit plus long qu'un long rapport", Napoleon Ier
See alsoPart I was on "data and databases": "ex-libris" of a Data Scientist - Part i
Part II, was on "models": "ex-libris" of a Data Scientist - Part II
Part III, was on "technology": "ex-libris" of a Data Scientist - Part III
Part IV, was on "code": "ex-libris" of a Data Scientist - Part IV
Part VI will be on communication. Bonus after that will be on management / leadership.Francois Dion
P.S.Je vais aussi avoir une liste de publications en francaisEn el futuro cercano voy a hacer una lista en espanol tambien
Categories: FLOSS Project Planets

The FSF needs Fall 2017 interns! Apply by August 25

FSF Blogs - Fri, 2017-08-11 16:05

As an intern, you work closely with FSF staff members in your area of interest, such as campaigns and community organizing, systems and network administration, GNU Project support, or Web development.

We're seeking interns for two teams at the FSF:

  • Tech team: Common tech team intern projects include writing free software, security auditing, interacting with one or more of our servers, and researching new technology that the FSF is interested in using. Past interns created HUBAngl, which we use for easy video streaming of our conferences, made progress in porting LibreJS to WebExtensions, pen-tested our network, and researched the Ceph distributed object storage system, which we are now rolling out as our latest infrastructure upgrade. However, we're also eager to hear what you would like to work on, because that can give us new ideas and open new doors. This position may work in our Boston office or remotely.

  • Campaigns team: This round, we'd love to find an intern who is adept at design and/or illustration to redo key handouts and guides. These items will make a great addition to your portfolio, and will be a huge help in our efforts to publicize our campaigns. This position is in our Boston office.

You can read more about our requirements for interns here, and see past intern projects here.

How to apply

Send a letter of interest and resume with two references by email to hiring@fsf.org. Make sure that your materials are in free software friendly formats (PDF and plain text work well), and include "Internship" in your subject line. If you can, please include links to sites you've made (personal blogs are okay!), designs or code you've done, and relevant writing. Please include these as URLs, though email attachments in free formats are acceptable, too.

Please direct any questions about the program to hiring@fsf.org.

Categories: FLOSS Project Planets

NumFOCUS: How rOpenSci uses Code Review to Promote Reproducible Science

Planet Python - Fri, 2017-08-11 13:30
This post was co-authored by the rOpenSci Editorial Board: Noam Ross, Scott Chamberlain, Karthik Ram, and Maëlle Salmon. — At rOpenSci, we create and curate software to help scientists with the data life cycle. These tools access, download, manage, and archive scientific data in open, reproducible ways. Early on, we realized this could only be […]
Categories: FLOSS Project Planets

Michal Čihař: Weblate 2.16

Planet Debian - Fri, 2017-08-11 13:15

Weblate 2.16 has been released today while I'm at DebConf17. There are quite some performance improvements (and more of that is scheduled for 2.17), new file formats support and various other improvements.

Full list of changes:

  • Various performance improvements.
  • Added support for nested JSON format.
  • Added support for WebExtension JSON format.
  • Fixed git exporter authentication.
  • Improved CSV import in certain situations.
  • Improved look of Other translations widget.
  • The max-length checks is now enforcing length of text in form.
  • Make the commit_pending age configurable per component.
  • Various user interface cleanups.
  • Fixed component/project/sitewide search for translations.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English SUSE Weblate

Categories: FLOSS Project Planets

Simple is Better Than Complex: Django Tips #21 Using The Redirects App

Planet Python - Fri, 2017-08-11 12:10

Django comes with a few optional apps that can easily be installed. One of those apps is the Redirects App, which is particularly useful in the cases where you want to update some existing URLs without compromising your Website SEO or in any case avoid 404 errors.

It basically works by creating a table in the database with two columns, old_path and new_path. Every time your Website raises a 404 error, the Redirects App will intercept the response and check this particular table for a match. If the requested URL is found in the column old_path, instead of raising the 404 error, it will redirect the user to the new_path returning a 301 code (Moved Permanently).

Alright, so let’s see how it works in practice.


The Django Redirects App requires the sites framework to be installed. You can install them by adding the apps to your project’s INSTALLED_APPS:


INSTALLED_APPS = [ 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'django.contrib.sites', 'django.contrib.redirects', ]

Set a SITE_ID so the sites framework works properly.



Now, add the redirects middleware to the MIDDLEWARE configuration:


MIDDLEWARE = [ 'django.middleware.security.SecurityMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.contrib.redirects.middleware.RedirectFallbackMiddleware', ]

Make sure you run the migrate command to create the required tables:

python manage.py migrate Usage

The easiest way to use is through Django Admin. If you are not currently using the Django Admin app, and it’s a one time thing (for example you are migrating a site from other platform), you can use just the Python API via command line or creating a fixture. If you are not using Django Admin and still wants to add it as a functionality for the site administrator, then you will have to create your own views for it.

Using the Redirects App with Django Admin

It will be automatically added to the Django Admin interface.

You will see, it’s very straightforward. Just add the paths and it will do all the hard work for you.

We can test it by typing the old path in the browser and see if redirects correctly. Another way is examining the response body in the terminal. You can easily do it by using curl:

curl --head HTTP/1.0 301 Moved Permanently Date: Fri, 11 Aug 2017 15:42:27 GMT Server: WSGIServer/0.2 CPython/3.6.1 Content-Type: text/html; charset=utf-8 Location: /tips/redirects-app/ X-Frame-Options: SAMEORIGIN Content-Length: 0 Using the Redirects App with the Python API

You can manually create the redirect records interacting directly with the Redirect model. It lives in django/contrib/redirects/models.py

You can start a Python shell with your project models loaded by running the following command:

python manage.py shell

Here is how you can create a few redirect entries:

from django.contrib.redirects.models import Redirect from django.contrib.sites.models import Site from django.conf import settings site = Site.objects.get(pk=settings.SITE_ID) Redirect.objects.create(site=site, old_path='/index.html', new_path='/') Redirect.objects.create(site=site, old_path='/tips/2017/08/11/django-tip-21.html', new_path='/tips/redirects-app/') Using the Redirects App with Fixtures

Just create a JSON file following the template of the example below:


[ { "model":"redirects.redirect", "fields":{ "site":1, "old_path":"/tips/2017/08/11/django-tip-21.html", "new_path":"/tips/redirects-app/" } }, { "model":"redirects.redirect", "fields":{ "site":1, "old_path":"/index.html", "new_path":"/" } } ]

Then you can load it directly to your database by running the command below:

python manage.py loaddata redirects-fixtures.json Installed 2 object(s) from 1 fixture(s)

And that’s it!

Categories: FLOSS Project Planets

Latte Dock v0.7, "...a tornado is coming..."

Planet KDE - Fri, 2017-08-11 12:05

Latte Dock v.0.7 has been released!!! The second Latte  stable release has just landed! 
Go get it fromgithub ! 

- youtube presentation -
Latte v0.7

if you dont want to build it yourself, you can wait a few days to launch on your distro repositiories!
Take notice, Latte v0.7 is only compatible with:

  • Plasma >= 5.9
  • KDE Frameworks >= 5.29
  • Qt >= 5.7

What to expect in the new release, you may ask...

multiple layouts in editor

Dynamic Layouts
you can have different layouts for your Latte which are updated dynamically without closing the application. At the same time you can assign these Layouts to your Activities, meaning that when you get into one of those Activities, Latte is updating its layout accordingly. To achieve the above goal we provide an all new Layouts Editor.

Hint: The previous Alternative session is now supported through Layouts

appearance page in basic modeBasic/Advanced Mode
we simplify things for new users by providing two different modes for the configuration window. If you prefer simplicity stay with the Basic mode. On the other hand if you prefer full customizability, the kde style, switch to Advanced mode. We tried to follow the kde moto:

" simple by default,
powerful when needed "

six different visibility modes

Windows Go Below
a sixth visibility mode was added, in order for your dock to be always on top without taking up space from other windows. So now we provide, Dodge Active, Dodge Fullscreen, Dodge Windows, Auto Hide, Always Visible, Windows Go Below

title tooltipsTitle Tooltips
Show the title of the items during hovering. Such as tasks or applets that support the parabolic effect.

background of Arc Dark theme with
35% opacity and no shadows

Enhance Configurability
You can change the dock offset, the panel transparency, define a different shadow for the applets and enable/disable the panel shadow.

top dock with no maximized window availableDynamic Background
same dock with maximized window

Show the panel background only for maximized windows and be transparent otherwise.

three separators (two as applets and one internal)
not blocking the parabolic effect

support separators everywhere including one special internal separator for tasks

hearing radio in the browserAudio Streams
audio stream indicator for tasks, the user can increase/decrease/mute the volume through this indicator

use the global launchers group
for this dock

Launchers Group
Unique: a unique set of launchersGlobal: the global set of launchersLayout: the layout set of launchers
Hint: these groups are used in order to sync launchers between different docks

official plasma taskmanager in LattePlasma Taskmanagers
support applets that take up all the free space of the dock (in Justify alignment).
So the user is now able to replace the Latte Tasks plasmoid with his favourite plasma taskmanager

hearing the radio, downloading a file and
three messages waiting to be read

libunity support
support the libunity way of showing counters and tasks progress through the plasma way of doing this.

Tip: the libunity9 library is needed

                           Global Shortcuts
Super : show the app launcher, howto...Super+` : show the dock if hidden and expose the task numberSuper+Number : activate the relevant taskSuper+Ctrl+Number : create a new instance for the relevant task

five unread e-mailsThunderbird Plugin

a community provided thunderbird plugin using the Latte dbus interface to expose the number of unread e-mails. You can download it from here.

Wayland Tech Preview

We are trying to support wayland for the Plasma environment and so we now provide a tech preview. You shouldnt notice any difference except bugs that exist also at the desktop environment. The docks are positioned correctly and most of the features should work already.

Hint: As this is a tech preview expect some things to break or not work correctly. Plasma team has moved its focus to wayland so you could expect from us improvements following of course their development steps...

fixes / improvements
  • switch completely to plasma libtaskmanager for launchers and tasks
  • improve color handling for window different states
  • add Widgets through the context menu
  • places support from Plasma 5.10
  • a special Latte spacer that its size can be set in pixels or in percentage according to the current Latte icon size
  • active window indicator for window previews
  • copy dock support, fantastic feature for multi-screen environments
  • remember last active window in a tasks group and use the mouse wheel to cycle through a tasks group
  • restart Latte in case of a crash
  • overlay over plasma applets such as forlderview in order to provide correct parabolic effect (bug: showing problematic animations for icon sizes smaller of 64px)
  • provide our own build-in active applet indicator in case the user wants to have uniformity across its docks
  • move the lock button from the drag area into the tooltip
  • disable automatic icon size shrinking when a plasma taskmanager is used
  • improvements for parabolic effect and  various animations
  • support import/export for layout independently and for the full configuration
  • support automatic and manual importing from v0.6 architecture

You can read Latte v.0.6 - fresh air... for features introduced in previous version...

-------------------Wallpaper    "Old Paper" at, wallpaperswide.com
Music:    1. BoxCat Games - "Epic Song" at, freemusicarchive.org
    2. Podington Bear - "Now Song" at, freemusicarchive.org 
    3. Podington Bear - "Buddy Guy" at, freemusicarchive.org

Categories: FLOSS Project Planets

Palantir: Learning by Doing: Palantir’s Internship Program

Planet Drupal - Fri, 2017-08-11 11:44
Learning by Doing: Palantir’s Internship Program brandt Fri, 08/11/2017 - 10:44 Alex Brandt Aug 14, 2017

Our interns bring fresh new perspective to our team.

In this post we will cover...
  • Why we love having interns
  • Some skills our interns learn
  • An intro to our current Summer interns

Stay connected with the latest news on web strategy, design, and development.

Sign up for our newsletter.

There are many different facets of “the Palantir way,” but one principle that sticks out the most is the encouragement to be continuously learning. As a company, we are strong advocates for the concept of “learning by doing,” which is why we’ve had a summer internship program going for years. We believe paid internship opportunities are essential to figuring out what career path is best for you, and they can be beneficial for both the company and the intern.

Our interns are provided the opportunity to see what it’s like to work on real projects with a development team while getting exposure to working through a process with clients. They gain experience using tools like Github and JIRA, and a deeper understanding of responsive design, open source software, and Agile development.

We’ve found that our interns bring huge value with new perspective to our team. They give other Palantiri an opportunity to work on mentorship, and our buddy system means we gain a quick understanding of our interns’ existing skills, so we can help them grow that skillset more effectively.

The added bonus of our internship program is that both sides get to leave with an understanding of whether or not it’s a good fit. Being a remote-first company, it’s nice for our interns to be able to test drive remote work and see if it works for them.

We’ve had such tremendous success in hiring our interns as full-time employees (you might be familiar with Ashley, Kelsey, Patrick, and Matt), that we’ve recently decided to expand our program beyond summer to accommodate the awesome candidates that have extended availability.

Meet Our 2017 Summer Interns! Lily Fisher

Q: Why were you excited to come work at Palantir?
A: While poking around the website and blog, I saw the previous clients Palantir worked with. I wanted my first job to be fulfilling and a learning experience that allowed me to grow during my pursual of a Computer Science career. Based on the eloquent, effective, and personal approach this company takes when serving their clients, I felt like working with Palantir would allow me to grow while working on real projects in a wholly-understanding professional environment.

Q: Who is the most famous person you’ve ever met?
A: I had a conversation with Alan Parson about my involvement in music.

Q: What do you most like to do to unwind?
A: Skateboard.

Q: What is the first thing you do when you wake up/start your day?
A: Cuddle with my hamster.

Jose Arreluce

Q: Why were you excited to come work at Palantir?
A: I was excited to come work at Palantir as I believed that Palantir’s internship perfectly fit what I was looking for. It presented the opportunity to work on real projects that would have an impact on real people, while also allowing me to learn extensively about how websites are developed in a professional environment. I was also excited by what I saw on Palantir’s website regarding its previous projects and the company culture, as well as by the emphasis on learning.

Q: What excites you about the web?
A: The vast amount of knowledge and opportunity for learning it provides. The memes are nice too.

Q: In 5 years time you hope to be. . .
A: In five years I hope to be working as a software engineer, pursuing an advanced degree, and to have run at least a half marathon.

Q: What do you most like to do to unwind?
A: Running, especially on the Chicago lakefront on a nice day.


Want to know more about Palantir? Check out our culture page or read through our bios. Think it sounds like a good fit? Send us your resume.

Want to work at Palantir?

Send us your resume!
Categories: FLOSS Project Planets

Mike Gabriel: @DebConf 2017: Ayatana Indicators

Planet Debian - Fri, 2017-08-11 11:30

On last Tuesday, I gave a 20 min talk about Ayatana Indicators at DebConf 17 in Montreal.

Ayatana Indicators Talk

The talk had video coverage, so big thanks to the DebConf video team for making it possible to send the below video link around to people in the world:


The document of notes shown in the video is available on Debian's Infinote (Gobby) server:

$ sudo apt-get install gobby $ sudo gobby infinote://gobby.debian.org/debconf17/talk/ayatana-indicators

The major outcome of this talk was getting to know Dimitri John Ledkov from the Foundation Team at Canonical Ltd. We agreed on investigating the following actions, targetting the Ubuntu 18.04 LTS release and later on Debian 10 (aka buster):

Upstream Todos
  • We need to find out what indicator applets are still needed (already there: application, session, power; w-i-p: messages, not yet touch: sound, datetime, transfer). If you maintain a desktop environment and need indicator support, please contact us.
  • Rip-out liburl-dispatcher and Mir related code from all ayatana-indicator-* code projects (upstream)
  • Build-time disable phone and tablet related code (upstream). If you are from the UBPorts project and have concerns about this, please contact us.
  • Fully deprecate all Ubuntu Indicators upstream projects on Launchpad and point to Ayatana Indicators as upstream source for indicators in the Ubuntu ecosystem
Debian/Ubuntu Todos
  • Update https://wiki.debian.org/Ayatana, most important change for packagers: The team will use Git from now on, not Bazaar.
  • Get in touch with people maintaining indicator related packages (packages that have libappindicator-dev as build-dependency) to prepare for the transition from Ubuntu Indicators (unmaintained upstream, unmaintained in Debian) to Ayatana Indicators (package list, see DDPO Ayatana Developers Overview)
  • File bug reports against all packages still dependending on Ubuntu Indicators in Debian and ideally provide patches to make those packages build against Ayatana Indicators
  • Do the Ayatana Indicator transition in Debian
Please get in Touch...

As this is going to be quite an effort, esp. if we want to get this done until 18.04 LTS, let me say, that this blog post is a call for help. If you are attached to Ubuntu and have used desktops with indicator support until now, please get in touch with the Ayatana Indicators team upstream as well as downstream (Debian/Ubuntu).


  • Ayatana Indicators upstream:
    • #arctica on Freenode IRC
  • Ayatana Indicators in Debian:
  • Ubuntu Desktop Developers:
    • #ubuntu-desktop on Freenode IRC

Looking forward to meeting you online or on person and possibly working together with you on this transition project.

Categories: FLOSS Project Planets

Mike Gabriel: @DebConf17: Story Telling about Debian Edu in Northern Germany

Planet Debian - Fri, 2017-08-11 10:40

Last Monday, I gave a 20min talk about our little FLOSS school project "IT-Zukunft Schule" at the Debian Conference 17 in Montreal.

The talk had video coverage, so may want to peek in, if you couldn't manage to watch the life stream:


I'd like to share some major outcomes (so far) of this talk.

  1. I realized how attached I am to "IT-Zukunft Schule" and how much it means to me that our kids grow up in a world of freedom and choice. Also and esp. when it comes to choosing your daily communication tools and computer working environment
  2. I met Foteini Tsiami and Alkis Georgopoulos from Greece. They work on LTSP and have deployed 1000+ schools in Greece with LTSP + Debian GNU/Linux + MATE Desktop Environment
  3. I met Vagrant Cascadian who is the maintainer of LTSP in Debian and also a major LTSP upstream contributor
  4. I received a lot of fine feedback that was very encouraging to go on with our local work in Schleswig-Holstein

If you have some more time for watching DebConf talks on video, I dearly recommend the talk given by Alkis and Foteini on their Greek FLOSS success story. If you don't have that much time, please skip through the video until you are at 26:15 and enjoy the map that shows how much Debian + LTSP has spread over all of Greece.


Unfortunately, the schools in Greece are so much smaller than schools in Germany. Most schools there have between 50 and 300 students. So at the Greek schools, it is possible to have a teacher machine being the server for one computer lab. This teacher / server machine provides the infrastructure for a room full of LTSP fat clients (no hard drive inside) and that's it.

For German schools, unfortunately, we need a larger scale setup. German schools often have 800+ students and network services need to be spread over more than one server machine. So, the current approach with one server running LDAP, Kerberos etc. is quite appropriate, but also extendible, possibly on municipality level or on county level.

We (from IT-Zukunft Schule) are quite positive that there will be opportunities for introducing FLOSS approaches more on the county level in Schleswig-Holstein in the near future. So stay tuned...

Categories: FLOSS Project Planets

Shane Curcuru: Dear future self (Time Capsule 2017)

Planet Apache - Fri, 2017-08-11 10:15
We’re rebuilding the front steps, and since the masons are using concrete blocks, we have an opportunity to include a time capsule. Here are a few notes we’re including. Dear Future Shane This is a message from the past. The … Continue reading →
Categories: FLOSS Project Planets

Lucas Nussbaum: systemd services, and queue management?

Planet Debian - Fri, 2017-08-11 08:40

I’ve been increasingly using systemd timers as a replacement for cron jobs. The fact that you get free logging is great, and also the fact that you don’t have to care about multiple instances running simultaneously.

However, sometimes I would be interested in more complex scenarios, such as:

  • I’d like to trigger a full run of the service unit: if the service is not running, it should be started immediately. If it’s currently running, it should be started again when it terminates.
  • Same as the above, but with queue coalescing: If I do the above multiple times in a row, I only want the guarantee that there’s one full run of the service after the last time I triggered it (typical scenario: each run processes all pending events, so there’s no point in running multiple times).

Is this doable with systemd? If not, how do people do that outside of systemd?

Categories: FLOSS Project Planets

Dutch Open Projects: Content Security Policy and Drupal

Planet Drupal - Fri, 2017-08-11 08:19
What is CSP?

Content Security Policy – or CSP – is a security feature of modern browsers. Browsers will ignore data from domains that are not cleared in the CSP http-response header. For instance if you embed a YouTube movie on a webpage and the domain is not whitelisted in the CSP header, then the movie will not be loaded. All traffic from youtube.com will be blocked and the movie cannot be displayed.

Categories: FLOSS Project Planets

InternetDevels: Web development “chemistry”: a fantastic reaction between Drupal and ReactJS

Planet Drupal - Fri, 2017-08-11 07:57

Combining different tools to produce fantastic reactions is the true “chemistry” of web development. The special trend of the day is using Drupal with JavaScript tools. We’ve had a chance to look at the benefits of using Drupal with Angular and Drupal with Node.

Read more
Categories: FLOSS Project Planets

agoradesign: Horizontal Tabs in Drupal 8

Planet Drupal - Fri, 2017-08-11 07:48
Drupal 8 ships with a great and easy to use 'vertical_tabs' form element but unlikely a horizontal counterpart is missing. I'll show you, how can get horizontal tabs into your forms.
Categories: FLOSS Project Planets

Anubavam LLC: PHP 7 can help improve Drupal site performance

Planet Drupal - Fri, 2017-08-11 06:38
PHP 7 can help improve Drupal site performance

Drupal is PHP 7-ready and sites that run many contrib modules, or particularly memory-intensive ones, will need more memory requirements. Optimizing Drupal website performance with PHP 7 version will boost the overall page speed. 

PHP 7 was released in December 2015 and offers high performance, huge load capacity and asynchronous programming support  for online applications. According to the latest study, PHP 7 is twice as fast as PHP 5.6 and reduces memory usage.

Why this is the right time to move to PHP 7

Drupal 7 core officially supports PHP 5.2.5 or higher  However, PHP 7 introduces backward incompatible changes which may need to be addressed in contributed or custom modules and themes. While some Drupal 7 sites may run on minimum of PHP versions, you can move to Drupal 8 with PHP 7 support to enhance the performance of the site.

Drupal 8 officially supports 200+ new features and improved functionalities, and upgrading to PHP 7 brings a lot of improvements and delivers high performance Drupal site, whether you are a website owner or a Drupal developer

Drupal core's automated test suite is now fully passing on a variety of environments where there were previously some failures (PHP 5.4, 5.5, 5.6, and 7). Several bugs affecting those versions were fixed as well. These PHP versions are officially supported by Drupal 7 and recommended for use where possible.

Anecdotal evidence from a variety of users suggests that Drupal 7 can be successfully used on PHP 7, both before and after the 7.50 release. 

A slow website load time impacts visitors, overall user experience, and the bottom line. With the improved speed enhancements of Drupal 7 and Drupal 8 with PHP 7, your user engagement and experience will increase and less likely they will leave your website

admin Fri, 08/11/2017 - 06:38 Drupal 8 Drupal Application Development
Categories: FLOSS Project Planets

Akademy; at 20, KDE reaches out

Planet KDE - Fri, 2017-08-11 04:08

Some of the talks, initiatives, conversations, and workshops that inspired me at Akademy. Thanks so much for the e.V. for sponsoring me.

A. Wikidata  - We have some work to do to get our data automatically uploaded into Wikidata. However, doing so will help us keep our Wikipedia pages up-to-date.

B. Looking for Love, Paul Brown's talk and workshop about Increasing your audience's appreciation for your project. Many of the top Google results for our pages don't address what people are looking for:

  1. What can your project do for me? 
  2. What does your application or library do?
Paul highlighted one good example: https://krita.org/. That crucial information is above the fold, with no scrolling. Attractive, and exactly the approach we should be taking in all our public-facing pages.

My offer to all projects: I will help with the text on any of your pages. This is a serious offer! Just ask in IRC or send an email to valorie at kde dot org for editing.

C. The Enterprise list for people with large KDE deployments, an under-used resource for those supporting our users in huge numbers, in schools, governments and companies. If you know of anyone doing this job who is not on the list, hand along the link to them.

D. Goalposts for KDE - I was not at this "Luminaries" Kabal Proposals BoF, but I read the notes. I'll be happy to see this idea develop on the Community list.

E. UserBase revival -- This effort is timely! and brings the list of things I'm excited about full circle. For many teams, UserBase pages are their website. We need to clean up and polish UserBase! Join us in #kde-wiki in IRC or the Telegram channel and https://userbase.kde.org/Wiki_Team_Page where we'll actually be tracking and doing the work. I'm so thankful that Claus is taking the leadership on this.

If you are a project leader and want help buffing your UserBase pages, we can help!

In addition to all of the above ideas, there is still another idea floating around that needs more development. Each of our application sites, at least, should have a quality metric box, listing things like code testing, translation/internationalization percentage, number of contributors, and maybe more. These should be picked up automatically, not generated by hand. No other major projects seem to have this, so we should lead. When people are looking for what applications they want to run on their computers, they should choose by more than color or other incidentals. We work so much on quality -- we should lead with it. There were many informal discussions about this but no concrete proposals yet.
Categories: FLOSS Project Planets

Anwesha Das: Blocking of archive.org in India

Planet Python - Fri, 2017-08-11 03:49

My morning starts with the quick look at twitter.

Yesterday some tweets drew my attention - The Internet Archive over at http://web.archive.org has been blocked in India. There was a long thread going on, and people were asking, updating thoughts and opinions on the matter.
Ok, this is something important.

What is archive.org?

I searched. I did not have any idea about this previously.
I found that one of the most important projects on the site is “The WayBack machine”; for the site serves/saves/documents the history of the world wide web. Therefore it gives you a salient history of different sites on a single search.

But for last few days many people, in India, could not access archive.org and The Wayback Machine.
Instead, this is what people saw

Specifically, the http://web.archive.org has been blocked but when you add the secure “s”; https://web.archive.org can be accessed.

It was important to have information about which ISPs were actually blocking the site. Tweets poured in from people, across the country. You can find an elaborate list of these ISPs in this blog post by Medianama.

Officials from archive.org were trying to contact the authorities, in India, at the Ministry of Electronics and Information Technology (MEITY) and the The Telecom Department (DoT). Unfortunately they never responded.

Recent update:

According to a tweet, the site was banned according to a judgment made by The Madras High Court, in Prakash Jha Productions v/s Bharat Sanchar Nigam Limited and Others (being, O.A.Nos. 705 to 707 of 2017 in C.S. No. 576 of 2017). It could not be confirmed due to the unavailability of the original judgment document.
According to the tweet by Anivar Arvind, it was a John Doe order. John Doe order means an order passed by the competent Court of Justice against unidentified defendants.

The confusion:

The silence and lack of/no communication on the part of the Government authorities created a lot of confusion.

There were questions such as -
1. Why is the site blocked?
2. Who blocked the site?
3. Is there is any provision to remove the block? And measures (if any) to be taken.

Unfortunately the request is not been heard by the concerned authorities till now.

The sole requirement in this context is, transparency and clarity.
We, the common people have the right to know what is happening in our digital space.
Denying that is a repudiation of a basic and primary right of ours.

The situation has posed a serious question in front of us,
Is this a step taken by the authorities to curb, and restrain our digital (fundamental) rights? (though the Government is trying its level best to prove that we do not have one.)

Categories: FLOSS Project Planets

Dirk Eddelbuettel: #8: Customizing Spell Checks for R CMD check

Planet Debian - Thu, 2017-08-10 22:29

Welcome to the eight post in the ramblingly random R rants series, or R4 for short. We took a short break over the last few weeks due to some conferencing followed by some vacationing and general chill.

But we're back now, and this post gets us back to initial spirit of (hopefully) quick and useful posts. Perusing yesterday's batch of CRANberries posts, I noticed a peculiar new directory shown the in the diffstat output we use to compare two subsequent source tarballs. It was entitled .aspell/, in the top-level directory, and in two new packages by R Core member Kurt Hornik himself.

The context is, of course, the not infrequently-expressed desire to customize the spell checking done on CRAN incoming packages, see e.g. this r-package-devel thread.

And now we can as I verified with (the upcoming next release of) RcppArmadillo, along with a recent-enough (i.e. last few days) version of r-devel. Just copying what Kurt did, i.e. adding a file .aspell/defaults.R, and in it pointing to rds file (named as the package) containing a character vector with words added to the spell checker's universe is all it takes. For my package, see here for the peculiars.

Or see here:

edd@bud:~/git/rcpparmadillo/.aspell(master)$ cat defaults.R Rd_files <- vignettes <- R_files <- description <- list(encoding = "UTF-8", language = "en", dictionaries = c("en_stats", "RcppArmadillo")) edd@bud:~/git/rcpparmadillo/.aspell(master)$ r -p -e 'readRDS("RcppArmadillo.rds")' [1] "MPL" "Sanderson" "Templated" [4] "decompositions" "onwards" "templated" edd@bud:~/git/rcpparmadillo/.aspell(master)$

And now R(-devel) CMD check --as-cran ... is silent about spelling. Yay!

But take this with a grain of salt as this does not yet seem to be "announced" as e.g. yesterday's change in the CRAN Policy did not mention it. So things may well change -- but hey, it worked for me.

And this all is about aspell, here is something topical about a spell to close the post:

This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.

Categories: FLOSS Project Planets

Bryan Pendleton: Backpacking 2017: Trinity Alps, South Fork of the Salmon River

Planet Apache - Thu, 2017-08-10 20:44

Some backpacking trips go exactly as planned.

Others do not.

This one did not go as planned, but in the end it was wonderful, in that "well, nobody was seriously hurt, after all!" way that mis-adventures sometimes happily are.

To get to the headwaters of the South Fork of the Salmon River, you need to be prepared to do a bit of driving:

  1. Make your way from wherever you may be to the quirky little town of Weaverville
  2. Head north from Weaverville, where you might decide to spend the night at the lovely little Bonanza King Resort if you wish
  3. The next morning, drive up the 20+ mile dirt road to the very end, where you'll find Big Flat Trailhead. This road will take you 75 minutes to drive. Honest.

From the Big Flat Trailhead, ready your pack, and don't forget to make sure you secure your car carefully so that it's completely boring to any California Black Bear who might wander through the campground (this is not uncommon, since the habitat of the California Black Bear is nearly a 100% overlap with the areas of California where there are campgrounds).

Once you're safely out of your car and ready, the rest is easy: walk south.

The canyon which forms the watershed which holds the headwaters of the South Fork of the Salmon River is a spectacularly beautiful mountain canyon. From the trailhead to the end of the canyon is a gentle, peaceful, 6-mile hike which starts at about 5,000 feet of elevation and climbs slowly and steadily to around 5,800 feet near the south end of the canyon.

Most hikers who enter the Trinity Alps Wilderness from this trailhead area actually headed out of the canyon, to one of a variety of destinations: southwest to the Caribou or Sapphire Lakes, south to Deer Creek, south-southeast to Ward and Horseshoe Lakes, or southeast to Bullard's Basin and the mining ghost town of Dorleska.

Instead, we decided to stay in the Salmon River headwaters canyon itself.

Well, I should be a bit more honest.

Originally, we were contemplating going to Ward Lake. But, after more studyand reading, I realized that this particular destination was going to be beyond our capabilities for a one day hike:

Total Length (round-trip): 12 miles
Elevation Gain: 2,549’ to the saddle, then -460’ down to the lake
Difficulty: Moderate-to-Strenuous
or, more colorfully: High above the densely forested moraine, just beginning to emerge against the cloudless blue, rose a massive fortress, a sheer vertical wall of gray rock, toward which our trail zig-zagged.

Uhm, yeah.

That wasn't going to work.

So instead we decided not to take the Kidd Creek trail to Ward Lake, and proceeded south, remaining in the main canyon of the South Fork of the Salmon.

Which is beautiful and delightful, and we made quite good time, until at about 3:00 PM we found ourselves at the far south end of the canyon, confronted by canyon walls on all three sides (east, south, west).

I had (sort of) a plan for this, for I had spotted on the map that the true headwaters of the Salmon River was found at Salmon Lake, a mere three quarters of a mile from where we stood.

And a mere 1,300 vertical feet above our 5,800 foot elevation at the time.

There is no trail to Salmon Lake, but we were standing on the shore of the Salmon River, looking up its course as it descended the narrow and steep canyon above us, and it seemed, tantalizingly, close.

So, with our minds probably clouded from the fatigue of the first 5.5 miles that we'd already hiked, we decided to try to go off-trail and bush-whack our way up the river canyon to the lake.

I estimate that we made it about one tenth of the way to the lake over the next 30 minutes, climbing slowly and stubbornly through dense manzanita fields that clung to scree slopes of sharp fractured shale that shifted unexpectedly and continuously underneath our feet.

And then the lightning clapped, and the thunder boomed, and the rain began.

And, at last, we came to our senses.

After we realized that our plan was hopeless, and we re-grouped back at the trail, we were soaked from the rain and a bit dispirited, even more so when we realized that the mid-slope ridgeline we were on held no decent campsites of any sort.

Worse, several of us had fallen during the bushwhacking on the wet shale, and so twisted ankles and bloodied shins were widespread.

As we sat, resting and recovering, watching a pair of trees on the opposite side of the canyon smouldering from lightning strikes, we cast our eyes below us, and realized that the canyon floor below us was beautiful, had a reliable source of water, and was almost certain to contain some spots where we could make camp.

So back down we headed, retracing our steps about a half mile down the trail until we were back to the canyon floor, then hiking another half mile or so south until we indeed found a spectacularly beautiful location to stay: not too far from water, but not too close either, with just enough trees for shelter, but just few enough to give us glorious views of the canyon ridges above.

Completely exhausted from more than 9 miles of walking with full packs, we just managed to set up camp and prepare dinner before it was fully dark and the stars were out.

Yet the next few days passed blissfully: each day dawned with blue skies and mile weather and we found many nearby areas for lovely day hikes, including an enjoyable long walk up the trail to the pass on the border of Trinity and Siskiyou counties, where we unexpectedly found a beautiful high mountain meadow, with hawks soaring and calling overhead and chipmunks and rabbits and quail busily occupying themselves amongst the meadow grasses.

Quite reliably, it thundered and lightninged and rained every afternoon, and once even delivered a dramatic 15-minute hailstorm, but after surviving our disastrous first day's hike, it all seemed like icing on an unexpectedly tasty celebration cake.

So if you ever find yourself wanting to go backpacking in the headwaters canyon of the South Fork of the Salmon River in the Trinity Alps wilderness, let me offer these simple suggestions:

  • Yes, Ward Lake is a long haul, and that ridgeline ascent is as miserable as you fear.
  • But Salmon Lake is even harder. You'd need to be a mountain goat to get there.
  • And, if you spot a lake on the map, even if it looks "close" to the trail, but when you go and search the Internet and you can't find EVEN A SINGLE PICTURE of anyone who's actually made it to the lake's shore, stop and recognize what that means: You Ain't Gonna Get to Salmon Lake
  • So just be happy exploring the beautiful Salmon River canyon instead.

That's what I have to say about that. Enjoy the pictures!

Categories: FLOSS Project Planets
Syndicate content