On Mon, May 5, 2008 at 10:00 PM, Aaron Shafovaloff <aarons...@gmail.com> wrote:
> Is the documentation at book.cakephp.org open source?
Why do you ask?
-- Chris Hartjes Internet Loudmouth Motto for 2008: "Moving from herding elephants to handling snakes..." @TheKeyBoard: http://www.littlehart.net/atthekeyboard
I'd like to put the content in an open wiki (using MediaWiki). Yeah,
I've heard the objections ("but why don't you..."). I'm aware of what
I can already do for book.cakephp.org, and I'm aware of the pro's and
con's of an open wiki.
On May 5, 8:06 pm, "Chris Hartjes" <chart...@gmail.com> wrote:
> On Mon, May 5, 2008 at 10:00 PM, Aaron Shafovaloff <aarons...@gmail.com> wrote:
> > Is the documentation at book.cakephp.org open source?
> Why do you ask?
> --
> Chris Hartjes
> Internet Loudmouth
> Motto for 2008: "Moving from herding elephants to handling snakes..."
> @TheKeyBoard:http://www.littlehart.net/atthekeyboard
The content is owned by the Cake Software Foundation and contributed
by loyal members of the CakePHP community who value collaboration and
central location for information and resources related to the CakePHP
project. Therefore, you cannot reproduce, distribute, or prepare
derivative works based on its content for any purpose, without the
permission of the Cake Software Foundation.
> The content is owned by the Cake Software Foundation and contributed
> by loyal members of the CakePHP community who value collaboration and
> central location for information and resources related to the CakePHP
> project. Therefore, you cannot reproduce, distribute, or prepare
> derivative works based on its content for any purpose, without the
> permission of the Cake Software Foundation.
> Thanks for the clarification. I'll just start from scratch.
> On May 5, 8:56 pm, Gwoo <gwoo.cake...@gmail.com> wrote:
> > The book is open. Anyone is free to contribute.
> > The content is owned by the Cake Software Foundation and contributed
> > by loyal members of the CakePHP community who value collaboration and
> > central location for information and resources related to the CakePHP
> > project. Therefore, you cannot reproduce, distribute, or prepare
> > derivative works based on its content for any purpose, without the
> > permission of the Cake Software Foundation.
The answer seems to be because some people believe that a wiki is the
solution to all of mankind's problems. I'd rather see people
contributing to the main docs personally, since it was launched the
Book has really helped me get answers faster (there's still some
things I need to refer to the API for but that'll change as time goes
by).
Steve
On May 6, 4:34 am, nate <nate.ab...@gmail.com> wrote:
> Why? Writing a documentation resource on CakePHP from scratch is
> quite an undertaking. What could possibly be your motivation for
> doing such a thing?
> On May 5, 10:59 pm, Aaron Shafovaloff <aarons...@gmail.com> wrote:
> > Thanks for the clarification. I'll just start from scratch.
> > On May 5, 8:56 pm, Gwoo <gwoo.cake...@gmail.com> wrote:
> > > The book is open. Anyone is free to contribute.
> > > The content is owned by the Cake Software Foundation and contributed
> > > by loyal members of the CakePHP community who value collaboration and
> > > central location for information and resources related to the CakePHP
> > > project. Therefore, you cannot reproduce, distribute, or prepare
> > > derivative works based on its content for any purpose, without the
> > > permission of the Cake Software Foundation.
> The content is owned by the Cake Software Foundation (...)
Can you elaborate why is that ? Why not use GPL ? GFDL ? Creative Commons ? For me it's wierd that a community contributed documentation cannot be used by the community without an approval.
I think some people are anxious to see the enhancement tickets for the
cookbook get some kind of response, particularly the ones that give
feedback as to the status of contributed content, versioning, etc.
These are "wiki" type enhancements that would help resolve the issue
where people submit something and then wonder what happened with it -
also the issue where readers want to see how content is evolving.
Right now it's kind of a mysterious drop box that stuff goes into but
nobody knows quite what happens then, and readers see what appears to
be a rather static resource unless they happen to notice a content
change (no news/updates/new content flags), etc.
All of that is a lot of work and there are a lot of enhancement
tickets open, so I'm sure Gwoo et al. are open to developers offering
their skills. I would, but I'm busy (and getting close to finished)
updating the bakery checkout (but if/when that stabilizes, guess where
my next stop is likely to be :P)
On a side note, have you folks (those wanting to fork a doc wiki)
already tried offering to Gwoo/John to help code/write the cookbook
app and have since decided to venture out on your own, or are you just
unsatisfied with the cookbook without offering to assist and wanting
to spearhead your own idea (i.e. the better mouse trap)?
Getting traffic, nate. Getting traffic. How many projects try to benefit from the popularity of another project for the sole purpose of getting some users in, and then placing an adsense?
-----Mensaje original----- De: cake-php@googlegroups.com [mailto:cake-php@googlegroups.com] En nombre de nate Enviado el: Martes, 06 de Mayo de 2008 12:35 a.m. Para: CakePHP Asunto: Re: Is the documentation at book.cakephp.org open source?
Why? Writing a documentation resource on CakePHP from scratch is quite an undertaking. What could possibly be your motivation for doing such a thing?
On Tue, May 6, 2008 at 6:20 PM, Sliv <slivi...@gmail.com> wrote:
> I think some people are anxious to see the enhancement tickets for the > cookbook get some kind of response, particularly the ones that give > feedback as to the status of contributed content, versioning, etc.
- Where is the SVN for cookbook code? Would like see if I can help out with some patches
