Hi John!

As I have stressed few threads ago, I do agree with you, we should not
fork or split our efforts on documenting CakePHP. I am just worried
about licensing issues, which would - at least in my thoughs - give a
fright on independent initiatives; and availability of resources, such
commenting and some sort of professional knowledge networking.

I speak Portuguese, as mother tongue, and I would be very glad on
joining you guys either producing documents in english as much as
translating them into portuguese.


Uldérico

On 19 jun, 19:14, "John David Anderson (_psychic_)"
<[EMAIL PROTECTED]> wrote:
> On Jun 19, 2007, at 3:45 PM, Finster wrote:
>
>
>
> > On Jun 19, 3:03 pm, "John David Anderson (_psychic_)"
> > <[EMAIL PROTECTED]> wrote:
>
> >> Why would you need to distribute the docs when they're already freely
> >> available?
>
> > Because they are, like the wiki apparently was, outdated. The manual
> > is great, but there is a LOT of stuff in there that is out of date.
> > And most of it has been addressed by bug submissions to
> > trac.cakephp.org. Why are these bug reports ignored? Who knows, but
> > all this complaining about the outdatedness of the wiki also applies
> > to the current manual as it stands now.
>
> Maybe it does, but there's a limited amount of resources helping out  
> on the docs. Last month there was one person working on it. Thanks to  
> some great people, that's now up to 5 or 6. I've made the decision to  
> place most of our efforts towards the 1.2 manual rewrite.
>
> Maybe I'll have to rethink that, but I think we can limp along with  
> what we've got until 1.2 comes out.
>
> -- John


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to