Re: Collective maintenance

["Jon Ciesla" <limb jcomserv net>]

> Hi,
>
> A friend of mine pinged me and asked about the status of this bug
>
> https://bugzilla.redhat.com/show_bug.cgi?id=442921
>
> Just using this as an example here since it a simple one. This is
> apparently just a simple missing dependency but hasn't been fixed in a
> while. Just using this as a example, assuming that the maintainer is
> busy, on vacation or something and cvsextras is open, many others could
> fix this issue bypassing the primary maintainer for the moment but there
> doesn't seem to be any policy on what kind of fixes can be collectively
> done. I remember seeing similar discussions before so this isn't a
> isolated problem. Do we need some guidelines on this so folks like
> Michael Schwendt (again, just as an example specific to this bug report)
> can just go ahead and fix the problem noting the details in the commit
> message instead of having to file a bug report?

My left brain side says, maybe we need a policy.  My right brain side
says, if the acl is open, and you can fix it, fix it.

Might actually check out doing that on some easy bugs I've reported.

-J

> Rahul
>
> --
> fedora-devel-list mailing list
> fedora-devel-list redhat com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>


-- 
novus ordo absurdum