[ruby-talk:9427] Ruby CVS repositories are ready now

Hello,

It is my pleasure to announce that the CVS repositories for Ruby are
ready now.  You can walk the repositories around by CVSweb:

	http://www.ruby-lang.org/~knu/cgi-bin/cvsweb.cgi/

Then come into the following directory:

	http://www.ruby-lang.org/~knu/cgi-bin/cvsweb.cgi/cvsup/supfiles/?cvsroot=tools

and you'll find "supfiles".  With them, you can get a part of or a
whole repository by means of CVSup.  Check out the README file in the
directory for details.

	http://www.ruby-lang.org/~knu/cgi-bin/cvsweb.cgi/cvsup/supfiles/README?rev=.&content-type=text/x-cvsweb-markup&cvsroot=tools

In addition, Anonymous CVS is also available:

	$ cvs -d :pserver:[e-mail]:/ruby login
	(Logging in to [e-mail])
	CVS password:  (anonymous)
	$ cvs -d :pserver:[e-mail]:/ruby co ruby

	$ cvs -d :pserver:[e-mail]:/doc login
	(Logging in to [e-mail])
	CVS password:  (anonymous)
	$ cvs -d :pserver:[e-mail]:/doc co doc

	$ cvs -d :pserver:[e-mail]:/www login
	(Logging in to [e-mail])
	CVS password:  (anonymous)
	$ cvs -d :pserver:[e-mail]:/www co www

If you have a commit privilege, use your own account and password in
place of anonymous/anonymous.  Note that each repository has its own
access control list, so you might not be listed as committer for all
repositories.

Hereinafter I'd show some guidelines on committing in each repository.

/ruby:
	As for ruby/, matz is the boss.  You are allowed to commit
	anything without his approval.

	For rubicon/, Dave Thomas is in charge.  Ask him before
	committing anything.

	If you want to import something else under /ruby, please
	consult [e-mail].  We are open to host
	ruby-related pieces of software.

/doc:
	Pending due to some procedural issues such as synchronizing
	between	Japanese and English documents.  Leave it as is, for
	the present.  Sorry for inconvenience.

/www:
	Anything that is discussed in public (i.e. on the mailing
	lists) can be freely committed.  If you find good news about
	Ruby, feel free to write a "What's New" entry!

/tools:
	This is the repository for the CVS administrators.  It
	contains CVS/CVSup administrative files and currently I (knu)
	am the only committer of this repository.  When and if you
	have a problem with CVS/CVSup or feel any doubt, feel free to
	contact [e-mail].


Here lists some simple and important rules for committers.  Please
follow them so we can maximize the fun of hacking on Ruby!

- Do not touch the files in the CVSROOT modules.  When you need to,
consult [e-mail] first.

- Fill the commit message when you commit so that other people
(imagive weeks, months and years later) can see what you did by the
commit and why you did it.  While copying from the ChangeLog entry is
the preferred way, put a one-line brief comment at least.

- If you forget to fill the commit log, forget to add something
important, or commit with a wrong log, then do a "null commit" with
the correct log against the files you committed.  A "null commit" can
be done by doing "cvs commit -f files..".  The -f flag forces cvs to
commit even if the files aren't modified.  For that reason, "null
commit" is also called "forced commit".  It is recommended to add
something like "This is a null commit to correct the previous log,
..." so one can see afterwards that it was a null commit.

- The use of "cvs admin" is prohibited.  Never use it!  If you find
you've committed something wrong by mistake, calm yourself and try
something like "cvs diff -D'1 minute ago' | patch".  After you check
that it succesfully reverted the files you committed by mistake,
commit them back with a commit message "I'm Sorry, I'm reverting the
previous commit that I did by mistake..", for example.  If you add a
file by accident, just "cvs remove" it.  When you get panicked, just
ask [e-mail] to get things back the way they were.  No
need to worry, because anything can be backed out unless you
carelessly use "cvs admin".  If you do "cvs admin" for some reason,
let [e-mail] know about it as soon as possible.

- Respect existing maintainers, respect other committers.  The
existing maintainer may be listed in each file.  If not listed, check
out the history of the file by "cvs log" or CVSweb and consider the
one who actively maintains it as the defacto maintainer, if any.  As
for Ruby interpreter, matz is the maintainer.  If you are to change
a file that someone else maintains, send him/her a patch and ask for a
review and the approval instead of committing without notice.  It is a
good idea to add Cc: to a mailing list for peer reviews.

- When in doubt on any procedure, ask first and listen to other
people.

- Any disputed change must be backed out pending resolution of the
dispute if requested by a maintainer.  In addition, Matz has the
absolute right to decide on everything.

- Do test before committing.  For C code, check if it compiles.  For
Ruby code, check if it passes in a "ruby -wc" test.  For RD documents,
check if it passes in formatting.

That's all, folks!  Happy hacking!

(Forgive my humble English.  I wrote this in a hurry ;)

-- 
                     /
                    /__  __            Akinori.org / MUSHA.org
                   / )  )  ) )  /     FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ /  ( (__(  @ iDaemons.org / and.or.jp

"We're only at home when we're on the run, on the wing, on the fly"