11:38 a.m.
With several Fedora deliverables ready (or nearly ready) to be
promoted to Edition status, we need a policy for how this will work.
After consulting with representatives from QA, Release Engineering,
and Fedora IoT, I drafted a proposed process[1]. The Council will
begin voting on Tuesday 28 July in accordance with the policy change
policy.
This has also been posted to the Fedora Community Blog[2].
[1] https://fedoraproject.org/wiki/Editions/Promotion_Process
[2]
https://communityblog.fedoraproject.org/council-policy-proposal-process-f...
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
4:10 p.m.
New subject: Council policy proposal: Process for promoting Fedora
deliverable to Edition
On Mon, Jul 13, 2020 at 12:38:14PM -0400, Ben Cotton wrote:
With several Fedora deliverables ready (or nearly ready) to be
promoted to Edition status, we need a policy for how this will work.
After consulting with representatives from QA, Release Engineering,
and Fedora IoT, I drafted a proposed process[1]. The Council will
begin voting on Tuesday 28 July in accordance with the policy change
policy.
This has also been posted to the Fedora Community Blog[2].
[1] https://fedoraproject.org/wiki/Editions/Promotion_Process
[2]
https://communityblog.fedoraproject.org/council-policy-proposal-process-f...
Looks pretty good to me, but in addtion to "holds regular public
meetings" perhaps it's worth spelling out that there should be a point
of contact or list of people to contact or a tracker to contact for
issues? It's sometimes tough to make meetings and there should be a way
to let the group know issues about their edition...
kevin
1:22 p.m.
New subject: Council policy proposal: Process for promoting Fedora deliverable
to Edition
Kevin reminded me that I never replied to this, so I'll do that now
On Tue, Jul 14, 2020 at 5:10 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
Looks pretty good to me, but in addtion to "holds regular public
meetings" perhaps it's worth spelling out that there should be a point
of contact or list of people to contact or a tracker to contact for
issues? It's sometimes tough to make meetings and there should be a way
to let the group know issues about their edition...
Agreed, but that's being covered in the team directory that Adam has
built a prototype for (see
https://pagure.io/Fedora-Council/tickets/issue/295 ), so I don't think
we need to cover it in this policy.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
1360
days inactive
1376
days old
council-discuss@lists.fedoraproject.org
2 comments
2 participants
participants (2)
-
Ben Cotton -
Kevin Fenzi