[go: up one dir, main page]

Page MenuHomePhabricator

Refresh membership of Toolforge standards committee
Closed, ResolvedPublic

Description

The Toolforge standards committee (née Tool Labs standards committee) was established in 2017 following a membership nomination process in December 2016. There have been no formal membership changes in the subsequent 7 years.

As one might imagine, a number of the highly active Toolforge members who formed the original committee have since drifted away from the project as their personal lives and interests have changed. Those that are still active within the movement seem to have drifted away from this particular functionary role.

Per the original charter of the committee, the process for membership changes is to be handled on an as-needed basis at the discretion of the Wikimedia Foundation. This was originally envisioned as an annually reviewed process, but here we are.

@bd808 feels both grateful to those who have served for so long and responsible for not helping them transition away more gracefully prior to now. It is long past time for us to thank @eranroz, @Huji, @Ladsgroup, @Matanya, @Quiddity, and @zhuyifei1999 for their efforts and find a new set of folks to carry on the work of the committee.

TODO:

Event Timeline

bd808 triaged this task as Medium priority.
bd808 added subscribers: JJMC89, Pintoch.
[16:03]  <    bd808> JJMC89: blame me for inventing a committee but then just hoping that they would fill in the processes to keep things working over time. It would be most excellent if someone showed up with a passion for rebooting that system.
[16:05]  <    dcaro> in the meantime, current toolforge roots will fill in when needed
[16:07]  <   JJMC89> IMO, WMCS should remove all the members and appoint a new committee. Then have the membership changes work like the CoCC (self-managed yearly).
[16:08]  <  pintoch> $1$.*+

...

[16:37]  <    bd808> JJMC89 and pintoch: can I put y'all down as core members for the next iteration? :)
[16:38]  <   JJMC89> yes
[16:39]  <    bd808> awesome! I do think it can all work; it just leaned too hard on a handful of folks who have mostly wandered away as their personal lives changed.

...

[20:01]  <  pintoch> bd808: ah yes that sounds fun, thanks for proposing
[20:01]  <  pintoch> good that I wrote random garbage in this chan at the right moment :-D
bd808 changed the task status from Open to In Progress.Jul 18 2024, 8:29 PM
bd808 moved this task from To Do to In Dev/Progress on the User-bd808 board.

I will work on the details for where we will collect nominations (probably on wikitech again) and make the announcement of the open process soon™. It should not take too long to get that much going.

I have thanked all 6 past committee members for their service with a wikilove post to their Wikitech talk page awarding each of them the teamwork barnstar.

Nominations are now closed. The list of nominated candidates is:

I will begin the vetting and Volunteer NDA process for these fine humans next week (2024-09-02 or so). One of the things I need to figure out is which of the several NDA processes we should be using these days. I somehow remember there being one process the last time around, but I now see a number of variations.

T154625: Facilitate Volunteer NDA application process for potential Tool Labs standards committee appointees was the tracking task for the 2017 NDA process and may help us figure out next steps in the 2024 process.

FWIW, work-me signed some NDA years ago (compare T208518). I try to keep my work and volunteer accounts pretty separate, but legally I’m still just one person, so idk if Legal will want me to sign the NDA again :) (but I don’t mind doing it either ^^)

What access needs to be covered in the NDA for TFSC? I'm in the process signing a volunteer NDA for other access (T369314) - let me know if I should try to get them to also include this in that one.

What access needs to be covered in the NDA for TFSC? I'm in the process signing a volunteer NDA for other access (T369314) - let me know if I should try to get them to also include this in that one.

T154641: Volunteer NDA for zhuyifei1999 is an example NDA request from the prior cycle.

The specific wording I used in T154625: Facilitate Volunteer NDA application process for potential Tool Labs standards committee appointees about the need for NDA protection was:

NDA protection is required for the Tool Labs standards committee members because in the course of their duties they may have access to unpublished and/or unlicensed source code as well as log files and credentials associated with tools and bots that they did not author.

I have just emailed the members of the admin tool to solicit their feedback on the candidates as the method for checking that these 8 individuals are all "active members in good standing of the Toolforge community." The Toolforge admins now have until 2024-09-12 end of day anywhere on earth (2024-09-13T12:00Z) to provide their feedback directly to me. Once the feedback period is closed I will inform this admins and the nominees who is invited to continue on to the final membership hurdle, signing the Volunteer NDA with WMF Legal.

I have just emailed the Wikimedia Foundation's Trust and Safety team and asked them to inform me if anyone on the nomination list should be deemed ineligible for this trusted functionary role based on existing issues known to them.

bd808 changed the task status from Stalled to In Progress.Oct 15 2024, 8:49 PM

I am going to close this task as {{done}}. I have created T379844: Define a process for keeping the committee membership "fresh" to track the major point I wanted to ensure happens this time so that we are less likely to end up needing a full reboot of the committee a few years from now.

Shouldn't the new members be added (or add themselves) to the Toolforge-standards-committee project?

Shouldn't the new members be added (or add themselves) to the Toolforge-standards-committee project?

Ideally all of you would choose to become watchers of that project so that you are notified of activity on tasks, but I don't think it is my place to force folks to get new alerts.