Free Software Directory:Backlog

From Free Software Directory
Revision as of 13:49, 30 March 2018 by Donaldr3 (talk | contribs)
Jump to: navigation, search


  • Approved revs bug. On the main entry pages, there is a bug where if a page has had at least one approval, then a non-admin edits it, the main page shows the latest edit instead of the last approved revision.
  • Remove exposure of database strip marks from pages under License namespace. Currently some (if not most) licenses in License namespace have a "pre"/"nowiki" element in their call text to their associated template. This is problematic because the template itself already wraps the text in "pre", so the result is a exposure of the database strip marks. When in the "Read" tab, pages in License namespace that are affected by this issue have a yellow triangle next to the start of the license text.
  • Make the license texts in License namespace preserve their initial space. Revisions 49613 and 49636 for the {{License}} template already implement a workaround for this issue, but this requires a mass replace in all calls to {{License}}, so as to replace |Full text= with |.
  • Make comments in License namespace point to license evaluation page of GNU project if they exist there. This should also add the benefit of having that page translated to the contributor or visitor/guest's language.
  • There should be a space dedicated for scripts that can be downloaded by FSD volunteer. I suggest a link to a page in the side-bar that lists the scripts.
  • Proof read: I have emailed already emailed to Donald and asked him to suggest the sysadmins to have a look on this. However, we must proof-read the FSF staff tasks section so the FSF sysadmins clearly understand the text so they can start working on this.
  • Proposed features for the FSD
  • Category browsing
  • Fix search results, so that template data doesn't get dumped into the description below the page links. In other words, just put in the beginning of the description.
  • When people set the license for a project to be "GPL 2 or higher", it gets added to the autocompletion list for that field, even though that license isn't on the approved list at: Property:License. ("GPL 2 or higher" isn't on the list because it is misformatted. The correct entry is "GPLv2orlater".)
  • add a link for binary download?
  • need to implement mass-emails about email verification, and directions for changing preferences.
  • Add/update GNU packages
  • Populate license pages, such as License:GPLv3. Also, we should just paste in the text of licenses to the page itself, to avoid the formatting issues we'd get if we passed it through a template. We should keep and populate the Name= and URL= fields though.
  • "Preview" button does not work for Template:Entry. It shows the unedited version, but I don' think there is a way around this from our end, as the displayed values are based on a query of the saved page.
  • Put a link to site dumps and info about the machine readability of that information on the main page.
  • Created HTML tooltips for the different fields in Form:Entry, or create a tutorial for Form:Entry that describes what each field is for.
  • Pages incorrectly created with Form:Bug_update (without the "Review:" namespace prefix) are queryable. If they are then moved to the Review: namespace, then they remain queryable. I'm not sure if a non-admin can edit the page, which could let them create a false entry in the directory.
  • Update the queries on GNU/Export to make sure the second column is the GNU package name property
  • Update each GNU project with the GNU package name
  • Add "table of contents" header above tabs inside noscript tags so that it only displays when javascript is turned off.
  • Autopopulate License verified date field if it is empty.
  • We need to let people submit bug reports, etc. without javascript enabled. If we could use something like a "noscript" tag, then we could display the following link: Example bug report link
  • 'new messages' text overlays the red FSF links bar, so you can't click it. Still, you can just click your 'talk' page link instead.
  • "New Packages RSS feed"'s license verification dates are messed up.
  • home page of every GNU package (yes, really) to be listed as <>
  • conditional statements should be created for various properties (e.g., "Audio:mp3" should result in "works-with::Audio" being set on a page automatically).
  • Turn off error/warnings in SMW <-- Why? It makes it impossible for administrators to debug the wiki. --David Hedlund (talk) 00:59, 29 March 2018 (EDT)
  • Add screenshots to entries.


  • Remove edit links in Search results
  • Linked "Related Projects" entries
  • The width values can be improved in {{Print entry}}:
    • <div style="float:left; width:60%; margin: 2px 4px 0px 4px;">
    • <div style="float:right; width:35%; margin: 2px 4px 0px 4px;">
  • Standardize the Homepage links for all 400+ GNU packages in
  • Indicate active IRC meetings. Fixed in
  • Set up RT for bug tracking and tiket making
    • need to create "Category:Review-triaged" once RT has been set up. (Probably won't happen)
  • there are some phantom details in the icecat entry, like the redundant license, verified in 2004, the prerequisites, etc. what i mean is that there is information showing up that isn't stored on the entry's source.
  • Fix both broken bug report links on pages that contain spaces in their names: GNU Linux-libre. The culprit is Template:Show.
  • Find a way to tell users that they need to login before they submit a bug. Right now, they are told: "You do not have permission to edit this page, for the following reason: The action you have requested is limited to users in the group: Users.". It's not a very helpful message.
  • Turn off 1,000 character limit for strings This was relate to a bug in MediaWiki, that has been fixed in an upgrade.
  • Searching for "python" or "ruby" shouldn't lead to "License:Python" or "License:Ruby" (The problem is because these pages, such as Ruby, or Expat redirect to License:Ruby, etc. We should do a <replace_text> command to remove these redirects. Jgay removed a couple by hand.) Now we just need to put entry info into Python, etc.
  • Devise a a way to hide the Submitted by and submitted date fields in Form:Entry, unless it is a new entry. Maybe we can auto-populate them too.
  • GNU Entries say "This is a GNU project". Kberry says that rms doesn't like the word "project", so we should change that to "package". Also, there are mentions of that word elsewhere, like the "Featured Projects" thing and the pages describing that feature..
  • "Edit with Form" doesn't allow one to update the "last reviewed by" field
  • List of categories on Main_Page is too long The layout has changed, an is hopefully more usable now.
    • fix the program tagging, so all programs are included in the main page redesign. This issue has been worked around.
  • Update the Form:Bug report to include the Category:Bug_report tag through a template.
    • Then update the pages in the Category:Bug_report name-space to visibly contain the category tag.
    • Then update Template:Bug_report to not include it automatically.
    • Should Category:Alert be changed like this as well, so we can distinguish new alerts from old ones? Done: one can change the "Nonfree" template field to "completed".
  • Make sure that the Bug_report pages and Review pages have links that are easily accessible by contributors. See FSD:Workflow.
  • For pages in Category:Review, we should have a link to create the relevant page (such as Review:xprog -> xprog) with Form:Entry if it doesn't already exist. We would need to use regular expressions to cut of the "-REV-ID-1" stuff. (or we could just set the proper pagename value as a property when Form:Submit is called.)
  • Rename the "Editor" property to "Editing", etc. (because the "Use" property is its parent, and its related value is "Editing", not "Editor". There are multiple instances of this dual naming.) Actually, Use: is not its parent. That property value refers to Audio editing (which is annoying because mixing, etc. also appears in Use: ).
  • Verify that '-'s have replaced spaces in all properties and their values. The issue was with Concept page names, which has been fixed.
  • Make sure that program names submitted through Form:Submit don't have leading or trailing spaces.
  • FSS subscribe box points to the wrong place (should point to <">, not
  • We should be able to easily browse to all categories from an entry
  • Fix link at bottom of page that links to "Free Software Directory:Copyrights" (in Style files)
  • Create Form Edit tab for appropriate users.
  • delete Audio, etc. (cf. Property:Property_name)
  • this page has a broken title: 2532_Gigs. The problem is that we are using Template:Pipe in the title, which inserts an image of a pipe. If we use the html code for the pipe character, then it gets converted to an actual pipe at some point during semantic queries, and therefore breaks things.
  • Create a template with semantic property that can identify a project as a High Priority Project. Ideally with a graphic, like for GNU projects.
  • Fix links to licenses I've make entries of 'GPLv3' redirect to 'License:GPLv3', etc. by using templates for displaying license query results. At the time of writing, pages should be going through the automatic update process.
  • Export all entries in XML format.
  • Both the user name and the current date should be used for the "submitted by" fields -- they should not be user selectable.
  • GNU Head goes away when you view "further results" in table of results. For instance: Category/Use/copying
    • Slight difference in code of Template:Getlist and ‘show embed code’ of semantic search for that page when viewed after clicking on further results.<|?Is GNU#{{GNU_Head_Small}},=GNU?> changes to < |?IsGNU#[[File:Heckert_gnu.small.png >. Fix the missing <,=GNU?>
  • Make sorting case-insensitive. (See this SMW bug response.)


GNU packages

Make a script to generate XML files that syncs GNU with which also list decommissioned GNU packages, a property that also should be imported, see

See for other examples.

Debian Packaging System

From by Freephile:

The Debian Package Tracking System produces RDF metadata and is already included in DBpedia. For example, here's a 'Turtle' representation of the GIMP package

If all Debian packages are not in the FSD, they could be added by consuming their RDF. If we incorporate their data systematically, then our data becomes easily updated and synchronized by bot.

XML update

Please study these XML outputs in IceCat

It's time to export the old add-on list from the FSD, then import the new list with 600̈́+ add-ons, then merge the extra field from the backup to it.

My example (look for differences) when I want to import 600 add-ons:

|Short description=Only enable JavaScript for sites you trust.
|Full description=The '''NoScript''' (aka '''NoScript Security Suite''') Firefox extension provides extra protection for Firefox, Seamonkey and other Mozilla-based browsers.  Its aim is to allow active content to run only from sites you trust, and protect yourself against XSS and Click-jacking attacks.  It is also useful to prevent Flash running on the browser.

But its main advantage could be the alerts given on its interface. There is an increasing number of Web sites that cannot run without non-free JavaScript programs downloaded and executed on the visitor's computer. Richard Stallman first raised this another concern with his article [ The JavaScript Trap], pointing out that most JavaScript programs are not freely licensed, and that even free software Web browsers are usually configured to download and run these non-free programs without informing the user.  So maybe NoScript could encourage people to keep informed about this related issue and [ take action].

Anyway, NoScript is an extremely valuable Firefox extension for security. Its unique white-list based pre-emptive script blocking approach prevents exploitation of security vulnerabilities (known and even not known yet!) with no loss of functionality...
|Homepage URL=
|User level=intermediate
|Extension of=IceCat
|Documentation note=Install NoScript and enable ‘Forbid scripts globally’ to improve the security of your browser by preventing 0day JavaScript attacks. This is a drastic option as it will render many websites unusable as they rely heavily on JavaScript. NoScript offers a whitelist you can use to selectively enable JavaScript for sites you trust, but this is considered [ especially bad for your anonymity] if you're using NoScript with Tor.
|Related projects=GNU LibreJS, NoScript Anywhere
|Version identifier=
|Version date=2015/05/23
|Version status=stable
|Version download=
|Last review by=David Hedlund
|Last review date=2016/04/21
|Is GNU=No
{{Project license
|License verified by=enyst
|License verified date=2013/03/24
|Resource audience=Users
|Resource kind=Forum
|Resource URL=
{{Software category
|Use=internet-application, security

License issues

  • List incomplete IceCat add-ons. Free Software Directory:IceCat extensions (proposed)/FSD bugs issue 1
  • Add required text for License. For Create, when a user try to save the page with Homepage not filled out the text There were errors with your form input; see below. will appear on the Save tab. On the General info tab the text Homepage URL (required) cannot be blank text will appear. However, there are no text that says that License fields must be filled if they are not.
  • List unapproved IceCat add-ons. We could reuse the source of so we can tweak to show only unapproved IceCat add-ons.
  • Entries with empty Licence fields should not be able to approve. It should only be possible to approve entries with filled License fields. This policy must include the automatic approval when pages are save.
  • License list is incomplete. How do we list all 251 licenses found in to "Edit -> Licenses" for entries?

The license list should only be a drop down menu

Currently the license list found under "Licenses" is a hybrid of a dropdown but you can also add text by hand there too. This is not good as only selected licenses will show up:

Therefore is should neither be possible to enter licenses in free text, it should be a dropdown menu only.

I added "Creative Commons Attribution Share-Alike 4.0" to Lets see if it shows up.
Should be modified to string?

Consistent CSS styling

Some custom templates have CSS style="" clauses scattered in them. One of such clauses was responsible for too narrow columns in the description. I'd suggest to:

  1. Check all local style clauses in our custom code
  2. Determine if they can be more generic. For example, colors, paddings, line widths should be unified to achieve visual consistency.
  3. A set of CSS classes should be designed to replace style clauses
  4. CSS class naming scheme should be decided
  5. New CSS classes should be introduced to MediaWiki:Common.css
  6. style clauses should be replaced with their class="css-class" counterparts.

Backlog Admin Group tasks

These are issues that has effectively been collaborated in the Backlog Admin Group.

Semantic Forms

Property:Resource URL is of type string/text, this allows any value, even phone numbers, SIP, XMPP, etc. Perhaps we should use something along the lines of "Allows pattern" special property in order to avoid abuses. Property:Resource URL is the one currently used in the entry form when someone fills the "resource URL".


To "Edit with form" (Example:

  • The "License" (friendly name: "License and version") input field is too liberal, it accepts any value and if the value is a non-existing page it will appear as a red link who will eventually be created by anyone who see it. Only licenses listed in should be on our "License and version:" drop-down menu.
    • Possible solutions:
      1. Change type from combobox to dropdown. Attempted, but reverted due to issues.
        • This would make the form edit misbehave, as it would not find the already existing values in old entries that are set before the change. Thus, in the form edit, if an already existing entry/page has MPLv2.0 set as License parameter for {{Project license}}, then it won't find it since it expects License:MPLv2.0. Making {{Project license}} set this doesn't work (it was already tried), the only fix for the already existing entries seems to be a mass-replace, so that every call for {{Project license}} that is like this {{Project license |License=MPLv2.0 }} becomes like this {{Project license |License=License:MPLv2.0 }}. The bug described in this item doesn't affect the show/read tabs of each entry.
          • Before attempting to fix this, see if fixing the item below would also fix this one.
        • Must make sure that the allowed values for Property:License or for that license-related input only point to pages at the License namespace. For example, currently Property:License describes Boost as one of the allowed values, however it seems to refer to Boost, not License:Boost.


proprietary program search

When a person searches for a proprietary program, a list of free software replacements for that program should appear in the search results, *however*, the proprietary program and its name should not appear anywhere on the wiki. To achieve this functionality, we may want to use the Enhanced Retrieval extension (obsolete).

License verification

When doing license verification, we need to ensure two things:

  1. More than one person checks a license
  2. We have a system in place for training volunteers (via some sort of mentorship) on how to properly check a project's license.

Point system and mentoring

Some ideas we have discussed is that we might have some sort of scoring system, so that more experienced individuals who check a license have more "points" than people less experienced. Let's say we have three tiers: level-1, level-2, level-3; with level-1 being the most experienced. A check by a level-1 person might be worth 15 points, a level-2 might be worth 10 points, and a check by a level-3 person might be worth 5 points. It might be that a license is properly "checked" if it has a score of at least 25 points. To coordinate this work we might consider using an extension such as Semantic Tasks.

But, more important than the point system is ensuring that level-3 individuals are not only verified by level-1 individuals, but, that some 1-on-1 guidance and help/mentoring is provided to level-3 individuals from level-1 individuals.

FSF staff tasks

Please give us a dedicated bug tracker. There are to many bugs and issues on this page now to work with it effectively. Everything is a mess.

Some work, like modifying the source files of MediaWiki, cannot be done by MediaWiki users themselves. We gather such tasks here so the FSF staff can help us fix them.

A dedicated bug tracker for the Directory

This page has to many bugs to effectively organize them. We need a dedicated bug tracker for the Directory.

The concept for public bug trackers for FSF run websites has been posted in Directory-Discuss mailing-list.

Matt Lee said that he back in January 2017 but nothing happened and he never replied!

Semantic MediaWiki

Link text

IRC (temporarily fixed)

The IRC resource is displayed twice like this on IceCat for example.

IRC general channel
  • I attempted to fix this but it seems that something is interfering with the formatting. Strangely enough, if I make a simple page without the form, and use the IRC template, it works as expected. I don't know if this is the case, but I think there is some template interfering.--Adfeno (talk) 23:23, 26 January 2018 (EST)
  • As requested in #fsf IRC channel, here is the comment I made there, describing my studies so far:
    • It basically involves three templates (it might involve more, but I only researched three so far) {{Print entry}} {{Entry}} and {{Show}}. There is a fourth one ({{IRC}}) but I think we might be able to replace it ({{Print entry}} calls it, so instead of calling {{IRC}}: we can take the code from it and insert in the caller template).
      • I think that #replace will just mask the underlying issue. --David Hedlund (talk) 10:49, 27 January 2018 (EST)
    • I think there is so far the following possibilities:
      1. an issue between the templates used;
      2. an issue with the #ask: queries and the template result format;
      3. we have reached a setting limit that makes the formatting not work (perhaps a limit on the template result format, although I have tried to remove the call to {{IRC}} but it didn't work, we might have to make tests by simplifying the template result calls even further to see if this is indeed the problematic setting);
      4. an issue with the "IRC [level name]" properties when setting (#set:) or their query and display.
    I think we can make use of #nowiki or #- display parameters when querying for the "IRC [level" properties of an entry (this is queried for in {{Show}}) in order to take the property value in raw (example: but then we will need to change either {{Print entry}} or {{IRC}} (the first one is the problematic, so I recommend to test with it first) so that it removes irc: but also allows any other : (because the URL scheme allows port numbers).
    --Adfeno (talk) 08:47, 27 January 2018 (EST)
  • While MediaWiki understands IRC URLs very well, Our copy Semantic MediaWiki gets confused if a property of type URL has a protocol different from HTTP, this problem also happens if the property definition/setting is invisible (using #set:), but in all cases it works as expected if the protocol is HTTP. I don't know if this is a bug in Semantic MediaWiki (or MediaWiki) but this affects at least our copy of it. An example of the issue with IRC property can be seen in: --Adfeno (talk) 11:32, 27 January 2018 (EST)
  • As of SMW 2.5.1, http https and ftp URL schemes will be printed with double slashes, all other without:  « Saper // @talk »  12:49, 27 January 2018 (EST)
Multiple software categories (temporarily fixed)

Not only are the text merged but also the URL in the link. For IceCat: <a href="/wiki?title=Category/Programming-language/C_C%2B%2B_javascript_rust&action=edit&redlink=1" class="new" title="Category/Programming-language/C C++ javascript rust (page does not exist)">Programming-language:C C++ javascript rust</a>


Remove duplication

Remove duplicated entries

The value of |Extension of= is displayed twice in some entries (one year ago perhaps 5 duplicated were displayed but John Sullivan and/or Joshua Gay managed to fix most of the duplicates either by himself or someone else). For example, "Add to Search Bar" appear twice there, but "Aardvark" appear only once.

The duplicates also affect lists that the entries are in, see this page for test purpose that I've set up:

       > I contacted Joshua in March this year about this and he responded.

       > "I will look into this. I am not sure why the redirects are making it
       > show-up twice. It shouldn't. However fixing it is not a simple matter of
       > removing them -- it is a bug in the software."

    Please report the bug to

    Dr Richard Stallman
    President, Free Software Foundation (,
    Internet Hall-of-Famer (
    Skype: No way! See

Remove duplicated short description ticket: [ #1205033]

Short description now appear automatically on software entry pages.

We had to copy the short description into the full description before thus creating duplicated text. The job to do now is to remove those duplicates. I added this to the Backlog.

Semantic search

Special:AdminLinks "Semantic search" is blank.

Comment: To fix all of the above MediaWiki debugging needs to be enabled. It is also good to see the PHP error log.  « Saper // @talk »  13:17, 27 January 2018 (EST)


Special pages

Broken pages in :

Maintenance reports

  • Broken redirects
  • Dead-end pages
  • Double redirects
  • Oldest pages
  • Orphaned pages
  • Pages with the fewest revisions
  • Pages without language links
  • Protected titles -- doesn't work despite that Protected pages list pages
  • Uncategorized categories
  • Uncategorized files
  • Uncategorized pages
  • Uncategorized templates
  • Unused categories
  • Unused files
  • Unused templates
  • Unwatched pages
  • Wanted categories
  • Wanted files
  • Wanted pages
  • Wanted templates

Lists of pages

  • List of redirects

Media reports and uploads

  • List of files with duplicates
  • MIME search -- "This special page is disabled for performance reasons."
  • Media statistics

High use pages

  • Most linked-to files
  • Most linked-to pages
  • Most transcluded pages
  • Pages with the most categories
  • Pages with the most interwikis
  • Pages with the most revisions

Page tools

  • Get data -- Blank page

Page Forms

  • Run query -- "Error: No form was found on page ""."


All the bureaucrats represents their user access level on their user page with static text. Example for User:Donaldr3:

My name is Donald Robertson and I am an administrator and bureaucrat of the Free Software Directory.

The problem with that method is that each time the user access level changes the text has should be updated, for example when someone from the FSF gets retired. But this typically doesn't happen because it's inconvenient.

With we can use this on the user pages for administrators and bureaucrats so they can represent their user access level on their user page dynamically. We can add this to a template that we add to the top of the users pages for example:

My name is {{#realname:alt}} and I am an {{#ifingroup:bureaucrat| [{{#username:alt}}&group=bureaucrat&limit=1 administrator and bureaucrat] |}} {{#ifingroup:administrator| [{{#username:alt}}&group=bureaucrat&limit=1 administrator] |}} of the Free Software Directory.

Import templates

Templates to display "EST" or "EDT"


No template works if copy/pasted directly from Wikipedia, not even those which print the current time zone offset in North America, either they require a setting to be passed, or they simply fail to find some string. Fortunately we managed to make Template:TZAbbrev which also has a default value that allows easily spotting for problems, besides accepting an optional parameter for testing, the documentation is in the template's page.



Personal JavaScripts are only available if $wgAllowUserJs is set to true. - wgAllowUserJs are set to true at but not at (see policy).

I cannot use the tool mw.loader.load('//'); in my User:David_Hedlund/common.js.
Hotcat is also pretty interesting: This code is MW version safe. It should run on any MediaWiki installation >= MW 1.15. Note that HotCat is supposed to run with or without jQuery, and also on older installations that do not yet have -

Change unapproved revs to category

Right now we have an issue where packages that aren't quite ready to be added to the Directory languish in unapproved revs. The packages don't need review; they need ongoing help to fix freedom issues. We want to keep these pages not listed in the Directory, but move them to like an Archive listing, where people can continue to file bugs and work with maintainers to fix the problems. But we want to get them out of unapprovedrevs, which is our listing for newly added packages that haven't been approved. mutante, a wikimedia amin, suggested that we just use categories rather than a special page. We can set the category automatically when people create the page, but then will later be able to change the category to either approved or archive as needed. This would also make it easier to take something down without deleting it, if freedom issues arise.

Suggested solution: I think SMW can evaluate unapproved/uncategorized entries. However, (and other #Special pages) are empty. --David Hedlund (talk) 15:39, 16 March 2018 (EDT)

Add a new name space: Group

I suggest a new name space "Group".

What links here?

We want the "What links here?" enabled in the sidebar, it's the standard procedure to maintain MediaWiki instances. It's not stored in I got this response from #mediawiki "It's enabled by default on normal pages. I'd say there may be an extension installed on that wiki that's hiding it. Moonbook,, has "What links here?". It's strange because it's not present in the original source code. it's not hidden with CSS or JavaScript"

W3M / text based browser is hard to use forms

report from mailing list:

I just managed to submit an entry for my "dtas" software, but it was a bit painful since leads to a "loading..." page which requires JavaScript.

He noticed that the javascript was trying to load a specific page, so he loaded it himself ( and was able to edit the form.

Session data

I get this message after ~1 minute (should be at least 5 minutes) of inactive form editing:

Sorry! We could not process your edit due to a loss of session data.

You might have been logged out. Please verify that you're still logged in and try again. If it still does not work, try logging out and logging back in, and check that your browser allows cookies from this site.

One must note that this expiration is common practice in order to avoid fake authentication attacks. We must instead take the message at face value and think: "What can cause someone to stay various minutes editing a page? And how can we segment the edit so that this doesn't happen?"

Steps to reproduce:

  1. Click on the edit link of a page (or even the "edit with form" link).
  2. Do some edit but don't submit.
  3. Wait at least 10min without visiting nor browsing any page related to both the FSD and the FSF (because these are linked by a CAS, central authentication server/service).
  4. Submit the edit.
    • The message appears. From this point on, if you try to submit again, the data is sent as expected.


date command

America/New_York is the zone for Boston, we checked it up with IANA, the developer of the Time Zone Database (tzdb)

  • We added this text to To see the meeting start time in your time zone, run this in GNU bash: date --date='TZ="America/New_York" 12:00 this Fri'"
  • The text should be added to the RSS/Atom feed by used by RSSBot[thekyriar that currently reads this in the #fsf channel:
RSSBot[thekyriar: (notice) FSF blogs posted a new article: Friday Free Software Directory IRC meetup: February 2nd starting at 12:00 p.m. EST/17:00 UTC<Add: To see the meeting start time in your time zone, run this in GNU bash: date --date='TZ="America/New_York" 12:00 this Fri'"> ( )
"If you would like to help update the directory, meet with us every Friday in #fsf on from 12 p.m. to 3 p.m. EST (16:00 to 19:00 UTC).<Add: To see the meeting start time in your time zone, run this in GNU bash: date --date='TZ="America/New_York" 12:00 this Fri'">"

Bot messages for IRC meetings

Upgrade history

It seems unprobable that the Semantic MediaWiki issues appeared on their own, most probably MediaWiki extensions got updated and some things do no longer work as before. Would be good to know the history of upgrades to identify changes that has been made and how they have affected this wiki.  « Saper // @talk »  10:58, 27 January 2018 (EST)


New Antifeature

I want to add "officeonlinesystems PDF editor online" ( to the Antifeature as an example for one of the following

please read about the program and tell me which section that match best.

Listing of all namespaces

find a way to list all pages in all namespaces

Workaround in software used by the Directory

The issues here are note issues in the Directory but in programs used by the project.

Revision entry on plain oldiff page displays "$7"

The bug can be seen in the revision summary next to the page title. Go to the history of a page, and click on any of the links that are in the dates (example "15:14, 27 January 2018‎").

This applies to the

  • main namespace, example [1]: Revision as of 17:08, 25 November 2016 by David Hedlund (talk | contribs | block)$7
  • project's namespace, example [2]: Revision as of 07:36, 24 October 2016 by David Hedlund (talk | contribs | block)$7
  • template namespace, example [3]: Revision as of 16:09, 27 January 2018 by David Hedlund (talk | contribs | block)$7

It doesn't affect:

  • property namespace (example: [4])
  • category namespace (example: [5])
  • Software software pages do not display revision summary at all so they are not either affected (example: [6]).

The $7 comes from the revision-info message (which can be seen at MediaWiki:Revision-info).

Programs that are incompatible with

The programs listed here has bugs that affect compatibility when you browse this website:

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.

The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.