I have created a Wiki entry under Community Efforts, called Area for Development of Wiki Entries. After an introduction, I've created a proposed Table of Contents for the Wiki. Because Akelos is a port of Rails, I am afraid of creating a documentation structure that looks too much like anything in Rails. (I already did that once.) Therefore, I want your OK before I proceed with this.
Alan,creating documentation that looks like something in Rails is OK while that content is licensed on a way we can use it without copyright issues. We do not want to be sued by copyright owners.
Salavert told you it was not OK to cut and paste a copyrighted book into the wiki. We can take content which have MIT license like the API docs or the rails documentation project. We can also take content from creative commons sources that allow us do adapt the content.
I think Salavert and Kaste will agree with me. ¿Don't you?
I know I don't want anyone to be sued. While I did cut and paste from the book, I altered everything to refer to Akelos and PHP, not Rails and Ruby. I tend to think "moral" rather than "legal" and here I am, a citizen of the most sue-happy country in the world as far as I know. What I produced would not have been competitive to the copyrighted book in any way.
My question this time around was that the Table of Contents that is now on the site is an altered copy of the TOC from the same book. I just don't know how different a document must be from a copyrighted work in order to be considered legally original. I just hope that the TOC is different enough.
I wanted you all to know just what I did, so that you wouldn't be unpleasantly surprised by some allegation.
Frankly, I hate to write documentation anyway, but when I have to work as hard as I have to find out how to do something, I want to note it so that the next person can profit from my experience.
1 to 3 of 3