Tuesday 23 October 2007, Jaroslaw Swierczynski wrote:
| 2007/10/23, gan lu <[EMAIL PROTECTED]>:
| > Moving a package to community is more due to "No dev wants to
| > maintain (without time or interest)" than "it's not popular"
|
| If a package is important to the distro, there will be a dev who
| wants to maintain it. If the devs don't have time and there is a
| popular demand for a package, the package should be maintained in
| community by a _TU_. If a package is not important nor popular,
| and there is a dev or a TU that happens to use it, IMHO the
| package should be in a binary repo BUT the repo should be extra if
| the maintainer is a dev or community if the maintainer is a TU.
| Otherwise the package should be dropped to unsupported. That's how
| I see it.
i share this view with one important addition:
if a pkg is system crucial, it must be maintained by a dev (inside
core)
if a pkg is a crucial dependency to other pkgs, it must be maintained
by a dev
- D
--
.·´¯`·.¸.·´¯`·.¸¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸.·´¯`·.¸¸.·´
° ° °
° ° °
><((((º> ° °
° °
° <º)))><
<º)))><
_______________________________________________
arch mailing list
arch@archlinux.org
http://archlinux.org/mailman/listinfo/arch
