⚓ T87730 Set up process / criteria for taking over abandoned tools
Page Menu
Phabricator
Create Task
Maniphest
T87730
Set up process / criteria for taking over abandoned tools
Closed, Resolved
Public
Actions
Edit Task
Edit Related Tasks...
Create Subtask
Edit Parent Tasks
Edit Subtasks
Merge Duplicates In
Close As Duplicate
Edit Related Objects...
Edit Commits
Edit Mocks
Mute Notifications
Protect as security issue
Assigned To
bd808
Authored By
yuvipanda
Jan 28 2015, 2:47 AM
2015-01-28 02:47:06 (UTC+0)
Tags
WMF-Legal
(Legal Done)
Toolforge
(Waiting for information)
Developer-Advocacy
(Team radar)
Community-Tech-Tool-Labs
(Doing)
User-bd808
(Needs Review/Feedback)
Community-consensus-needed
(Unsorted)
User-notice-archive
(Backlog)
Referenced Files
None
Subscribers
-jem-
Aklapper
Andrew
Andyrom75
bd808
Bmueller
coren
View All 34 Subscribers
Description
NOTE:
The RfC on meta
has closed with approval of both proposed policies.
We currently do not have a process for this, and
@Cyberpower678
wants to take over Hedonil's tools. We should have one.
See
for discussion.
Also announced on
Discussion reboot
Straw dog proposals on wikitech
Announcements
Timeline
2016-09-21 to 2016-10-12: Discuss and refine straw dog proposals on wikitech and meta
2016-11-20 to 2016-12-09:
Vote on adopting one or both proposals on meta
Related Objects
Search...
Task Graph
Mentions
Duplicates
Status
Subtype
Assigned
Task
Declined
None
T91585
Cleanup duplicate bibleversefinder tools
Resolved
bd808
T102066
Make sure tools can be taken over after they are abandoned
Resolved
bd808
T102081
Provide an easy way for Tool Labs tools to expose their source code
Resolved
bd808
T133252
Create application "Striker" to manage Diffusion repositories for a Tool Labs project
Resolved
bd808
T134188
Create application that allows associating a LDAP account with a SUL account
Resolved
mmodell
T134959
LTC needed for user.ldapquery conduit api
Resolved
mmodell
T135249
create conduit method for the creation of phabricator policy objects
Resolved
bd808
T136256
Deploy "Striker" Tool Labs console to WMF production
Resolved
dpatrick
T135784
Security review of Tool Labs console application
Resolved
bd808
T141014
Create Puppet module and role for Striker
Resolved
mmodell
T142539
Create Phabricator bot account for Striker
Resolved
jcrespo
T142545
Create production database and users for Striker
Resolved
bd808
T143253
Ensure that scap3 from tin can access californium
Resolved
bd808
T143172
Send Striker logs to Logstash
Resolved
bd808
T137001
Create Conduit API method to lookup Phabricator accounts by MediaWiki user name
Resolved
bd808
T137004
Create a Conduit API method to lookup Policy information
Resolved
bd808
T87730
Set up process / criteria for taking over abandoned tools
Resolved
bd808
T154625
Facilitate Volunteer NDA application process for potential Tool Labs standards committee appointees
Resolved
Aklapper
T154628
Volunteer NDA for Quiddity
Resolved
Aklapper
T154641
Volunteer NDA for zhuyifei1999
Resolved
Aklapper
T154642
Volunteer NDA for Huji
Resolved
Aklapper
T154688
Volunteer NDA for Eranroz
Resolved
Aklapper
T154910
Volunteer NDA for James Hare
Mentioned In
T102066: Make sure tools can be taken over after they are abandoned
T158462: Identify high-use gadgets and ensure that they have proper long-term maintenance
T144083: Crosswatch gives a server-error after login: "No watchlist could be retrieved"
T121279: Figure out a way to keep MerlBot running when the HTTP POST loophole is closed
T133326: p50380g50816__pop_stats (popularpages) using 53G on labsdb1001 (enwiki)
Mentioned Here
T156075: Figure out how communications and meetings will work for the Tool Labs standards committee
T91585: Cleanup duplicate bibleversefinder tools
T127494: Add new maintainer to tools.drtrigonbot and tools.asurabot
T102920: What to do with old open patches for unmaintained/inactive repositories when not even the uploader responds
Duplicates Merged Here
T127994: Craft a policy for seizing abandoned tools and projects
Event Timeline
There are a very large number of changes, so older changes are hidden.
Show Older Changes
scfc
moved this task from
Backlog
to
Ready to be worked on
on the
Toolforge
board.
Feb 18 2015, 5:04 PM
2015-02-18 17:04:10 (UTC+0)
scfc
moved this task from
Ready to be worked on
to
In Progress
on the
Toolforge
board.
Feb 18 2015, 5:06 PM
2015-02-18 17:06:47 (UTC+0)
scfc
moved this task from
In Progress
to
Waiting for information
on the
Toolforge
board.
Aklapper
updated the task description.
(Show Details)
Feb 19 2015, 12:14 PM
2015-02-19 12:14:02 (UTC+0)
Aklapper
added a project:
Developer-Advocacy
Aklapper
updated the task description.
(Show Details)
Feb 19 2015, 2:06 PM
2015-02-19 14:06:54 (UTC+0)
Ricordisamoa
added a comment.
Feb 19 2015, 3:28 PM
2015-02-19 15:28:09 (UTC+0)
Comment Actions
In
T87730#1000846
@coren
wrote:
The "real" solution remains to hound maintainers to make certain they are not alone with access to a tool if it starts getting some use - so that there is already someone with all the right accesses to take over at need, of course. :-)
Definitely. It may not solve the problem for already abandoned tools, but existing maintainers should be encouraged to recruit other trusted users from the beginning.
scfc
added a parent task:
T91585: Cleanup duplicate bibleversefinder tools
Apr 6 2015, 4:02 AM
2015-04-06 04:02:07 (UTC+0)
Ricordisamoa
awarded a token.
Apr 6 2015, 5:04 AM
2015-04-06 05:04:01 (UTC+0)
Qgil
subscribed.
Apr 30 2015, 10:28 AM
2015-04-30 10:28:51 (UTC+0)
Comment Actions
Is someone planning to work on this task during the month of May? If so, please take it. If not, maybe it is better to lower its priority?
Technical13
added a comment.
Apr 30 2015, 12:48 PM
2015-04-30 12:48:39 (UTC+0)
Comment Actions
In
T87730#1248601
@Qgil
wrote:
Is someone planning to work on this task during the month of May? If so, please take it. If not, maybe it is better to lower its priority?
@Qgil
- the only thing holding this up is waiting for someone to close the RfC on meta that has been idle for almost two months now. Do you think you could close it or find someone to do so? That would be great. Thanks.
yuvipanda
added a comment.
Apr 30 2015, 4:17 PM
2015-04-30 16:17:23 (UTC+0)
Comment Actions
I don't know if just closing the rfc on meta is enough - this needs some
consensus from the tech community / toollabs admins / wikimedia foundation
ops.
Technical13
added a comment.
Apr 30 2015, 11:47 PM
2015-04-30 23:47:38 (UTC+0)
Comment Actions
In
T87730#1249301
@yuvipanda
wrote:
I don't know if just closing the rfc on meta is enough - this needs some
consensus from the tech community / toollabs admins / wikimedia foundation
ops.
Perhaps, but it seems like that would be the logical next step to get this moving again. :)
JanZerebecki
subscribed.
May 15 2015, 5:25 PM
2015-05-15 17:25:34 (UTC+0)
Qgil
added a subscriber:
Cloud-Services
Jun 28 2015, 8:20 AM
2015-06-28 08:20:09 (UTC+0)
Comment Actions
Is the
Cloud-Services
team considering this task as a July-September quarterly goal, at a team or individual level? Or is there anybody else willing to contribute time to push this task further in the next months?
Restricted Application
added a project:
Cloud-Services
View Herald Transcript
Jun 28 2015, 8:20 AM
2015-06-28 08:20:09 (UTC+0)
Qgil
lowered the priority of this task from
Medium
to
Low
Aug 24 2015, 11:42 AM
2015-08-24 11:42:05 (UTC+0)
Aklapper
added a comment.
Aug 26 2015, 10:19 PM
2015-08-26 22:19:29 (UTC+0)
Comment Actions
In
T87730#1249301
@yuvipanda
wrote:
I don't know if just closing the rfc on meta is enough - this needs some consensus from the tech community / toollabs admins / wikimedia foundation ops.
So somebody needs to drive finding consensus by reaching out to venues like
wikitech-l@
labs-l@
, operations@ and ask for providing more input on
Any on-wiki places or other venues that come to anybody's mind who should be contacted?
I'm also wondering how much this whole process is (not) similar/comparable to
(as we discuss defining and dealing with inactive code repositories in
T102920
).
Qgil
moved this task from
To triage
to
October - December 2015
on the
Developer-Advocacy
board.
Sep 17 2015, 9:05 AM
2015-09-17 09:05:53 (UTC+0)
Qgil
moved this task from
October - December 2015
to
January-March 2016
on the
Developer-Advocacy
board.
Oct 27 2015, 7:25 PM
2015-10-27 19:25:25 (UTC+0)
coren
added a comment.
Nov 30 2015, 4:26 PM
2015-11-30 16:26:07 (UTC+0)
Comment Actions
In
T87730#1577350
@Aklapper
wrote:
I'm also wondering how much this whole process is (not) similar/comparable to
(as we discuss defining and dealing with inactive code repositories in
T102920
).
Very much - at least conceptually. I would expect that many cases of one would also involve the other, for that matter. Both conversations are parallel enough that merging them seems indicated.
Qgil
moved this task from
January-March 2016
to
Team radar
on the
Developer-Advocacy
board.
Jan 12 2016, 7:41 AM
2016-01-12 07:41:50 (UTC+0)
Andrew
merged a task:
T127994: Craft a policy for seizing abandoned tools and projects
Feb 24 2016, 5:36 PM
2016-02-24 17:36:03 (UTC+0)
Andrew
added subscribers:
StudiesWorld
JEumerus
Andrew
tom29739
subscribed.
Feb 24 2016, 9:41 PM
2016-02-24 21:41:33 (UTC+0)
scfc
subscribed.
Mar 14 2016, 7:17 PM
2016-03-14 19:17:20 (UTC+0)
Comment Actions
This task has been idling for about a year now, with the RfC going nowhere, and I don't remember any other requests apart from
T127494
. Is a formal process with lots of criteria and instructions to be followed to the letter still needed? If so, there needs to be someone who drives the discussion and distills it into a draft policy.
bd808
added a project:
Community-Tech-Tool-Labs
Mar 24 2016, 11:53 PM
2016-03-24 23:53:15 (UTC+0)
Technical13
added a comment.
Mar 25 2016, 1:31 AM
2016-03-25 01:31:51 (UTC+0)
Comment Actions
In
T87730#2119736
@scfc
wrote:
This task has been idling for about a year now, with the RfC going nowhere, and I don't remember any other requests apart from
T127494
. Is a formal process with lots of criteria and instructions to be followed to the letter still needed? If so, there needs to be someone who drives the discussion and distills it into a draft policy.
T91585
is also blocked waiting on this project. I'd still like to be added as an admin for that tool.
bd808
moved this task from
Backlog
to
Needs Discussion
on the
Community-Tech-Tool-Labs
board.
Mar 25 2016, 2:16 AM
2016-03-25 02:16:08 (UTC+0)
ZhouZ
moved this task from
Backlog
to
Legal Done
on the
WMF-Legal
board.
Apr 14 2016, 1:24 AM
2016-04-14 01:24:38 (UTC+0)
ZhouZ
subscribed.
bd808
added a parent task:
T102081: Provide an easy way for Tool Labs tools to expose their source code
May 2 2016, 8:27 PM
2016-05-02 20:27:44 (UTC+0)
bd808
added a parent task:
T102066: Make sure tools can be taken over after they are abandoned
Izno
subscribed.
May 26 2016, 12:44 AM
2016-05-26 00:44:15 (UTC+0)
Qgil
mentioned this in
T133326: p50380g50816__pop_stats (popularpages) using 53G on labsdb1001 (enwiki)
May 31 2016, 9:04 PM
2016-05-31 21:04:27 (UTC+0)
bd808
mentioned this in
T121279: Figure out a way to keep MerlBot running when the HTTP POST loophole is closed
Jun 8 2016, 10:21 PM
2016-06-08 22:21:50 (UTC+0)
Bmueller
subscribed.
Jun 13 2016, 2:17 PM
2016-06-13 14:17:45 (UTC+0)
Danny_B
removed a subscriber:
Cloud-Services
Aug 8 2016, 11:41 AM
2016-08-08 11:41:35 (UTC+0)
Jfhutson
subscribed.
Sep 19 2016, 5:52 PM
2016-09-19 17:52:13 (UTC+0)
Matthewrbowker
subscribed.
Sep 20 2016, 10:11 PM
2016-09-20 22:11:29 (UTC+0)
bd808
updated the task description.
(Show Details)
Sep 21 2016, 9:40 PM
2016-09-21 21:40:57 (UTC+0)
bd808
claimed this task.
Sep 21 2016, 9:47 PM
2016-09-21 21:47:19 (UTC+0)
bd808
added projects:
Community-consensus-needed
User-notice
bd808
subscribed.
Comment Actions
I have drafted two straw dog proposals and am proposing that they be discussed and refined until 2016-10-13. I would then like to call for a consensus vote by the Tool Labs developer community to adopt one or both policies.
Restricted Application
added a project:
User-bd808
View Herald Transcript
Sep 21 2016, 9:47 PM
2016-09-21 21:47:20 (UTC+0)
JJMC89
subscribed.
Sep 21 2016, 9:49 PM
2016-09-21 21:49:08 (UTC+0)
bd808
moved this task from
To Do
to
Needs Review/Feedback
on the
User-bd808
board.
Sep 21 2016, 10:04 PM
2016-09-21 22:04:23 (UTC+0)
DannyH
subscribed.
Sep 21 2016, 10:49 PM
2016-09-21 22:49:11 (UTC+0)
Johan
moved this task from
To Triage
to
In current Tech/News draft
on the
User-notice
board.
Sep 22 2016, 6:52 PM
2016-09-22 18:52:13 (UTC+0)
-jem-
subscribed.
Sep 23 2016, 7:24 PM
2016-09-23 19:24:40 (UTC+0)
Superyetkin
subscribed.
Sep 26 2016, 7:02 PM
2016-09-26 19:02:21 (UTC+0)
Johan
moved this task from
In current Tech/News draft
to
Recently announced in Tech/News
on the
User-notice
board.
Sep 27 2016, 4:41 AM
2016-09-27 04:41:54 (UTC+0)
Aklapper
raised the priority of this task from
Low
to
Medium
Sep 27 2016, 12:40 PM
2016-09-27 12:40:28 (UTC+0)
Framawiki
subscribed.
Sep 27 2016, 4:30 PM
2016-09-27 16:30:35 (UTC+0)
Johan
moved this task from
Recently announced in Tech/News
to
Already announced/Archive
on the
User-notice
board.
Oct 6 2016, 11:56 AM
2016-10-06 11:56:55 (UTC+0)
Qgil
added a comment.
Oct 27 2016, 1:37 PM
2016-10-27 13:37:14 (UTC+0)
Comment Actions
Would this task be a good topic for the
Wikimedia-Developer-Summit (2017)
? If so, the deadline to submit new proposals is next Monday, October 31:
bd808
added a comment.
Oct 27 2016, 3:30 PM
2016-10-27 15:30:51 (UTC+0)
Comment Actions
In
T87730#2748277
@Qgil
wrote:
Would this task be a good topic for the
Wikimedia-Developer-Summit (2017)
? If so, the deadline to submit new proposals is next Monday, October 31:
If the RfC discussion is still open in January then I will have failed the community and my team's quarterly goals.
bd808
mentioned this in
T144083: Crosswatch gives a server-error after login: "No watchlist could be retrieved"
Nov 22 2016, 10:37 PM
2016-11-22 22:37:21 (UTC+0)
bd808
updated the task description.
(Show Details)
Nov 22 2016, 10:40 PM
2016-11-22 22:40:28 (UTC+0)
bd808
moved this task from
Triage
to
In Progress
on the
Cloud-Services
board.
Nov 24 2016, 9:42 PM
2016-11-24 21:42:18 (UTC+0)
bd808
updated the task description.
(Show Details)
Dec 11 2016, 5:48 PM
2016-12-11 17:48:15 (UTC+0)
bd808
added a subscriber:
MarcoAurelio
Dec 14 2016, 11:06 PM
2016-12-14 23:06:17 (UTC+0)
Comment Actions
The
RfC vote on meta
has been closed by
@MarcoAurelio
The results of the vote are as follows:
The proposal to enact the "Tool Labs right to fork policy" and form a committee to help oversee the policy. With 29 votes in favor and 2 votes against the proposal passes with a 93.54% approval.
The proposal to enact the "Tool Labs abandoned tool policy" and form a committee to help oversee the policy. With 19 votes in favor and 4 votes against, the proposal passes with 82.60% of approval.
The result of this RFC has been concluded using an objective measure: counting votes and calculating the support, so whist this user has voted in this RFC, the results are not altered. —MarcoAurelio 16:04, 11 December 2016 (UTC)
Next steps will be to discuss the
initial structure for the volunteer committee to oversee the new policies
and
bootstrap that committee
. Minor changes to the policies themselves will be needed to incorporate the approved committee system.
Qgil
awarded a token.
Dec 15 2016, 10:55 AM
2016-12-15 10:55:00 (UTC+0)
Jfhutson
unsubscribed.
Dec 15 2016, 1:42 PM
2016-12-15 13:42:37 (UTC+0)
StefenTower
subscribed.
Dec 16 2016, 1:59 PM
2016-12-16 13:59:41 (UTC+0)
bd808
moved this task from
Needs Discussion
to
Doing
on the
Community-Tech-Tool-Labs
board.
Jan 4 2017, 9:35 PM
2017-01-04 21:35:21 (UTC+0)
bd808
created subtask
T154625: Facilitate Volunteer NDA application process for potential Tool Labs standards committee appointees
Jan 4 2017, 10:40 PM
2017-01-04 22:40:23 (UTC+0)
bd808
closed subtask
T154625: Facilitate Volunteer NDA application process for potential Tool Labs standards committee appointees
as
Resolved
Jan 19 2017, 6:03 PM
2017-01-19 18:03:51 (UTC+0)
bd808
added a comment.
Jan 19 2017, 6:08 PM
2017-01-19 18:08:27 (UTC+0)
Comment Actions
The final step in this initial process is for me to write up the outcome of the various votes and polls and announce the formation of the initial committee. Then the committee can get started on their work to flesh out the skeleton policies and start working with the Tool Labs community. It would be nice to get these final parts resolved before the 2nd birthday of this task. :)
Huji
subscribed.
Jan 19 2017, 8:36 PM
2017-01-19 20:36:43 (UTC+0)
Wesalius
subscribed.
Jan 20 2017, 11:21 AM
2017-01-20 11:21:07 (UTC+0)
zhuyifei1999
subscribed.
Jan 20 2017, 6:23 PM
2017-01-20 18:23:39 (UTC+0)
bd808
added a comment.
Jan 23 2017, 10:31 PM
2017-01-23 22:31:06 (UTC+0)
Comment Actions
Committee announced:
bd808
added a comment.
Jan 24 2017, 6:02 AM
2017-01-24 06:02:58 (UTC+0)
Comment Actions
Created
Toolforge-standards-committee
and kicked off discussion of
T156075: Figure out how communications and meetings will work for the Tool Labs standards committee
Quiddity
subscribed.
Jan 25 2017, 2:39 AM
2017-01-25 02:39:55 (UTC+0)
bd808
closed this task as
Resolved
Jan 26 2017, 4:24 AM
2017-01-26 04:24:33 (UTC+0)
Comment Actions
I'm going to declare victory on this task. The committee will have more work to do before they handle the first takeover request, but the basic policies and structure are in place. Thanks to everyone who helped move this forward, especially
@yuvipanda
for at least indirectly challenging me to see if it was a solvable problem.
Liuxinyu970226
unsubscribed.
Jan 26 2017, 4:30 AM
2017-01-26 04:30:01 (UTC+0)
RandomDSdevel
subscribed.
Jan 27 2017, 10:22 PM
2017-01-27 22:22:59 (UTC+0)
RandomDSdevel
unsubscribed.
Samwilson
mentioned this in
T158462: Identify high-use gadgets and ensure that they have proper long-term maintenance
Feb 28 2017, 2:29 AM
2017-02-28 02:29:07 (UTC+0)
Phabricator_maintenance
removed a subscriber:
yuvipanda
Jun 7 2017, 6:55 PM
2017-06-07 18:55:30 (UTC+0)
bd808
mentioned this in
T102066: Make sure tools can be taken over after they are abandoned
Jan 9 2020, 10:46 PM
2020-01-09 22:46:19 (UTC+0)
Ladsgroup
edited projects, added
User-notice-archive
; removed
User-notice
Cloud-Services
Aug 13 2022, 1:54 PM
2022-08-13 13:54:41 (UTC+0)
Log In to Comment
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct.
Wikimedia Foundation
Code of Conduct
Disclaimer
CC-BY-SA
GPL
Credits
US