Friday, April 3, 2020

Re: A Community Change process to mirror the System Change process

On Fri, Apr 03, 2020 10:13:47 -0400, Ben Cotton wrote:
> On Fri, Apr 3, 2020 at 10:08 AM Matthew Miller <> wrote:
> >
> > On Thu, Apr 02, 2020 at 09:54:30PM +0100, Ankur Sinha wrote:
> > > Maybe we shouldn't overthink this and go looking for a new "perfect"
> > > process. Let's just adapt the current change process, which we know
> > > works, and then tweak it later? Nothing in Fedora is written in stone. :)
> >
> > This all sounds good to me. :)
> >
> As Jean-Baptiste pointed out, we can already use the Changes process.
> So maybe let's just start there. Like I said, creating a new process,
> even one that is very close to the existing Changes process, is more
> complicated than it looks on the surface.
> I think what may be needed here is policy (well really guidance), not
> process. I'm going to try really hard to come up with something
> specific to discuss that may address the concerns without requiring me
> to develop and manage a new process.

I wasn't thinking that this would be managed by the FPgM at all
actually. Community changes do not necessarily sync with the release
cycle, so I was thinking this process would be largely independent of
it, and thus not something the FPgM (who is in-charge of running the
release on schedule from what I understand) would oversee.

My initial thought would be that Mindshare/CommOps (community
operations?) would oversee it. The process remains similar to the change
process, the template remains similar, what is done in Bugzilla can get
implemented in Pagure (or any other ticket platform that we end up
using), and a set of people would do what you do all by yourself.

Any Mindshare/CommOps folks here to weigh in? :)

(I'm not officially on either team, so I don't want this to come across
as me volunteering people to do more work. I've always assisted whatever
team can use me, so I'll keep doing that. The idea is just to ensure
that changes in the community are treated the same as the engineering
related changes currently are.)

Ankur Sinha "FranciscoD" (He / Him / His) |
Time zone: Europe/London

No comments:

Post a Comment