Difference between revisions of "Free Software Directory:Backlog"

From Free Software Directory
Jump to: navigation, search
(Enhanced backlog page)
(Tag: Replaced)
(FSF staff tasks: added namespace listing task)
(260 intermediate revisions by 10 users not shown)
Line 1: Line 1:
= Official Backlog of the Free Software Directory =
+
==Highly prioritized issues==
These sections are used by administrative staff to ensure a good user experience over time.<br>
 
The administrators of the [[FSD:Backlog_Admin_Group|Backlog Admin Group]] constantly manage and update these sections.
 
  
== Bugs ==
+
===Proof read===
 +
<span style="background-color:pink">I have emailed already emailed https://directory.fsf.org/wiki/Free_Software_Directory:Backlog#FSF_staff_tasks 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.</span>
  
{{AttentionBox
+
===Indicate active IRC meetings===
|title=Info
+
Fixed in https://directory.fsf.org/wiki/Template:IRC_text
|color=#15317E
 
|icon=<span style="font-size: 250%;">&#9888;</span>
 
|message=See our new [[Free_Software_Directory:Infrastructure|infrastructure]] plan.
 
  
Please report confidential or urgent issues to [mailto:bug-directory@gnu.org bug-directory@gnu.org].}}
+
===Semantic Forms===
  
Did you find a new bug?<br>
+
[[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 [https://www.semantic-mediawiki.org/wiki/Help:Special_property_Allows_pattern "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".
Append the detailed description of the bug to the '''list of active bugs''':
+
 
* [[FSD:Backlog_active|<span class="mw-ui-button" title="List of bugs to solve" role="button" aria-disabled="false">{{{1|Active bugs}}}</span>]] List of unresolved bugs.<br>All users can queue a bug to this list, but administrators must approve it to ensure it is reproducible. Include as much information as possible. Thank you!<br><br>''Note'': security problems must always be [mailto:bug-directory@gnu.org reported privately] to FSF administrators and have the highest priority.
+
=====Add=====
<br>
+
To "Edit with form" (Example: https://directory.fsf.org/wiki?title=IceCat&action=formedit&debug=true#tab=1__General_info):
When a bug has been fixed, the backlog administrators can move it to the '''archive''':
+
 
* [[FSD:Backlog_archive|<span class="mw-ui-button" title="Archive of already fixed bugs" role="button" aria-disabled="false">{{{1|Archived bugs}}}</span>]] List of resolved or obsolete bugs.
+
* <span style="background-color:lightgreen">General info: Inbuilt extensions -- Each entry represent a list titled '''Extensions, plug-ins, or add-ons for this program''' (see |Extension of= in [[Template:Entry]]). We should add a '''Inbuilt extensions, plug-ins, or add-ons for this program'''. For example [[LibreJS]] is inbuilt in [[IceCat]].</span>
 +
** [[User:Adfeno|Adfeno]] made [[Property:Inbuilt extension of]] and set this in the entry for [[LibreJS]] (which was moved to its own page to), it's set to point to [[IceCat]]. However, respecting the <code>#ask</code> query requirements in [[Template:Show]], it will only display if [[Property:License copyright]] exists in [[LibreJS]].
 +
** <span style="background-color:pink">I added "This is an inbuilt extension, add-on, or plugin to: IceCat" in https://directory.fsf.org/wiki/HTML5_Video_Everywhere!, https://directory.fsf.org/wiki/LibreJS, and https://directory.fsf.org/wiki/HTTPS_Everywhere, but only "Inbuilt extensions, plug-ins, or add-ons for this program  HTML5 Video Everywhere!" is listed in https://directory.fsf.org/wiki/IceCat</span>
 +
*** [[User:Adfeno|Adfeno]] says: This is because [[Template:Show]] demands that for the entries to be displayed they must have all of the following properties set: [[Property:License]], [[Property:License copyright]], [[Property:License verified by]], [[Property:License verified date]]. Personally, as well as to avoid any potentially non-free entry to be listed, I consider this a '''wontfix'''.
 +
* <strike>General info:Decommissioned/Obsolete</strike>
 +
* <strike>General info: Checksum</strike>
 +
* <strike>OpenPGP signature URL</strike>
 +
* <strike>OpenPGP public key</strike>
 +
* <strike>Resource info -> Resource kind: Telephony</strike>
 +
* <strike>Resource info -> Resource kind: Videotelephony</strike>
 +
* <strike>Resource info -> Resource kind: E-mail: OpenPGP public key</strike>
 +
** <span style="background-color:pink">This item is placed next to "E-mail" but it doesn't display next to "E-mail" in the drop down menu in "Edit with form -> Resource kind" drop down menu.</span>
 +
 
 +
=====Modify=====
 +
 
 +
* 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 https://www.gnu.org/licenses/license-list.html#SoftwareLicenses should be on our "License and version:" drop-down menu.
 +
** Possible solutions:
 +
**# Change type from <code>combobox</code> to <code>dropdown</code>. [https://directory.fsf.org/wiki?title=Form:Entry&oldid=55564 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 <code>MPLv2.0</code> set as <code>License</code> parameter for {{Tl|Project license}}, then it won't find it since it expects <code>License:MPLv2.0</code>. Making {{Tl|Project license}} set this doesn't work ([https://directory.fsf.org/wiki?title=Template:Project_license&oldid=55610 it was already tried]), the only fix for the already existing entries seems to be a mass-replace, so that every call for {{Tl|Project license}} that is like this {{#tag:code|<nowiki>{{Project license |License=MPLv2.0 }}</nowiki>}} becomes like this {{#tag:code |<nowiki>{{Project license |License=License:MPLv2.0 }}</nowiki>}}. 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 <code>License</code> namespace. For example, currently [[Property:License]] describes <code>Boost</code> as one of the allowed values, however it seems to refer to [[Boost]], not [[License:Boost]].
 +
 
 +
== Old bugs and suggestions ==
 +
This section is merged from the old **Free Software Directory:Bugs** page (request by Ian Kelling).
 +
 
 +
* [[FSD:Features|Proposed features for the FSD]]
 +
* [[FSD:Features/Browse|Category browsing]]
 +
* <strike>Set up RT for bug tracking and tiket making
 +
** need to create "Category:Review-triaged" once RT has been set up.</strike> (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 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?
 +
* <strike>Fix both broken bug report links on pages that contain spaces in their names: [[GNU Linux-libre]]. The culprit is [[Template:Show]].</strike>
 +
* need to implement mass-emails about email verification, and directions for changing preferences.
 +
* 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.
 +
* <strike>Turn off 1,000 character limit for strings</strike> This was relate to a bug in MediaWiki, that has been fixed in an upgrade.
 +
* Turn off error/warnings in SMW
 +
* [[FSD:GNU | 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.
 +
* <strike>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.)</strike> Now we just need to put entry info into [[Python]], etc.
 +
* "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.
 +
* <strike>Add an "obsolete/decomissioned" boolean field to [[Template:Entry]], and maybe even a "replaced by" field to give the link to another project.</strike>
 +
* 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.
 +
* 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..
 +
* 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: [http://directory.fsf.org/wiki/Special:FormEdit/Bug_report?Bug_report&#91;Project_page&#93;={{PAGENAME}}&amp;namespace=Review Example bug report link]
 +
* <strike>"Edit with Form" doesn't allow one to update the "last reviewed by" field</strike>
 +
* <strike>List of categories on Main_Page is too long</strike> The layout has changed, an is hopefully more usable now.
 +
** <strike>fix the program tagging, so all programs are included in the main page redesign.</strike> This issue has been worked around.
 +
* <strike>Update the [[Form:Bug report]] to include the Category:Bug_report tag through a template.</strike>
 +
** <strike>Then update the pages in the Category:Bug_report name-space to visibly contain the category tag.</strike>
 +
** <strike>Then update [[Template:Bug_report]] to not include it automatically.</strike>
 +
** <strike>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".</strike>
 +
* <strike>Make sure that the Bug_report pages and Review pages have links that are easily accessible by contributors.</strike> See [[FSD:Workflow]].
 +
* <strike>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.)</strike>
 +
* <strike>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.)</strike> Actually, Use: is not its parent. That property value refers to Audio editing (which is annoying because mixing, etc. also appears in Use: ).
 +
* <strike>Verify that '-'s have replaced spaces in all properties and their values.</strike> 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.
 +
* <strike>FSS subscribe box points to the wrong place (should point to <https://crm.fsf.org/civicrm/profile?reset=1&amp;gid=31">, not lists.fsf.org. </strike>
 +
* 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)
 +
* "New Packages RSS feed"'s license verification dates are messed up.  
 +
* home page of every GNU package (yes, really) to be listed as <http://www.gnu.org/software/PKGNAME>
 +
* conditional statements should be created for various properties (e.g., "Audio:mp3" should result in "works-with::Audio" being set on a page automatically).
 +
* <strike>Create Form Edit tab for appropriate users.</strike>
 +
* <strike>delete [[Audio]], etc. (cf. [[Property:Property_name]])</strike>
 +
* <strike>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.</strike>
 +
* <strike>Create a template with semantic property that can identify a project as a High Priority Project. Ideally with a graphic, like for GNU projects.</strike>
 +
* '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.
 +
* <strike>Fix links to licenses</strike> 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.
 +
* <strike>Export all entries in XML format.</strike>
 +
** Create cron job to do this
 +
** Create cron job to update CSV output page of GNU all projects
 +
* 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 <tt>noscript</tt> tags so that it only displays when javascript is turned off.
 +
* Remove edit links in Search results
 +
* Fix links (multimedia, etc) at top of search results
 +
* Autopopulate ''License verified date'' field if it is empty.
 +
* Both the user name and the current date should be used for the "submitted by" fields -- they should not be user selectable.
 +
* <strike>GNU Head goes away when you view "further results" in table of results. For instance: [[Category/Use/copying]]</strike>
 +
**<strike>Slight difference in code of Template:Getlist and ‘show embed code’ of semantic search for that page when viewed after clicking on further results.<nowiki><|?Is GNU#{{GNU_Head_Small}},=GNU?> changes to < |?IsGNU#[[File:Heckert_gnu.small.png >. Fix the missing <,=GNU?></nowiki></strike>
 +
* Make sorting case-insensitive. (See this [https://bugzilla.wikimedia.org/show_bug.cgi?id=33134 SMW bug response].)
 +
 
 +
=== Future ===
 +
 
 +
* We can use the autoedit links for things like allow admins to do things like confirm that they have reviewed an entry or as a way for "voting-up" etc. Or any number of things. See [http://www.mediawiki.org/wiki/Extension:Semantic_Forms/Linking_to_forms autoedit section at bottom of Semantic Forms page].
 +
 
 +
=== 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 [http://smwforum.ontoprise.com/smwforum/index.php/Semantic_MediaWiki_Plus#Enhanced_Retrieval_extension Enhanced Retrieval extension].
 +
 
 +
=== License verification ===
 +
 
 +
When doing license verification, we need to ensure two things:
 +
 
 +
# More than one person checks a license
 +
# 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 [http://www.mediawiki.org/wiki/Extension:Semantic_Tasks 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.
 +
 
 +
 
 +
==Upload scripts==
 +
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.
 +
 
 +
== Debian Packaging System ==
 +
 
 +
From https://directory.fsf.org/wiki?title=Org:DBpedia&oldid=41404#Debian_Packaging_System by Freephile:
 +
 
 +
The [https://packages.qa.debian.org/common/index.html Debian Package Tracking System] produces RDF metadata and is already included in DBpedia.  For example, here's a 'Turtle' representation of the GIMP package https://packages.qa.debian.org/g/gimp.ttl
 +
 
 +
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.
 +
 
 +
==wgAllowUserJs==
 +
Personal JavaScripts are only available if $wgAllowUserJs is set to true. - https://www.mediawiki.org/wiki/Manual:Interface/JavaScript#Personal_scripts. wgAllowUserJs are set to true at wikipedia.org but not at directory.fsf.org (see [[Free Software Directory:Policy|policy]]).
 +
:I cannot use they nice tool <code>mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:Hedonil/XTools/XTools.js&action=raw&ctype=text/javascript');</code> in my [[User:David_Hedlund/common.js]].
 +
:Hotcat is also pretty interesting: <code>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 window.mw.</code> - https://commons.wikimedia.org/wiki/MediaWiki:Gadget-HotCat.js
 +
 
 +
==Portals==
 +
Wikipedia have Portals, for example https://en.wikipedia.org/wiki/Portal:Free_software and https://en.wikipedia.org/wiki/Portal:Java
 +
 
 +
* Should we start [[Portal:IceCat]]?
 +
 
 +
==XML update==
 +
 
 +
Please study these XML outputs in IceCat
 +
 
 +
* https://directory.fsf.org/wiki/Special:Export/IceCat/NoScript (view-source)
 +
* https://addons.mozilla.org/api/v3/addons/addon/noscript/ (view-source)
 +
** https://addons.mozilla.org/api/v3/addons/addon/noscript/versions/1910123/ (view-source)
 +
 
 +
It's time to export the old add-on list https://directory.fsf.org/wiki/Free_Software_Directory:IceCat_extensions_(proposed)/ 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:
 +
<pre>
 +
{{Entry
 +
|Name=NoScript
 +
|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 [https://www.gnu.org/philosophy/javascript-trap.html 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 [https://www.fsf.org/campaigns/freejs 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=http://noscript.net/
 +
|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 [https://www.torproject.org/docs/faq.html.en#TBBCanIBlockJS especially bad for your anonymity] if you're using NoScript with Tor.
 +
|Related projects=GNU LibreJS, NoScript Anywhere
 +
|Version identifier=2.6.9.25.1-signed
 +
|Version date=2015/05/23
 +
|Version status=stable
 +
|Version download=https://addons.mozilla.org/firefox/downloads/file/318124/noscript_security_suite-2.6.9.25-sm+fn+fx.xpi
 +
|Last review by=David Hedlund
 +
|Last review date=2016/04/21
 +
|Status=
 +
|Is GNU=No
 +
}}
 +
{{Project license
 +
|License=GPLv2
 +
|License verified by=enyst
 +
|License verified date=2013/03/24
 +
}}
 +
{{Resource
 +
|Resource audience=Users
 +
|Resource kind=Forum
 +
|Resource URL=http://forums.informaction.com/viewforum.php?f=3
 +
}}
 +
{{Software category
 +
|Internet-application=privacy
 +
|Use=internet-application, security
 +
}}
 +
{{Featured}}
 +
</pre>
 +
 
 +
==Set empty default values==
 +
This is a Semantic MediaWiki issue.
 +
 
 +
I find that most of my problems concerning empty or missing properties in a template are helped by setting default template values. You might need to poke runJobs.php. Then you can query on the default value. So you might have Template:Software looking like:
 +
 
 +
Software license: [[SoftwareLicense::{{{LICENSE|None}}}]]
 +
 
 +
Then you can pick out the pages with undeclared software license by ask'ing on [[SoftwareLicense::None]] to get the ones that aren't declared.
 +
 
 +
==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 https://directory.fsf.org/wiki?title=Special:ApprovedRevs&show=unapproved 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 https://directory.fsf.org/wiki/Category:License 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:
 +
 
 +
* I added this page: https://directory.fsf.org/wiki/License:Creative_Commons_Attribution_Share-Alike_4.0
 +
* I Added "Creative Commons Attribution Share-Alike 4.0" to https://directory.fsf.org/wiki/Anti-Adblock_Killer
 +
* Anti-Adblock Killer is not listed in https://directory.fsf.org/wiki/IceCat/Greasemonkey. It will list Anti-Adblock Killer only if I select a license from the list
 +
 
 +
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 https://directory.fsf.org/wiki/Property:License. Lets see if it shows up.'''
 +
: Should https://directory.fsf.org/wiki/Property:License_text be modified to string?
 +
 
 +
==Free_Software_Directory:Requirements==
 +
From https://directory.fsf.org/wiki/Free_Software_Directory_talk:Requirements
 +
I think this should be added to the page:
 +
 
 +
* Click on "Create account" at top right in this wiki to create a ''Free Software Foundation Central Login Username''. Log in.
 +
* Adding a description at you profile page is optional but not doing so might trick people that your user is inactive as your link text will remain red.
 +
 
 +
==Related issues==
 +
 
 +
==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.
 +
 
 +
==Special FSD pages==
 +
Organize
 +
* [[Historical]]
 +
 
 +
==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 [https://directory.fsf.org/wiki?title=Free_Software_Directory:Backlog&oldid=38505]: Revision as of 17:08, 25 November 2016 by David Hedlund (talk | contribs | block)$7
 +
* project's namespace, example [https://directory.fsf.org/wiki?title=Free_Software_Directory:Participate&oldid=37133]: Revision as of 07:36, 24 October 2016 by David Hedlund (talk | contribs | block)$7
 +
* template namespace, example [https://directory.fsf.org/wiki?title=Template:Print_software_category&oldid=48882]: Revision as of 16:09, 27 January 2018 by David Hedlund (talk | contribs | block)$7
 +
 
 +
It doesn't affect:
 +
* property namespace (example: [https://directory.fsf.org/wiki?title=Property:IRC_help&oldid=12374])
 +
* category namespace (example: [https://directory.fsf.org/wiki?title=Category:Bug_report&oldid=14428])
 +
* Software software pages do not display revision summary at all so they are not either affected (example: [https://directory.fsf.org/wiki?title=IceCat&oldid=46220]).
 +
 
 +
The $7 comes from the <code>revision-info</code> message (which can be seen at [[MediaWiki:Revision-info]]).
 +
 
 +
*This is a bug in [[:mw:Extension:ApprovedRevs]]. The author has been informed.
 +
*'''Workaround:''' Edit [[MediaWiki:Revision-info]] and remove $7 by hand. This message has to be deleted when this bug is fixed.
 +
 
 +
==Consistent CSS styling==
 +
Some custom templates have CSS <code>style=""</code> clauses scattered in them. One of such clauses was responsible for too narrow columns in the description. I'd suggest to:
 +
# Check all local style clauses in our custom code
 +
# Determine if they can be more generic. For example, colors, paddings, line widths should be unified to achieve visual consistency.
 +
# A set of CSS classes should be designed to replace <code>style</code> clauses
 +
# CSS class naming scheme should be decided
 +
# New CSS classes should be introduced to [[MediaWiki:Common.css]]
 +
# <code>style</code> clauses should be replaced with their <code>class="'''css-class'''"</code> counterparts.
 +
 
 +
===Improve===
 +
* The width values can be improved in {{tl|Print entry}}:
 +
** <nowiki><div style="float:left; width:60%; margin: 2px 4px 0px 4px;"></nowiki>
 +
** <nowiki><div style="float:right; width:35%; margin: 2px 4px 0px 4px;"></nowiki>
 +
 
 +
== 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 [https://directory.fsf.org/wiki?title=Template:License&oldid=49613 49613] and [https://directory.fsf.org/wiki?title=Template:License&oldid=49636 49636] for the {{Tl|License}} template already implement a workaround for this issue, but this requires a mass replace in all calls to {{Tl|License}}, so as to replace <code>|Full text=</code> with <code>|</code>.
 +
 
 +
== 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.
 +
 
 +
==FSF staff tasks==
 +
<span style="background-color:red; color: white">'''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.'''</span>
 +
 
 +
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 [http://lists.gnu.org/archive/html/directory-discuss/2017-05/msg00004.html 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.
 +
 
 +
<pre>
 +
IRC general channel
 +
    [irc:chat.freenode.net/icecat irc:chat.freenode.net/icecat]
 +
</pre>
 +
 
 +
* 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.--[[User:Adfeno|Adfeno]] ([[User talk: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) {{tl|Print entry}} {{tl|Entry}} and {{tl|Show}}. There is a fourth one ({{tl|IRC}}) but I think we might be able to replace it ({{tl|Print entry}} calls it, so instead of calling {{tl|IRC}}: we can take the code from it and insert in the caller template).
 +
*** I think that #replace will just mask the underlying issue. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 10:49, 27 January 2018 (EST)
 +
** I think there is so far the following possibilities:
 +
**# an issue between the templates used;
 +
**# an issue with the <code>#ask:</code> queries and the <code>template</code> result format;
 +
**# we have reached a setting limit that makes the formatting not work (perhaps a limit on the <code>template</code> result format, although I have tried to remove the call to {{tl|IRC}} but it didn't work, we might have to make tests by simplifying the <code>template</code> result calls even further to see if this is indeed the problematic setting);
 +
**# an issue with the "IRC [level name]" properties when setting (<code>#set:</code>) or their query and display.
 +
*: I think we can make use of <code>#nowiki</code> or <code>#-</code> display parameters when querying for the <nowiki>"IRC [level"</nowiki> properties of an entry (this is queried for in {{tl|Show}}) in order to take the property value in raw (example: <code>irc:chat.freenode.net/fsf</code>) but then we will need to change either {{tl|Print entry}} or {{tl|IRC}} (the first one is the problematic, so I recommend to test with it first) so that it removes <code>irc:</code> but also allows any other <code>:</code> (because the URL scheme allows port numbers).
 +
*: --[[User:Adfeno|Adfeno]] ([[User talk: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 <code>URL</code> has a protocol different from HTTP, this problem also happens if the property definition/setting is invisible (using <code>#set:</code>), 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: https://directory.fsf.org/wiki?title=Free_Software_Directory:Sandbox&oldid=48884 --[[User:Adfeno|Adfeno]] ([[User talk: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: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/568d058ea68859d134654a959001ba0739c781e3/includes/dataitems/SMW_DI_URI.php#L68-L70 &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 12:49, 27 January 2018 (EST)
 +
 
 +
;Log
 +
* [https://directory.fsf.org/wiki?title=Template:Print_entry&diff=48853&oldid=48834 Adding <code>#-</code>] didn't seem to help. &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 08:54, 27 January 2018 (EST)
 +
** We unfortunately need a function to remove <code>irc:</code> in order to use <code>#nowiki</code> or <code>#-</code>.--[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 09:35, 27 January 2018 (EST)
 +
* Removed dependency on {{tl|IRC}}: https://directory.fsf.org/wiki?title=Template:Print_entry&oldid=48860
 +
* Use <code>#replace</code> in IRC URL properties to get the address correctly: https://directory.fsf.org/wiki?title=Template:Print_entry&oldid=48889 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 11:59, 27 January 2018 (EST)
 +
* Use <code>#nowiki</code> in the query for IRC URL properties to pass the property value to {{tl|Print entry}}: https://directory.fsf.org/wiki?title=Template:Show&oldid=48890 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 11:59, 27 January 2018 (EST)
 +
 
 +
=====Multiple software categories (temporarily fixed)=====
 +
Not only are the text merged but also the URL in the link. For [[IceCat]]: <nowiki><a href="/wiki?title=Category/Programming-language/C_C%2B%2B_javascript_rust&amp;action=edit&amp;redlink=1" class="new" title="Category/Programming-language/C C++ javascript rust (page does not exist)">Programming-language:C C++ javascript rust</a></nowiki>
 +
 
 +
* (analysis) This issue occurs when multiple items in one software category are selected in the form. The property value seems to contain space-separated values. But {{tl|Print software category}} seems to use <code>[[:mw:Extension:Page_Forms/Page_Forms_and_templates#arraymap|#arraymap]]</code> with a separator <code>,</code> to split values.
 +
* [https://semantic-mediawiki.org/wiki/Help:Using_a_space_to_separate_multiple_values_in_set/subobject Using a space to separate multiple values in set/subobject] from SMW website cmay or may not be helpful
 +
 
 +
;Log
 +
* Attempt to force valuesep to comma so that software categories are displayed correctly: https://directory.fsf.org/wiki?title=Template:Show&oldid=48988 --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:47, 27 January 2018 (EST)
 +
** This seems to solve the issue, I visited [[IceCat]]. [[Mingw-w64]] and [[GCC]], and all seems to be working well. This is of course an ugly workaround, because I have choosen not to do a mass replace of the already existing categories separated by commas (because I think it would be resource expensive). Imagine, using Special:RepplaceText, in almost 10,000 pages. I prefer to leave this mass replace to the real admins, if they feel confident enough so as to remove my valuesep setting. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:47, 27 January 2018 (EST)
 +
*** This workaround is needed because [https://www.semantic-mediawiki.org/w/index.php?title=Help:Template_format&oldid=57732#Usage_for_valuesep_.28value_separator.29 since SMW 2.5.3, in the <code>template</code> result format, the default for <code>valuesep</code> is changed from space to comma], however we are using SMW 2.5.1, so the default us is currently space. The mass replace is not required if we manage to upgrade to 2.5.3. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 08:24, 28 January 2018 (EST)
 +
* It didn't help to edit <nowiki>{{</nowiki>[[Template:Print_software_category|Print_software_category]]<nowiki>}}</nowiki> and replace comma with <nowiki>&#32</nowiki> in <nowiki>{{#if:{{{15|}}}|{{#arraymap:{{{15}}}|,|xvarx|<li>[[Category/Interface/xvarx{{!}}Interface:xvarx]]</li>|}}|<nowiki/>}}</nowiki>, see https://directory.fsf.org/wiki?title=Template:Print_software_category&diff=48880&oldid=48746
 +
 
 +
====Remove duplication====
 +
 
 +
=====Remove duplicated entries=====
 +
 
 +
* Duplication of entries in https://directory.fsf.org/wiki/Special:ApprovedRevs
 +
* Some entries has duplications of "Extension or Plugin". For example, https://directory.fsf.org/wiki/Adblock_Plus has 3 Iridium entries listed.
 +
* This was asked to sysadmin@fsf.org over one year ago:
 +
 
 +
The value of ''|Extension of='' is displayed twice in some entries (one year ago perhaps 5 duplicated were displayed but John Sullivan and/or [[User:Jgay|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: https://directory.fsf.org/wiki/IceCat
 +
 
 +
<pre>
 +
      > 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 sysadmin@gnu.org.
 +
 
 +
    --
 +
    Dr Richard Stallman
 +
    President, Free Software Foundation (gnu.org, fsf.org)
 +
    Internet Hall-of-Famer (internethalloffame.org)
 +
    Skype: No way! See stallman.org/skype.html.
 +
 
 +
</pre>
 +
 
 +
=====Remove duplicated short description=====
 +
sysadmin@gnu.org ticket: [gnu.org #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 [[:mw:Manual:How to debug|MediaWiki debugging]] needs to be enabled. It is also good to see the PHP error log. &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 13:17, 27 January 2018 (EST)
 +
 
 +
===MediaWiki===
 +
 
 +
====Special pages====
 +
Broken pages in https://directory.fsf.org/wiki/Special:SpecialPages :
 +
 
 +
'''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 [https://directory.fsf.org/wiki/Special:ProtectedPages 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 ""."
 +
 
 +
====Extension:UserFunctions====
 +
All the [https://directory.fsf.org/wiki?title=Special:ListUsers&group=bureaucrat 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 [http://directory.fsf.org/wiki?title=Special%3AListUsers&username=Donaldr3&group=bureaucrat&limit=1 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 https://www.mediawiki.org/wiki/Extension:UserFunctions we can use this on the user pages for [https://directory.fsf.org/wiki?title=Special%3AListUsers&username=&group=sysop administrators] and [https://directory.fsf.org/wiki?title=Special:ListUsers&group=bureaucrat 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 <nowiki>{{#ifingroup:bureaucrat| [http://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator and bureaucrat] |}} {{#ifingroup:administrator| [http://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator] |}}</nowiki> of the Free Software Directory.
 +
 
 +
===Import templates===
 +
* Import https://en.wikipedia.org/wiki/Template:Ref from Wikipedia so we can use <code><ref>Reference goes here</ref></code>. This is perhaps the single most important Template to import.
 +
* Import https://en.wikipedia.org/wiki/Template:Reply_to -- it's a pain to use the Talk pages every time, especially to communicate on pages like this Backlog.
 +
* Import https://en.wikipedia.org/wiki/Template:Mbox
 +
 
 +
====Templates to display "EST" or "EDT"====
 +
* Export https://directory.fsf.org/wiki/Template:Current_daylight_saving_offset_in_North_America (or https://en.wikipedia.org/wiki/Template:Daylight_saving_in_time_zone) and import it to the Directory.
 +
* Modify <nowiki>{{Current_daylight_saving_offset_in_North_America}}</nowiki> (or <nowiki>{{Daylight_saving_in_time_zone}}</nowiki>) to display "EST" and "EDT" instead of "0" and "1" respectively.
 +
* Add message "Join us 12:00-15:00 <nowiki>{{Daylight saving in time zone}}</nowiki>"
 +
 
 +
=====Workaround=====
 +
<span style="background-color:pink">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.</span>
 +
 
 +
===Misc===
 +
 
 +
====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, https://directory.fsf.org/wiki/Special:UncategorizedPages (and other [[#Special pages]]) are empty.  --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 15:39, 16 March 2018 (EDT)
 +
 
 +
====Footer====
 +
The link http://static.fsf.org/nosvn/directory/fdl-1.3-standalone.html appears three times in the footer template, two of them are redundant. See https://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_change_the_footer.3F for how to modify the footer template.
 +
 
 +
====Add a new name space: Group====
 +
I suggest a new name space "Group".
 +
* Move all pages in [[Free Software Directory:Participate/Project Team]] to the Group name space.
 +
* Move [[Free Software Directory:Participate/Project Team]] to [[Free Software Directory:Participate/Groups]].
 +
 
 +
====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 https://directory.fsf.org/wiki?title=MediaWiki:Sidebar&action=edit. 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, https://directory.fsf.org/wiki/IceCat?useskin=monobook, 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"
 +
 
 +
====Invalid HTML====
 +
The IceCat entry in the FSD is not valid, 28 errors: https://validator.w3.org/check?uri=https%3A%2F%2Fdirectory.fsf.org%2Fwiki%2FIceCat&charset=%28detect+automatically%29&doctype=Inline&group=0
 +
 
 +
====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 http://directory.fsf.org/wiki/Form:Entry 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 (directory.fsf.org/wiki/Special:FormEdit/Entry/dtas)
 +
and was able to edit the form.
 +
 
 +
====OpenSearch installation error====
 +
Free Software Directory search can be installed from https://addons.mozilla.org/en-US/firefox/addon/fsf-directory/?src=ss but not from [[Free Software Directory search]] (I approved this entry for this test purposes only). --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 23:56, 16 April 2015 (EDT)
 +
 
 +
====Session data====
 +
I get this message after ~1 minute (should be at least 5 minutes) of inactive form editing:
 +
 
 +
<pre style="white-space: pre-wrap;">
 +
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.
 +
</pre>
 +
 
 +
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:
 +
 
 +
# Click on the edit link of a page (or even the "edit with form" link).
 +
# Do some edit but don't submit.
 +
# 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).
 +
# Submit the edit.
 +
#* The message appears. From this point on, if you try to submit again, the data is sent as expected.
 +
 
 +
=====Actions take a long time to complete=====
 +
The Move (More -> Move) page loads for perhaps a minute when I hit the "Move page" button despite that the page has been moved. Same issue when you create new pages.
 +
 
 +
====Upload SVG files====
 +
We want to upload SVG files but [[Special:Upload]] says: "Permitted file types: png, gif, jpg, jpeg, webp."
 +
 
 +
===Suggestions===
 +
 
 +
====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 https://directory.fsf.org/wiki/Template:IRC_text: 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:
 +
<pre>
 +
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'"> ( http://www.fsf.org/blogs/directory/friday-free-software-directory-irc-meetup-february-2nd-starting-at-12-00-p-m-est-17-00-utc )
 +
</pre>
 +
* The pages listed in https://www.fsf.org/blogs/directory reads:
 +
<pre>
 +
"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. 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'">"
 +
</pre>
 +
 
 +
====Bot messages for IRC meetings====
 +
* The RSSBot[thekyriar could be used to print this message in the channel every hour on the IRC Friday Meetings: "We're are entering the x hour of the free software directory meeting.  If it is your first time joining us, please check out the participation guide http://directory.fsf.org/wiki/Free_Software_Directory:Participate"
 +
 
 +
====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. &nbsp;«&nbsp;[[User:Saper|Saper]]<span style="font-size: 70%">&nbsp;//&nbsp;</span>[[User talk:Saper|@talk]]&nbsp;»&nbsp; 10:58, 27 January 2018 (EST)
 +
 
 +
===Donald===
 +
 
 +
====New Antifeature====
 +
I want to add "officeonlinesystems PDF editor online" (https://addons.mozilla.org/en-US/firefox/addon/editor-pdf-online/) to the Antifeature as an example for one of the following
 +
 
 +
* https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Service_as_a_Software_Substitute
 +
* https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#SaaSS
 +
* https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Tethered
 +
* https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Nonfree_Network_Services
 +
 
 +
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
 +
 
 +
==Programs that are incompatible with directory.fsf.org==
 +
The programs listed here has bugs that affect compatibility when you browse this website:
 +
 
 +
* LibreJS
 +
** Bug report [https://lists.gnu.org/archive/html/bug-librejs/2018-01/msg00006.html LibreJS below version 7.0 (the WebExtension) inserts unwanted blank lines in text fields]
 +
** directory.fsf.org compatibility issue: You cannot edit the Directory with LibreJS
 +
** Solution: Disable LibreJS when you edit https://directory.fsf.org/wiki/
 +
* Lynx
 +
** Bug report: [https://savannah.nongnu.org/bugs/?53057 Table column rendering needs more spacing or a better separator]
 +
** directory.fsf.org compatibility issue: mediawiki tables in the [[Collection:Windows|Windows]] page for example are not displayed correctly.
 +
*** Disclaimer: https://www.gnu.org/software/for-windows.html is not better displayed https://directory.fsf.org/wiki/Windows in Lynx 2.8.9dev.16 from GNU Guix in Trisquel 7
 +
** Solution: Use another text-based web browser.

Revision as of 19:56, 26 March 2018

Contents

Highly prioritized issues

Proof read

I have emailed already emailed https://directory.fsf.org/wiki/Free_Software_Directory:Backlog#FSF_staff_tasks 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.

Indicate active IRC meetings

Fixed in https://directory.fsf.org/wiki/Template:IRC_text

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".

Add

To "Edit with form" (Example: https://directory.fsf.org/wiki?title=IceCat&action=formedit&debug=true#tab=1__General_info):

Modify
  • 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 https://www.gnu.org/licenses/license-list.html#SoftwareLicenses 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.

Old bugs and suggestions

This section is merged from the old **Free Software Directory:Bugs** page (request by Ian Kelling).

  • Proposed features for the FSD
  • Category browsing
  • 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 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?
  • Fix both broken bug report links on pages that contain spaces in their names: GNU Linux-libre. The culprit is Template:Show.
  • need to implement mass-emails about email verification, and directions for changing preferences.
  • 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.
  • Turn off error/warnings in SMW
  • 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.
  • 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.
  • "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.
  • Add an "obsolete/decomissioned" boolean field to Template:Entry, and maybe even a "replaced by" field to give the link to another project.
  • 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.
  • 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..
  • 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
  • "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 <https://crm.fsf.org/civicrm/profile?reset=1&gid=31">, not lists.fsf.org.
  • 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)
  • "New Packages RSS feed"'s license verification dates are messed up.
  • home page of every GNU package (yes, really) to be listed as <http://www.gnu.org/software/PKGNAME>
  • conditional statements should be created for various properties (e.g., "Audio:mp3" should result in "works-with::Audio" being set on a page automatically).
  • 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.
  • '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.
  • 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.
    • Create cron job to do this
    • Create cron job to update CSV output page of GNU all projects
  • 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.
  • Remove edit links in Search results
  • Fix links (multimedia, etc) at top of search results
  • Autopopulate License verified date field if it is empty.
  • 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.)

Future

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.

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.


Upload scripts

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.

Debian Packaging System

From https://directory.fsf.org/wiki?title=Org:DBpedia&oldid=41404#Debian_Packaging_System 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 https://packages.qa.debian.org/g/gimp.ttl

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.

wgAllowUserJs

Personal JavaScripts are only available if $wgAllowUserJs is set to true. - https://www.mediawiki.org/wiki/Manual:Interface/JavaScript#Personal_scripts. wgAllowUserJs are set to true at wikipedia.org but not at directory.fsf.org (see policy).

I cannot use they nice tool mw.loader.load('//meta.wikimedia.org/w/index.php?title=User:Hedonil/XTools/XTools.js&action=raw&ctype=text/javascript'); 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 window.mw. - https://commons.wikimedia.org/wiki/MediaWiki:Gadget-HotCat.js

Portals

Wikipedia have Portals, for example https://en.wikipedia.org/wiki/Portal:Free_software and https://en.wikipedia.org/wiki/Portal:Java

XML update

Please study these XML outputs in IceCat

It's time to export the old add-on list https://directory.fsf.org/wiki/Free_Software_Directory:IceCat_extensions_(proposed)/ 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:

{{Entry
|Name=NoScript
|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 [https://www.gnu.org/philosophy/javascript-trap.html 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 [https://www.fsf.org/campaigns/freejs 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=http://noscript.net/
|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 [https://www.torproject.org/docs/faq.html.en#TBBCanIBlockJS especially bad for your anonymity] if you're using NoScript with Tor.
|Related projects=GNU LibreJS, NoScript Anywhere
|Version identifier=2.6.9.25.1-signed
|Version date=2015/05/23
|Version status=stable
|Version download=https://addons.mozilla.org/firefox/downloads/file/318124/noscript_security_suite-2.6.9.25-sm+fn+fx.xpi
|Last review by=David Hedlund
|Last review date=2016/04/21
|Status=
|Is GNU=No
}}
{{Project license
|License=GPLv2
|License verified by=enyst
|License verified date=2013/03/24
}}
{{Resource
|Resource audience=Users
|Resource kind=Forum
|Resource URL=http://forums.informaction.com/viewforum.php?f=3
}}
{{Software category
|Internet-application=privacy
|Use=internet-application, security
}}
{{Featured}}

Set empty default values

This is a Semantic MediaWiki issue.

I find that most of my problems concerning empty or missing properties in a template are helped by setting default template values. You might need to poke runJobs.php. Then you can query on the default value. So you might have Template:Software looking like:

Software license: None

Then you can pick out the pages with undeclared software license by ask'ing on None to get the ones that aren't declared.

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 https://directory.fsf.org/wiki?title=Special:ApprovedRevs&show=unapproved 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 https://directory.fsf.org/wiki/Category:License 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 https://directory.fsf.org/wiki/Property:License. Lets see if it shows up.
Should https://directory.fsf.org/wiki/Property:License_text be modified to string?

Free_Software_Directory:Requirements

From https://directory.fsf.org/wiki/Free_Software_Directory_talk:Requirements I think this should be added to the page:

  • Click on "Create account" at top right in this wiki to create a Free Software Foundation Central Login Username. Log in.
  • Adding a description at you profile page is optional but not doing so might trick people that your user is inactive as your link text will remain red.

Related issues

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.

Special FSD pages

Organize

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).

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.

Improve

  • 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;">

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.

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
    [irc:chat.freenode.net/icecat irc:chat.freenode.net/icecat] 
  • 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: irc:chat.freenode.net/fsf) 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: https://directory.fsf.org/wiki?title=Free_Software_Directory:Sandbox&oldid=48884 --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: https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/568d058ea68859d134654a959001ba0739c781e3/includes/dataitems/SMW_DI_URI.php#L68-L70  « Saper // @talk »  12:49, 27 January 2018 (EST)
Log
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>

Log

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: https://directory.fsf.org/wiki/IceCat

       > 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 sysadmin@gnu.org.

    --
    Dr Richard Stallman
    President, Free Software Foundation (gnu.org, fsf.org)
    Internet Hall-of-Famer (internethalloffame.org)
    Skype: No way! See stallman.org/skype.html.

Remove duplicated short description

sysadmin@gnu.org ticket: [gnu.org #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)

MediaWiki

Special pages

Broken pages in https://directory.fsf.org/wiki/Special:SpecialPages :

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 ""."

Extension:UserFunctions

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 https://www.mediawiki.org/wiki/Extension:UserFunctions 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| [http://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator and bureaucrat] |}} {{#ifingroup:administrator| [http://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator] |}} of the Free Software Directory.

Import templates

Templates to display "EST" or "EDT"

Workaround

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.

Misc

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, https://directory.fsf.org/wiki/Special:UncategorizedPages (and other #Special pages) are empty. --David Hedlund (talk) 15:39, 16 March 2018 (EDT)

Footer

The link http://static.fsf.org/nosvn/directory/fdl-1.3-standalone.html appears three times in the footer template, two of them are redundant. See https://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_change_the_footer.3F for how to modify the footer template.

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 https://directory.fsf.org/wiki?title=MediaWiki:Sidebar&action=edit. 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, https://directory.fsf.org/wiki/IceCat?useskin=monobook, 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"

Invalid HTML

The IceCat entry in the FSD is not valid, 28 errors: https://validator.w3.org/check?uri=https%3A%2F%2Fdirectory.fsf.org%2Fwiki%2FIceCat&charset=%28detect+automatically%29&doctype=Inline&group=0

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 http://directory.fsf.org/wiki/Form:Entry 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 (directory.fsf.org/wiki/Special:FormEdit/Entry/dtas) and was able to edit the form.

OpenSearch installation error

Free Software Directory search can be installed from https://addons.mozilla.org/en-US/firefox/addon/fsf-directory/?src=ss but not from Free Software Directory search (I approved this entry for this test purposes only). --David Hedlund (talk) 23:56, 16 April 2015 (EDT)

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.
Actions take a long time to complete

The Move (More -> Move) page loads for perhaps a minute when I hit the "Move page" button despite that the page has been moved. Same issue when you create new pages.

Upload SVG files

We want to upload SVG files but Special:Upload says: "Permitted file types: png, gif, jpg, jpeg, webp."

Suggestions

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 https://directory.fsf.org/wiki/Template:IRC_text: 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'"> ( http://www.fsf.org/blogs/directory/friday-free-software-directory-irc-meetup-february-2nd-starting-at-12-00-p-m-est-17-00-utc )
"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. 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

  • The RSSBot[thekyriar could be used to print this message in the channel every hour on the IRC Friday Meetings: "We're are entering the x hour of the free software directory meeting. If it is your first time joining us, please check out the participation guide http://directory.fsf.org/wiki/Free_Software_Directory:Participate"

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)

Donald

New Antifeature

I want to add "officeonlinesystems PDF editor online" (https://addons.mozilla.org/en-US/firefox/addon/editor-pdf-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

Programs that are incompatible with directory.fsf.org

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.