On Wed, Jun 11, 2025 at 3:08 PM Robie Basak <robie.basak@ubuntu.com> wrote:
> > So something like a 2-year term a volunteer commits to. Perfectly fine
> > (not ideal) to step down at any point in time. And should ask TB to
> > run again when their membership is about to expire (like T-30 days or
> > something).
>
> To save on admin, would you consider it sufficient to use Launchpad's
> team membership expiry feature? We could set the term to two years in
> Launchpad, and allow members to self-renew with the usual explicit
> affirming action. If a member doesn't want to make a further two year
> commitment, they could then allow their Launchpad team membership to
> lapse with no further action. It'd be nice to communicate with the DMB
> and TB at the time, of course, but we don't have to make that a
> requirement.
That'd be good, yes. +1.
Whilst at it, might I suggest the DMB terms to be 1 year with
self-renew instead of 2 years? This will at least aid the volunteers
in feeling less committed if they wish to apply at all.
> I'd be happy to document what the TB and DMB take the team membership
> term, expiry and self-renewal to *mean* in a policy document - that
> would be a straightforward, bounded and one-off task.
Definitely. +1.
- u
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
