Previously Maurits van Rees wrote:
> Jens Vagelpohl, on 2008-05-29:
> > On May 29, 2008, at 04:19 , Philipp von Weitershausen wrote:
> >> 
> >> http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt
> > Ah, good resource, thanks for pointing that out.
> > Thanks to everyone for the input. I'll go with putting the license
> > file right with the software instead of into a docs folder at the top
> > where setup.py resides. I find it more intuitive to have all
> > documentation where the software is, and leave the "egg scaffolding"
> > in a state where you don't have to touch anything "up high" once it's
> > working.
> Suits me fine. Anyone in favour of updating the ZopeSkel templates to
> fit that pattern? (Sorry, bit out of topic here on the cmf list as
> there are no cmf skeletons there. Care to add one? :-))
I want all documentation to be the first thing I see when I unpack
something. I don't want to be forced to delve into 3 or 4
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests