On Dec 29, 2007, at 6:51 AM, gobblez wrote:
> Perhaps the official tutorial should be un-deprecated? Maybe add
> comments where people can chime in, php.net or Bakery style?
It's in the works. I'm moving manual content to the new system already.
> Would it
> really take more than 20 minutes to update it or move it to the Bakery
> (so people can add updates to the same page without the author lifting
> a finger) and change the link?
Most likely, especially given the fact that it hasn't been done yet. I
should mention that someone has taken the assignment and is currently
working on upgrading the blog tute for 1.2, however.
> The repeated "n00bie blog tutorial
> questions" that bug you guys so much (enough to warrant internet tough
> guy sarcasm) could/should have been solved/prevented a long time ago.
> People shouldn't have to be familiar with some guy's third party blog
> for a workaround or solution.
I totally agree.
> After so long and it being brought up
> all the time, you'd think somebody on the dev or doc team would
> notice. Now go ahead and reply to me with some sort of lecture where
> you talk about open source (as if people having trouble with the
> beginners tutorial are really capable of submitting a patch or making
> sense of "trac")
I think I will. You're mentioning it like that doesn't make it any
less valid.
If you are noticing critical problems that are easy to solve, that
aren't being solved, I suppose that could mean at least one of two
possible situations:
1. The Cake team is inept.
2. The Cake team is spread thin.
Choose whichever suits you best.
Beginners can feel free to submit solutions (especially documentation
solutions) in whatever format they prefer. There is nothing stopping
new people from submitting bits of documentation, or at least logging
tickets. Right now we've only got a baker's dozen worth of tickets
related to documentation. We're really focusing on doing better at
that, so please feel free to jump in and help out there by submitting
tickets. The very best solution is to supply some sample documentation
to fix things, but even a note on what you think is missing is better
than nothing. Most definitely better than a rant on the mailing list.
> and shift responsibilities away instead of
> considering that fixing the tutorial is a simple solution that makes
> sense and would benefit the project and is a no brainer that it should
> be done. kthxbai.
Interesting to note that this tirade seems to try to shift that
responsibility away from yourself as well. Given the "no-brainer"
benefit of your proposal, one wonders why you haven't volunteered to
complete it. The fact that you haven't yet may be the answer to why it
isn't yet done. It's not a matter of "brains" it's a matter of
priorities and available bandwidth.
No, I can take responsibility for the state of the documentation. I
don't expect the community to do it all, but I do expect those who
complain to at least attempt to help out. You should also be aware of
the fact that 1.2 is not yet even beta software. I think what we've
got up at tempdocs.cakephp.org is not unreasonable, since technically
you're using a developer version that was never meant to be as
documented as it is anyway.
Next time, please consider contributing in a positive manner.
Thanks,
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
-~----------~----~----~----~------~----~------~--~---
