Open Stack

Hello,

First, thanks Ben for this email.

I'm personally in favor of experimenting with the DPL on oslo during W.

If nobody wants the release liaison role then I volunteer to keep this role
during W.

I also volunteer to become the meeting chair if nobody else wants that
role, we need to ensure that we continue to run our weekly meetings,
especially with a distributed governance model.

I think that our core members can match well with the majority of listed
roles and they can easily assume some of these who are not yet assigned.

Also to continue with this topic we need to follow the related process [1],
Ben do you plan to submit the related patch?

[1]
https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html#process-for-opting-in-to-distributed-leadership

Le mer. 30 sept. 2020 à 23:50, Jeremy Stanley <fungi at yuggoth.org> a écrit :

> On 2020-09-30 16:35:10 -0500 (-0500), Ben Nemec wrote:
> [...]
> > The general consensus from the people I've talked to seems to be a
> > distributed model. To kick off that discussion, here's a list of roles
> that
> > I think should be filled in some form:
> >
> > * Release liaison
> > * Security point-of-contact
> > * TC liaison
> > * Cross-project point-of-contact
> > * PTG/Forum coordinator
> > * Meeting chair
> > * Community goal liaison (almost forgot this one since I haven't actually
> > been doing it ;-).
> >
> > I've probably missed a few, but those are the the ones I came up with to
> > start.
> [...]
>
> The TC resolution on distributed project leadership also includes a
> recommended list of liaison roles, though it's basically what you
> outlined above:
>
>
> https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html
>
> --
> Jeremy Stanley
>


-- 
Hervé Beraud
Senior Software Engineer
Red Hat - Openstack Oslo
irc: hberaud
-----BEGIN PGP SIGNATURE-----

wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+
Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+
RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP
F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G
5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g
glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw
m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ
hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0
qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y
F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3
B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O
v6rDpkeNksZ9fFSyoY2o
=ECSj
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201001/fb7ed8cc/attachment-0001.html>