On Sat, Nov 12, 2005 at 08:58:43PM +0000, James Ogley wrote: > But yes, this is an area I would see myself naturally fitting in, > assuming you mean working in a packager capacity.
No, you don't need a seat in the core team for that ;-) I meant input on how the packaging tools and build infrastructure should be developed. Incidentally, the current core team doesn't decide on that either, but the people who are actually implementing it. > > - selection of packages to be included on the base distribution. > > Again, yes, I would see this as an area to have influence in, allied > with decisions on how to package them. A good example of this (and I > know I've never added this to bugzilla - my bad) is Abiword. Again, you don't need the core team for that, but more responsive developers - point taken as SUSE R&D could (and in my opinion, should) be more active on the lists, but for this kind of package-specific discussion bugzilla is a terrific platform now that it's open. So what could a community core team member do that is not possible through "normal" contributions and discussions on this list? I am really interested and don't want to counter all your good arguments, but at the moment a large part of the core team work is more or less administrative stuff, and coordinating work with other departments (e.g. for infrastructure). Having a voice from the community right there just for the sake of it and for transparency is a major reason and we'll discuss it in any case. I just wouldn't want anyone of you to be bored in regular conf calls if it isn't worth it. Sonja -- Sonja Krause-Harder ([EMAIL PROTECTED]) Research & Development SUSE Linux Products GmbH --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
