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

From Free Software Directory
Jump to: navigation, search
m (Make timezone name and group as properties.)
(Restructure page.)
Line 5: Line 5:
 
     |?TZ database time zone name
 
     |?TZ database time zone name
 
     |limit=0
 
     |limit=0
     |searchlabel=Members of this team.
+
     |searchlabel=Table with team members and their time zones.
 
}}
 
}}
  
1: Used for internal meetings, example: <code>date --date='TZ="YOUR_TZ_DATABASE_TIME_ZONE" 12:00 this Fri'</code>
+
For internal meetings, the column about [[Property:TZ database time zone name]] from the above link can be used to display what would be the members' local time when the meeting start, given  this example: <code>TZ="MEMBER_TIME_ZONE" date --date='TZ="America/New_York" 12:00 this Fri'</code>.
 +
 
 +
== Membership policy ==
  
===Membership policy===
 
 
* The Backlog Admin Group only accept volunteers with [[Special:ListUsers/sysop|Administrator]] privileges.
 
* The Backlog Admin Group only accept volunteers with [[Special:ListUsers/sysop|Administrator]] privileges.
  
===Group issues===
+
== Schedule ==
 +
 
 
* We'll schedule meetings every year or so to actually operate in group activity.
 
* We'll schedule meetings every year or so to actually operate in group activity.
  
====Permissons====
+
== Testing instance ==
 +
 
 
During David's internship: The BAG members got full access to a fresh copy of the main server to investigate setting files etc:
 
During David's internship: The BAG members got full access to a fresh copy of the main server to investigate setting files etc:
 
* Browser: https://directory2p.fsf.org/wiki/Main_Page
 
* Browser: https://directory2p.fsf.org/wiki/Main_Page
Line 25: Line 28:
 
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.
 
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.
  
===Candidates===
+
== Candidates for membership ==
 +
 
 
* People at irc://chat.freenode.net/#mediawiki and irc://chat.freenode.net/#semantic-mediawiki at <code>chat.freenode.net</code> if full of people that are skilled with ParserFunctions, we should gently ask if someone want to be part of our team.
 
* People at irc://chat.freenode.net/#mediawiki and irc://chat.freenode.net/#semantic-mediawiki at <code>chat.freenode.net</code> if full of people that are skilled with ParserFunctions, we should gently ask if someone want to be part of our team.
  
==Tools==
+
== Testing pages in the main instance ==
* [[Dummy]] -- for a software/entry
+
 
* [[Sandbox2]] -- for a software/entry
+
See the [[:Category:Test|test category]].
* [[Free Software Directory:Sandbox]] -- for a page which isn't an entry
+
 
 +
== How to modify [[Form:Entry]] ==
 +
 
 +
First read the [[FSD:Hack|hacking section]]. After this pick an aspect to modify.
  
==How to modify the form edit==
+
For properties, one could do like this:
[[Free_Software_Directory:Hack|Hack]]
 
  
Modify:
 
 
* Property:<custom name>
 
* Property:<custom name>
 
* [[Form:Entry]] (click on Edit)
 
* [[Form:Entry]] (click on Edit)
Line 47: Line 52:
 
* [[Template:Show]]
 
* [[Template:Show]]
  
===How to add file upload to form edit===
+
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. All templates go like this:
 +
 
 +
* {{Tl|Entry}} is the property-setter, and is the one used by [[Form:Entry]], so {{Tl|Entry}} doesn't display anything to the pages by itself.
 +
* {{Tl|Print entry}} is a intermediary --- it prints somethings but only if called.
 +
* {{Tl|Show}} calls {{Tl|Print entry}} and other intermediary templates in order to display things.
 +
* The first thing that {{Tl|Entry}} does is to call {{Tl|Show}}, then it proceeds to do all the property settings.
 +
 
 +
[[Form:Entry]] or (the <code>Submit a new entry</code> 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 {{Tl|Entry}}.
 +
 
 +
== How to add file upload to form edit ==
 +
 
 +
To do.
 +
 
 +
== Special pages not found in [[Special:SpecialPages]] ==
  
==Special pages not found in [[Special:SpecialPages]]==
 
 
* [[MediaWiki:Common.css]]
 
* [[MediaWiki:Common.css]]
 
* [[MediaWiki:Common.js]]
 
* [[MediaWiki:Common.js]]
 
* [[MediaWiki:Deletereason-dropdown]]
 
* [[MediaWiki:Deletereason-dropdown]]
  
==Special workarounds==
+
== Special workarounds ==
 +
 
 +
=== Unlisted name spaces ===
  
===Unlisted name spaces===
 
 
* Move the page
 
* Move the page
 
* Use (Main) as name space.
 
* Use (Main) as name space.
 
* Set "NAMESPACE:<title>" in the title wpNewTitleMain text form, example: "Draft:Main page"
 
* Set "NAMESPACE:<title>" in the title wpNewTitleMain text form, example: "Draft:Main page"
  
==Set empty default values==
+
== Issues ==
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:
+
=== Assigned ===
  
Software license: [[SoftwareLicense::{{{LICENSE|None}}}]]
+
* [[FSD:Backlog active#Show changes (TOP_PRIORITY)]]: Adfeno
  
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.
+
=== Not assigned ===
  
== How to manage possible properties for an entry and its templates ==
+
==== Set empty default values ====
  
Go to any entry and "Edit" it (without the form), in the bottom you will see a list of all templates it currently uses. {{Tl|Entry}} is the property-setter, and is the one used by [[Form:Entry]], so it doesn't display anything to the pages by itself. {{Tl|Print entry}} is a intermediary --- it prints somethings but only if called ---, {{Tl|Show}} calls {{Tl|Print entry}} and other intermediary templates in order to display things. In turn, the first thing that {{Tl|Entry}} does is to call {{Tl|Show}}, then it proceeds to do all the property settings.
+
This is a Semantic MediaWiki issue.
  
[[Form:Entry]] or (the <code>Submit a new entry</code> 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 {{Tl|Entry}}.
+
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:
  
==Issues==
+
Software license: [[SoftwareLicense::{{{LICENSE|None}}}]]
  
===Assigned issues===
+
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.
* [[Free_Software_Directory:Backlog_active#Show_changes_.28TOP_PRIORITY.29]]: Adfeno
 
  
===Main issue===
+
==== Homepage shouldn't be required ====
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
+
* 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.
 +
* [[FSD:Backlog#Donald]]. <!-- always keep that link here -->
  
===Friday IRC meeting===
+
==== Non-official compiled/non-source releases ====
* The "Homepage" field should not mandatory to fill in entries. For example: https://directory.fsf.org/wiki/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.
 
* https://directory.fsf.org/wiki/Free_Software_Directory:Backlog#Donald<!-- always keep that link here -->
 
  
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
+
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.
 
(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
+
== External links ==
: 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==
 
 
* [https://www.mediawiki.org/wiki/Help:Magic_words Magic words]
 
* [https://www.mediawiki.org/wiki/Help:Magic_words Magic words]
  
 
[[Category:Project Team]]
 
[[Category:Project Team]]

Revision as of 22:57, 2 May 2020

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

Table with team members and their time zones.

For internal meetings, the column about Property:TZ database time zone name from the above link can be used to display what would be the members' local time when the meeting start, given this example: TZ="MEMBER_TIME_ZONE" date --date='TZ="America/New_York" 12:00 this Fri'.

Membership policy

  • The Backlog Admin Group only accept volunteers with Administrator privileges.

Schedule

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

Testing instance

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.

Candidates for membership

Testing pages in the main instance

See the test category.

How to modify Form:Entry

First read the hacking section. After this pick an aspect to modify.

For properties, one could do like this:

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. All templates go like this:

  • {{Entry}} is the property-setter, and is the one used by Form:Entry, so {{Entry}} 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.
  • 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}}.

How to add file upload to form edit

To do.

Special pages not found in Special:SpecialPages

Special workarounds

Unlisted name spaces

  • Move the page
  • Use (Main) as name space.
  • Set "NAMESPACE:<title>" in the title wpNewTitleMain text form, example: "Draft:Main page"

Issues

Assigned

Not assigned

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.

Homepage shouldn't be required

  • 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.
  • FSD:Backlog#Donald.

Non-official compiled/non-source releases

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.

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.