Am Dienstag, 14. Februar 2006 19:41 schrieb Paul Dumais:
> Thanks, everyone for your comments. I'm not sure how commited I am to
> doing this, but I might as well take the rock soup approach. A rock
> soup is better than no soup, and everyone else can add their favorite
> ingredients to make it into something tasty.

I'm sure that I'll also try to give some ingredients for the soup!

> I like the latex approch. There is a latex to html converter that the
> python website documentation uses (at least some of it). That means we
> could just do a latex to pdf and a latex to html conversion say once
> each month after doing an svn up.

I also think that pure Latex would be the best choice. It's convertible into a 
lot different formats and can be edited just using a simple text editor.

> Should I get svn commit permission on the site and do this on
> a branch there? 

Since we need to start from scratch there is nothing to branch. ;-)
I think Jim Fulton is responsible for giving checkin permission to the Zope 

> I presume the ZPL liscense would apply in this case. 
> Would it be better to set up a repository somewhere else and use a
> different liscence (GPL, LGPL, ...)? I'm not too savy with the
> different liscenses out there. I'm happy as long as anyone is free to
> make derivative works without getting permission.
> On 2/14/06, Stephan Richter <[EMAIL PROTECTED]> wrote:
> > On Tuesday 14 February 2006 12:15, Paul Dumais wrote:
> > > Do we start from scratch?
> >
> > I think you have to, because both current books have licenses that do not
> > allow any other commercial use.
> >
> > > Can we use any of the material from Stephan
> > > or Phillip's books? The Zope 3 Developer's Handbook by Stephan Richter
> > > doesn't seem to have any copywrite notice on it (on line pdf version
> > > at least). Can someone tell me what are the restrictions on it's use?
> >
> > That is not true. The online, PDF and paper version all have an appendix
> > with the license of the book. See:
> >
> >
> >k/CreativeCommonsAttributionNoDerivsNonCommercialLicense
> >
> > > What form should it take? Should we make it a latex file and check-in
> > > changes via svn? Should it be a simple wiki?
> >
> > I would urge you to use latex or some other advanced format. ReST and
> > other low-tech solutions will not provide you the flexibility you need to
> > develop a printable book.
> >
> > > What liscense if any should the document have? How do anonymous/
> > > community users contribute and fix errors?
> >
> > If it is a community book, then make it the most open CC license you
> > possibly can.

Zope3-users mailing list

Reply via email to