Difference between revisions of "Free Software Directory:Backlog active"

From Free Software Directory
Jump to: navigation, search
m (Template:EntryGNU and Template:EntryDetails (top priority))
(Performance tuning: we already have zend opcache and apcu installed and enabled.)
(424 intermediate revisions by 18 users not shown)
Line 1: Line 1:
<!-- DO NOT EDIT -->
 
{{DISPLAYTITLE:Active Backlog|noerror}}
 
 
{{AttentionBox
 
{{AttentionBox
 
  |title=Info
 
  |title=Info
 
  |color=#15317E
 
  |color=#15317E
 
  |icon=<span style="font-size: 250%;">&#9888;</span>
 
  |icon=<span style="font-size: 250%;">&#9888;</span>
  |message=See our [[Free_Software_Directory:Infrastructure|infrastructure]] plan.
+
  |message=Please report confidential issues to [mailto:bug-directory@gnu.org bug-directory@gnu.org].}}
  
Please report confidential or urgent issues to [mailto:bug-directory@gnu.org bug-directory@gnu.org].}}
+
== General ==
 +
* Make it possible to upload software thumbnail icons in the edit form. Display the icons next to the title in the entries. I asked https://directory.fsf.org/wiki/User_talk:Vibhuti to do this since he made it possible to upload screenshots in the edit form recently. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 15:16, 20 April 2018 (EDT)
 +
* Bot messages for IRC meetings: A dedicated bot (not the RSS bot) should be used to print this message in the #fsf 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 https://directory.fsf.org/wiki/Free_Software_Directory:Participate" Ian: "if you write the configuration, and instructions, fsf can run it"
 +
* Approved revs bug. On the main entry pages, there is a bug where if a page has had at least one approval, then a non-admin edits it, the main page shows the latest edit instead of the last approved revision.
 +
* Remove exposure of database strip marks from pages under License namespace. Currently some (if not most) licenses in License namespace have a "pre"/"nowiki" element in their call text to their associated template. This is problematic because the template itself already wraps the text in "pre", so the result is a exposure of the database strip marks. When in the "Read" tab, pages in License namespace that are affected by this issue have a yellow triangle next to the start of the license text.
 +
* Make the license texts in License namespace preserve their initial space. Revisions [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.
 +
* There should be a space dedicated for scripts that can be downloaded by FSD volunteer. I suggest a link to a page in the side-bar that lists the scripts.
 +
* Proof read: <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>
 +
* [[FSD:Features|Proposed features for the FSD]]
 +
* [[FSD:Features/Browse|Category browsing]]
 +
* Fix search results, so that template data doesn't get dumped into the description below the page links. In other words, just put in the beginning of the description.
 +
* When people set the license for a project to be "GPL 2 or higher", it gets added to the autocompletion list for that field, even though that license isn't on the approved list at: [[:Property:License]]. ("GPL 2 or higher" isn't on the list because it is misformatted. The correct entry is "GPLv2orlater".)
 +
* add a link for binary download?
 +
* need to implement mass-emails about email verification, and directions for changing preferences.
 +
* [[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.
 +
* "Preview" button does not work for [[Template:Entry]]. It shows the unedited version, but I don' think there is a way around this from our end, as the displayed values are based on a query of the saved page.
 +
* Put a link to site dumps and info about the machine readability of that information on the main page.
 +
* Created HTML tooltips for the different fields in Form:Entry, or create a tutorial for Form:Entry that describes what each field is for.
 +
* Pages incorrectly created with [[Form:Bug_update]] (without the "Review:" namespace prefix) are queryable. If they are then moved to the Review: namespace, then they remain queryable. I'm not sure if a non-admin can edit the page, which could let them create a false entry in the directory.
 +
* Update the queries on [[GNU/Export]] to make sure the second column is the GNU package name property
 +
* Update each GNU project with the GNU package name
 +
* Add "table of contents" header above tabs inside <tt>noscript</tt> tags so that it only displays when javascript is turned off.
 +
* Autopopulate ''License verified date'' field if it is empty.
 +
* We need to let people submit bug reports, etc. without javascript enabled. If we could use something like a "noscript" tag, then we could display the following link: [https://directory.fsf.org/wiki/Special:FormEdit/Bug_report?Bug_report&#91;Project_page&#93;={{PAGENAME}}&amp;namespace=Review Example bug report link]
 +
* 'new messages' text overlays the red FSF links bar, so you can't click it. Still, you can just click your 'talk' page link instead.
 +
* "New Packages RSS feed"'s license verification dates are messed up.
 +
* home page of every GNU package (yes, really) to be listed as <https://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).
 +
* Turn off error/warnings in SMW <-- Why? It makes it impossible for administrators to debug the wiki. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 00:59, 29 March 2018 (EDT)
 +
* Implement an in-browswer irc client that displays only when meetings are live on the [[Main Page]] in addition to the "The meeting is active right now!" (see <nowiki>Template:IRC_text</nowiki>).
 +
** That will require a free SaaSS (like https://webchat.freenode.net/) but we don't recommend third-party SaaSS in general, however I think this would be ok if the FSF should embed a web-based IRC widget into something like irc://webchat.fsf.org/fsf (for the [[Main_Page|Directory]]) and irc://webchat.fsf.org/libreplanet (for [https://libreplanet.org/wiki/Main_Page Libre Planet]). However, the listed [[Free_Software_Directory:Free_software_evaluation#IRC_clients|web-based IRC clients are not compatible with LibreJS]], that must be fixed first. The authors of these programs accept patches, perhaps the FSF can evaluate which client the want to use and patch it? Related: IceCat, [https://savannah.gnu.org/bugs/index.php?53530 Free web-based IRC client replacement for Mibbit needed]. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 02:22, 31 March 2018 (EDT)
  
 
+
===Fixed===
{{AttentionBox
+
* <strike>Started Category/Protocol/tor and added entries to it.</strike>
|title=Info
+
* <strike>Remove edit links in Search results</strike>
|color=#15317E
+
* <strike>Linked "Related Projects" entries</strike>
|icon=<span style="font-size: 250%;">&#9888;</span>
+
* <strike>The width values can be improved in {{tl|Print entry}}:
|message=After [[FSD:Issues|our new tracker's issues are solved]], issues will be merged to it by their priority.}}
+
** <nowiki><div style="float:left; width:60%; margin: 2px 4px 0px 4px;"></nowiki>
 
+
** <strike><nowiki><div style="float:right; width:35%; margin: 2px 4px 0px 4px;"></nowiki></strike>
Append the new bugs you find in the FSD to this page.<br>Remember to '''follow the [[FSD:Participate|participation guide]] and sign your contribution'''. Thank you!
+
* <strike>Standardize the Homepage links for all 400+ GNU packages in https://directory.fsf.org/wiki/GNU</strike>
 
+
* <strike>Indicate active IRC meetings. Fixed in https://directory.fsf.org/wiki/Template:IRC_text</strike>
The bugs are archived after at least one week from their resolution or if the bug cannot be identified due to lack of information.
+
* <strike>Set up RT for bug tracking and tiket making
<!-- DO NOT EDIT -->
+
** need to create "Category:Review-triaged" once RT has been set up.</strike> (Probably won't happen)
 
+
* <strike>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.</strike>
<!-- APPEND TO THE END OF THE PAGE -->
+
* <strike>Fix both broken bug report links on pages that contain spaces in their names: [[GNU Linux-libre]]. The culprit is [[Template:Show]].</strike>
 
+
* <strike>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>
 
+
* <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.
== Uncategorized ==
+
* <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.
 
+
* <strike>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.</strike>
 
+
* <strike>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..</strike>
=== Add GNU promoted text to GNU entries automatically ===
+
* <strike>"Edit with Form" doesn't allow one to update the "last reviewed by" field</strike>
<span id="Add-GNU-promoted-text-to-GNU-entries-automatically"></span>
+
* <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>
Stalled by:
+
** <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>
* [[#Add-GNU-promoted-text-to-GNU-entries-automatically]]
+
** <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]].
This text is included in all [[GNU]] entries:
+
* <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>
<pre>
+
* <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: ).
'''Selection from the [https://shop.fsf.org/ FSF shop]'''
+
* <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.
 
+
* <strike>Make sure that program names submitted through Form:Submit don't have leading or trailing spaces.</strike>
[https://shop.fsf.org/books/free-freedom-20-richard-stallman Free as in Freedom 2.0, by Richard Stallman]
+
* <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>
 
+
* <strike>We should be able to easily browse to all categories from an entry</strike>
[https://shop.fsf.org/books-docs/introduction-command-line Introduction to the Command Line]
+
* <strike>Fix link at bottom of page that links to "Free Software Directory:Copyrights" (in Style files)<strike>
 
+
* <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>
'''[https://www.gnu.org/help/help.html Helping the GNU Project and the Free Software Movement]'''
+
* <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>
----
+
** <strike>Create [[Collection:High Priority Projects]] and add entries to it.</strike>
----
+
* <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>
If you have corrections to this entry or questions about it, please contact: mailto:maintainers@gnu.org
+
* <strike>Both the user name and the current date should be used for the "submitted by" fields -- they should not be user selectable.</strike>
----
+
* <strike>GNU Head goes away when you view "further results" in table of results. For instance: [[Category/Use/copying]]</strike>
</pre>
+
**<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>
 
+
* <strike>Make sorting case-insensitive. (See this [https://bugzilla.wikimedia.org/show_bug.cgi?id=33134 SMW bug response].)</strike>
I think we should:
+
* <strike>Add screenshots to entries.</strike>
# <s>Remove the above text from all entries listed in [[GNU]]</s>
+
* <strike>Scripting Lanuages just have empty pages: Is there a particular reason why popular scripting languages, have empty pages with no content. Perhaps people actually browse the free software directory and might be deterred and uncertain as to whether the scripting languages are free (as in freedom) when they find an empty page. See: [[Python]], [[Perl]], [[Ruby]] [[User:Ajn|Ajn]] ([[User talk:Ajn|talk]]) 14:51, 11 April 2013 (EDT) You are right, these do deserve [[Form:Entry|entries]]. I figured out the reason the pages were created blank -- it's nothing special, more of a mishap than something intentional. Basically the pages used to have the license for Perl, Ruby, and Python respectively; when the licenses were moved over to [[License:Perl]], [[License:Python]], [[License:Ruby]], the normal pages were left behind as blank pages -- probably due to an unintential space or blank line. --[[User:Jgay|Jgay]] ([[User talk:Jgay|talk]]) 15:11, 12 April 2013 (EDT)</strike>
# <s>Place the above text in a template, say Template:GNU_promotions</s>
 
# Convert this texted idea to SMW code: if "Is GNU=Yes" then use Template:GNU_promotions"
 
# Add the code to https://directory.fsf.org/wiki/Template:Show or some other link found at https://directory.fsf.org/wiki/Free_Software_Directory:Backlog_Admin_Group#How_to_modify_the_form_edit
 
 
 
: 1. Is now solved (sysadmin: please execute <code>runjobs.php</code> when appropriate to apply the substitutions and allow for further development of this Backlog Task). --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 14:07, 4 December 2020 (EST)
 
: 2. Is now solved (see [[Template:GNU_promotions]]). --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 13:08, 4 December 2020 (EST)
 
: 3. Stalled by pt. 1.
 
 
 
 
 
=== SPDX-related issues ===
 
<span id="SPDX-related-issues"></span>
 
 
 
 
 
Stalled by:
 
 
 
* [[#1520]]
 
* [[#Replace-License-text-in-program-entries]]
 
 
 
See the [https://spdx.org/licenses/ SPDX License List] for license identifiers.
 
 
 
Software Package Data Exchange (SPDX) is a file format used to document information on the software licenses under which a given piece of computer software is distributed. '''The FSF has decided that we are going to switch to the SPDX identifiers''' (eg switch from MPL1.1 to MPL-1.1).
 
 
 
Related links:
 
* https://directory2p.fsf.org/wiki/Property:License
 
* https://directory2p.fsf.org/wiki?title=Special%3APrefixIndex&prefix=&namespace=502
 
* https://directory2p.fsf.org/wiki/Category:License
 
* https://directory2p.fsf.org/w/api.php?action=query&meta=siteinfo&siprop=statistics
 
* https://directory2p.fsf.org/wiki/Form:Entry -- See "values from property=License"
 
</div>
 
 
 
 
 
=== 1520 ===
 
<span id="1520"></span>
 
 
 
 
 
: Is there a way for us to HTTP ping those without using JavaScript?<br/>I think we'll need to add a dedicated script. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 15:26, 24 April 2020 (EDT)
 
 
 
 
 
=== Replace License text in program entries ===
 
<span id="Replace-License-text-in-program-entries"></span>
 
 
 
 
 
See [[Free_Software_Directory:SPDX_Group]] for text to replace
 
 
 
Avoid https://directory.fsf.org/wiki/Special:ReplaceText
 
# https://directory.fsf.org/wiki/Special:ReplaceText is limited to 250 pages per execution. That means to much job, "License:GPLv2orlater" is used in [https://directory.fsf.org/wiki?title=Special:WhatLinksHere/License:GPLv2orlater {{#ask:[[License::GPLv2orlater]]| format=count}}] pages to give a picture.
 
# to slow, 10 pages modified in 3 minutes (https://directory.fsf.org/wiki/Special:RecentChanges monitored), or 250 pages in 90 minutes.
 
 
 
<pre>
 
Original text:
 
|License=GPLv3orlater
 
Replacement text:
 
|License=GPL-3.0-or-later
 
 
 
Search in namespaces:Main
 
Replace only in category: Entry
 
</pre>
 
 
 
Do not use regex like this, it will add "^|License=GPLv3orlater$" at the very beginning of the page:
 
 
 
<pre>
 
Original text:
 
^|License=GPLv3orlater$
 
Replacement text:
 
|License=GPL-3.0-or-later
 
 
 
Use regular expressions
 
Search in namespaces:Main
 
Replace only in category: Entry
 
</pre>
 
 
 
 
 
=== 453654 ===
 
<span id="453654"></span>
 
 
 
 
 
Stalled by:
 
 
 
* [[#Internationalization-and-localization]]
 
 
 
[[FSD:Features|Proposed features for the FSD]]
 
 
 
 
 
=== 665349 ===
 
<span id="665349"></span>
 
 
 
 
 
[[FSD:Features/Browse|Category browsing]]
 
 
 
 
 
=== 494394 ===
 
<span id="494394"></span>
 
 
 
 
 
Add a link for binary download?
 
 
 
 
 
=== 348594 ===
 
<span id="348594"></span>
 
 
 
 
 
Need to implement mass-emails about email verification, and directions for changing preferences.
 
 
 
 
 
=== 905235 ===
 
<span id="905235"></span>
 
 
 
 
 
[[FSD:GNU | Add/update GNU packages]]
 
 
 
 
 
=== 593493 ===
 
<span id="593493"></span>
 
 
 
 
 
Put a link to site dumps and info about the machine readability of that information on the main page.
 
 
 
::[[User:David_Hedlund|David]], clarification is required. Please specify the position of the site dumps. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 13:11, 14 June 2019 (EDT)
 
 
 
 
 
=== 345653 ===
 
<span id="345653"></span>
 
 
 
 
 
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.
 
 
 
 
 
=== 453224 ===
 
<span id="453224"></span>
 
 
 
 
 
Add "table of contents" header above tabs inside <tt>noscript</tt> tags so that it only displays when javascript is turned off.
 
 
 
 
 
=== 234ed3 ===
 
<span id="234ed3"></span>
 
 
 
 
 
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: [https://directory.fsf.org/wiki/Special:FormEdit/Bug_report?Bug_report&#91;Project_page&#93;={{PAGENAME}}&amp;namespace=Review Example bug report link]
 
 
 
 
 
=== 432490 ===
 
<span id="432490"></span>
 
 
 
 
 
'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.
 
 
 
 
 
=== 23431f ===
 
<span id="23431f"></span>
 
 
 
 
 
"New Packages RSS feed"'s license verification dates are messed up.
 
 
 
 
 
=== d34234 ===
 
<span id="d34234"></span>
 
 
 
 
 
Conditional statements should be created for various properties (e.g., "Audio:mp3" should result in "works-with::Audio" being set on a page automatically).
 
 
 
 
 
=== 451154 ===
 
<span id="451154"></span>
 
 
 
 
 
Implement an in-browser irc client that displays only when meetings are live on the [[Main Page]] in addition to the "The meeting is active right now!" (see <nowiki>Template:IRC_text</nowiki>).
 
 
 
: That will require a free SaaSS (like https://webchat.freenode.net/) but we don't recommend third-party SaaSS in general, however I think this would be ok if the FSF should embed a web-based IRC widget into something like irc://webchat.fsf.org/fsf (for the [[Main_Page|Directory]]) and irc://webchat.fsf.org/libreplanet (for [https://libreplanet.org/wiki/Main_Page Libre Planet]). However, the listed [[Free_Software_Directory:Free_software_evaluation#IRC_clients|web-based IRC clients are not compatible with LibreJS]], that must be fixed first. The authors of these programs accept patches, perhaps the FSF can evaluate which client the want to use and patch it? Related: IceCat, [https://savannah.gnu.org/bugs/index.php?53530 Free web-based IRC client replacement for Mibbit needed]. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 02:22, 31 March 2018 (EDT)
 
 
 
 
 
=== 453654 ===
 
<span id="453654"></span>
 
 
 
 
 
Create a new standard template to list the translations of each page in a professional way. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]])
 
 
 
: On second thought we should use a dedicated module, so we can enlist the translations on the left user bar. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 15:01, 15 May 2020 (EDT)
 
 
 
 
 
=== set empty default values ===
 
<span id="set-empty-default-values"></span>
 
 
 
 
 
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.
 
 
 
 
 
=== homepage should not be required ===
 
<span id="homepage-should-not-be-required"></span>
 
 
 
 
 
The "Homepage" field should not mandatory to fill in entries. For [[Icedove]] doesn't have any homepage and it shouldn't be set to the Thunderbird homepage because it's not free due to trade mark issues.
 
 
 
=== non-official compiled or non-source releases ===
 
<span id="non-official-compiled-or-non-source-releases"></span>
 
 
 
 
 
Should we add to [[FSD:Requirements]] that we only permit data related to official releases? For example, the current Windows download link for [[IceCat]] is unofficial, but it's made by jenslody@fedoraproject.org
 
 
 
: (20:43:02) David_Hedlund: But it's still a unofficial release. I think we should discuss this policy.
 
 
 
===Randomize Approved revisions page===
 
Or at least offer such option, because [[Special:ApprovedRevs|current aplhabetical sort]] will lead to projects named AAAA something getting frequent updates and projects called ZZZ never getting updated. Perhaps sort by age would make sense too. --[[User:Mviinama|Mviinama]] ([[User talk:Mviinama|talk]]) 12:24, 31 August 2021 (EDT)
 
 
 
===Project pages===
 
A way to have a single project page which has multiple programs (thus entries) under it. Example: The project page would not have a version download field. The need for this comes up quite a bit, but https://github.com/OpenDroneMap was the project that inspired this entry ~craigt
 
  
 
==Import==
 
==Import==
  
 +
===GNU packages===
 +
Make a script to generate XML files that syncs [[GNU]] with https://www.gnu.org/software/ which also list decommissioned GNU packages, a property that also should be imported, see https://directory.fsf.org/wiki/Property:Decommissioned/Obsolete
  
=== import GNU packages ===
+
See https://directory.fsf.org/wiki/User_talk:Bendikker/cleanlinksgnusoftware for other examples.
<span id="import-GNU-packages"></span>
 
 
 
 
 
Make a script to generate XML files that syncs [[GNU]] with https://www.gnu.org/software/ which also list decommissioned GNU packages, a property that also should be imported, see https://directory.fsf.org/wiki/Property:Decommissioned/Obsolete
 
  
See https://directory.fsf.org/wiki/User_talk:Bendikker/cleanlinksgnusoftware (deleted, I asked why: [[User_talk:Bendikker#cleanlinksgnusoftware]]) for other examples.
+
=== Debian Packaging System ===
  
 +
From https://directory.fsf.org/wiki?title=Org:DBpedia&oldid=41404#Debian_Packaging_System by Freephile:
  
=== import screenshots ===
+
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
<span id="import-screenshots"></span>
 
  
 +
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.
  
 +
====Screenshots====
 
https://screenshots.debian.net/
 
https://screenshots.debian.net/
  
It's not possible to download the archive right now.
+
===XML update===
 
 
" The current version features a large JSON blog that gives you
 
information about all packages and the related screenshots. You could
 
load the screenshots directly from directory.fsf.org if you like. That's
 
what several other websites like packages.debian.org do. The only
 
challenge you would face might be to match the "upstream" package name
 
to the software name you use in your database." -- Christoph Haas, the Debian Screenshots maintainer
 
 
 
 
 
=== import icons ===
 
<span id="import-icons"></span>
 
 
 
 
 
The https://screenshots.debian.net/ maintainer said that he will add icons for Debian packages (provided by https://wiki.debian.org/AppStream) in the bug tracker: https://salsa.debian.org/debian/debshots/boards.
 
 
 
 
 
=== Software icons ===
 
Make it possible to upload [https://en.wikipedia.org/wiki/Icon_(computing) software icons] in the edit form. Display the icons next to the title in the entries. I asked https://directory.fsf.org/wiki/User_talk:Vibhuti to do this (and to write down a howto in https://directory.fsf.org/wiki/Free_Software_Directory:Backlog_Admin_Group#How_to_add_file_upload_to_form_edit) since she made it possible to upload screenshots in the edit form recently. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 15:16, 20 April 2018 (EDT)
 
 
 
=== import other repo data ===
 
<span id="import-other-repo-data"></span>
 
 
 
* [https://notabug.org/Calinou/awesome-gamedev awesome-gamedev]
 
* [https://www.debian.org/devel/debian-med/ Debian Med]
 
* GetDeb, and it's sister project Playdeb
 
 
 
==== FSWDB ====
 
[[User:LorenzoAncora|LorenzoAncora]]'s (former Backlog Admin Group member) [https://fswdb.eu/ FSWDB]. By the way, he's having a plan to sync the Directory to his site too.
 
 
 
====Software specific====
 
 
 
=====Emacs=====
 
[[Package repositories for GNU Emacs]]
 
 
 
=== wikidata ===
 
<span id="wikidata"></span>
 
 
 
 
 
Take data from wikidata.org that's not in Debian's main repository.
 
 
 
 
 
=== XML update ===
 
<span id="XML-update"></span>
 
 
 
  
 
Please study these XML outputs in IceCat
 
Please study these XML outputs in IceCat
Line 339: Line 113:
  
 
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.
 
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.
<div class="mw-collapsible mw-collapsed">
+
 
<div>My example (look for differences) when I want to import 600 add-ons:</div>
+
My example (look for differences) when I want to import 600 add-ons:
<pre class="mw-collapsible-content">
+
<pre>
 
{{Entry
 
{{Entry
 
|Name=NoScript
 
|Name=NoScript
Line 380: Line 154:
 
{{Featured}}
 
{{Featured}}
 
</pre>
 
</pre>
</div>
 
  
 +
==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
  
=== consistent CSS styling ===
+
Therefore is should neither be possible to enter licenses in free text, it should be a dropdown menu only.
<span id="consistent-CSS-styling"></span>
 
  
 +
:'''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?
  
 +
==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:
 
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
 
# Check all local style clauses in our custom code
Line 395: Line 184:
 
# <code>style</code> clauses should be replaced with their <code>class="'''css-class'''"</code> counterparts.
 
# <code>style</code> clauses should be replaced with their <code>class="'''css-class'''"</code> counterparts.
  
 +
==Backlog Admin Group tasks==
 +
These are issues that has effectively been collaborated in the Backlog Admin Group.
  
== Backlog Admin Group ==
+
===Semantic Forms===
 
 
===headertabs ('''absolute number 1 top priority''')===
 
The ''headertabs'' are used by software entries (random example: [[Emacs]]). The problem is that the tabs are not always displayed! It's complicated to break down software entries, instead the simple user page for [[User:Sudoman|Sudoman]] that is using headertabs can be used to reproduce the issue.
 
 
 
See: '''Extension talk:Header Tabs: [https://www.mediawiki.org/wiki/Topic:W1i6hpx023qc4pe9 Header Tabs sometime fails to load]''' for more info. [https://www.mediawiki.org/w/index.php?title=Topic:W1i6hpx023qc4pe9&topic_showPostId=x3yxtr1n0c7kosyk#flow-post-x3yxtr1n0c7kosyk Potential solutions are at the end of the page.]
 
 
 
I think we should try to solve this issue once and for all, with submitted and followed up bug reports. Because this even gives the admins of the Directory the impression that the site is unstable.
 
 
 
: I vote for removing headertabs from the submission form, without replacements. I didn't do much research on the alternatives, so I don't know the full details, but if we do decide to provide a replacement so as to present a shorter version of the form, perhaps we can do one of:
 
:# implement a collapsible div to replace the forbidden details/summary elements (MediaWiki might already have said div class), or;
 
:# divide the form and templates into subpages of an entry and do all transclusions in the entry's main page (might be complicated, since one needs to find a way to do all that using page forms, and also to allow any "edit" links to point to the form of the subpage instead, not to the section). This last option might provide other advantage in regards to allowing limited web browsers to send contributions since less things need to be received/sent. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 20:51, 10 March 2024 (EDT)
 
 
 
===Main page (top priority)===
 
* [[Free_Software_Directory:Backlog_Admin_Group/Main_page]]
 
* [[Draft:Main page]]
 
 
 
This section and page is reserved because it represents the site. If it does not exist, it means that we are not working on it at the moment but will work on it at some point in the future.
 
 
 
===Template:EntryGNU and Template:EntryDetails (top priority)===
 
<pre>
 
################################
 
Visible
 
 
 
https://directory.fsf.org/wiki/Bayonne
 
{{Entry
 
|Is High Priority Project=Yes
 
|Is GNU=Yes
 
   
 
################################
 
Not visible
 
 
 
{{EntryGNU
 
|Is GNU=Yes
 
 
 
https://directory.fsf.org/wiki/Emacs
 
 
 
 
 
{{EntryDetails
 
|Is High Priority Project=Yes
 
 
 
https://directory.fsf.org/wiki/H-client
 
</pre>
 
--[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 17:59, 8 September 2021 (EDT)
 
 
 
: I think we need to do one of the following:
 
:# Change [[Template:Entry]] such that [[Template:EntryDetails]] and [[Template:EntryGNU]] are included in the first. I was going to do this, but due to the risks that follow I decided to leave the points here for future vote. '''Risks:''' might make a high MediaWiki job queue; templates might misbehave by not showing values correctly to other templates.
 
:# Since there are old entries that still call [[Template:Entry]] to define parameters that are now expected to be used with [[Template:EntryGNU]] or [[Template:EntryDetails]], find [[Free Software Directory:Participate/Editing multiple pages|a way to list, download, edit and then upload the many affected pages]]. '''Risks:''' might make a high MediaWiki job queue.
 
:# Depending on how many pages use the new templates, see if their use is reversible and try to rework on the [[Form:Entry]] design such that it allows the section breaks and if other requirements can be fulfilled. I don't know if the number is a bug or not, but [[Special:WhatLinksHere]] shows that there are only 1,000 entries that link/transclude each one of [[Template:EntryDetails]] and [[Template:EntryGNU]]. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 15:27, 22 March 2024 (EDT)
 
 
 
===Text browsers evaluation (top priority)===
 
 
 
 
 
'''Top priority issue!'''
 
 
 
Move the text browers listed at https://directory.fsf.org/wiki/Collection_talk:Text_mode_browsers,_and_IceCat_WebExtensions_for_text_editors to https://directory.fsf.org/wiki/Collection:Text_mode_browsers,_and_IceCat_WebExtensions_for_text_editors once the wiki doesn't require JS.
 
 
 
=== IRC bot (top priority) ===
 
[[Free Software Directory:IRC bot]]. Assigned to [[User:Noisytoot]]. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 15:46, 24 September 2021 (EDT)
 
 
 
=== edit with form has to be reloaded to work ===
 
<span id="edit-with-form-has-to-be-reloaded-to-work"></span>
 
 
 
 
 
'''Top priority issue!'''
 
 
 
Software entries have a "Edit with form" tab. Example, https://directory.fsf.org/wiki?title=Gnuzilla&action=formedit
 
 
 
You have to reload the page in the browser to make the tabs visible (including the "Save" tab). Volunteers who doesn't know about will most likely not be able to update existing entries. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 08:50, 14 May 2020 (EDT)
 
 
 
: A possible solution could involve defining a checkbox with opacity:0 (display:none doesn't work for this); make the tab title as a label for that checkbox; and style the tab content so that when the checkbox is checked, the contents show and all the rest disappears. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:39, 1 May 2020 (EDT)
 
: Please could you extend this issue by adding a link to a video/GIF which shows the steps to reproduce the bug in a popular web browser? --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
: On a second thought, I have tested my suggestion and that doesn't work since MediaWiki forbids the required HTML elements. I think we should remove headertabs, without replacement. Optionally we could later implement a collapsible div for each part or simplify the form itself for the contributor (this one might require complex MediaWiki notation). --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:04, 10 March 2024 (EDT)
 
 
 
i noticed this myself; and was quite confused by it - this is definitely a high-priority UX bug [[User:Bill-auger|Bill-auger]] ([[User talk:Bill-auger|talk]]) 12:29, 19 August 2022 (EDT)
 
 
 
=== Antifeature templates ===
 
https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures
 
 
 
* "Attention!
 
Sample text." - https://directory.fsf.org/wiki/Adblock_Plus
 
* Some entries are using the AttentionBox template, example https://directory.fsf.org/wiki/Adblock_Plus
 
 
 
=== display-a-Role-column ===
 
<span id="display-a-Role-column"></span>
 
 
 
 
 
'''Top priority issue!'''
 
 
 
See [[Free Software Directory:Backlog Admin Group/Sandbox2]]
 
 
 
"Tried everything I could but can't make it combine team, role, IRC and
 
time zone. There are two options:
 
 
 
a) Make [[Property:Member of team]] of type Record, and so allow it to
 
hold a team+role a pair, but for that each user *must* use {{#subobject:
 
… }} to *set* [[Property:Member of team]] *for each* team they are
 
member of. This will have caveat that there will be *no known way* to
 
get both the user's role and his time zone and IRC nick, since these two
 
will be blank. This also has disadvantage that anyone could declare
 
themselves as Team Captain and no notification would be sent regarding that.
 
 
 
b) Make [[Property:Member of team]] of type Page and so forget the roles
 
and only refer to team pages. This allows queries to see both the users'
 
time zone and IRC nick, besides being simple to set (because you can
 
either use {{#set: … }} or [[Member of::TEAM PAGE]]. As a side note, the
 
Team Captain would still have to declare his role in the teams' main
 
page anyways, since this is the most important role. Besides, provided
 
everyone involved has that page in their watchlist, then no one would
 
dare autodeclare themselves as Team Captain.
 
 
 
I applied (b) for now since I think it's the best option. As a side note
 
if we no longer will use [[Property:Team captain]] nor [[Property:Team
 
member]], we should remove it." - Adonay, 2020-05-05 05:21
 
 
 
 
 
====Group tables with mixed dynamic and static data====
 
In [[Free Software Directory:Backlog Admin Group]], and [[Free Software Directory:SPDX Group]], the table should have static values for:
 
* User
 
* Role
 
* Reference
 
 
 
However, columns with global data should be loaded dynamically from the user page (like we did [https://directory.fsf.org/wiki?title=Free_Software_Directory:Backlog_Admin_Group&oldid=81043 before]):
 
* Time zone
 
* libera.chat nick
 
* Title
 
--[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 20:48, 8 September 2021 (EDT)
 
 
 
=== Exclude unapproved entries from High Priority Projects ===
 
[[Collection:High Priority Projects]] lists Unapproved entries like [[Komodo]]. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 22:35, 20 August 2021 (EDT)
 
 
 
[[Category/Works-with-format/pdf]] also lists unapproved entries, for example [[Ipfs]] on that page, if you show more entries (needs JS enabled). [[User:JacobK|JacobK]] ([[User talk:JacobK|talk]]) 09:21, 27 February 2023 (EST)
 
 
 
=== Module Countdown ===
 
<span id="Module-Countdown"></span>
 
 
 
 
 
We should ask the FSF if the tech team can install https://en.wikipedia.org/wiki/Module:Countdown in MediaWiki<br>
 
If they agree, then we must implement recurring events first in https://en.wikipedia.org/wiki/Module:Countdown and then install it on the Directory.
 
--[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 13:00, 14 February 2020 (EST)
 
: I don't agree, the current implementation in wikicode works correctly and the compatibility of an unofficial module must be guaranteed manually from version to version. Furthermore, replacing the work already done would make all the time spent useless, with minimal advantages. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 13:58, 14 February 2020 (EST)
 
:: The issue was solved, so we can archive this Active Backlog Task. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 15:01, 15 May 2020 (EDT)
 
 
 
 
 
=== High Priority Projects Project Teams and Translations ===
 
<span id="High-Priority-Projects-Project-Teams-and-Translations"></span>
 
 
 
 
 
'''Top priority issue!'''
 
 
 
The high priority pages consist of collections and categories that manually have been added to https://directory.fsf.org/wiki/Main_Page like this:
 
<pre>
 
  <li>[[Collection:PRISM|PRISM]] (collection)</li>
 
  <li>[[Collection:Privacy pack|Privacy pack]] (collection)</li>
 
  <li>[[Category/Interface/accessibility|Interface: Accessibility]]</li>
 
  <li>[[Category/Internet-application/privacy|Internet-application: Privacy]]</li>
 
  <li>[[Category/Internet-application/security|Internet-application: Security]]</li>
 
  <li>[[Category/Live-communications|Live-communications]]</li>
 
  <li>[[Category/Protocol/tor|Protocol: Tor]]</li>
 
  <li>[[Category/Security|Security]]</li>
 
</pre>
 
 
 
 
 
=== Templates to sort ===
 
* Randomly sort the entries in https://directory.fsf.org/wiki/Template:Featured_single -- because it's boring to see the same featured programs on the main page every time you visit it.
 
 
 
Entries that are not sorted alphabetically that should be that:
 
* https://directory.fsf.org/wiki/Template:Category-page
 
** Randomly sorted: https://directory.fsf.org/wiki/Category/Runs-on
 
** Mostly alphabetically: https://directory.fsf.org/wiki/Category/Protocol -- "tox", and "tor" is sorted after "xmpp"   
 
* Please also update the code in https://directory.fsf.org/wiki/Template:Subcategory-page
 
--[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 08:53, 28 August 2021 (EDT)
 
 
 
=== n2io34d ===
 
<span id="n2io34d"></span>
 
 
 
 
 
Check the [[Free_Software_Directory:Backlog_Admin_Group/Sandbox|sandbox]]: I cannot get rid of the "Category/", and the coma, from the text in the links. The links should be formatted like they are displayed at https://directory.fsf.org/wiki/Template:Category_table_divided. --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 08:41, 29 March 2020 (EDT)
 
 
 
=== it234902 ===
 
<span id="it234902"></span>
 
 
 
 
 
Stalled by:
 
 
 
* [[#Internationalization-and-localization]]
 
 
 
<nowiki>[[Category:Italian_translations]]</nowiki> is not listed at [[Free Software Directory:Backlog Admin Group/Sandbox]]
 
 
 
 
 
=== pl329423 ===
 
<span id="pl329423"></span>
 
 
 
 
 
[[Special:PermanentLink/80634]] has my attempt to fix most of these. I was unable to solve the case of [[:Category:Translations]] subcategories not being listed. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 22:06, 24 April 2020 (EDT)
 
 
 
 
 
=== form-entry-accessibility-BAG ===
 
<span id="form-entry-accessibility-BAG"></span>
 
 
 
 
 
Stalled by:
 
 
 
* [[#form-entry-licenses-proposal-BAG]]
 
* [[#form-entry-resource-info-proposal-BAG]]
 
* [[#form-entry-categories-proposal-BAG]]
 
 
 
: We won't abandon the existing table layout, however there is no reason for not making it adaptive, as HTML tables can be stylized like any other element and are still fully supported.<br>I believe we should add a CSS fix for small-screen/mobile devices. Feel free to propose (a tested) one during the next FSD meetings. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
 
 
 
 
=== form-entry-general-info-proposal-BAG ===
 
<span id="form-entry-general-info-proposal-BAG"></span>
 
 
 
 
 
<ol>
 
<li>Move "Dev languages" to Categories ("Programming-language").
 
<li>Remove "Related projects". Categories do this instead. One could also make a link to a separate query (no need to embed the query), with which the person could look for other projects which have similar properties or categories.
 
<li>Make "User level" a dropdown, since only one can be selected.
 
<li>Remove "Component programs" and make redirects named after each values inside these. If the entry A is also known as B and no other program has the same alias (B), then B should be a redirect to A.
 
<li>While "Checksum" suggests to paste the result of <code>sum</code> command, [[Property:Checksum]] is URL, and many packages use it to point to actual files where the result of <code>sha256sum</code>, <code>sha512sum</code> or <code>md5sum</code> are stored, and none of these are related to <code>sum</code> command.
 
<li>Move "Test entry" to the top. The idea is to advise users to use this more often when they are not confortable with their edits. </ol>--[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:39, 1 May 2020 (EDT)
 
 
 
: I do not agree with pt. 1 to 4 but I agree with pt. 5 and 6, at the following conditions: <code>sum</code> should be replaced with <code>SHA or MD5</code> and "Test Entry" should be smaller and placed in the top-right angle of the form and not keyboard selectable. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
 
 
 
 
=== form-entry-licenses-proposal-BAG ===
 
<span id="form-entry-licenses-proposal-BAG"></span>
 
 
 
 
 
: This does not seem the best solution, how about adding a clarification near the copyright widget? --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
 
 
 
 
=== form-entry-resource-info-proposal-BAG ===
 
<span id="form-entry-resource-info-proposal-BAG"></span>
 
 
 
 
 
Also, change "Resource kind" so that:
 
<ol>
 
<li>"Mailing List Subscribe" and "Mailing List Info/Archive" are merged with "Mailing List".
 
<li>Remove "VCS Repository Webview".
 
<li>Make "Bug Tracking", "Developer", "General", "Support" and all their "Subscribe" counter parts instances to "Mailing List" and add "Resource audience" corresponding to the first names I said (example: "Bug Tracking", "Support")
 
<li>Rename "Download" to "Object code download" or "Non-source download" or "Binary download".</ol> --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:39, 1 May 2020 (EDT)
 
 
 
: I agree only with pt. 1 and 4. We can do pt. 4 directly during the next meeting, but for pt. 1 we should take into account the DB. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
 
 
 
 
=== form-entry-categories-proposal-BAG ===
 
<span id="form-entry-categories-proposal-BAG"></span>
 
 
 
 
 
Generally, make each category a listbox. This makes the place less crowded.
 
Also, we must avoid name conflicts, like "security" in "Internet-application" and "internet" in "Security".
 
The proposed mapping would be like this (as page names):-excess HTML; +missing signature marks; -wrong page c
 
<div style="overflow-y:scroll;height:200px;">
 
* Goal-to-be-used-for
 
** comparing
 
** converting
 
** editing
 
** playing-or-viewing
 
* Goal-to-enhance-development
 
** Downcase all from "Version-control"
 
** bug-tracking-system
 
** debugging
 
** game-development
 
** manual-or-automated-build
 
** small-specific-development-task
 
** static-analysis
 
** version-control
 
* Goal-to-work-with-data-of-type
 
** 2d
 
** 3d
 
** archive-or-backup
 
** audio
 
** barcode
 
** color-profile
 
** contact
 
** date-or-time
 
** dictionary
 
** metadata
 
** model-or-project
 
** plot
 
** raster-image
 
** text
 
** text-font
 
** vector-image
 
** video
 
* Goal-to-work-with-database-or-query-language
 
** blockchain
 
** recutils
 
** sparql
 
** sql
 
** xpath
 
* Goal-to-work-with-multimedia-format
 
** mp3
 
** iso9660
 
** ogg-vorbis
 
** speex
 
** flac
 
** ogg-theora
 
** opus
 
** webm
 
** flv
 
** swf
 
* Goal-to-work-with-structure-or-style-language
 
** atom
 
** css
 
** csv-or-dsv
 
** docbook
 
** enriched-text
 
** html
 
** json
 
** latex
 
** markdown
 
** mediawiki
 
** opendocument
 
** org-mode
 
** pdf
 
** portable-object
 
** postscript
 
** rdf
 
** rich-text-format
 
** rss
 
** sgml
 
** smil
 
** svg
 
** tex
 
** texinfo
 
** textile
 
** webvtt
 
** xml
 
** xsl
 
** yaml
 
* Interface-through
 
** bot
 
** console
 
** daemon-or-server
 
** email
 
** library
 
** web
 
** Downcase all from "UI-toolkit"
 
* Other-goal
 
** accessibility
 
** accounting
 
** animation-or-movie-making
 
** architecture
 
** astronomy
 
** authentication
 
** automated-theorem-proving
 
** aviation
 
** biology
 
** chemistry
 
** commerce
 
** design
 
** education
 
** encryption
 
** engineering
 
** faxing
 
** financial-mathematics
 
** firewall
 
** forensics
 
** gaming-or-entertainment
 
** genealogy
 
** geography
 
** geology
 
** ham-radio
 
** health-care
 
** home-automation
 
** layouting-or-typesetting
 
** live-communcation
 
** meteorology
 
** model-or-quality-checking
 
** monitoring
 
** network-routing
 
** news-aggregation-or-reading
 
** payment-system
 
** physics
 
** psychology
 
** productivity
 
** project-management
 
** publishing
 
** scheduling
 
** security
 
** simulation
 
** software-configuration
 
** sports
 
** statistics
 
** stock-market
 
** symbolic-mathematics
 
** telephony
 
** localization-or-translation
 
** virtualization
 
* Programming-language
 
** Downcase all from the original
 
** Move "c++" to "cpp" or "c-plus-plus"
 
** lisp
 
** r
 
* Protocol
 
** Downcase all from the original
 
** tcp
 
* Runs-on
 
** Downcase all from the original
 
</div>
 
--[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 21:39, 1 May 2020 (EDT)
 
 
 
: This issue was already solved in your absence during the latest FSD meeting (May the 1st) by fixing the existing CSS to guarantee correct alignment and subdivision. For now it would not be wise to change the UX so much, but I suggest to keep your tip here for the future. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 08:29, 5 May 2020 (EDT)
 
 
 
 
 
=== other2377 ===
 
<span id="other2377"></span>
 
 
 
  
 
[[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".
 
[[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".
  
 
+
=====Add=====
=== frm5d33 ===
 
<span id="frm5d33"></span>
 
 
 
 
 
 
To "Edit with form" (Example: https://directory.fsf.org/wiki?title=IceCat&action=formedit&debug=true#tab=1__General_info):
 
To "Edit with form" (Example: https://directory.fsf.org/wiki?title=IceCat&action=formedit&debug=true#tab=1__General_info):
  
* <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 <nowiki>|Extension of=</nowiki> 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>
+
* <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]].
 
** [[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]].
** 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 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'''.
 
*** [[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:Decommissioned/Obsolete</strike>
Line 827: Line 205:
 
* <strike>Resource info -> Resource kind: Videotelephony</strike>
 
* <strike>Resource info -> Resource kind: Videotelephony</strike>
 
* <strike>Resource info -> Resource kind: E-mail: OpenPGP public key</strike>
 
* <strike>Resource info -> Resource kind: E-mail: OpenPGP public key</strike>
** 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 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>
 
 
  
=== autoedit ===
+
=====Modify=====
<span id="autoedit"></span>
 
  
 +
* The "irc:" is displayed twice like this: irc://irc:is broken, see Template:Print entry. And if you remove irc://, it prepends http://. Form edit requires irc:: "must have the correct URL format, starting with "http""
 +
* 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]].
  
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 [https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Linking_to_forms autoedit section at bottom of Semantic Forms page].
+
=== 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 [https://www.mediawiki.org/wiki/Extension:Semantic_Forms/Linking_to_forms autoedit section at bottom of Semantic Forms page].
  
 
=== proprietary program search ===
 
=== proprietary program search ===
<span id="proprietary-program-search"></span>
 
 
  
 
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 <strike>[http://smwforum.ontoprise.com/smwforum/index.php/Semantic_MediaWiki_Plus#Enhanced_Retrieval_extension Enhanced Retrieval extension]</strike> (obsolete).
 
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 <strike>[http://smwforum.ontoprise.com/smwforum/index.php/Semantic_MediaWiki_Plus#Enhanced_Retrieval_extension Enhanced Retrieval extension]</strike> (obsolete).
 
  
 
=== License verification ===
 
=== License verification ===
<span id="License-verification"></span>
 
 
 
Licenses and license notifications should preferably be verified by a license compliance software system (like FOSSology).
 
 
When doing license verification by hand, 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.
 
 
: I fully agree and I believe all should be bounded by well defined rules.<br>Having such systems and workflows in place is fundamental. If necessary, I am also willing to mentor during meetings.  --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 14:45, 31 January 2020 (EST)
 
  
 +
When doing license verification, we need to ensure two things:
  
=== Point system and mentoring ===
+
# More than one person checks a license
<span id="Point-system-and-mentoring"></span>
+
# 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 [https://www.mediawiki.org/wiki/Extension:Semantic_Tasks Semantic Tasks].  
 
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 [https://www.mediawiki.org/wiki/Extension:Semantic_Tasks Semantic Tasks].  
Line 866: Line 238:
 
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.
 
But, more important than the point system is ensuring that level-3 individuals are not only verified by level-1 individuals, but, that some 1-on-1 guidance and help/mentoring is provided to level-3 individuals from level-1 individuals.
  
 
+
==FSF staff tasks==
=== Component programs and Prerequisite description serve the same purpose ===
+
<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>
<span id="Component-programs-and-Prerequisite-description-serve-the-same-purpose"></span>
 
 
 
 
 
[[Property:Component programs]] and [[Property:Prerequisite description]] serve the same purpose, that is to say, they describe dependencies.
 
 
 
This is a request for vote and also for comments or better proposals. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 17:21, 23 April 2021 (EDT)
 
 
 
 
 
=== Make Component programs and Prerequisite description of type Page ===
 
<span id="Make-Component-programs-and-Prerequisite-description-of-type-Page"></span>
 
 
 
 
 
[[Property:Component programs]] and [[Property:Prerequisite description]] should be of type Page, so that arbitrary text is not allowed.
 
 
 
Furthermore, they should allow only existing entries. As an additional feature, they could allow autocompletion.
 
 
 
I have implemented this proposal in [[Special:Permalink/83793|a form]], [[Special:Permalink/83794|a template]], and [[Special:Permalink/83765|a property]], which can be seen from [[Special:Permalink/83795|this dummy entry]] and each value appears correctly in the property browser in the left navigation bar. The proposal has the disadvantage that it requires Select2 JavaScript to work (according to MediaWiki Page Forms extension documentation).
 
 
 
I tried using a "listbox" Page Forms input type, but that can be slow for the wiki to process, since all entries will be displayed at once.
 
 
 
This is a request for vote and also for comments or better proposals. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 17:21, 23 April 2021 (EDT)
 
 
 
== FSF ==
 
  
 
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.
 
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===
  
=== Debian import ===
+
This page has to many bugs to effectively organize them. We need a dedicated bug tracker for the Directory.
The Debian meta-data import script is broken: http://git.savannah.gnu.org/cgit/directory.git/tree/export.py
 
 
 
# The import script must be fixed
 
# The Directory must be [[Free_Software_Directory:Infrastructure#Page_structure|structured]]
 
# The import script should be run at continuous intervals, once per week, ideally a few hours before the Friday IRC meeting.
 
 
 
=== Internationalization and localization ===
 
<span id="Internationalization-and-localization"></span>
 
  
 +
The concept for public bug trackers for FSF run websites has been posted in [https://lists.gnu.org/archive/html/directory-discuss/2017-05/msg00004.html Directory-Discuss mailing-list].
  
'''Top priority issue!'''
+
Matt Lee said that he back in January 2017 but nothing happened and he never replied!
  
 +
===Internationalization and localization===
 
https://en.wikipedia.org/wiki/Free_Software_Directory is available in these languages at this writing:
 
https://en.wikipedia.org/wiki/Free_Software_Directory is available in these languages at this writing:
 +
<pre>
 +
Languages:
 +
Español
 +
Français
 +
Italiano
 +
Nederlands
 +
日本語
 +
Русский
 +
中文
 +
</pre>
  
* Español
+
We need to enable internationalization and localization in our MediaWiki instance so volunteers easily can add new translated pages. For example [[Collection:IOS]] (4 languages) and [[Collection:Windows]] (3 languages) need the translation links in the sidebar.
* Français
 
* Italiano
 
* Nederlands
 
* 日本語
 
* Русский
 
* 中文
 
 
 
We need to enable [https://www.mediawiki.org/wiki/Extension:Translate internationalization and localization] in our MediaWiki instance so volunteers easily can add new translated pages. For example [[Collection:IOS]] (4 languages) and [[Collection:Windows]] (3 languages) need the translation links in the sidebar.
 
  
:: This issue is blocking the [[Free_Software_Directory:Translators|translation team]]: without it, it is not possible to plan and assign translations, nor to prepare translators properly. ''This extension should be installed as soon as possible''. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 04:17, 17 February 2021 (EST)
+
===Semantic MediaWiki===
  
=== job-queue ===
+
====Link text====
<span id="job-queue"></span>
 
  
 +
=====IRC (temporarily fixed)=====
 +
The IRC resource is displayed twice like this on [[IceCat]] for example.
  
[[:mw:Job queue|Job queue length]]
 
* Semantic Mediawiki jobs: https://www.semantic-mediawiki.org/wiki/Help:UpdateJob
 
* Rebuilding Semantic Mediawiki data by hand: https://www.semantic-mediawiki.org/wiki/Help:Maintenance_script_rebuildData.php
 
* <code>jobs</code> value from the API call: https://directory.fsf.org/w/api.php?action=query&meta=siteinfo&siprop=statistics
 
* On dev there is an alias
 
 
<pre>
 
<pre>
alias wikijobs='curl -s '\''https://directory2p.fsf.org/w/api.php?action=query&meta=siteinfo&siprop=statistics&format=json'\'' | jq -r .query.statistics.jobs'
+
IRC general channel
 +
    [irc:chat.freenode.net/icecat irc:chat.freenode.net/icecat]
 
</pre>
 
</pre>
  
Full rebuild of Semantic Mediawiki data took over 14 hours, after that there were 0 jobs in the queue
+
* 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:
<pre>
+
** 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).
437206 IDs refreshed.
+
*** 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:
Memory used: 180260544 (b: 13003608, a: 193264152) with a runtime of 53171.62 sec (886.19 min)
+
**# an issue between the templates used;
 
+
**# an issue with the <code>#ask:</code> queries and the <code>template</code> result format;
</pre>
+
**# 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).
=== icecataddons ===
+
*: --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 08:47, 27 January 2018 (EST)
<span id="icecataddons"></span>
+
* 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)
 
 
List incomplete IceCat add-ons. [[Free Software Directory:IceCat extensions (proposed)/FSD bugs issue 1]]
 
 
 
=== icecatun ===
 
<span id="icecatun"></span>
 
 
 
 
 
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.
 
 
 
 
 
=== Multiple software categories -temporarily fixed- ===
 
<span id="Multiple-software-categories--temporarily-fixed-"></span>
 
  
 +
;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>
 
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>
  
Line 973: Line 311:
 
* 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
 
* 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 A ===
+
=====Remove duplicated entries=====
<span id="Remove-duplicated-entries-A"></span>
 
 
 
  
Duplication of entries in https://directory.fsf.org/wiki/Special:ApprovedRevs. 1)  https://directory.fsf.org/wiki?title=Special:ApprovedRevs&action=purge reads "Pages whose approved revision is not their latest" -- the text doesn't use the word "revisions". 2)The "(diff from latest)" links are identical for each entry instead of pointing to unique revisions.
+
* 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.
 
* 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:
 
* 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.
=== 262dup ===
 
<span id="262dup"></span>
 
 
 
 
 
The value of <nowiki>|Extension of=</nowiki> 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
 
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
Line 1,008: Line 340:
 
</pre>
 
</pre>
  
 
+
=====Remove duplicated short description=====
=== Remove duplicated short description rs ===
 
<span id="Remove-duplicated-short-description-rs"></span>
 
 
 
 
 
 
sysadmin@gnu.org ticket: [gnu.org #1205033]
 
sysadmin@gnu.org ticket: [gnu.org #1205033]
  
Line 1,019: Line 347:
 
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.
 
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.
  
=== Faceted search ===
+
:'''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)
<span id="Faceted-search"></span>
 
 
 
 
 
Make an advanced search page used to filter out entries based on their SMW data.
 
 
 
Examples of filters:
 
* Is GNU
 
* Accepts cryptocurrency donation
 
* User level
 
* Categories...
 
 
 
: There is already a page for that, [[Special:Ask]]. Unless you provide more details and examples on how this request could be different from what is already there, I consider this a '''wontfix'''. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 17:59, 18 December 2020 (EST)
 
 
 
 
 
=== wiki special pages ===
 
<span id="wiki-special-pages"></span>
 
  
 +
===MediaWiki===
  
 +
====Special pages====
 
Broken pages in https://directory.fsf.org/wiki/Special:SpecialPages :
 
Broken pages in https://directory.fsf.org/wiki/Special:SpecialPages :
  
<div style="overflow-y:scroll;height:200px;">
 
 
'''Maintenance reports'''
 
'''Maintenance reports'''
 
* Broken redirects
 
* Broken redirects
Line 1,081: Line 396:
  
 
'''Page tools'''
 
'''Page tools'''
* Get data -- Blank page, suggested solution: Special:GetData: Display a message by default - https://phabricator.wikimedia.org/T201660
+
* Get data -- Blank page
</div>
 
  
 +
'''Page Forms'''
 +
* Run query -- "Error: No form was found on page ""."
  
=== Extension Approved Revs ===
+
====Extension:UserFunctions====
<span id="Extension-Approved-Revs"></span>
+
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 [https://directory.fsf.org/wiki?title=Special%3AListUsers&username=Donaldr3&group=bureaucrat&limit=1 administrator and bureaucrat] of the Free Software Directory.
 
 
Some pages show up in https://directory.fsf.org/wiki?title=Special:ApprovedRevs&limit=500&offset=0&show=invalid. It's not possible to approve or unapprove the Collection namespace. I was told it could be solved by playing with $egApprovedRevsNamespaces in LocalSettings.php.
 
* Approved pages (and their redirects) becomes unapproved when they are Moved.
 
* On the entry pages, there is a bug where if a page has had at least one approval and a non-admin edits it, the entry page shows the latest edit instead of the last approved revision.
 
  
 +
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.
  
=== Extension UserFunctions ===
 
<span id="Extension-UserFunctions"></span>
 
 
 
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:Craigt]]:
 
: My name is '''Craig Topham''' and I am an [https://directory.fsf.org/wiki?title=Special%3AListUsers&username=Craigt&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:
 
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:
Line 1,107: Line 412:
 
My name is '''{{#realname:alt}}''' and I am an <nowiki>{{#ifingroup:bureaucrat| [https://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator and bureaucrat] |}} {{#ifingroup:administrator| [https://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator] |}}</nowiki> of the Free Software Directory.
 
My name is '''{{#realname:alt}}''' and I am an <nowiki>{{#ifingroup:bureaucrat| [https://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator and bureaucrat] |}} {{#ifingroup:administrator| [https://directory.fsf.org/wiki?title=Special%3AListUsers&username={{#username:alt}}&group=bureaucrat&limit=1 administrator] |}}</nowiki> of the Free Software Directory.
  
There is also https://www.mediawiki.org/wiki/Extension:RightFunctions.
+
====Performance tuning====
 
 
=== Performance tuning ===
 
<span id="Performance-tuning"></span>
 
 
 
 
 
https://www.mediawiki.org/wiki/Manual:Performance_tuning
 
 
 
 
A lot of contributors have complained that the FSD has been slow in the past years. The most damaging aspect with this is that we are loosing contributors. It must with other words be fixed if we want more contributors -- something that has been suggested as being one of the most important thing with the project at all.
 
A lot of contributors have complained that the FSD has been slow in the past years. The most damaging aspect with this is that we are loosing contributors. It must with other words be fixed if we want more contributors -- something that has been suggested as being one of the most important thing with the project at all.
  
Line 1,121: Line 419:
 
* <strike>Install memcached</strike>, or find some other way to improve performance of the site. We already have Zend OPcache, for opcache, and APCu, for data store, installed and enabled. Memcached is like APCu, but slower.
 
* <strike>Install memcached</strike>, or find some other way to improve performance of the site. We already have Zend OPcache, for opcache, and APCu, for data store, installed and enabled. Memcached is like APCu, but slower.
  
 
+
=====Session data=====
=== wiki Session data ===
 
<span id="wiki-Session-data"></span>
 
 
 
 
 
Disclaimer: Andrew was said that this is most likely not an issue with the programs that hosts the Directory. -- 2018-05-17
 
 
 
 
It may take a minute to move a page. Also, I get this message after ~1 minute (should be at least 5 minutes) of inactive form editing:
 
It may take a minute to move a page. Also, I get this message after ~1 minute (should be at least 5 minutes) of inactive form editing:
  
Line 1,146: Line 438:
 
#* The message appears. From this point on, if you try to submit again, the data is sent as expected.
 
#* The message appears. From this point on, if you try to submit again, the data is sent as expected.
  
 +
===Import templates===
 +
* Import https://en.wikipedia.org/wiki/Template:Ref from Wikipedia so we can use <code><nowiki><ref>Reference goes here</ref></nowiki?</code>. This is perhaps the single most important Template to import.
 +
** To <code><nowiki><ref>...</ref></nowiki></code> should work provided <code><nowiki><references/></nowiki></code> is included on the page, since this is a part of a [[:mediawiki:Extension:Cite|Extension:Cite]] extension which needs to be installed.
 +
* 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
  
=== Import templates ===
+
====Templates to display "EST" or "EDT"====
<span id="Import-templates"></span>
+
* 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>"
<ul>
 
<li> Import https://en.wikipedia.org/wiki/Template:Ref from Wikipedia so we can use <code><nowiki><ref>Reference goes here</ref></nowiki?</code>.
 
This is perhaps the single most important Template to import.
 
To <code><nowiki><ref>...</ref></nowiki></code> should work provided <code><nowiki><references/></nowiki></code> is included on the page, since this is a part of a [[:mediawiki:Extension:Cite|Extension:Cite]] extension which needs to be installed.
 
<li> 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.
 
<li> Import https://en.wikipedia.org/wiki/Template:Mbox
 
 
 
 
 
=== Templates to display EST or EDT ===
 
{{Template:Permanent time observation in the United States}}
 
 
 
====Local time zone (solved)====
 
After many hours of reading documentation and per consensus with Adfeno, I just deleted and replaced our custom-made <nowiki>Template:TZAbbrev</nowiki> with local time zone parser functions (which we didn't know existed at the time) to <nowiki>Template:IRC text</nowiki>: --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 15:49, 17 December 2022 (EST)
 
* <nowiki>{{#timel:T}}</nowiki> -- To Eastern Standard Time (EST, which is UTC−05:00), or Eastern Daylight Time (EDT, which is UTC−04:00)
 
* <nowiki>{{#timel:e}}</nowiki>: IANA time zone identifier, "America/New_York"
 
 
 
=====Local time zone on outdated MediaWiki system=====
 
I'm curious how MediaWiki servers are affected by this.
 
 
 
The time zones are stored in MediaWiki, so it can be expected that the MediaWiki LTS version upgrade that is released after March 2023 will display the America/New_York correctly. Is this correct?
 
 
 
Trisquel is used to host the FSD as far as I know, and the current Trisquel MediaWiki LTS lags 1.5 years behind about up to two years at maximum from the latest LTS release.
 
 
 
If all of this is true, then I guess that I might take about 2 years before the America/New_York (Boston) time zone is updated in MediaWiki on the FSD.
 
 
 
 
 
: '''Short version:''' if we decide to use <code><nowiki>wgLocaltimezone</nowiki></code> or the <code><nowiki>timel</nowiki></code> parser function, then this may become an FSF staff task since, if the local copy of PHP is not made to use GNU's <code><nowiki>date</nowiki></code> timezone database, then the correct observation of time will depend on either the installation of a PHP extension that updates the database, or upgrading PHP such that the builtin <code><nowiki>timelib</nowiki></code> database has the desired change. The long version follows after this paragraph, showing what I have found so far.
 
:
 
: Downloading [https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/REL1_31 the <code><nowiki>REL1_31</nowiki></code> branch of MediaWiki core], which should correspond to our 1.31.16 as seen on [[Special:Version]], extracting it somewhere and looking for which files interact with $wgLocaltimezone (<code><nowiki>grep --exclude-dir='.git' -EiR 'wglocaltimezone'</nowiki></code>) gives me a hint to look at <code><nowiki>includes/Setup.php</nowiki></code> and it's use of a function called <code><nowiki>date_default_timezone_set</nowiki></code>.
 
:
 
: Since I couldn't find any such function definition in MediaWiki itself, I looked at PHP, first by downloading [https://www.php.net/releases/#7.0.33 version 7.0.33], which is similar to the one seen on [[Special:Version]], then by using grep in the same way as before, giving me a hint to look at <code><nowiki>ext/date/php_date.c</nowiki></code>.
 
:
 
: At one point, the <code><nowiki>ext/date/php_date.c</nowiki></code> file goes on to define both the setter and getter (<code><nowiki>date_default_timezone_get</nowiki></code>), the last of which is even more interesting, since it queries a "timezone database" (<code><nowiki>DATE_TIMEZONEDB</nowiki></code>) using <code><nowiki>get_timezone_info</nowiki></code>. The same file conditionally defines <code><nowiki>DATE_TIMEZONEDB</nowiki></code> to use either a global database or PHP's builtin (<code><nowiki>timelib_builtin_db</nowiki></code>, from <code><nowiki>ext/date/lib/parse_tz.c</nowiki></code>) which, all in all, is just a construct of <code><nowiki>timelib_timezone_db_data_builtin</nowiki></code> from <code><nowiki>ext/date/lib/timezonedb.h</nowiki></code>.
 
:
 
: Unfortunatelly, <code><nowiki>timelib_timezone_db_data_builtin</nowiki></code> is hardcoded. So the other side of the <code><nowiki>DATE_TIMEZONEDB</nowiki></code> definition seems to be more viable, which takes into account a supposed use of an external/global timezone database, which unfortunatelly leaves us with  [http://pecl.php.net/package/timezonedb <code><nowiki>timezonedb</nowiki></code> from third-party repositories such as PHP's PECL].
 
:
 
: Another alternative, although probably undoable as of today, is to make PHP use the same timezone information database as GNU's <code><nowiki>date</nowiki></code>, this would allow the system administrator to only have to deal with one update.
 
:
 
: Another workaround would be not to use <code><nowiki>wgLocaltimezone</nowiki></code>, or force MediaWiki to consider the local system time (in <code><nowiki>America/New_York</nowiki></code>) as +00:00 or any numeric offset that you so desire. But for this hack to work, we might need to test a way to prevent actual change of time (hour and minute) in MediaWiki.
 
 
 
: The last approach has the downside that, the displayed time may deceive most users, specially if a user logged in the FSD has set preference for another timezone, since when viewing the FSD, then it will be off by <code><nowiki>[real FSF offset]+[FSD offset]+[User preferences' offset]</nowiki></code>. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 15:23, 17 December 2022 (EST)
 
 
 
:: Upon further search, there are performance reasons, and probably legal motivations, as to why PHP doesn't use the system's timezone database, as can be seen from [https://stackoverflow.com/a/22786582 a discussion on Stack Overflow]. However, I don't know if all the reasons are still valid. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 16:00, 17 December 2022 (EST)
 
 
 
Can the hard coded files be updated manually?
 
* Can ext/date/php_date.c be updated with https://github.com/php/php-src/blob/master/ext/date/php_date.c
 
* and  ext/date/lib/timezonedb.h be updated with https://github.com/php/php-src/blob/master/ext/date/lib/timezonedb.h ?
 
--[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 16:01, 17 December 2022 (EST)
 
 
 
: It might work, but both of the newer versions of the mentioned files have too many differences from the originals, that can impact when rebuilding PHP. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 16:28, 17 December 2022 (EST)
 
 
 
:: Ignoring the timezone issue, the <code><nowiki>timezonedb.h</nowiki></code> file seems to be the one to cause less issues in regards to functionality of PHP. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 16:40, 17 December 2022 (EST)
 
 
 
=== GNU links License not in SPDX ===
 
<span id="GNU-links-License-not-in-SPDX"></span>
 
 
 
 
 
GNU website links to License namespace pages that are not identified according to SPDX.
 
I'm not saying that we should fix all of those, since SPDX might not have all licenses. Besides, I already took care to discard public domain.
 
This is visible at least on https://www.gnu.org/licenses/license-list.html, which links to the following pages --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 19:30, 18 December 2020 (EST)
 
<div style="overflow-y:scroll;height:100px;">
 
* [[License:AFLv3]]
 
* [[License:AGPLv1]]
 
* [[License:Apache1.0]]
 
* [[License:Apache1.1]]
 
* [[License:Apache2.0]]
 
* [[License:APSLv1.x]]
 
:: Tricky, since GNU website mentions it as a umbrella for all 1.x versions.
 
* [[License:APSLv2.0]]
 
* [[License:ArtisticLicense2.0]]
 
* [[License:Artistic_v1.0]]
 
* [[License:BitTorrentOSL1.1]]
 
* [[License:Boost1.0]]
 
* [[License:BSD_3Clause]]
 
* [[License:BSD_4Clause]]
 
* [[License:CC0]]
 
* [[License:CDDLv1.0]]
 
* [[License:CeCILL-B]]
 
* [[License:CeCILL-C]]
 
* [[License:CeCILLv2]]
 
* [[License:Clarified_Artistic_License_1.0]]
 
* [[License:ClearBSD]]
 
* [[License:CNRI]]
 
* [[License:Common_Public_Attribution_License_Version_1.0]]
 
* [[License:Commons-Clause]]
 
* [[License:CPLv1.0]]
 
* [[License:CryptixGL]]
 
* [[License:ECL2.0]]
 
* [[License:ECos2.0]]
 
* [[License:ECosPLv1.1]]
 
* [[License:EFLv2]]
 
* [[License:EPLv1.0]]
 
* [[License:EUDataGrid]]
 
* [[License:EUPLv1.1]]
 
* [[License:EUPLv1.2]]
 
* [[License:Expat]]
 
:: [[License:X11]] is <code>X11</code>, while Expat is <code>MIT</code>.
 
* [[License:fdk]]
 
* [[License:Free-Art-L-v1.3]]
 
* [[License:FreeType]]
 
* [[License:GPL-PA]]
 
* [[License:HESSLA]]
 
* [[License:Historical_Permission_Notice_and_Disclaimer]]
 
* [[License:IBMPLv1.0]]
 
* [[License:IllinoisNCSA]]
 
* [[License:IntelACPI]]
 
* [[License:IPA_Font_License]]
 
* [[License:JabberOSLv1.0]]
 
* [[License:JahiaCSL]]
 
* [[License:LaTeX_ecfonts]]
 
* [[License:Lha]]
 
* [[License:LPPLv1.2]]
 
* [[License:LPPLv1.3a]]
 
* [[License:LucentPLv1.02]]
 
* [[License:MPLv1.1]]
 
* [[License:MPLv2.0]]
 
* [[License:MsPL]]
 
* [[License:MsRL]]
 
* [[License:Ms-SS]]
 
* [[License:NASA-OSA_v1.3]]
 
* [[License:NokOSv1.0a]]
 
* [[License:NOSLv1.0]]
 
* [[License:Oculus_VR_Rift_SDK_License]]
 
* [[License:ODbl]]
 
* [[License:Old_ksh93]]
 
* [[License:Old-plan9]]
 
* [[License:OpenLDAPv2.3]]
 
* [[License:OpenLDAPv2.7]]
 
* [[License:OpenPLv1.0]]
 
* [[License:OSLv3.0]]
 
* [[License:Phorum2.0]]
 
* [[License:PHPv3.01]]
 
* [[License:PINE]]
 
* [[License:PPL]]
 
* [[License:PPL3a]]
 
* [[License:Python1.6b1]]
 
* [[License:QPLv1.0]]
 
* [[License:ReciprocalPLv1.3]]
 
* [[License:RPSLv1.0]]
 
* [[License:Scilab-old]]
 
* [[License:SCOSL-3.0]]
 
* [[License:Scratch]]
 
* [[License:SGIFreeBv2]]
 
* [[License:SimpleM]]
 
* [[License:SISSL-1.1]]
 
* [[License:SPLv1.0]]
 
* [[License:Squeak-old]]
 
* [[License:SSSCFR-1.1]]
 
* [[License:StandardMLofNJ]]
 
* [[License:SunCSLv2.8]]
 
* [[License:TheUnlicense]]
 
* [[License:TrueCrypt]]
 
* [[License:Unicode]]
 
* [[License:Universal_Permissive_License]]
 
* [[License:UnivUtahRFPL]]
 
* [[License:Vim7.2]]
 
* [[License:W3C_31Dec2002]]
 
* [[License:WebM]]
 
* [[License:WTFPL-2]]
 
* [[License:WxWindows_Library_Licence-3.1]]
 
* [[License:XFree86_1.1]]
 
* [[License:YaST-license]]
 
* [[License:YPLv1.1]]
 
* [[License:ZELv2.0]]
 
* [[License:ZPL-1.0]]
 
* [[License:ZPL-1.3]]
 
</div>
 
 
 
  
=== misc issues ===
+
=====Workaround=====
<span id="misc-issues"></span>
+
<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===
  
 
* Deletion options (eg https://directory.fsf.org/wiki?title=FOO&action=delete)
 
* Deletion options (eg https://directory.fsf.org/wiki?title=FOO&action=delete)
 
** Reason: "Duplicated entry"
 
** Reason: "Duplicated entry"
 
** A lot of entries has been submitted that don't run in GNU systems, something required by our policy. Add reason: "Doesn't run on GNU systems"
 
** A lot of entries has been submitted that don't run in GNU systems, something required by our policy. Add reason: "Doesn't run on GNU systems"
* Namespaces we need
+
* Namespaces
** Draft: Example, move https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures/Draft to https://directory.fsf.org/wiki/Draft:Free_Software_Directory:Antifeatures
 
 
** Portals: Wikipedia has Portals, for example https://en.wikipedia.org/wiki/Portal:Free_software and https://en.wikipedia.org/wiki/Portal:Java. Should we start [[Portal:IceCat]]?
 
** Portals: Wikipedia has Portals, for example https://en.wikipedia.org/wiki/Portal:Free_software and https://en.wikipedia.org/wiki/Portal:Java. Should we start [[Portal:IceCat]]?
 
* Create cron job to update CSV output page of GNU all projects
 
* Create cron job to update CSV output page of GNU all projects
 +
* Fix search links: <strike>Fix links (multimedia, etc) at top of search results.</strike>
 
* Footer: The link https://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.
 
* Footer: The link https://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.
 
* 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
 
* 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
Line 1,337: Line 467:
 
* 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)
 
* 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)
  
 
+
====wgAllowUserJs====
=== wgAllowUserJs ===
 
<span id="wgAllowUserJs"></span>
 
 
 
 
 
 
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]]).
 
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 the 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]].
 
:I cannot use the 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
 
: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
  
 
+
====Change unapproved revs to category====
=== Change unapproved revs to category ===
 
<span id="Change-unapproved-revs-to-category"></span>
 
 
 
 
 
 
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.
 
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)
 
: 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)
  
 
+
====Add a new name space: Group====
=== Add the new Group namespace ===
 
<span id="Add-the-new-Group-namespace"></span>
 
 
 
 
 
 
I suggest 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 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]].
 
* Move [[Free Software Directory:Participate/Project Team]] to [[Free Software Directory:Participate/Groups]].
  
: I consider this a '''wontfix''' since moving and making namespaces is expensive, the wiki administrators themselves must deal and better organize the structure they already have in meaningful ways, for example, avoid inserting a collection as a project team, since the goal of the collection page is to point to “curated” list of software for a specific purpose, not to give information of a said group that edits that page. --[[User:Adfeno|Adfeno]] ([[User talk:Adfeno|talk]]) 18:08, 18 December 2020 (EST)
+
====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"
 
 
=== W3M and text based browser are hard to use forms ===
 
<span id="W3M-and-text-based-browser-are-hard-to-use-forms"></span>
 
  
 +
====W3M / text based browser is hard to use forms====
  
 
report from mailing list:
 
report from mailing list:
Line 1,382: Line 497:
 
and was able to edit the form.
 
and was able to edit the form.
  
 +
===Suggestions===
  
=== Category Candidates for deletion ===
+
====date command====
<span id="Category-Candidates-for-deletion"></span>
+
Add: date --date='TZ="America/New_York" 12:00 this Fri'
 
+
* <strike>https://directory.fsf.org/wiki/Template:IRC_text</strike>
 
+
* <strike>The entries in https://www.fsf.org/blogs/directory/ -- updated by Ted</strike>
Donald pointed out that https://directory.fsf.org/wiki/Category:Candidates_for_deletion lists pages that don't include the Category:Candidates_for_deletion tag:
 
<pre>
 
Category/Business/pim
 
Category/Editor
 
Category/Localization
 
Category/Localization/language-adaptations
 
Category/Text-creation
 
Category/Use/organizing
 
Category/Works-with/pim
 
Category/Works-with/text
 
</pre>
 
 
 
 
 
=== Upgrade history ===
 
<span id="Upgrade-history"></span>
 
 
 
  
 +
====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)
 
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)
  
{{Template:BacklogIssue|id=Promote online services|text=
+
===Donald===
I've observed that currently one of the major issues in libre community is that end-users are unaware of libre alternatives to online services which forces the end-users to rely on Internet services where the common practice seems to be libre service providers doing self-promotions by upstream and it's users e.g. Example: <i><nowiki>https://github.com/PhoenicisOrg/phoenicis/pull/1917</nowiki></i>.
 
 
 
Common real-life example based on my experience would be end-user using Internet service like GitHub to host their code without being aware of services like gitea and it's providing networks which these users then migrate within a month after a discovery which was also how it happened in my case.
 
 
 
I believe that by promoting these services we can either solve this presented issue or contribute to it's solution. --[[User:Kreyren|Kreyren]] ([[User talk:Kreyren|talk]]) 21:05, 20 November 2020 (CET)
 
 
 
=== Logos ===
 
<span id="Logos"></span>
 
 
 
 
 
* Why don't we use .svg files over .png files?
 
 
 
 
 
=== namimg ===
 
<span id="namimg"></span>
 
 
 
 
 
* Naming policy. Shouldn't .png files generated from .svg files be named with the .svg.png to indicate that (example.svg.png)? This is what Wikipedia does: https://upload.wikimedia.org/wikipedia/en/thumb/2/22/Heckert_GNU_white.svg/150px-Heckert_GNU_white.svg.png
 
 
 
 
 
=== IceCatMeeting ===
 
<span id="IceCatMeeting"></span>
 
 
 
 
 
I'd like to have a IRC meetings with Ruben at least a few times per year. Suggested plan: 1 hour every 3rd month.
 
 
 
 
 
=== Backlog Admin Group -BAG- and FSF Tech Team ===
 
<span id="Backlog-Admin-Group--BAG--and-FSF-Tech-Team"></span>
 
 
 
 
 
I suggest a voice conference between the BAG and the FSF. Suggested plan: 1 hour every 3rd month.
 
 
 
 
 
=== Mozilla and FSD joint project ===
 
<span id="Mozilla-and-FSD-joint-project"></span>
 
 
 
 
 
Mozilla closes to many relevant issues:
 
 
 
* Apache License, version 2.0 is not on the add-on license list - https://github.com/mozilla/addons-server/issues/8545
 
* API: Please adopt SPDX - https://github.com/mozilla/addons-server/issues/8706
 
* Allow GNU [L]GPL x.x or later - https://github.com/mozilla/addons-server/issues/8707
 
* The API `name` parameter makes bad MediaWiki URL's - https://github.com/mozilla/addons-server/issues/8790
 
* Make a drop-down menu with all SPDX licenses - https://github.com/mozilla/addons-server/issues/8866
 
* Cannot list collections in desired formats - https://github.com/mozilla/addons/issues/722
 
* API: Add "last_license" to the search pages - https://github.com/mozilla/addons-server/issues/8945
 
 
 
Solution: I think the FSF should help the Project Team for IceCat WebExtension to have IRC meetings with Mozilla. Suggested plan: 1 hour every 3rd month.
 
 
 
 
 
=== Blog template ===
 
<span id="Blog-template"></span>
 
 
 
 
 
Disclaimer: This has been implemented since "No Friday Free Software Directory IRC meetup on Friday July 20th" in https://www.fsf.org/blogs/directory. Check a few more blogs to make sure it's well implemented.
 
 
 
<div style="overflow-y:scroll;height:200px;">
 
Sent to donald@fsf.org
 
 
 
<pre>
 
What do you think about this?: Move the paragraph with unique text to
 
the top of the body text and add the remaining text under a section
 
called "About the Free Software Directory". Example for
 
https://www.fsf.org/blogs/directory/friday-free-software-directory-irc-meetup-time-june-22nd-starting-at-12-00-p-m-edt-16-00-utc-1
 
 
 
##############################
 
 
 
Current version
 
 
 
Join the FSF and friends Friday, June 22nd, from 12:00 p.m. to 3 p.m.
 
EDT (16:00 to 19:00 UTC) to help improve the Free Software Directory
 
this week by helping to promote it.
 
 
 
Help improve the Free Software Directory by adding new entries and
 
updating existing ones. Every Friday we meet on IRC in the #fsf channel
 
on irc.freenode.org.
 
 
 
Tens of thousands of people visit directory.fsf.org each month to
 
discover free software. Each entry in the Directory contains a wealth of
 
useful information, from basic category and descriptions, to providing
 
detailed info about version control, IRC channels, documentation, and
 
licensing info that has been carefully checked by FSF staff and trained
 
volunteers.
 
 
 
When a user comes to the Directory, they know that everything in it is
 
free software, has only free dependencies, and runs on a free OS. With
 
over 16,000 entries, it is a massive repository of information about
 
free software.
 
 
 
While the Directory has been and continues to be a great resource to the
 
world for many years now, it has the potential to be a resource of even
 
greater value. But it needs your help! And since it's a MediaWiki
 
instance, it's easy for anyone to edit and contribute to the Directory.
 
 
 
A few weeks back we launched a new Project Team to create a logo that
 
packages can use to show off that they are included in the Directory.
 
But at this time, we still haven't found a team captain for the project.
 
This project could really help promote the Directory, as well as helping
 
packages to demonstrate that they care about software freedom. This
 
week, we'll be working to recruit a team captain, as well as trying to
 
get the project off the ground.
 
 
 
If you are eager to help, and you can't wait or are simply unable to
 
make it onto IRC on Friday, our participation guide will provide you
 
with all the information you need to get started on helping the
 
Directory today! There are also weekly Directory Meeting pages that
 
everyone is welcome to contribute to before, during, and after each
 
meeting. 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'
 
 
 
 
 
##############################
 
 
 
Proposed template.
 
 
 
Join the FSF and friends Friday, June 22nd, from 12:00 p.m. to 3 p.m.
 
EDT (16:00 to 19:00 UTC) to help improve the Free Software Directory
 
this week by helping to promote it.
 
 
 
A few weeks back we launched a new Project Team to create a logo that
 
packages can use to show off that they are included in the Directory.
 
But at this time, we still haven't found a team captain for the project.
 
This project could really help promote the Directory, as well as helping
 
packages to demonstrate that they care about software freedom. This
 
week, we'll be working to recruit a team captain, as well as trying to
 
get the project off the ground.
 
 
 
[About the Free Software Directory]
 
 
 
Help improve the Free Software Directory by adding new entries and
 
updating existing ones. Every Friday we meet on IRC in the #fsf channel
 
on irc.freenode.org.
 
 
 
Tens of thousands of people visit directory.fsf.org each month to
 
discover free software. Each entry in the Directory contains a wealth of
 
useful information, from basic category and descriptions, to providing
 
detailed info about version control, IRC channels, documentation, and
 
licensing info that has been carefully checked by FSF staff and trained
 
volunteers.
 
 
 
When a user comes to the Directory, they know that everything in it is
 
free software, has only free dependencies, and runs on a free OS. With
 
over 16,000 entries, it is a massive repository of information about
 
free software.
 
 
 
While the Directory has been and continues to be a great resource to the
 
world for many years now, it has the potential to be a resource of even
 
greater value. But it needs your help! And since it's a MediaWiki
 
instance, it's easy for anyone to edit and contribute to the Directory.
 
 
 
If you are eager to help, and you can't wait or are simply unable to
 
make it onto IRC on Friday, our participation guide will provide you
 
with all the information you need to get started on helping the
 
Directory today! There are also weekly Directory Meeting pages that
 
everyone is welcome to contribute to before, during, and after each
 
meeting. 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>
 
</div>
 
 
 
 
 
=== GPL ===
 
<span id="GPL"></span>
 
 
 
 
 
https://github.com/mozilla/addons-server/issues/8707 -- Mozilla (and perhaps most other developers) don't avoid the term "GNU General Public License, version 2.0" (or "GNU General Public License, version 3.0") as Ian pointed out later in that issue (https://github.com/mozilla/addons-server/issues/8707#issuecomment-401471396). Is the plan to split the license into two different licenses to avoid this issue completely: "GNU General Public License, version 4.0 only", "GNU General Public License, version 4.0 or later"?
 
 
 
Donald: "only" and "or later" are handled in license notices
 
 
 
 
 
=== New Antifeature ===
 
<span id="New-Antifeature"></span>
 
 
 
  
 +
====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
 
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
  
Line 1,592: Line 520:
 
please read about the program and tell me which section that match best.
 
please read about the program and tell me which section that match best.
  
 +
=== Listing of all namespaces ===
  
=== CASAuth ===
+
find a way to list all pages in all namespaces
<span id="CASAuth"></span>
 
 
 
 
 
* [https://github.com/CWRUChielLab/CASAuth/issues/8#issuecomment-399434050 Maintanance] -- CASAuth is not maintained any more and FSF are welcome to take over the project
 
* [https://github.com/CWRUChielLab/CASAuth/issues/7 Feature request: MediaWiki API integration]
 
** [[Free Software Directory:Pywikibot|Pywikibot]]
 
 
 
 
 
=== reventry ===
 
<span id="reventry"></span>
 
  
 +
==Workaround in software used by the Directory==
 +
The issues here are note issues in the Directory but in programs used by the project.
  
Revision entry on plain oldiff page displays "$7":
+
===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‎").
 
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‎").
  
Line 1,624: Line 545:
 
*'''Workaround:''' Edit [[MediaWiki:Revision-info]] and remove $7 by hand. This message has to be deleted when this bug is fixed.
 
*'''Workaround:''' Edit [[MediaWiki:Revision-info]] and remove $7 by hand. This message has to be deleted when this bug is fixed.
  
 
+
==Programs that are incompatible with directory.fsf.org==
=== Client-side ===
 
<span id="Client-side"></span>
 
 
 
 
 
 
The programs listed here has bugs that affect compatibility when you browse this website:
 
The programs listed here has bugs that affect compatibility when you browse this website:
  
Line 1,640: Line 557:
 
*** 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
 
*** 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.
 
** Solution: Use another text-based web browser.
 
 
=== JavaScript errors ===
 
<span id="JavaScript-errors"></span>
 
 
 
<code>InvalidAccessError: A parameter or an operation is not supported by the underlying object  ext.headertabs.core.js:41</code>
 
<code>TypeError: ss.rules is undefined[Learn More]  wiki:477:35</code><br>
 
''might be mediawiki issue''<br>
 
<code>TypeError: pf.select2.base is not a constructor[Learn More]  ext.pf.select2.combobox.js:35:23</code><br>
 
<code>TypeError: pf.select2.base is not a constructor[Learn More]  ext.pf.select2.tokens.js:36:21</code><br>
 
<code>initFunction is not a function $.fn.PageForms_registerInputInit</code>
 
<pre>
 
jQuery.Deferred exception: initFunction is not a function $.fn.PageForms_registerInputInit/<@https://directory.fsf.org/w/extensions/PageForms/libs/PageForms.js?0b6cb:330:17
 
resolve/</mightThrow@https://directory.fsf.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0hndq7l:3583:21
 
resolve/</process<@https://directory.fsf.org/w/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=0hndq7l:3651:12
 
</pre>
 
 
URL: https://directory.fsf.org/wiki?title=Sandbox&action=formedit&debug=true#tab=3__Licenses
 
 
Related to date picker initialization in <code>input_23</code>
 
 
 
=== Server-side issues for Outreachy ===
 
<span id="Server-side-issues-for-Outreachy"></span>
 
 
 
These are some of the tasks that will be worked on by Outreachy interns during summer 2018
 
 
* Improve responsiveness for mobile devices
 
* Sync Debian package info into the directory
 
 
 
=== HTML Logos ===
 
<span id="HTML-Logos"></span>
 
 
 
Donald suggested logos in different sizes with HTML caption "Listed in the Free Software Directory". "something that packages could put on their website to show that they are free software and included in the directory". See these logos for example:
 
* https://www.gnu.org/graphics/license-logos.html -- for inspiration of logos in different sizes. It would be good if the image had the same sizes as these logos since some developers use them and can put the new logo next to them on their website.
 
* https://commons.wikimedia.org/wiki/File:FSF-Logo_part.svg
 
* https://static.fsf.org/nosvn/ryf/RYF-with-fill.svg, https://static.fsf.org/nosvn/ryf/RYF-with-fill.png
 
 
"The Free Software Directory (FSD, or simply Directory) is a project of..." - https://directory.fsf.org/wiki/Main_Page
 
 
Proposed text on the logo
 
* "Free Software Directory"
 
* "Directory"
 
* "FSD" -- But FSD can also mean "Free Software Definition", a term used at https://www.gnu.org/philosophy/free-sw.en.html
 
** I added "FSD" - https://directory.fsf.org/wiki?title=Template:About_text&diff=37857&oldid=37762 -- should I remove it? --[[User:David Hedlund|David Hedlund]] ([[User talk:David Hedlund|talk]]) 07:00, 9 July 2018 (EDT)
 
 
 
=== Upload form not working ===
 
<span id="Upload-form-not-working"></span>
 
 
 
The form for uploading screenshots to be displayed in the form does not work. As a user I receive [https://i.postimg.cc/GtVgKdfY/Screenshot-2018-11-23-Edit-Entry-Kanban-Free-Software-Director.png this error] and I cannot upload new screenshots. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 13:00, 23 November 2018 (EST)
 
 
 
=== Wikilinks in Software Prerequisites not working ===
 
<span id="Wikilinks-in-Software-Prerequisites-not-working"></span>
 
 
 
The insertion of links in some parts of the template does not work, for example:
 
<nowiki>{{Software prerequisite
 
|Prerequisite kind=Required to use
 
|Prerequisite description=[[Termenu]]
 
}}</nowiki>
 
The link <nowiki>[[Termenu]]</nowiki> will be filtered and transformed to simple text.
 
The consequence is that it is not possible to link the prerequisites to other pages of the FSD. Being able to do it would give us enormous advantages as the pages would be better indexed by search engines and users could find new useful software starting from the dependencies of those already visited. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 12:58, 14 December 2018 (EST)
 
 
 
=== Obsolete categories ===
 
<span id="Obsolete-categories"></span>
 
 
 
During the latest FSF IRC meeting, <span title="adfeno and craigt" style="cursor:help;text-decoration:overline;">users and administrators</span> reported that the categories listed in [[Free_Software_Directory:Workflow#Bugs_and_suggestions]] appear to be unused.
 
Mr. Hedlund is currently maintaining the new service page [[Free_Software_Directory:Buggy_entries]] and users have easy access to the #fsf IRC channel by using web chats.<br>
 
<em>Question</em>: should we maintain these old categories or should we transit completely to these new methods? --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 15:30, 25 January 2019 (EST)
 
 
 
=== pending entries ===
 
<span id="pending-entries"></span>
 
 
 
On 6 Dec 2020, [[User:LorenzoAncora|Lorenzo]] pointed out an issue that unapproved and pending entries for the FSD could be construed as free software when they may or may not be free. [[Cyberduck_CLI]] was used as the example. After some discussion, key elements of the solution were obvious.
 
# <del>Any pending entry is CLEARLY marked (I say absurdly marked), that it is currently under review for inclusion in the FSD and we have not concluded that it is fully free software. If there is a way to change the color of a pending entry, that would be cool.</del> <span style="color: green">Done.</span>
 
# Control how and when nonfree entries show up in the FSD search and other web search engines. I think the default is to exclude as much as possible, but there may be unexplored advantages to include them in various search results. One undesired example being that if a user just searches for something, sees the search results include it as being on the free software Directory, they might assume the work is free without visiting the page.<br>One example: https://directory.fsf.org/wiki?title=Cyberduck_CLI&oldid=82006, we could maybe mitigate old unapproved revisions with something like User-agent: * Disallow: /wiki*oldid=*$<br>I do not know of a way to completely automatically add unapproved entries to the robots file (and remove them once approved). There might be a way to completely do this using the API, some programming, and cron jobs. The robots approach also assumes that the scraper is following the restrictions in robots file which we know from logs and sysadmin emergencies is not always the case.<br>We should consider adding `<nowiki>__NOINDEX__</nowiki>` to the unapproved message text.<br>I think I most of these search engine issues moving forward by making a robots.txt file (we did not have one) and taking a snippet from wikipedia and the mediawiki doc. https://directory.fsf.org/robots.txt, https://en.wikipedia.org/robots.txt, https://www.mediawiki.org, wiki/Manual:Robots.txt
 
# Pending entries should have an educational component that allows visitors to learn more about the status of the entry. Talk: pages should work for this.
 
# Reviewing an entry is optimally done in private, similar to our compliance guidelines. However, for this to be useful, we have to list nonfree programs so staff and volunteers don't repeatedly review the same program over and over again. The presentation of pending entries should not reflect badly on a program, but this may be tricky to do. suggestions? --[[User:Craigt|Craigt]] ([[User talk:Craigt|talk]]) 15:30, 18 December 2020 (EST)
 
 
:: The bold mark on pages without approved revisions was a direct request by RMS, motivated by practical reasons. I think we can improve its appearance by reducing its size and using gray in place of black, but changing the color scheme of the unapproved revisions might compromise accessibility; the robots.txt solution won't work, because the Robots Exclusion Standard doesn't support regular expressions and globbing: <code><nowiki>__NOINDEX__</nowiki></code> should be the most appropriate solution; software Talk pages are already used to start the revision processes and to add administrative notifications, but I could attach an extra documentation link to unapproved entries, using JavaScript; I think it is sufficient that the warning shown on unapproved pages maintains a ''purely technical'' connotation. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]])
 
::: It was recomended by [[User:adfeno|adfeno]] to make use of the [[Template:AttentionBox]] to increase visibility of an entry's status. --[[User:Craigt|Craigt]] ([[User talk:Craigt|talk]]) 13:32, 24 December 2020 (EST)
 
:::: I don't think this is a good solution, for two reasons: the use of templates does not natively integrate with JavaScript or CSS and therefore would require manual changes to the code of the extension included in the instance, changes that would be difficult to maintain in the long term (also, using XHRs to download the template would degrade the loading performance); a big message saying "Warning!" violates the prerequisite of this Issue (<q>The presentation of pending entries should not reflect badly on a program</q>). I suggest to add a message like <q>This page revision is not approved and may not represent free software. Please browse the <u>latest revision</u>.</q> at the bottom of all old page revisions. I've produced a [https://i.postimg.cc/wMg59TvX/preview.png preview]. My mantra is: let's preserve the existing UX as much as possible, adding changes gradually and unobtrusively. ;-) --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 07:06, 26 December 2020 (EST)
 
::: It was suggested by ggoes, "I think "is free software" would be clearer than "represents free software" Represents makes me think of some kind of spokesman thing. --[[User:Craigt|Craigt]] ([[User talk:Craigt|talk]]) 13:32, 24 December 2020 (EST)
 
:::: Ok, the message can be edited without any problems, but we must all agree in order to minimize changes over time. The main problem is that ''all'' pages are subject to review and approval, so saying <q>is free software</q> might not be always correct in each context. I think that if the current message is too formal, we can replace ''represents'' with ''contains'' or ''links to'' and its truthfulness wouldn't be reduced. Additionally, we might even think about centring the message on the page if it's not yet prominent enough. I've produced a [https://i.postimg.cc/VkWWHtkY/preview2.png preview] of both changes. 🎅 --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 07:06, 26 December 2020 (EST)
 
::::: What about reversing this statement, using an alternative expression of the same fact? '''"We do not yet know if this page links to proprietary software!"''' I think that is very clear and is explicit in what it is warning of. --[[User:Freefish|Freefish]] ([[User talk:Freefish|talk]]) 13:00, 25th of January 2021 (GMT)
 
:::::: Hi [[User:Freefish|Freefish]], TY for the suggestion, however I think it's too specific to catch all our use cases (the Directory rejects all non-free software, not only proprietary applications) and it does not represent the same fact (the opposite of free is non-free). If the ''administration'' really feels the need to change the phrase, we could use '''"This page is a submission in progress.\nWe do not yet know if this page exclusively refers or links to free software."'''. Such a comprehensive statement should please and protect everyone. [[User:Craigt|Craig]], do you think this new phrasing is adequate? --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 06:11, 29 January 2021 (EST)
 
::::::: I support the more comprehensive statement. However, I think we can provide even more detail. It should direct readers to the Discussion page for more information and include an explanation as to why we are taking this approach with in-progress entries. [[User:Craigt|Craigt]] ([[User talk:Craigt|talk]]) 13:38, 12 February 2021 (EST)
 
:::::::: Good. The new message is online since the last meeting and no issue was reported. If there are no complaints, this Issue will be archived during the next meeting. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 04:35, 17 February 2021 (EST)
 
::::: Regarding the presentation of this message, given that nearly all other visual elements in the Directory are left-aligned, centering the warning will not necessarily make it more prominent. In general, when adding emphasis to an inline element it is usually best to use HTML's <code><nowiki><em></nowiki></code> tag and let the user's browser choose how to display this emphasis. This is because it results in better accessibility and compatibility than with custom styling. --[[User:Freefish|Freefish]] ([[User talk:Freefish|talk]]) 13:00, 25th of January 2021 (GMT)
 
:::::: <code>EM</code> tags are forbidden/ignored in CSS <code>content</code>; also, inline elements cannot influence the absolute alignment of a widget and there is no actual evidence of an enhancement from an accessibility PoV. --[[User:LorenzoAncora|LorenzoAncora]] ([[User talk:LorenzoAncora|talk]]) 06:11, 29 January 2021 (EST)
 
 
 
=== multiple_rejections ===
 
<span id="multiple_rejections"></span>
 
 
 
[[User:Craigt|Craigt]] mentioned recently on IRC that there were some entries that have been submitted and rejected multiple times, due to there being no record of previously rejected entries. I would suggest adding a new category, 'Rejected entries', that would include proprietary packages. Each page therein would include not a description of the package, but rather a description listing the licensing problem(s) that the package has, as well as whether that list is conclusive or not (so that it can be seen if, after one issue has been fixed, the package is a candidate for re-submission). A message would be added to the new entry form politely asking users to check this category to see if their entry has been rejected in the past. Finally, all pages in this category would be invisible to non-registered users to help avoid any misunderstanding that these packages are free. [[User:Freefish|Freefish]] ([[User talk:Freefish|talk]]) 12:24, 25th of January 2021 (GMT)
 
 
:: I added a robots file a few weeks ago that should not index revision pages.  I second adding `[https://www.mediawiki.org/wiki/Manual:Noindex <nowiki>__NOINDEX__</nowiki>]` to the template. [[User:Mmcmahon|Mmcmahon]] ([[User talk:Mmcmahon|talk]]) 11:15, 25 January 2021 (EST)
 
 
 
=== category_page_broaden_links ===
 
<span id="category_page_broaden_links"></span>
 
 
 
I fixed a bug related to a hard coded value on [[Template:Breadcrumbs|the breadcumbs template]], but now there is the remaining issue that pages like [[Category/Business]] link to themselves, rather than to the [[Main Page]]. It might make sense to check where that template is used, and maybe hard-code links to the main page, rather than using a query. If it's used in many places, we could make templates for different cases. [[Template:Subcategory-page|This template]] has similar code, which may be useful when working on the breadcrumbs template page. -- [[User:Sudoman|Sudoman]] ([[User talk:Sudoman|talk]]) 15:16, 10 February 2021 (EST)
 
 
::I changed the template call in category pages to just contain the breadcrumbs for the main page. That seems easiest, and to do what we want. this issue can be closed now. -- [[User:Sudoman|Sudoman]] ([[User talk:Sudoman|talk]]) 15:16, 10 February 2021 (EST)
 
 
 
=== expose the ethical rating of repository references ===
 
<span id="expose-the-ethical-rating-of-repository-references"></span>
 
 
 
New Feature Proposal
 
 
The FSF evaluates the ethical attributes of some repository services here:
 
 
https://www.gnu.org/software/repo-criteria-evaluation.html
 
 
The FSF Directory is littered with hyperlinks to MS Github and gitlab.com.  Users can conveniently click on those links and effectively be sent by FSF into a walled garden that FSF gives a low rating to.  This is the problem:
 
 
* Visitors are sent to Github and gitlab.com using their browser.  Those pages force execution of non-free javascript.  The common way to access projects with free software is to use git (e.g. "git clone").  On Feb.12, 2021 this was briefly discussed at the Directory meeting in #fsf.  It was argued that the links to respositories that push non-free javascript should be inactive links to discourage execution of non-free js whilst making it easier to copy/paste links for use with "git clone", as attempts to copy a hyperlink often inadvertently triggers the link.
 
 
* Visitors and those working on free software projects are not informed as to the ethical aspects of the repository.  This is a missed opportunity.  It would be useful to take this opportunity to inform the public about the repo evaluation.
 
 
* (perhaps unrelated) gitlab.com currently has an incorrect rating of "C".  The evaluation is not about the repo software, but rather the service.  While the Gitlab Community Edition is free software, the enterprise edition that the gitlab.com service uses pushes non-free javascript (including but not limited to CloudFlare's hCAPTCHA).  The rating links to "gitlab.com", which therefore must be downgraded from "C" to "F".
 
 
Note that none of the above reflects any agreements or decisions.  No decisions were made at the meeting on Feb.12, 2021.  There was merely attention on the issue.  Particulars about how to solve the above mentioned matters probably still need discussion. --[[User:Cypherpunks|Cypherpunks]] ([[User talk:Cypherpunks|talk]]) 15:20, 12 February 2021 (EST)
 
 
 
=== filter-search-by-os ===
 
<span id="filter-search-by-os"></span>
 
 
 
There is a feature request for limited search by OS.  This functionality would be nontrivial to implement as the dataset is implete and would require hacking on mediawiki's search functions. [[User:Mmcmahon|Mmcmahon]] ([[User talk:Mmcmahon|talk]]) 11:04, 24 June 2021 (EDT)
 
 
 
=== Instructions for archiving defunct or abandonded programs ===
 
* Need to draft up instructions for archiving defunct programs and add them to the https://directory.fsf.org/wiki/Free_Software_Directory:Participate page.
 
* Should include:
 
  * link to latest available source code from archive.org or softwareheritage.org (fsf needs to clarify)
 
  * provide a short message about the status
 
 
=== Need to sort out how programming languages are included in the FSD ===
 
* For languages listed on https://directory.fsf.org/wiki/Category/Programming-language some have entries some don't.
 
* Need to document and provide criteria for how new programming languages are added.
 
* Need to decide if and how we want to include languages in the FSD for reference.
 
 
== Example project team ==
 
 
 
=== New issue title ===
 
 
 
<span id="old-identity-of-this-issue"></span>
 
 
<span id="white space issue"></span>
 
Wikitext
 
 
 
=== Other issue, without old identity ===
 
 
 
Wikitext.
 
 
=== High Priority Project page needs to be updated to current campaign's HPP list ===
 
 
Campaign's High Priority list https://www.fsf.org/campaigns/priority-projects needs to be supported by and correspond with https://directory.fsf.org/wiki/Category:High_Priority_Projects. The HPP collection page https://directory.fsf.org/wiki/Collection:High_Priority_Projects needs to be grouped by the items listed on the campaigns page, so the items can link and provide a list of programs designated to support the campaign's HPP list.
 

Revision as of 10:47, 16 May 2018

Info

Please report confidential issues to bug-directory@gnu.org.

General

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

Fixed

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

Import

GNU packages

Make a script to generate XML files that syncs GNU with https://www.gnu.org/software/ which also list decommissioned GNU packages, a property that also should be imported, see https://directory.fsf.org/wiki/Property:Decommissioned/Obsolete

See https://directory.fsf.org/wiki/User_talk:Bendikker/cleanlinksgnusoftware for other examples.

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.

Screenshots

https://screenshots.debian.net/

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=https://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=https://forums.informaction.com/viewforum.php?f=3
}}
{{Software category
|Internet-application=privacy
|Use=internet-application, security
}}
{{Featured}}

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?

Consistent CSS styling

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

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

Backlog Admin Group tasks

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

Semantic Forms

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

Add

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

Modify
  • The "irc:" is displayed twice like this: irc://irc:is broken, see Template:Print entry. And if you remove irc://, it prepends http://. Form edit requires irc:: "must have the correct URL format, starting with "http""
  • 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.

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

License verification

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

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

Point system and mentoring

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

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

FSF staff tasks

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

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

A dedicated bug tracker for the Directory

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

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

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

Internationalization and localization

https://en.wikipedia.org/wiki/Free_Software_Directory is available in these languages at this writing:

Languages:
Español
Français
Italiano
Nederlands
日本語
Русский
中文

We need to enable internationalization and localization in our MediaWiki instance so volunteers easily can add new translated pages. For example Collection:IOS (4 languages) and Collection:Windows (3 languages) need the translation links in the sidebar.

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

Performance tuning

A lot of contributors have complained that the FSD has been slow in the past years. The most damaging aspect with this is that we are loosing contributors. It must with other words be fixed if we want more contributors -- something that has been suggested as being one of the most important thing with the project at all.

  • Ask FSF admins to provide an exact copy of the environment (database + software) so that can be reproduced locally and properly troubleshoot.
  • Switching to PHP 7 might help a bit but I think we have a problem with writing data to Semantic MediaWiki, this might me an issue with forms.
  • Install memcached, or find some other way to improve performance of the site. We already have Zend OPcache, for opcache, and APCu, for data store, installed and enabled. Memcached is like APCu, but slower.
Session data

It may take a minute to move a page. Also, 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.

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

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 the 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

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)

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"

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 https://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.

Suggestions

date command

Add: date --date='TZ="America/New_York" 12:00 this Fri'

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

Workaround in software used by the Directory

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

Revision entry on plain oldiff page displays "$7"

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

This applies to the

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

It doesn't affect:

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

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

Programs that are incompatible with 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.