[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: so what? Re: Debian development modem

On Wed, 27 May 1998, Shaleh wrote:

> I have not been paying attention that long and for that -- I apologize. 
> Frankly this is where the problem is coming from -- a group wants to be
> a RH competitor in market share or whatever and a group which wants to
> maintain a community product.  I can not see the too existing.  RH makes
> it to deadline for two reasons: they cut corners and they have paid
> staff who can be dedicated to the work.  This is the same resaon you see
> more R&D from them.  I guess the only real solution to to get everyone
> to stop and vote for a purpose and let those who want to leave go their
> own way.  Until this happens the current situation will not change. 
> Although some may not see this as a problem.  Debian is not a single
> goal project like kernel development or making a new window manager.  SO
> it is harder to shoe horn into a set path.

if there really is such a split in the goals of debian developers then
why not formalise it?

firstly, those who just want to work on producing packages and improving
debian just keep on doing what they're doing, uploading stuff into
'unstable' as always.

a second team focuses on taking the best of unstable and making a CD
release of it, making *whatever* modifications are necessary (according
to their goals) to any package AND passing those changes back to
the package maintainers.  They would also work on boot disks, the
installation scripts and so on.

a third team could focus on marketing and market research. promoting
debian and ferreting out the details of exactly what debian users (and
potential users) want, and drafting proposals (using the net standard of
"rough consensus and working code") on how to implement those wants.

it should be permitted, of course, to be on several teams at once. in
fact, it should be encouraged.

debian always was intended to be a base for other distributions, maybe
we should demonstrate how that could work by doing it ourselves....
create a little bit of separation between "back-room techs" and
"production" and "marketing".

one important point...if we do anything like this, we should make avoid
creating an "us" versus "them" attitude between the teams. focus on
co-operation between the teams who are each doing one important piece of
the work, rather than on competition and power games. 


craig sanders

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: