On Thu, 2023-05-11 at 01:40 +0300, Taavi Väänänen wrote:
Hi,
On 5/11/23 01:07, Seyram Komla Sapaty wrote:
Hello Admins,
The build service is ready for the next phase, and we want to get
some
early users to test it and give early feedback!
This next step is going to start this Monday, when around 100 tool
maintainers will kindly receive an email asking them to try and
test the
service.
The full list will be made available in the task [1]
This is very different from what I was told at the Toolforge Council
meeting last week. My impression was that you'd be reaching to a
handful
of maintainers for tools we know that can be migrated to the
currently
very "Python web service without any database migrations or other
complications" centric system. How will those maintainers be
selected?
The communications regarding the release so far have been a bit vague,
this is the first one in which we aim to add more definition to it. And
yes, that means that different people understood different things,
sorry for that.
I'll let Komla reply about the process of selection of the maintainers,
but there's a few goals in mind here:
* Feedback on the build process itself
* Feedback on migration paths (so we can iterate on adding support for
those)
* Feedback on other new/unexpected use cases (so we can adapt where the
project is going)
* Help finding bugs
You can read a
draft of the email here[2]
Please clarify in the email which features are actually available
today
and which are not. Right now the draft gives an impression that push
to
deploy is currently supported, which is not true.
Thanks for the feedback, will do!
There's still many things to figure out, and
many more will show up
during this phase, your help and input will be critical in shaping
this
service.
This is unfortunately not the impression I have about this project.
Most
of the decision-making and coordination still seems to happen in
private
and undocumented spaces despite my multiple requests to get involved
in
those conversations.
I'm sad to hear that, we have made a huge effort in the last few
quarters to make sure that coordination and decisions are made in the
open and collaboratively (two different things).
That was one of the main drivers for the Toolforge Workgroup[1], the
Toolforge Build Service project page[2], and the phabricator board[3]
with iterations on it.
The only communication specific to this project that currently happens
in private (that I'm aware of) is the bi-weekly sync meeting, in which
we decide the tasks each will take for the next iteration, and then is
reflected publicly on the project board. We can consider opening it for
anyone if you are interested.
Any major decision made has been going through the public decision
request process[4], and minor decisions are either directly on-task or
on code review.
There's also twice a week "co-working space" meeting that is mostly to
pair on a specific issue or just hang out in a video call, it's more of
a social space than technical one, if you want to join you are more
than welcome to, just let me know and I'll send an invite. This one is
not related to the project though.
The use of slack channels has been reduced to daily syncs, that we are
working on moving to IRC soon enough (I raised it a couple team
meetings back[5]), but want to avoid the noise on the main channel, so
will have to figure out an alternative.
That one is not specific to the project either, and not everyone gives
updates, it's a voluntary "I'm doing this today, I need help with that"
daily message.
If there's any particular decision you think you were left out of,
please share and we'll figure out a way to make them more accessible.
Everyone makes mistakes, the important part is that we continue trying
to fix them.
[1]
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Workgroup
[2]
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Ongoing_Efforts/Toolfo…
[3]
https://phabricator.wikimedia.org/project/board/5596/
[4]
https://phabricator.wikimedia.org/tag/cloud_services_proposals/
[5]
https://etherpad.wikimedia.org/p/WMCS-2023-05-03
Taavi
_______________________________________________
Cloud-admin mailing list -- cloud-admin(a)lists.wikimedia.org
List information:
https://lists.wikimedia.org/postorius/lists/cloud-admin.lists.wikimedia.org/