Difference between revisions of "Free Software Directory:Backlog Admin Group"

From Free Software Directory
Jump to: navigation, search
(Members: Converted the list to a table)
m (Members)
Line 35: Line 35:
1: Used for meetings: <code>date --date='TZ="YOUR_TZ_DATABASE_TIME_ZONE" 12:00 this Fri'</code>
1: Used for meetings, example: <code>date --date='TZ="YOUR_TZ_DATABASE_TIME_ZONE" 12:00 this Fri'</code>
===Membership policy===
===Membership policy===

Revision as of 12:16, 29 May 2019

The Backlog Admin Group (BAG) is a dedicated group to work on our Backlog.


User Real name Admin verification tz database time zone[1] Role
Adfeno Adonay Felipe Nogueira Verified America/Sao_Paulo Participant
David Hedlund David Hedlund Verified Europe/Stockholm Team Captain
LorenzoAncora Lorenzo L. Ancora Verified Europe/Rome Participant
Saper Marcin Cieślak Verified Europe/Warsaw Participant

1: Used for meetings, example: date --date='TZ="YOUR_TZ_DATABASE_TIME_ZONE" 12:00 this Fri'

Membership policy

  • The Backlog Admin Group only accept volunteers with Administrator privileges
  • The leader the 1st day every month to improve the leadership skills for every member.

Group issues

  • We'll schedule meetings every year or so to actually operate in group activity.


During David's internship: The BAG members got full access to a fresh copy of the main server to investigate setting files etc:

The FSF will consider if we will keep it after David's internship.

I think we should keep these permissions for two reasons 1) the FSF will get gratis sysadmin work 2) the members in BAG will learn to work with the backend. For the moment only saper is a skilled MW admin but other group members would like learn how to maintain MW.


  • #mediawiki and #semantic-mediawiki at chat.freenode.net if full of people that are skilled with ParserFunctions, we should gently ask if someone want to be part of our team.


How to modify the form edit



How to add file upload to form edit

Set empty default values

This is a Semantic MediaWiki issue.

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

Software license: None

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

How to manage possible properties for an entry and its templates

Go to any entry and "Edit" it (without the form), in the bottom you will see a list of all templates it currently uses. {{Entry}} is the property-setter, and is the one used by Form:Entry, so it doesn't display anything to the pages by itself. {{Print entry}} is a intermediary --- it prints somethings but only if called ---, {{Show}} calls {{Print entry}} and other intermediary templates in order to display things. In turn, the first thing that {{Entry}} does is to call {{Show}}, then it proceeds to do all the property settings.

Form:Entry or (the Submit a new entry link in the navigation menu) is used to display editable things that can be found in "Edit with form". When done, Form:Entry automatically makes a page which uses {{Entry}}.


Main issue

From https://directory.fsf.org/wiki/Free_Software_Directory:Backlog#Update_the_license_field :

I've updated https://directory.fsf.org/wiki/Property:License but https://directory.fsf.org/w/api.php?action=pfautocomplete&format=json&property=License&substr=MPL doesn't show the update. Same issue with the old server http://directory-dev.fsf.org/wiki/Property:License and http://directory-dev.fsf.org/w/api.php?action=pfautocomplete&format=json&property=License&substr=Foo

Friday IRC meeting

Should we add to https://directory.fsf.org/wiki/Free_Software_Directory: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.

"—The Speex codec has been obsoleted by Opus. It will continue to be available, but since Opus is better than Speex in all aspects, users are encouraged to switch—" - https://www.speex.org/ . Should we remove speex from the Directory: https://directory.fsf.org/wiki/Category/Works-with-format/speex

You could provide a message like "this package is superseded by X".
Also, what would happen if we remove a free/libre software from FSD, and after many years another project is added but depends on it. Surely the reviewer will want to know if Speex is free/libre based on the FSD or some free/libre distro repository.
If we decide for "removing superseded entries", then we will have the extra work of removing every one of these.

External links

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.