Source code of the cookbook application has been released

Published on and tagged with cakephp  project

Today, Andy Dawson (aka AD7six) announced in his blog that the source code of the cookbook application (which powers http://book.cakephp.org) is now available for everyone: http://thechaw.com/cakebook.

As you can see from the url, this project is hosted in a different place than other projects from the Cake team. It would be good if all such projects would be consolidated in one single place.

Anyway, here a list with places from where you can get the source code of those projects:

Update 2008-11-21: See also the official announcement of The Chaw.

30 comments baked

  • gwoo

    I have to say, once again your tone is obnoxious.

    We release a piece of hard work for the world and all you can say is its not good enough because its hosted in another place. Of course, you failed to realize that exact goal behind http://thechaw.com is to consolidate things into one place.

    Have a nice day.

  • phishy

    why must you hurt people’s feelings?

  • rafaelbandeira3

    well done putting it all together Daniel.
    must say that, although thechaw looks pretty good and that it has a lot of potential, I was really hoping to see it all being forked and commented all over github till the end of the year, no luck though

  • cakebaker

    @gwoo: Calm down.

    I didn’t say anything about the application not being good enough. I simply described the current state of six projects in five different places, and came to the logical conclusion it would be better to have everything in one place. So what? What’s wrong with that? It’s feedback for you that something could be improved…

    And whether The Chaw is the future place for all projects is not evident for an outsider, it could also have been github, or something else.

    @phishy: Why must you ask such a biased question?

  • nate

    @cakebaker: Interesting that you start from the assumption that Garrett is not calm. ;-) Sounds to me like a biased statement. Once again, you examine everyone’s biases but your own.

    As to the fact that several projects are hosted in different places, I a colloquial rejoinder would be [sarcasm] Thank you, Captain Obvious! [/sarcasm]

    Everyone is already aware that the hosting of CakePHP projects is currently fragmented. Further, from Garrett’s statement, it is clear that we are in a period of transition, but it doesn’t surprise me that you fail to see that, or that hosting an official project on GitHub was a strategic part of this transition.

    As everyone can now see, we are already moving in the direction of unified project hosting. Pointing out the fact that we’re not there now helps no one. The transition process takes a lot of work to ensure that things go smoothly, and that the community is served.

    If you wish to give feedback, please find feedback that can actually help, rather than feedback that is simply critical and self-serving. If you or anyone else has a question about the state of the project or the reasons for it, any member of the team is readily available for comment by many different means of communication.

    Given that, it is not necessary for you to feign ignorance, unless you specifically have negative intentions.

  • Ian

    Sorry CakePHP Team, I’ve had enough.

    From a completely un-biased standpoint, I saw absolutely no hostility in cakebakers’ statements – even after gwoo’s comments, I re-read his post and still couldn’t find hostility.

    But, unfortunately, that’s the straw that broke this camel’s back. I’m sick of the childish behaviour of the CakePHP community and I’m done with it. Zend Framework, here I come.

  • Joel Moss

    Well that was blown way out of proportion! Calm down guys.

  • Daniel

    Honestly guys… I happen to agree with Ian although I can’t just up and leave(got projects on Cake). But if the dev team can’t handle things in a more mature way than this I’ll start looking at Akelos for future projects. All that gwoo had to say was:

    “We are transitioning things to this new site, The Chaw, but it will take a while. Look for an official announcement shortly.”

  • The Mullet

    I fully understand the disappointment that gwoo and nate feel when daniels blog simply abuses the event that something good has been released for adding another entry to his never ending bashing on the CakeDevs. Daniels motivation is cheap: he still has not gotten over being removed from the core team after not contributing anything of value for months.

    “Captain Obvious” – thats really a great name for this blog, too, which once was arguably the best on Cake. These days, daniel produces almost nothing of interest. Unfortunately, he uses the little power he has built through this blog to simply enervate people. And whoever Ian (who turns his back on cake) is: grats Daniel, today you have reached your goal of damaging the cake world once more.

    Hope you are proud of your achievement, Daniel.

    Gwoo, nate… daniel is not worth it. Just ignore him, Keep cool when reading his worthless tickets, and be assured that there are many people out there who are aware of how inexpressibly ridiculous his behavior is.

    And also be assured that many people understand and appreciate how much quality work you give to us through the framework.

  • Brendon Kozlowski

    Lack of information/communication + actual observation + assumptions = greater communication breakdown.

    Pretty sure if Dawson’s blog post also mentioned the reasons for it being located elsewhere there wouldn’t be any confusion, and it’d be a completely positive post we’d be reading here. Yes, there is some noticed negativity, or perhaps concern, in Daniel’s post. Is it unwarranted? Perhaps, perhaps not. I don’t believe it was meant completely as a stab at anyone or anything…nor do I blame Dawson for sharing his news in earnest, it’s a great effort that *everyone* will be excited about, and I’d encourage him to start blogging again, regardless of this fragmented communication between Daniel and core team members’ plans or roadmap. Increased communication is a two-sided sword, it increases awareness, but it can also raise more questions, concerns and unwarranted comments or criticisms. But, we all have to take the good with the bad.

    As far as Daniel not providing any useful information, I tend to disagree. I’d rather not point out specifics as I feel it’s unnecessary, and as it is a blog he’s able to be bias (though should also be wary as with “power” comes “responsibility”). Either way, overall, this is still great news – even if I did read it on Dawson’s page first (and also wondered why it wasn’t on Cakeforge, so now I know).

  • Thomas

    Great Comment, Brendon :)

    Some things went terribly wrong here somehow. A striking number of posts seem to me like their writers perhaps reacted a little “touchy”…

    Like Ian, I also view Daniels blog from a perhaps more objective (outsider’s) point of view. And for someone like me I agree this post does not contain any striking hostility towards cake.

    So here are my thoughts:
    Obnoxious tone – did gwoo perhaps react a little too TOUCHY after having had a load of work and perhaps expecting more credit for it? Maybe he overreacted.

    Ian “being done” with CakePHP because of bagatelles like unfortunate comments instead of the framework’s (great) quality… also a little TOUCHY and overreacted?

    The Mullet: Perhaps you (and the cake devs, too) should be more worried that the once core-developer Daniel turns his back on cake, not one “simple” (no offense intended) user like Ian. I think Daniel would be a far greater loss to the CakePHP community than a cake user. Dan’s blog contains many VERY useful hints (especially for newbies and intermediate bakers).

    ad hominem things like

    "obnoxious",
    "it doesn’t surprise me that you fail to see that",
    "Captain Obvious",
    "daniel is not worth it",
    "you have reached your goal of damaging the cake world",
    "his worthless tickets",
    "how inexpressibly ridiculous his behavior is"

    do not help anybody – who ever wrote it. And it this what’s hurting the CakePHP community: fights between core and ex core developers that should not be fought in public !!!!
    I wonder: is it Daniel bashing on cake or the cake devs or the cake devs bashing on Daniel? Or can they agree that perhaps it is a little of both?

    My suggestion (especially to The Mullet) is to encourage Daniel to write more kick ass cake posts of great quality and maybe this blog will stay / re-enter in the top 5 of “the best on cake”… Daniel, I think your blog is great and it has already helped me a lot of times. Keep up the great work.
    Core devs: CakePHP is awesome, thank you for the great work and keep it up!

    daniel, gwoo, nate and who else it may concern: Pleeeeeeeaaaaaase settle your differences in private and spare the community. I as a user feel awkward and think it is embarassing. There must be a way!

    To everybody: read http://www.wikihow.com/Give-a-Feedback-Sandwich.

    Gute Nacht !

  • Thomas

    Great Comment, Brendon :)

    Some things went terribly wrong here somehow. A striking number of posts seem to me like their writers perhaps reacted a little “touchy”…

    Like Ian, I also view Daniels blog from a perhaps more objective (outsider’s) point of view. And for someone like me I agree this post does not contain any striking hostility towards cake.

    So here are my thoughts:
    Obnoxious tone – did gwoo perhaps react a little too TOUCHY after having had a load of work and perhaps expecting more credit for it? Maybe he overreacted.

    Ian “being done” with CakePHP because of bagatelles like unfortunate comments instead of the framework’s (great) quality… also a little TOUCHY and overreacted?

    The Mullet: Perhaps you (and the cake devs, too) should be more worried that the once core-developer Daniel turns his back on cake, not one “simple” (no offense intended) user like Ian. I think Daniel would be a far greater loss to the CakePHP community than a cake user. Dan’s blog contains many VERY useful hints (especially for newbies and intermediate bakers).

    ad hominem things like

    "obnoxious",
    "it doesn’t surprise me that you fail to see that",
    "Captain Obvious",
    "daniel is not worth it",
    "you have reached your goal of damaging the cake world",
    "his worthless tickets",
    "how inexpressibly ridiculous his behavior is"

    do not help anybody – who ever wrote it. And it this what’s hurting the CakePHP community: fights between core and ex core developers that should not be fought in public !!!!
    I wonder: is it Daniel bashing on cake or the cake devs or the cake devs bashing on Daniel? Or can they agree that perhaps it is a little of both?

    My suggestion (especially to The Mullet) is to encourage Daniel to write more kick ass cake posts of great quality and maybe this blog will stay / re-enter in the top 5 of “the best on cake”… Daniel, I think your blog is great and it has already helped me a lot of times. Keep up the great work.
    Core devs: CakePHP is awesome, thank you for the great work and keep it up!

    daniel, gwoo, nate and who else it may concern: Pleeeeeeeaaaaaase settle your differences in private and spare the community. I as a user feel awkward and think it is embarassing. There must be a way!

    To everybody: read http://www.wikihow.com/Give-a-Feedback-Sandwich.

    Gute Nacht :)

  • ajmacaro

    Hey ALL! there is nothing to argue here!
    “COOKBOOK SOURCE CODE! HAS BEEN RELEASE!”

    There is nothing more important thing than that, right now!

    @daniel : everyday i read your blog, but sometimes you sounds like you
    are preaching the cakedev’s on what they must do or how they must do
    their jobs. cake devs are humans too.

    @cakedev’s : Thank you for all the hard work!. but right now the only
    thing that makes me wonder is. whats with the name? “thechaw”? if you are
    planning to surprise us. you dont have to answer now. i can wait till
    christmas. :)

  • Manny

    @daniel, no idea why you’ve got a target on your head. But I love the drama. BTW, I didn’t see any maliciousness in your entry.

    Here’s an outsiders perspective. Toyed with cake 1.1 but bailed after no doc’s, unstable code, suspect performance and unstable dev team. No idea what’s changed except for doc’s! I’m only going to try cake when it reaches 1.2 PRODUCTION ready code.

  • The Mullet

    Brendon:
    >My suggestion (especially to The Mullet) is to encourage
    > Daniel to write more kick ass cake posts of great quality

    Well, if you go back a little to Daniels recent post on helper callbacks which offer some insight on how shallow-brained Daniels research is, I am not sure how much encouragement is needed to bring him up to speed with the developments in the Cake world.

    But I have no problem with Daniel writing stuff that is only of concern for people who cannot see the simple things.

    What I do have a problem with is that Daniel is using almost every chance of annoying the Core Team members and distracting their valuable time through posting and ever re-opening worthless tickets which almost always carry notes like “I would expect things to work another way”:
    The history between Daniel and the core team is well known. I wrote myself in the mentioned helper callback thread that I do often not agree on Nate’s comments against others. But From my point of view, Daniel is the one that has the bigger share in this dispute.

    Yeah, this is Captain Obviouses blog, so he can do what he wants. Thats why I suggested Cake Core members to simply ignore him and this blog. That’s the only way to avoid having this dispute erupt over and over.

  • dr. Hannibal Lecter

    Wow.

    Don’t take this wrong, but you all sound like a bunch of sissies.

    Which part of the “It would be good if all such projects would be consolidated in one single place.” is offensive? “It would be good” is offensive?

    I honestly don’t know what the heck are you all doing in open source if you can’t take criticism. Even if it was an offensive criticism (and in this particular case it wasn’t).

    So, WTFunk?

  • The Mullet

    the offense is: Someone (as far as I understand: gwoo) has been putting a lot of effort into an application and releases it. I don’t know about you, but whenever I release something, that’s a happy day for me and my team.

    And what happens: Captain Obvious, whose contribution to this application is null, posts a blog entry on this app, and his post of 10 lines length has 8 lines on the fact that Cake Projects lack a focal starting point.

    Once again, I don’t know about you, but on release-day where I prefer to celebrate, this is not what I want to read. Captain O. could have chosen to delve into the features of the app, but as always, he finds something to drag about. Why didn’t he? Well, it would have meant digging deeper into something new – and thats something Daniel is known for being a little poor at (see recent postings). So, as often, Captain Obvious chose the easy way and bemoaned the fact that the world is not perfect.

  • rafaelbandeira3

    so, The Mullet is virtually employed as a body guard for his own dumbness, and as he got nothing worthy to do he keeps bloating this thread with ridiculous comments that only shows how nonsense and boring he is. Shut up already?

  • dr. Hannibal Lecter

    > and his post of 10 lines length has 8 lines on the fact that Cake Projects lack a focal starting point.

    Is this a lie? I’d say no.
    Was it meant to be offensive? I’d say no.

    If someone else besides Daniel has written this, no one would even notice. You may claim someone would, but I beg to differ. This is nothing but bad blood from the past.

    As far as “Captain Obvious” is concerned, I’d always pick someone who writes bad articles over someone who employs name-calling in an argument. Go figure.

  • theman

    Seriously where is the professionalism?

    I’ve been watching the cake community for a couple years now and it seems like this project is being run by children. If there isn’t enough kudos for all the hard work being done on the cake-dev team then the pouting starts.

    If you don’t like what Daniel says then don’t read his blog. Concentrate on the superb code you’re creating and drop the expectation of having everyone hump your leg for the major sacrifice you as a cake-dev are making by being part of this project.

    Do you realize how volatile you make this project feel, like maybe tomorrow Gwoo or nate will decide Daniel (or someother cakebaker) has hurt their egos one too many times and that will be that. No more cakephp??

    As someone wanting to invest time into learning, using and leveraging a cool technology the behaviour from the cakephp team really does make me wary of sinking too much time/commitment into this project.

    Even if Daniel is picking on the cake-dev team who cares? It’s his blog and he presents a different view. He may also keep people accountable for the decisions they make in design and implementation, which is a good thing.

    Gwoo, Nate seriously just put your heads down and code. Every time you open your mouths in this fashion you make the other competing technologies seem that much more attractive.

  • Martin Bavio

    Haha this post is hilarious! Seriously guys, you are all grown-up people, and you are all internet guys, so I´m guessing that you all know that there are more private channels to discuss about your personal differences, dont you?

    Anyway, many thanks for the release of such a cool piece of code, and please, start to wash your dirty clothes inside your own homes. I don´t want to think that my favourite framework by far is leaded by a bunch on babies.

    Cheers,
    Martin Bavio

  • Jonah

    Personally when I read this post I sensed that cakebaker was showing aggression towards the cake dev team. But sometimes our senses can fool us.

    Why did I see this as aggressive? The first sentence he writes explains that the cookbook application source code was recently released. After I read this I thought (literally) “wow, this is really cool. Perhaps we can study the way they wrote the cookbook and learn from it.” I then expected the next few sentences of cakebaker’s post to congratulate the team for the release of the app and to comment on how we could learn from their code.

    But then I continue reading and find that *all* he has to say after that, is that “this project is hosted in a different place than other projects from the Cake team. It would be good if all such projects would be consolidated in one single place. ” (sentences 2-3). He simply moves on to the negative. I can definitely see how this would be hurtful to some certain people that worked on the cookbook.

    Also I believe that the dev team needs to refrain from commenting on this blog. It does not look good for Cake to me. Due to human nature I can see how that would be hard however.

  • cakebaker

    @all: Wow, I didn’t expect such a reaction on this short article. Anyway, thanks for your comments!

    @nate: Good to hear you are already in the process of transitioning. Something learned, I wasn’t aware of that.

    Well, you can find more feedback in my article. It is a bit hidden, but I’m sure you will find it if you look for it (a hint: it has not much to do with where the projects are hosted).

    And there is also a lot of feedback for you (and gwoo) in the other comments.

    @Ian: I’m sorry to hear that, anyway, have fun with the Zend framework!

    @Joel: I agree with you.

    @Daniel: Yes, such a comment would have been more appropriate.

    @The Mullet: I don’t know what to say to your comment, I’m speechless… You disqualify yourself with such a comment (though there is still something to learn from it for me).

    @Brendon: Yes, there is probably a bit of concern/irritation to hear in what I wrote, because I assumed github would be the future place for official cakephp projects and I wasn’t aware of the role of “The Chaw” at the time I wrote the article.

    And yes, I have some responsibility and I am aware of it. Unfortunately, you can’t control how an article is perceived by the readers. The same message, like this article, can be perceived as negative (“A guy bitching that not all projects are in one place”), neutral (“A guy mentioning the release of some code and pointing to other projects of the same authors”), or positive (“A guy pointing me to a project which is exactly what I was looking for”), depending on the reader.

    @Thomas: Yes, I agree with you, something went quite wrong :|

    Well, I’m not turning my back on cake, I’m still using it, and I intend to do so in the future. Despite its developers. I’m not sure whether the differences can be settled, too much inappropriate things were said in the past by cake devs (for example in the comments of this article). Sure, I’m not entirely innocent, I question things, and not everyone likes that.

    Oh, and thanks for the link about the feedback sandwich.

    @ajmacaro: I care about software design/engineering, and when I see things that violate basic development principles I pick them up in my blog and write about them. Yes, sometimes it is preaching. Preaching good software development/design practices. Not only to the cake devs, but to everyone.

    @Manny: It’s the past that haunts me ;-) In principle, cake 1.2 is production ready, even though it is still labeled as a release candidate. There are many who already use it in live applications.

    @The Mullet: You talk in your comments about the so-called “worthless” tickets I open and that they often carry notes like “I would expect things to work another way”. Well, does such a note really mean a ticket is worthless? What defines a “worthless” ticket anyway? Believe me, there is usually a good reason why I open a ticket.

    I’m open for feedback, but please be more specific. About how many tickets do we talk here? One ticket, ten tickets, hundred tickets (if you look on trac you will see I opened hundreds of tickets over the years)? And which tickets do you mean? And what is it, that makes those tickets worthless in your opinion? Just saying some tickets are worthless is not very helpful for me…

    @Hannibal Lecter: It looks to me like a typical overreaction…

    @The Mullet: Well, you are mixing things. This article is about the release of the source of the cookbook application, an application which already runs for around six months, and not about the application “The Chaw”, on which cakebook’s source is hosted.

    Saying I didn’t contribute anything to this application (the cookbook application) is wrong, see trac for the cookbook-related tickets I opened. And regarding contributing to “The Chaw”, well, it’s difficult to contribute anything to an application you are not even aware it exists…

    In all your comments to this article you question what I contribute to the CakePHP project and imply I have bad intentions regarding the cake project. So let me ask you one simple question: what do *you* contribute to CakePHP?

    @Rafael: Keep cool! And please don’t use the same style as “The Mullet”. Even if you don’t agree with his comments, it is not worth to attack him on a personal level. It usually helps to wait with a response until the anger is gone (for example, my response to “The Mullet” would have been very different if I answered him immediately).

    @theman: Well said.

    @Martin: As Hannibal wrote, it is bad blood from the past. And after all those things that were written in the past, it is quite difficult to settle the personal differences…

    @Jonah: Thanks for sharing your thoughts about why you saw this article as aggressive.

    It’s true, sentences 2+3 are slightly negative. My thoughts were: “Oh no, not again a different place for an official project! It would be really cool to have everything in one single place”.

    And here most stopped with reading, I guess, and overlooked the final part. In this part I accept the fact that the official projects are currently in different places and provide links to where you can find the sources of those projects.

  • Daniel Harrington

    Guys … come on. Please(!) take the time to enjoy a coffee/beer together and talk about what went wrong in the past. I’m sure everyone is going to benefit from that. Obviously I (and many others) don’t like to see posts/comments like these and … you just have to find a way out of it!

  • Brendon Kozlowski

    This is a prime example of “How you know your product is successful” by using qualitative *and* quantitative measures. Some people believe that negative criticism is some of the best in OSS areas too, as it brings about a slurry of information that may not have been known before. Although a lot of the middle and end of the comments seem to be “calm down” and “wow, seriously?” type of comments, the Cake devs definitely gave out some further information on what’s going on in their projects’ timelines…always good!

  • fred

    I love this blog. Seriously.
    This is definately the most entertaining blog i am following. It gets better and better. And I am not even a PHP guy!

    I really hope nothing will change and commenters will keep bashing each other. Please.

  • sosa

    I’m stopping reading this blog’s comments. This is going to make me 10% happier.

  • Brendon Kozlowski

    So I finally looked at TheChaw.com – looks impressive!

  • Rui Cruz

    Damn, how old are you?

    Every bit of information is useful even if written in a negative or whatever tone.

    It’s up to the CakePHP team to filter what is relevant and ignore the rest. Time is only wasted if one embraces in these types of comments.

  • cakebaker

    @all: Thanks for your comments!

    @Daniel: Enjoying a coffee/beer together is quite difficult, as we are on two different continents ;-) And I’m not sure whether it would be so easy to resolve the conflict, too much happened in the past… At least at the moment I don’t see a way to settle the differences :(

    @Brendon: Yes, there is always something you can learn from such threads.

    @fred: *g*, you are a cynic ;-)

    @Brendon: Yes, it looks nice.

    @Rui: Yes, I agree with you.

Bake a comment




(for code please use <code>...</code> [no escaping necessary])

© daniel hofstetter. Licensed under a Creative Commons License