Every week free software activists from around the world come together in #fsf on irc.freenode.org to help improve the Free Software Directory. This recaps the work we accomplished at the Friday, May 26th, 2017 meeting.

Our most recent meeting was focused on adding new entries. A new feature of the recent update to the Directory played a big role. Occasionally when sorting through unapproved pages (new pages that haven't been reviewed), we would would come across a page that was actually just a redirect. Sometimes a package will change names, or a variation in naming would cause multiple entries to end up in the Directory. Having the old page redirect to the correct one helps to keep the Directory clean and easy to navigate. But it turns out these redirects were making for a messy log of unapproved pages, as they would end up generating a new page that required approval. With the recent update, these redirected pages are now highlighted, which enabled us to get through about thirty of them during the meeting on Friday.

In the spirit of adding more to the Directory, we also launched a volunteer project for importing large amounts of entries. The project enables us to import package information from free software repositories. Long ago a friend put together scripts that we used to import thousands of entries. But thousands upon thousands more could be added if we update the import scripts.

The project has been sitting idle for a while now at https://savannah.gnu.org/p/directory, just waiting for volunteers to jump in and refine it. The scripts are in Python, so if you're a seasoned Python hacker this would be a great way to contribute.

While it will take quite a bit of work, the effort will have a truly profound effect on the Directory. If we can get the project up and running, it will greatly expand the number of entries and in the future can help to keep them up to date.

If you are interested in lending a hand, please email directory@fsf.org with the subject "Directory Import Volunteer" and tell us a bit about yourself.

If you would like to help update the directory, meet with us every Friday in #fsf on irc.freenode.org from 12 p.m. to 3 p.m. EDT (16:00 to 19:00 UTC).

(as of May 25, 2017):

• artanis-0.2.1
• diffutils-3.6
• emms-4.3
• gcc-7.1.0
• global-6.5.7
• gnupg-2.1.21
• gnutls-3.5.12
• guile-cv-0.1.4
• icecat-52.1.0-gnu1
• kawa-2.4
• libidn2-2.0.2
• libmicrohttpd-0.9.54
• linux-libre-4.11.2-gnu
• nano-2.8.4
• orgadoc-0.9
• parallel-20170522

For announcements of most new GNU releases, subscribe to the info-gnu mailing list: https://lists.gnu.org/mailman/listinfo/info-gnu.

To download: nearly all GNU software is available from https://ftp.gnu.org/gnu/, or preferably one of its mirrors from https://www.gnu.org/prep/ftp.html. You can use the URL https://ftpmirror.gnu.org/ to be automatically redirected to a (hopefully) nearby and up-to-date mirror.

This month, we welcome Bernhard Voelker as a new co-maintainer of GNU Findutils and John Darrington as maintainer of the new package GNU spread-sheet-widget.

A number of GNU packages, as well as the GNU operating system as a whole, are looking for maintainers and other assistance: please see https://www.gnu.org/server/takeaction.html#unmaint if you'd like to help. The general page on how to help GNU is at https://www.gnu.org/help/help.html.

If you have a working or partly working program that you'd like to offer to the GNU project as a GNU package, see https://www.gnu.org/help/evaluation.html.

As always, please feel free to write to us at maintainers@gnu.org with any GNUish questions or suggestions for future installments.

In this edition, we interviewed AJ Jordon, the founder of gplenforced.org, a project for hosting easy to use badges for copyleft licenses. By using the badge, a project can share their values and the importance of copyleft enforcement with all their users.

What inspired the creation of the GPL enforced badge?

So basically Bradley Kuhn gave a talk at FOSDEM '17 about GPL enforcement and I was like, wow, it sucks how many companies and people think that enforcing the GPL is a bad idea. I mean, if you disagree with copyleft that's fine (though I personally would argue with that position), but then you should use a suitable license. Like MIT. The very idea that we shouldn't enforce the GPL just doesn't make sense to me because it suggests that the text of the license is watery and unimportant. I don't know about you, but when I say I want my programs to respect users' freedom, I mean it.

So GPL enforcement is important. It seemed to me that there are probably a lot of developers out there who want to support GPL enforcement but don't have a good way to voice that support. gplenforced.org is essentially a quick and dirty hack I wrote to make that dead-simple.

Tell us more about gplenforced.org

gplenforced.org is a small site I made that has exactly two purposes: host a badge suitable for embedding into a README file on GitLab or something, and provide some text with an easy and friendly explanation of GPL enforcement for that badge to link to.

Putting badges in READMEs has been pretty trendy for a while now — people add badges to indicate whether their test suite is passing, their dependencies are up-to-date, and what version is published in language package managers. gplenforced.org capitalizes on that trend to add the maintainer's beliefs about license enforcement, too.

How can projects make use of the GPL enforced badge?

It's super easy! All you have to do is add some Markdown to your README.md file (or some AsciiDoc, etc.). Then it will show up on your code hosting site and link to the website. That's it. Instructions are on gplenforced.orhg.

That's what makes this project work, I think: as I alluded to above, it's such an easy process there aren't really a whole lot of reasons not to do it as long as you support the message. It gives people a way to support GPL enforcement who otherwise wouldn't have time to do something more involved.

Are there plans to create badges for other copyleft licenses?

Absolutely (it's bug #3 in the issue tracker). The current plan is to add badges for the LGPL and AGPL only — this will allow us to keep the site 100% static, which makes it dead-simple to host.

Letting people use arbitrary badges would require making the site dynamic. So I might consider doing that if there's a need for it, but for right now the plan is to add badges on an ad hoc basis, as people want them. Not letting people use arbitrary badges also means that they couldn't make, say, an "MIT enforced" badge which maybe doesn't really make sense.

How can users or developers help out?

Send patches and encourage adoption! There's a small list of TODOs in the issue tracker that people can work on, and of course if anyone has ideas about how to improve the project, they're welcome to add to that list. I take issues and patches via email too.

What's the next big thing for gplenforced.org?

Adoption! In particular when I get around to adding the other licenses I plan to send patches to prominent GPL'd/LGPL'd/AGPL'd projects on GitLab and GitHub suggesting they add it. This project is about raising awareness — and the best way to do that is to spread it as far and wide as possible.

Enjoy this interview? Check out our previous entry in this series, featuring the MegaGlest Project

Participate in supporting the Directory by adding new entries and updating existing ones. We will be on IRC in the #fsf channel on irc.freenode.org.

Tens of thousands of people visit directory.fsf.org each month to discover free software. Each entry in the Directory contains a wealth of useful information, from basic category and descriptions, to providing detailed info about version control, IRC channels, documentation, and licensing info that has been carefully checked by FSF staff and trained volunteers.

While the Directory has been and continues to be a great resource to the world over the past decade, it has the potential of being a resource of even greater value. But it needs your help!

A lot of great work is being done keeping the Directory up to date. But it must keep growing if it is to be a useful resource. This week we'll be working on adding new entries to the Directory, and reviewing packages that haven't been reviewed yet. We'll also be looking to launch a new project that could greatly increase the number of works in the Directory.

If you are eager to help and you can't wait or are simply unable to make it onto IRC on Friday, our participation guide will provide you with all the information you need to get started on helping the Directory today! There are also weekly Directory Meeting pages that everyone is welcome to contribute to before, during, and after each meeting.

Every week free software activists from around the world come together in #fsf on irc.freenode.org to help improve the Free Software Directory. This recaps the work we accomplished at the Friday, May 19th, 2017 meeting.

This week the Directory meeting looked at education software. During the meeting, we had numerous pieces of software being offered up for inclusion. In addition, new software was added to the Directory, as well as some older entries getting an update. The meeting also spent some time exploring the relationship between software and educational institutions. The dialogue centered on how these educational institutions indoctrinate dependence on nonfree software and ways to shift this paradigm. AlKamoD returned this week and was getting ready to run tests to automate certain tasks, the results of this are anticipated.

If you would like to help update the directory, meet with us every Friday in #fsf on irc.freenode.org from 12 p.m. to 3 p.m. EDT (16:00 to 19:00 UTC).