Max Spevack wrote:
>
Ok, comment, flame me, tell me how I'm out of touch and all of this is
already spelled out somewhere that I just haven't seen. :-)
I'm a non @redhat.com-er, but I like what I see! no further comments,
except for one:
> 2) Once a package passes review, a couple of things have to happen
> a) Current maintainer (someone who is @redhat.com) needs to agree to
> a freeze.
> b) Current maintaner needs to get a Fedora account.
> c) Package's "upstream" is moved from internal CVS and build system
> to external CVS and build system (basically Extras)
> d) Current maintainer decides if anyone else should have
> "maintainer" ACLs at this time
I would like to see the current maintainer encouraged to seek out
interested community members here. Many core packages have many bugs
open against them, in some cases that is because there are many bugs for
a package which are hard to fix, take the kernel for example. In other
cases however most of the many open bug are purely a matter of not
enough time getting invested into the package (for whatever reasons, I'm
not trying to judge anyone here). I believe that in the not enough time
invested cases the package and thus Fedora could benefit enormously from
the help of one or 2 interested community members.
Let me put my money where my mouth is, if any core package maintainer
would like a hand and is serious about this. Then drop me a mail with a
couple of BZ id's you would like a hand with, or a package name for
which you want me to go through bugzilla and fix any bugs against that
package in general. Note you should be willing to treat me as a fellow
developer and not as some kinda newbie (which I'm not).
> e) Development resumes
>
Regards,
Hans
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
