Greetings,
I'd like to start contributing to Subversion, having read this list
for some time and haunted #svn for a month or so. Heresay has it that
the manpage documentation needs a maintainer. My commitment to
Subversion at my company is already such that I must know it as well
as I can, and can only benefit from being closer to reference
documentation. What, then, could be better than contributing to the
docs?
Chatting with Ben Collins-Sussman about documentation, we discussed
the possibility of me maintaining the manpages. The users I support
have been requiring that I write them additional documentation on our
Wiki so they can spend their time hacking product code instead of
fully appreciating Subversion. I'm priveleged, in a sense, to have
the full range of users, seasoned developers to others that remind me
every time I fail to put things in most approachable terms. Let me
know what to do, I can send patches of the nroff documents, or
participate in whatever way you like while I get sufficient clue about
your subversive ways.
I work at a software company in the Boston area with >100 developers
and doc people and am tasked with bringing them under one SCM from the
several we currently employ, both commercial and free. It may be
amusing that what hinged on my decision to not go with CVS was not
whether Subversion was better, but that on April 16 (0.21.0) the
downloads page and INSTALL indicated that Subversion was STABLE and
its production use was being recommended. These words, among other
things, were enough for me to justify (in a meeting) this leap. My
name is on the line with this choice, and my company has promised to
invest more than my time if this story proves to be a successful one,
in review. Go Subversion! :-)
Many of our people write programs on fine IBM Mainframes, and I can
provide testing environments on several of these platforms (MVS, VM,
PPC64 Linux, aka P-Linux or Suse Enterprise, and Z-Linux), along with
most Unix, and that other OS. We've managed to compile CVS under the
USS (Unix System Services side of Z/OS) side of these machines and are
about to try building Subversion there. Trust me, it will be nothing
short of radical to have mainframe programmers using modern SCM
practices. Educating and supporting them will dwarf the task of
getting things to build, I suspect.
Having just entered a few weeks of harmless, non-production testing,
my users are already saying the stock, command-line will not be
enough, that they want the tools that are most Suave! I'm trying to
grok how the python binding work because that will be the best way to
do it, right? Finally, I must say that the doxygen output of the
Subverion internals is an inspiration and that I'll have to implement
it at our company.
Good Day,
Toby
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 30 00:05:28 2003