> Please do not lose sight of the goal to automate this, but IMHO waiting for
> it should not be a blocker and therefore no eventual reason why it was
> moved in 2029 instead of in a few weeks :-)
I specifically didn't ask for automation or dictate how it should be
done. For example, as a stopgap, a script could notify relevant people
to fix the team membership on the GitHub side when Launchpad team
membership (or GitHub mappings, when we have that[1]) has changed. Then
they could handle it manually. That could be good enough, and that
should take all of twenty minutes to write. I'm asking that we do not
create second class citizens for the sake of some thoughtfulness and
really not very much time. Otherwise the pain is only felt by new team
members, so there is never any incentive to fix it for those who can. We
all know that this means that it will never get fixed. See today's
example at
https://lists.ubuntu.com/archives/devel-permissions/2025-August/002887.html
for an example of how not to do it. I don't want this to become yet
another "ping the right people but we're never sure who" situation.
[1] OK, that part's tricker, but we can at least do the basic thing.
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
