-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 8/5/10 16:52 , yuppie wrote:
> Charlie Clark wrote:
>> I'm actively abstaining as while I understand the need to clean things up,
>> I'm not sure I understand the whole context (my lack of understanding
>> rather than any lack of explanation). CMF is actually empty, isn't it?
>> Apart from the history that is.
> 
> And these files might still contain some useful information, but need to 
> be cleaned up:
> 
> - INSTALL.txt and INSTALL_SVN.txt
> 
> - README.txt

Hi Yuppie,

You do realize if you're trying to create one "supported" buildout for
developers and end users there's a new support burden to shoulder.
CMF.buildout was explicitly billed as a developer convenience. What's it
going to be for a central CMF package?

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkxa0oIACgkQRAx5nvEhZLIyfACgtbWmxNwIEeF/yHOO6+MOFlVj
t08An3Yyo1/zSF4Zjm+MNxdEosmeoBPG
=atcK
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Reply via email to