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

From Free Software Directory
Jump to: navigation, search
(Undo revision 80882 by David Hedlund (talk))
(Tag: Undo)
(Revert to Property:Member of team to [Property:Page]] type.)
Line 1: Line 1:
 
The '''Backlog Admin Group''' ('''BAG''') is a dedicated group to work on our [[Free_Software_Directory:Backlog|Backlog]].
 
The '''Backlog Admin Group''' ('''BAG''') is a dedicated group to work on our [[Free_Software_Directory:Backlog|Backlog]].
  
{{#ask:[[Team captain::{{FULLPAGENAME}}]] OR [[Team member::{{FULLPAGENAME}}]]
+
{{#ask:
  |?TZ database time zone name
+
    [[Member of team::{{FULLPAGENAME}}]]
  |?IRC Freenode nick
+
    |?IRC Freenode nick
  |offset=0
+
    |?TZ database time zone name
  |limit=500
+
    |limit=0
 +
    |searchlabel=Table with team members and their time zones.
 
}}
 
}}
  

Revision as of 22:45, 4 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.