Jake Colman <colman(a)ppllc.com> writes:
Hello Jake,
Who do I speak to about getting cvs commit access so that I can put
the
oo-browser module under cvs control? And do I do this only after it's all
working or can I do this even if it is still a work in progress?
To answer this and your other question. I'm responsible for some of
the stuff. I can give you commit access (at the moment I need
Adrian's and Stephen's help, because I haven't yet done this).
You should send me a tarball of the sources to be used in an initial
import (along with vendor and start tag if possible). I import the
sources and you get commit access to the respective subtree. Future
mangling of the code is basically up to you. Sometimes, sweeps go
through all Makefiles, but changes to the code base are up to you. At
least someone should request your approval before committing anything
in your playground.
After you're confident the package builds for you, send me a heads up,
I hook it up and pre-release a first version of it. Yes, I'm
responsible for keeping package-compile.el in sync. Also, I change
the xemacs-packages/Makefile.
Stephen, you've got that wonderful welcome text. Could you send a
copy to Jake? Thanks. BTW, I've got no objection to the current
wording.
norbert.