Hello Admins,
As communicated earlier, we have put together a list of about 100 tools
whose maintainers we propose to invite in the next round of testing.
This expanded list now includes tools written in languages other than
Python.
You can see the list here[0]
The feedback and suggestions around custom and secret environment variable
support[1] and package installation for buildservice[2] have all now been
successfully rolled out to toolforge.
If there's no changes requested, the new invites will be sent on the 23rd
of Jun.
Kindly reach out if you have any questions or feedback.
Thank you!
[0] https://etherpad.wikimedia.org/p/second-round
[1]
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Install_ap…
[2] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Envvars_Service
After talking with both Arturo and Birgit about things we might
present at Wikimania, I came up with this abstract for a talk:
Co-creating platforms and products: how the Wikimedia Cloud Services
team works with the larger Wikimedia technical community to build and
maintain Cloud VPS, Toolforge, Quarry, PAWS, and more
Did you know that volunteers are involved in planning, building, and
maintaining the Cloud VPS and Toolforge projects as co-equals with
paid staff from the Wikimedia Foundation? Since the start of the
"Labs" project in 2011, one of the guiding principles for WMCS
projects has been improving collaboration between Foundation staff and
technical volunteers. Learn more about some of the policies and
practices that are used to make this collaboration possible.
The submission would be under either the "governance" or "technology"
tracks. I think it would work best as a panel discussion that is
either "hybrid" (some folks in Singapore, some on-line) or
pre-recorded video.
I think this is something that folks in the community might be
interested in learning a bit about. I also think it would be
interesting for those of us who have participated in this process to
take some time to reflect on how we have worked together in the past
and how we might like to see those those processes and practices
evolve in the future. To make this talk work well there should be
active voices from both the paid and volunteer staff involved. Towards
that end, I'm mailing the cloud-admin@ list + 4 of you that I know
have been active in the past in helping with Toolforge and/or Cloud
VPS admin and features work to gauge your interest in participating.
Thoughts?
Bryan
--
Bryan Davis Technical Engagement Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808
Hi!
Given that in gitlab we can't add more than one reviewer, and to help the
flow of code reviews, I have started adding the label `Ready for review` as
an indication that the attention of someone else is needed in the patch,
and the removal of the label to indicate that the attention of the author
is needed (either changes required, questions need answering or MR
accepted).
I'm going to keep using that flow while it works, but I think it would be
useful for anyone else also if they want my or other's attention to their
MRs.
I'm also going over all the MRs in the following search relatively often to
review/help with code reviews, feel free to do the same:
https://gitlab.wikimedia.org/groups/repos/cloud/-/merge_requests?scope=all&…
If you use it and you think it's working well for most of us we can
document it as a best practice for the repos in gitlab.
Cheers!