[Pkg-tcltk-devel] first things first

[Chris Waters]

Ok, this is taking too long.  Sorry.  I guess I keep hoping that
things will spontaneously self-organize, which is silly.  But then, if
I had time to do everything that needs done, I wouldn't be trying to
organize a team to maintain tcl/tk in the first place.

We need to set up our SVN space, so that team members have somewhere
to collaborate, and so that non-members can more easily contribute as
well.  Then we need to get packages with the team listed as maintainer
uploaded to the archive.  With a debian freeze coming up soon, we
probably don't want to get too ambitious at first--but with SVN, we
can always set up experimental branches if we really need or want to.
But our immediate focus should be etch, and what needs to be done for
that.

SVN documentation is on-line at http://svnbook.red-bean.com/

I chose SVN for the usual reasons: it's a big step up from CVS, but
similar enough to CVS that there shouldn't be a major learning curve
for most people.  Since most of the upstream projects use CVS, this is
a fairly important factor.  Many of you are probably already familiar
with SVN.  Me, I've used it a little, but this will be my first
serious attempt to set up a repository.  So bear with me, and feel
free to shout advice.  In fact, please shout some advice, ASAP!  :)

Anyway, pretty much the first thing we're going to need to do is
decide on a layout for the SVN repository.  We're going to have
multiple modules, one for each source package, so we're going to need
a non-trivial layout.  The obvious default is to have package names at
the top level, and trunk-tags-branches below that, but other
suggestions are welcomed.

I'd like to use debian svn-buiildpackage for the actual building of
packages, so that may constrain things a little.  I've used
cvs-buildpackage for years, but never svn-buildpackage, so we may need
to consult with some people with svn-buildpackage experience.
Unfortunately, svn-buildpackage does not seem to be just a drop-in
replacement for cvs-buildpackage, but it can't be too complicated, or
someone would have shot the maintainer by now!  :)

All team members, and anyone else who's interested in contributing or
helping with this project should make sure they have the
svn-buildpackage package installed.

Anyway, there's some immediate goals.  Hopefully that will be enough
to get this thing started.

cheers
-- 
Chris Waters           |  Pneumonoultra-        osis is too long
xtifr at debian.org       |  microscopicsilico-    to fit into a single
or xtifr at speakeasy.net |  volcaniconi-          standalone haiku