I guess it's OK if we have enough dev sources, so we can afford to maintain a big mount of extra packages. Moving a package to community is more due to "No dev wants to maintain (without time or interest)" than "it's not popular", in fact I think it's a choice of reality we can't help out right now. Or can we put forward to accept more TU as dev? And package in community does have high quality in my opinion.
On 10/23/07, Jaroslaw Swierczynski <[EMAIL PROTECTED]> wrote: > > Excuse my butting in but I'd like to express my opinion on this. IMHO > the devs shouldn't have access to community. If they want to mantain a > package, why not just do that in extra. Even if it's used by only a > few people, so what? Moving a package to community because it's not > popular is not right, it distorts the idea and purpose of community. > Let me remind you that community is supposed to be a place where > popular user-contributed packages go. If a dev feels that a package > doesn't belong to extra (for whatever reason), he should drop the > package to unsupported. Then if a TU feels that the package should be > in community (again, for whatever reason), he will move it there. > Please don't consider community a place for worse packages, it's not > its purpose! > > -- > Jaroslaw Swierczynski <[EMAIL PROTECTED]> > www.archlinux.org | www.juvepoland.com > > _______________________________________________ > arch mailing list > arch@archlinux.org > http://archlinux.org/mailman/listinfo/arch >
_______________________________________________ arch mailing list arch@archlinux.org http://archlinux.org/mailman/listinfo/arch
