On Tue, Jul 06, 2010 at 01:26:21PM +0200, Thomas Spura wrote:
> If this is implemented, the 'next' co-maintainer should become the real
> maintainer after another 8 weeks non-commiting by the former maintainer.
I think this is another problem with pkgdb or Fedora. Why is there a
maintainer ("owner"?) and co-maintainers, rather than just having all
co-maintainers be equal?
As people know, my default position is for inclusion: we should try to
include as many packages in Fedora that we can, except where there is
a legal or insuperable technical problem with that.
So I think it's valid for packages to have 0, 1, 2, or more
maintainers.
If #maintainers == 0 then the package is either just sitting there (as
long as there are no serious bugs), or is being best-effort maintained
by provenpackagers, at least until that becomes a burden and only then
should the package be dropped.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://et.redhat.com/~rjones/libguestfs/
See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
