Aaron Griffin wrote: > On 5/9/07, James <[EMAIL PROTECTED]> wrote: >> On 5/10/07, Aaron Griffin <[EMAIL PROTECTED]> wrote: >>> On 5/9/07, Georg Grabler <[EMAIL PROTECTED]> wrote: >>>> Heya. >>> This is great, thanks a lot. I just want to comment so I can get some >>> clarity here. >>> >>>> Beryl - merged with compiz >>>> whole games section - might should be moved to a games repo, maintained by >>>> TUs >>> I think a handful of us agree that we should kill all the 'games' >>> current/extra. Would anyone have a severe problem with these things >>> moving to the AUR/community? >>> >> Um, no. This is where it becomes counterproductive. >> >> What if I want to maintain these games? Why do games get specially >> picked out, I say we remove all multimedia packages too then... you >> get the idea. >> >> Before randomly dropping things, at least see if someone wants to >> maintain them. I'm happy to maintain some more games. If you've got >> decent games and dont want them devs, ask me.
I think its not just about being willing to maintain them, its _which_ repository to maintain them in. Games don't cut across as *core* to a distro. > > I need to clarify: we are _NOT_ talking about dropping packages. We > are talking about moving them. > > There is no reason a developer cannot maintain community packages - it > is, in fact, encouraged. (And it is 2 less steps to rebuild the DB > too) aha.. that's exactly what I meant to say. > > What we are talking about is the fact that 'current' and 'extra' > DEFINE ArchLinux. No amount of wishing will make anyone ever say "Oh, > ArchLinux is that distro with Frozen Bubble, right?" - this is more > about making a refined base of packages that define us as a distro, > and pushing everything else to community. It seems like it's quite a > lot, but it makes sense. Agreed again. Small, fast, lean and extremely mean core. This kinda of stuff will be easy for the small core of devs to maintain. > > The power that comes with maintaining packages in community is > immense. It is fairly easy to bring new TUs on, and setup is minimal. > We have HUNDREDS of users to pick from. It's just such a better idea > to push things that are non-critical over there. It's a more agile > architecture. > > Let me say this, and it's something a lot of people may take issue > with: there is 0 (null, zip, none, ziltch) difference between a > "developer" and a "tu" when it comes to building packages. most > people are just as qualified, if not more. And they're underutilized. > Right now, TUs are more-or-less stuck maintaining packages that > weren't deemed "good enough to be in extra", and that's sad. Yeah... make wanna be contributors feel like second fiddle actually, but if more *usefull* stuff is moved into community, everyone feels equally committed. Eventually, we may find needs to reorganize community (maybe make more sense of the various labels), but even that is only possible when there's actually critical (but not *core*) apps in community. my 2 kobo. Cheers, Essien > > _______________________________________________ > arch mailing list > [email protected] > http://archlinux.org/mailman/listinfo/arch > _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
