Re: Interest in a xmms-dev package?

Well, the key thing here at the end of the day is
write access to the CVS respository. No matter how
many "core" developers you have, they aren't any use
until they have CVS write access.

--- Micheal Marineau <[email protected]> wrote:

> Bastiaan Jacques wrote:
> > Hi Michael,
> > 
> > 
> > I concur with your sentiment. I would like to say
> that XMMS development
> > isn't actually halted; it's just very slow. And I
> believe this is
> > because there is only one active maintainer,
> Håvard Kvålen, and he seems
> > to have very little time. I think one or more
> maintainers should be
> > added so that patches can be reviewed quickly. Of
> course, we would need
> > to motivate Håvard to do so; however, he seems to
> be of good will.
> > 
> > I personally think it is better to see if the
> current team can be
> > expanded than to fork the code and create a split.
> A healthy production
> > environment is already in place - bugzilla, cvs,
> etc.
> > 
> I agree that expanding the xmms team would make more
> sense than a fork,
> and even if there was a fork I would hope that it
> would eventually get
> merged back into xmms.  The only reason why I
> brought it up was in
> responce to the thread from last month where a
> number of people showed
> interest in a new tree to give some of the long
> ignored patches floating
> around some light of day.  I just hate to see xmms
> fade into the past.
> Does anyone have any suggestions for what would be
> nessicary to open up
> development a little and give it some life?
> 
> -- 
> Michael Marineau
> [email protected]
> Oregon State University
> 

> ATTACHMENT part 1.2 application/pgp-signature
name=signature.asc
> _______________________________________________
> xmms-devel mailing list
> [email protected]
> http://lists.xmms.org/mailman/listinfo/xmms-devel
>