[vorbis-dev] Hello and questions

[Monty]

> Anyways, I guess I want real CVS access so I can check the changes in, 
> and I'd like to slap the cmdline thing around a bit more to see it
> actually become useful (#if 0 suggests that the code isn't ready for
> prime time).
> 
> Whose ass do I kiss to get a real CVS account?

Mine. (Hi!)

R/W CVS access implies coordination and accountability; I'm happy to give it
out so long as that's understood.  Mike Whitson, despite not having alot of
time to work on the code, understands where the player is going as well as I do
(if not better) and has access to to large chunks of code being recycled into
the new player from a previous incarnation of Ogg.  They're not in CVS yet
and getting them there is the greatest priority in the player.  Perhaps a
temporary commit of the code in question is a good idea until it's all
reassembled.

In any case, player work should coordinate with Mike for the time being (unless
he hands that over) even if he's not doing any actual coding.  That doesn't
mean that you can't have r/w access, just be sure you know where things are
going.  If Mike is too busy to respond, I'll field coordination issues.  It's 
important to avoid committing changes that clobber another's work; folks will 
just spend time trying to win commit races.

Libvorbis changes should be discussed with me.  There's less work to be done
here than in the player and the API parts that exist should build and run.

As a summary, there's still alot of wholesale coding to be done; we're not in
an 'iterate and tweak' phase yet.  If you still want r/w access, send a note 
and it shall be done.  Keep the list informed as to ongoing work, however.

(This wasn't really directed toward ESP but the list in general so that folks 
know my take on CVS access.  Feel free to comment)

Monty

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/