Active Backlog
See our infrastructure plan.
Please report confidential or urgent issues to bug-directory@gnu.org.
ⅉ It is a good idea to read the manual of Template:BacklogIssue before editing the page. ⅉ
Append the new bugs you find in the FSD to this page.
Remember to follow the participation guide and sign your contribution. Thank you!
The bugs are archived after at least one week from their resolution or if the bug cannot be identified due to lack of information.
Uncategorized
'''Selection from the [https://shop.fsf.org/ FSF shop]''' [https://shop.fsf.org/books/free-freedom-20-richard-stallman Free as in Freedom 2.0, by Richard Stallman] [https://shop.fsf.org/books-docs/introduction-command-line Introduction to the Command Line] ---- ---- '''[https://www.gnu.org/help/help.html Helping the GNU Project and the Free Software Movement]''' ---- ---- If you have corrections to this entry or questions about it, please contact: mailto:maintainers@gnu.org ----
I think we should:
Remove the above text from all entries listed in GNUPlace the above text in a template, say Template:GNU_promotions- 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
runjobs.php
when appropriate to apply the substitutions and allow for further development of this Backlog Task). --LorenzoAncora (talk) 14:07, 4 December 2020 (EST) - 2. Is now solved (see Template:GNU_promotions). --LorenzoAncora (talk) 13:08, 4 December 2020 (EST)
- 3. Stalled by pt. 1.
- Is there a way for us to HTTP ping those without using JavaScript?
I think we'll need to add a dedicated script. --LorenzoAncora (talk) 15:26, 24 April 2020 (EDT)
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 4471 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.
Original text: |License=GPLv3orlater Replacement text: |License=GPL-3.0-or-later Search in namespaces:Main Replace only in category: EntryDo not use regex like this, it will add "^
- David, clarification is required. Please specify the position of the site dumps. --LorenzoAncora (talk) 13:11, 14 June 2019 (EDT)
- 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 Directory) and irc://webchat.fsf.org/libreplanet (for Libre Planet). However, the listed 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, Free web-based IRC client replacement for Mibbit needed. --David Hedlund (talk) 02:22, 31 March 2018 (EDT)
- On second thought we should use a dedicated module, so we can enlist the translations on the left user bar. --LorenzoAncora (talk) 15:01, 15 May 2020 (EDT)
I find that most of my problems concerning empty or missing properties in a template are helped by setting default template values. You might need to poke runJobs.php. Then you can query on the default value. So you might have Template:Software looking like:
Software license: None
Then you can pick out the pages with undeclared software license by ask'ing on None to get the ones that aren't declared.
- (20:43:02) David_Hedlund: But it's still a unofficial release. I think we should discuss this policy.
Import
It's not possible to download the archive right now.
" 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
- Debian Med
- GetDeb, and it's sister project Playdeb
- https://directory.fsf.org/wiki/Special:Export/IceCat/NoScript (view-source)
- https://addons.mozilla.org/api/v3/addons/addon/noscript/ (view-source)
It's time to export the old add-on list https://directory.fsf.org/wiki/Free_Software_Directory:IceCat_extensions_(proposed)/ from the FSD, then import the new list with 600̈́+ add-ons, then merge the extra field from the backup to it.
{{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}}
style=""
clauses scattered in them. One of such clauses was responsible for too narrow columns in the description. I'd suggest to:
- Check all local style clauses in our custom code
- Determine if they can be more generic. For example, colors, paddings, line widths should be unified to achieve visual consistency.
- A set of CSS classes should be designed to replace
style
clauses - CSS class naming scheme should be decided
- New CSS classes should be introduced to MediaWiki:Common.css
style
clauses should be replaced with theirclass="css-class"
counterparts.
Backlog Admin Group
- 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. --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? --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
"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 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 or 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
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. --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. --LorenzoAncora (talk) 13:58, 14 February 2020 (EST)
- The issue was solved, so we can archive this Active Backlog Task. --LorenzoAncora (talk) 15:01, 15 May 2020 (EDT)
<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>
- 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.
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. --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
- Move "Dev languages" to Categories ("Programming-language").
- 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.
- Make "User level" a dropdown, since only one can be selected.
- 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.
- While "Checksum" suggests to paste the result of
sum
command, Property:Checksum is URL, and many packages use it to point to actual files where the result ofsha256sum
,sha512sum
ormd5sum
are stored, and none of these are related tosum
command. - 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.
- I do not agree with pt. 1 to 4 but I agree with pt. 5 and 6, at the following conditions:
sum
should be replaced withSHA or MD5
and "Test Entry" should be smaller and placed in the top-right angle of the form and not keyboard selectable. --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
- This does not seem the best solution, how about adding a clarification near the copyright widget? --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
Also, change "Resource kind" so that:
- "Mailing List Subscribe" and "Mailing List Info/Archive" are merged with "Mailing List".
- Remove "VCS Repository Webview".
- 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")
- Rename "Download" to "Object code download" or "Non-source download" or "Binary download".
- 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. --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
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
- 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
- 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
- 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
- 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. --LorenzoAncora (talk) 08:29, 5 May 2020 (EDT)
- 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.
- 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
#ask
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
- 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.
- 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
General info:Decommissioned/ObsoleteGeneral info: ChecksumOpenPGP signature URLOpenPGP public keyResource info -> Resource kind: TelephonyResource info -> Resource kind: VideotelephonyResource info -> Resource kind: E-mail: OpenPGP public key- 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.
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.
Having such systems and workflows in place is fundamental. If necessary, I am also willing to mentor during meetings. --LorenzoAncora (talk) 14:45, 31 January 2020 (EST)
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.
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Русский
- 中文
- This issue is blocking the 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. --LorenzoAncora (talk) 04:17, 17 February 2021 (EST)
- 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
jobs
value from the API call: https://directory.fsf.org/w/api.php?action=query&meta=siteinfo&siprop=statistics- On dev there is an alias
alias wikijobs='curl -s '\''https://directory2p.fsf.org/w/api.php?action=query&meta=siteinfo&siprop=statistics&format=json'\'' | jq -r .query.statistics.jobs'
Full rebuild of Semantic Mediawiki data took over 14 hours, after that there were 0 jobs in the queue
437206 IDs refreshed. Memory used: 180260544 (b: 13003608, a: 193264152) with a runtime of 53171.62 sec (886.19 min)
- For the first case (existing entries with License field blank when edited with form), these entries do still have their old property value. This is due to the fact that such entries weren't updated after Update-the-license-field was solved. However, when viewing such entries, the information is displayed as expected. With this in mind, one can keep both an editing and a viewing tab open to ease the process of recollecting the old license to match the new one. Finally, provided no other change to page listing on License namespace is made, future revisions of an existing entry and also new entries should display the information fine both on the form and on the view page. --Adfeno (talk) 17:54, 18 December 2020 (EST)
- (analysis) This issue occurs when multiple items in one software category are selected in the form. The property value seems to contain space-separated values. But {{Print software category}} seems to use
#arraymap
with a separator,
to split values. - Using a space to separate multiple values in set/subobject from SMW website cmay or may not be helpful
- Log
- Attempt to force valuesep to comma so that software categories are displayed correctly: https://directory.fsf.org/wiki?title=Template:Show&oldid=48988 --Adfeno (talk) 21:47, 27 January 2018 (EST)
- This seems to solve the issue, I visited IceCat. Mingw-w64 and GCC, and all seems to be working well. This is of course an ugly workaround, because I have choosen not to do a mass replace of the already existing categories separated by commas (because I think it would be resource expensive). Imagine, using Special:RepplaceText, in almost 10,000 pages. I prefer to leave this mass replace to the real admins, if they feel confident enough so as to remove my valuesep setting. --Adfeno (talk) 21:47, 27 January 2018 (EST)
- This workaround is needed because since SMW 2.5.3, in the
template
result format, the default forvaluesep
is changed from space to comma, however we are using SMW 2.5.1, so the default us is currently space. The mass replace is not required if we manage to upgrade to 2.5.3. --Adfeno (talk) 08:24, 28 January 2018 (EST)
- This workaround is needed because since SMW 2.5.3, in the
- This seems to solve the issue, I visited IceCat. Mingw-w64 and GCC, and all seems to be working well. This is of course an ugly workaround, because I have choosen not to do a mass replace of the already existing categories separated by commas (because I think it would be resource expensive). Imagine, using Special:RepplaceText, in almost 10,000 pages. I prefer to leave this mass replace to the real admins, if they feel confident enough so as to remove my valuesep setting. --Adfeno (talk) 21:47, 27 January 2018 (EST)
- It didn't help to edit {{Print_software_category}} and replace comma with   in {{#if:{{{15|}}}|{{#arraymap:{{{15}}}|,|xvarx|<li>[[Category/Interface/xvarx{{!}}Interface:xvarx]]</li>|}}|<nowiki/>}}, see https://directory.fsf.org/wiki?title=Template:Print_software_category&diff=48880&oldid=48746
- Some entries has duplications of "Extension or Plugin". For example, https://directory.fsf.org/wiki/Adblock_Plus has 3 Iridium entries listed.
- This was asked to sysadmin@fsf.org over one year ago:
The 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.
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.
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. --Adfeno (talk) 17:59, 18 December 2020 (EST)
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, suggested solution: Special:GetData: Display a message by default - https://phabricator.wikimedia.org/T201660
- 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.
- 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.
There is also https://www.mediawiki.org/wiki/Extension:RightFunctions.
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.
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:
- Click on the edit link of a page (or even the "edit with form" link).
- Do some edit but don't submit.
- Wait at least 10min without visiting nor browsing any page related to both the FSD and the FSF (because these are linked by a CAS, central authentication server/service).
- Submit the edit.
- The message appears. From this point on, if you try to submit again, the data is sent as expected.
- Import https://en.wikipedia.org/wiki/Template:Ref from Wikipedia so we can use
<ref>Reference goes here</ref></nowiki?</code>. This is perhaps the single most important Template to import. To <code><nowiki><ref>...</ref>
should work provided<references/>
is included on the page, since this is a part of a 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
- 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 {{Current_daylight_saving_offset_in_North_America}} (or {{Daylight_saving_in_time_zone}}) to display "EST" and "EDT" instead of "0" and "1" respectively.
- Add message "Join us 12:00-15:00 {{Daylight saving in time zone}}" 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.
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 --Adfeno (talk) 19:30, 18 December 2020 (EST)
- 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
X11
, while Expat isMIT
.
- License:X11 is
- 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
- 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"
- Namespaces we need
- 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?
- Create cron job to update CSV output page of GNU all projects
- 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
- Actions take a long time to complete: The Move (More -> Move) page loads for perhaps a minute when I hit the "Move page" button despite that the page has been moved. Same issue when you create new pages.
- Upload SVG files: We want to upload SVG files but Special:Upload says: "Permitted file types: png, gif, jpg, jpeg, webp."
- OpenSearch installation error: Free Software Directory search can be installed from https://addons.mozilla.org/en-US/firefox/addon/fsf-directory/?src=ss but not from Free Software Directory search (I approved this entry for this test purposes only). --David Hedlund (talk) 23:56, 16 April 2015 (EDT)
- 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
- 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)
- 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.
- 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. --Adfeno (talk) 18:08, 18 December 2020 (EST)
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.
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
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. --Kreyren (talk) 21:05, 20 November 2020 (CET)
- 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
Sent to donald@fsf.org
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'
- Add new entries to https://directory.fsf.org/wiki/Collection:High_Priority_Projects
- https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Service_as_a_Software_Substitute
- https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#SaaSS
- https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Tethered
- https://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures#Nonfree_Network_Services
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
- LibreJS
- Bug report LibreJS below version 7.0 (the WebExtension) inserts unwanted blank lines in text fields
- directory.fsf.org compatibility issue: You cannot edit the Directory with LibreJS
- Solution: Disable LibreJS when you edit https://directory.fsf.org/wiki/
- Lynx
- Bug report: Table column rendering needs more spacing or a better separator
- directory.fsf.org compatibility issue: mediawiki tables in the Windows page for example are not displayed correctly.
- Disclaimer: https://www.gnu.org/software/for-windows.html is not better displayed https://directory.fsf.org/wiki/Windows in Lynx 2.8.9dev.16 from GNU Guix in Trisquel 7
- Solution: Use another text-based web browser.
InvalidAccessError: A parameter or an operation is not supported by the underlying object ext.headertabs.core.js:41
TypeError: ss.rules is undefined[Learn More] wiki:477:35
might be mediawiki issue
TypeError: pf.select2.base is not a constructor[Learn More] ext.pf.select2.combobox.js:35:23
TypeError: pf.select2.base is not a constructor[Learn More] ext.pf.select2.tokens.js:36:21
initFunction is not a function $.fn.PageForms_registerInputInit
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
URL: https://directory.fsf.org/wiki?title=Sandbox&action=formedit&debug=true#tab=3__Licenses
Related to date picker initialization ininput_23
- Improve responsiveness for mobile devices
- Sync Debian package info into the directory
- 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? --David Hedlund (talk) 07:00, 9 July 2018 (EDT)
{{Software prerequisite |Prerequisite kind=Required to use |Prerequisite description=[[Termenu]] }}
The link [[Termenu]] 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. --LorenzoAncora (talk) 12:58, 14 December 2018 (EST)
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.
- 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.
- 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.
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=*$
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.
We should consider adding `__NOINDEX__` to the unapproved message text.
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? --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:
__NOINDEX__
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. --LorenzoAncora (talk)- It was recomended by adfeno to make use of the Template:AttentionBox to increase visibility of an entry's status. --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 (
The presentation of pending entries should not reflect badly on a program
). I suggest to add a message likeThis page revision is not approved and may not represent free software. Please browse the latest revision.
at the bottom of all old page revisions. I've produced a preview. My mantra is: let's preserve the existing UX as much as possible, adding changes gradually and unobtrusively. ;-) --LorenzoAncora (talk) 07:06, 26 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 (
- 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. --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
is free software
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 preview of both changes. 🎅 --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. --Freefish (talk) 13:00, 25th of January 2021 (GMT)
- Hi 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. Craig, do you think this new phrasing is adequate? --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. 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. --LorenzoAncora (talk) 04:35, 17 February 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. Craigt (talk) 13:38, 12 February 2021 (EST)
- Hi 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. Craig, do you think this new phrasing is adequate? --LorenzoAncora (talk) 06:11, 29 January 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
<em>
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. --Freefish (talk) 13:00, 25th of January 2021 (GMT)EM
tags are forbidden/ignored in CSScontent
; also, inline elements cannot influence the absolute alignment of a widget and there is no actual evidence of an enhancement from an accessibility PoV. --LorenzoAncora (talk) 06:11, 29 January 2021 (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. --Freefish (talk) 13:00, 25th of January 2021 (GMT)
- 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
- It was recomended by adfeno to make use of the Template:AttentionBox to increase visibility of an entry's status. --Craigt (talk) 13:32, 24 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:
- I added a robots file a few weeks ago that should not index revision pages. I second adding `__NOINDEX__` to the template. Mmcmahon (talk) 11:15, 25 January 2021 (EST)
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".
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.