Am Dienstag, 8. Mai 2007 22:30:59 schrieb Tobias Powalowski:
> Hi
> something is really going wrong at the moment.
> People claim for having other interests or not time for doing the packaging
> work.
> I start here only with [current] first.
> Jan quit doing maintenance of important parts of our distro and probably
> also of doing quite some update tirades through current.
>
> Let me stress this, from my point of view Jan and me did the most [current]
> updates the last weeks, even if we didn't use the software for our own
> stuff, correct me if im wrong.
>
> We have inactive package maintainers, no doubt.
> Judd, Dorphell, Aurelien, Gregor, Woody, Arjan
>
> It's time to cleanup [current].
> Orphan all packages of Judd, Dorphell, Aurelien, Gregor
> 1 week of time to grab what packages you wanna have.
> Keep in mind it's your job then to test and ensure that the package works!
> Please one of the enablers do this, or give me the permission to orphan
> them.
>
> After that period, look whats left if noone feels responsable for a package
> make a list of possible drops or try to find one on ML who wants to
> maintain it. It's better to have 1 maintainer for just 1 package who is
> active and knows the package well, then 1 who just cross updates because he
> saw the version bump.
>
> come on guys participate it's the base of our distro!
> Without it Arch cannot work.
>
> greetings
> tpowa

Well, I see the point. Perhaps there too much packages in [current] and 
[extra] for too few devs. (compare: there are less packages in [community] 
but we have more active TUs than Devs)

I don`t see any problem in stripping down [current] and [extra] to only those 
packages which are really used. E.g. there are some experimntal ones like 
beryl, several unstable kernels like ck, beyond, mm etc. which will do well 
in [community].

Perhaps there should be a guideline which package has to be part of the core 
distribution. For example: if a TU becomes a DEV he often moves all his 
packages to extra. Esspecially for Arch64 this causes some problems because 
we TUs wont be able to help by porting those packages.

Pierre

_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch

Reply via email to