Help:Toolforge/Toolforge standards committee: Difference between revisions - Wikitech
Jump to content
From Wikitech
Help:Toolforge
Browse history interactively
← Older edit
Newer edit →
BryanDavis
talk
contribs
3 user groups
Bureaucrats, Interface administrators, Administrators
9,657
edits
Content deleted
Content added
Visual
Wikitext
Inline
Revision as of 03:57, 5 January 2017
view source
BryanDavis
talk
contribs
Bureaucrats
Interface administrators
Administrators
9,657
edits
Add navbar and
Category:Tool Labs policies
← Older edit
Revision as of 22:28, 23 January 2017
view source
BryanDavis
talk
contribs
Bureaucrats
Interface administrators
Administrators
9,657
edits
Add initial committee members
Newer edit →
Line 3:
Line 3:
== Committee membership ==
== Committee membership ==
=== Current members ===
* {{u|Eranroz}}
* {{u|Harej}}
* {{u|Huji}}
* {{u|Ladsgroup}}
* {{u|Matanya}}
* {{u|Quiddity}}
* {{u|Zhuyifei1999}}
=== Membership criteria ===
=== Membership criteria ===
Revision as of 22:28, 23 January 2017
Toolforge
Cloud Services overview
Toolforge user docs
Toolforge changelog
Get started
Quickstart: set up and get access
How Toolforge works
Rules you must follow
Tutorials
Build and run tools
Navigate tool accounts and files
Build container images for tools
Run a web service
Schedule and manage jobs
Manage tool runtime configuration (envvars)
Deploy your tool on every push (beta)
Language-specific details:
Python
Pywikibot
Node.js
PHP
...more languages/frameworks
Use Redis for caching
Index content with Elasticsearch
Access shared storage and databases
Access shared storage and public wiki dumps
Access the Wiki Replicas databases
Access replica search indices
Manage
tool databases
Sending and receiving email
as tools
Share and maintain tools
Set up version control and code review
Develop successful tools
Find and share tools on Toolhub
Delete a tool
Get help
How and where to get help
Troubleshooting
Contribute to Toolforge
Useful links
Toolforge admin docs
List of tools
Toolforge Admin Console (toolsadmin)
Toolforge API
edit
The
Tool Labs Standards Committee
is a group of Wikimedia volunteers who review, approve, and facilitate access requests for the source code of Tool Labs hosted tools, and adoption and usurpation of abandoned tools. These powers are granted by the
Right to fork policy
and the
Abandoned tool policy
Committee membership
Current members
Eranroz
Harej
Huji
Ladsgroup
Matanya
Quiddity
Zhuyifei1999
Membership criteria
Members of the Tool Labs Standards Committee
must
Be active members in good standing of the Tool Labs community
Have signed the Wikimedia Foundation's
Volunteer NDA
before being appointed
Membership changes
Committee members are appointed by the Wikimedia Foundation on an as needed basis. Nominations for appointment are accepted annually and/or upon the removal of an existing committee member. Self nomination is acceptable.
Committee members can be removed for failure to participate in committee discussions, by the Wikimedia Foundation for any reason, or by a majority request from the other committee members.
Quorum
The committee must have three members to function. There is no set upper limit on committee membership. If the membership of the committee falls below three members the activities of the committee will be suspended until quorum is restored.
Committee duties
The duties of the committee are primarily outlined in the
Right to fork policy
and the
Abandoned tool policy
which may be amended by the Wikimedia Foundation in consultation with the Tool Labs project members. See the current versions of the policies for complete details.
Committee members are expected to conduct their activities with a high degree of transparency. Decisions should be documented on Phabricator in tasks related to the original requests. The committee is granted leeway to determine its own internal policies and procedures, but these must be documented on Wikitech and may be subject to alteration by the Wikimedia Foundation for technical, privacy, or legal reasons.
Procedures
Tool access
Members of the committee may need to have access to a tool account in order to review the files present on Tool Labs servers. When possible, the committee should attempt to work directly with the current maintainers of the tool before requesting membership changes from the Tool Labs administrators. When no maintainers can be found to grant access, a Phabricator ticket will be created to request access to the tool in question. This access request will be handled by a Tool Labs administrator adding individual committee members as co-maintainers of the tool.
See also
Abandoned tool policy
Right to fork policy
task T87730
Set up process / criteria for taking over abandoned tools
Retrieved from "
Categories
Toolforge
Tool Labs policies
Help:Toolforge/Toolforge standards committee: Difference between revisions
Add topic