Re: Committing documentation

2004-07-29 Thread Simon Pepping
On Wed, Jul 28, 2004 at 01:24:22PM -0700, Clay Leeds wrote: On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of

Re: Committing documentation

2004-07-28 Thread Simon Pepping
On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab. Indeed, it is. Does this mandate a specific

Re: Committing documentation

2004-07-28 Thread Clay Leeds
On Jul 28, 2004, at 11:51 AM, Simon Pepping wrote: On Sun, Jul 25, 2004 at 12:51:56PM -0700, Clay Leeds wrote: As I understand it, you're primarily doing documentation that is more developer and/or embedded oriented, which is one of the reasons why I would want to have a new 'Documentation' tab.

(Copyright question) Re: Committing documentation

2004-07-26 Thread Glen Mazza
I believe the key word below is transferable, i.e., before checking any work in, it still needs to be copyright The Apache Software Foundation at the time of it being cvs committed. Dirk-Willem, might you know more about this? (Original comments in [1] below.) But I noticed Simon already

Re: (Copyright question) Re: Committing documentation

2004-07-26 Thread Simon Pepping
I completely agree with Christian's comment and extract of the CLA. I have signed it and thereby it applies to any work I commit to FOP's repository. That is my intention with the documentation. I wrote 'copyright the Authors', with the idea that every contributor adds his name as an author. But

Re: (Copyright question) Re: Committing documentation

2004-07-26 Thread Glen Mazza
Simon, My past emails on this topic had a rude tone to it that I regret...I apologize for that. I just didn't know how things should be copyrighted once they're in the repository and just wanted to make sure we are doing things properly. Thanks for your work (especially since it's in Docbook ;)

Committing documentation

2004-07-25 Thread Simon Pepping
I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl

Re: Committing documentation

2004-07-25 Thread Clay Leeds
On Jul 25, 2004, at 11:43 AM, Simon Pepping wrote: I am preparing my documentation for check-in into the repository. What would be a suitable place. A directory in src/documentation/content/xdocs? Would that be in the way of the forrest build of the web site? Regards, Simon I've been thinking

Re: Committing documentation

2004-07-25 Thread Glen Mazza
Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom of any of the FOP site's web pages.) Else, best not to commit it--we can always add

Re: Committing documentation

2004-07-25 Thread Christian Geisert
Glen Mazza wrote: Simon, a word of caution*, I believe that anything that goes into the Apache repository will need to be copyright The Apache Software Foundation and only The Apache Software Foundation. (Just look at the bottom No, the contribution is covered by the CLA (which you should have