From: "Sean E. Russell" <ser@...>
Date: 2004-02-12T05:36:18+09:00
Subject: Re: Standard libraries


--Boundary-02=_fIpKAcPuTFODko/
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 11 February 2004 14:36, Dave Thomas wrote:
> I'd like to propose two more criteria.
>
> 1. Nothing new gets added without complete documentation

This is interesting.  Where, in CVS, should the non-sourcecode documentatio=
n=20
go?  Are we encouraged to start making directories in ruby/doc?  For that=20
matter, where's the official location for unit tests and all the extra bits=
=20
of a project?

In the short time that I've been maintaining REXML in the Ruby tree, I've=20
found it rather difficult to maintain because I'm maintaining two distinct=
=20
source trees.  It is unlikely that I'll ever use the Ruby CVS as my primary=
=20
source repository, but it would help if I had the entire REXML tree in ther=
e=20
somewhere, so that I could easily run tests.

> 2. For every library that gets added, another existing library should
> be removed (using deprecation initially, but actually removed
> eventually).

What happens when some new functionality gets added?  IE, what do you=20
deprecate when LDAP support is added to the library set?

=2D-=20
### SER  =20
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Aikido
### http://www.germane-software.com/~ser  jabber.com:ser  ICQ:83578737=20
### GPG: http://www.germane-software.com/~ser/Security/ser_public.gpg

--Boundary-02=_fIpKAcPuTFODko/
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAKpIfP0KxygnleI8RAszxAJ9/+i+v0KUiDjPxJ0ItQrY6tETlAgCfacxb
Oa40dLISYSHYLHxMXgCguNI=
=tNdN
-----END PGP SIGNATURE-----

--Boundary-02=_fIpKAcPuTFODko/--