I have a few articles published in the Bakery. This does not make me an authority on the subject but Since my first one was back in 2007 (I think), before it was even called the Bakery, I do have some experience of it over a pretty long time.
My personal set of guidelines for writing articles are: - Write and edit, preview and check... a lot. - Only publish once. Don't ever edit a published post unless you are at gunpoint. - Instead post additions or edits as author comments. - Keep the rss feed of comments to each of your articles in your feed reader. - Respond to real comments and delete spam comments. (I only delete spam I am certain of) I have developed some of this due to the sometimes very slow moderation process. A spell-correction once lingered for many weeks. This is of-course frustrating. But, if everyone took great care to check their articles before publishing their content I believe the process would be significantly quicker. Other points in my list are there to improve the quality of the article and to take on a small part of the burden of comment moderation. By keeping track of comments and responding to them you improve the quality of your article and the Bakery as a whole. Even if it is just a tiny improvement, it is something everyone can do. No forking required. ;) I believe that the main problems that need to be addressed in the software are related to spam. It if not perfect in most other respects, few things are, but the spam comments are the most urgent problem. They also take up a lot of time, I imagine. (There is also the thing where an author can't delete his/her own articles.) The other frustrations I have experience from time to time are probably more due to human resources, or a shortage thereof. It is important to point out that the people involved are NOT the problem... the rest of us, not involved, are so to speak. I am sure that with more insight one could see ways of improving the software that would streamline the work of moderators. /Martin On Apr 26, 3:10 am, Graham Weldon <gra...@grahamweldon.com> wrote: > Most definitely. We're keeping pretty busy with work on the core at the > moment, with releases for 1.2.7 and 1.3.0 out recently, we have a fair load > of work ahead to push through on CakePHP 2.0. > > If anyone has an interest in developing and working on the bakery, we would > very much welcome it. > > Cheers, > Graham Weldon (aka. Predominant) > > > > > > On Mon, Apr 26, 2010 at 10:49 AM, jacmoe <jac...@mail.dk> wrote: > > I think you misunderstand: > > When you make a fork of a project on Github, you can make merge > > requests back. > > Which means that if you're unsatisfied with the Bakery (as software), > > just fork it, fix it, and make a merge request. > > Even for small fixes, doesn't matter. > > I am sure Graham and Mark and the rest of the CakePHP team would > > appreciate that. :) > > > That's what I mean by forking. > > > Cheers > > > Jacob > > > On Apr 26, 2:04 am, calvin <cal...@rottenrecords.com> wrote: > > > I haven't published anything on the Bakery except for comments, so I > > > can't comment on the process. However, I will note that the software > > > is pretty screwed up. All my article reply notifications are blank e- > > > mails--not even a link to the comment/article. I personally hate it > > > when people send me e-mails or make forum posts where they don't write > > > anything in the message body and just use the subject-line as the > > > message. And I think this, along with dead links in the Cookbook, both > > > make Cake look very unprofessional. > > > > But I don't think just forking the Bakery is a solution. Cake needs a > > > centralized/official article/plugins repository. There are just a few > > > things that need to be fixed is all. Even if someone were to fork the > > > Bakery, it would not be as successful/useful. The Bakery is only so > > > useful today because lots of people know about and use it--it's linked > > > to right from the CakePHP homepage. So this "if you don't like it, > > > just fork it" attitude is not appropriate. It's similar to the > > > attitude that, if you find Cake's documentation lacking, you should > > > write it yourself. FOSS is about cooperation and free exchange of > > > ideas and information. It's not an excuse to deflect all criticism or > > > pin all responsibilities on the user/critic. > > > > And a person does not need to have contributed to Cake's source code > > > to level a valid criticism. > > > > On Apr 25, 2:46 pm, jacmoe <jac...@mail.dk> wrote: > > > > > That doesn't give you carte blanche to be arrogant, does it? > > > > > What have you done for CakePHP if I may ask? :) > > > > > A couple of weeks ago I posted this topic: > >http://groups.google.com/group/cake-php/browse_thread/thread/e3a1f469... > > > > With the title 'Let's get rid of The Bakery'. > > > > > I volunteered as a moderator, but there's still lots of things to do. > > > > And the software itself needs some fixing. > > > > > Feel free to fork it. > > > > > I would probably delete the article as well, if there haven't been any > > > > response in three months - I don't know what article it was, since I > > > > concentrate on removing spam rather than approving articles. > > > > Due to my newness to CakePHP mostly. > > > > > So: what have you done for CakePHP ? :D > > > > > Cheers > > > > > Jacob > > > > > On Apr 25, 11:42 am, Jayesh Wadhwani <jwadhw...@gmail.com> wrote: > > > > > > The Bakery is supposed to be a place where cakePHP developers > > exchange > > > > > ideas which in turn enhances the framework. > > > > > > I recently published a helper and it languished for pending review > > for > > > > > weeks on end. I visited the IRC and other than rude and arrogant > > > > > answers there was not much help. > > > > > > I did not receive any emails as to why there was a delay. > > > > > > Today I log in and see this message.. "This article has been deleted > > > > > and is not available for publication. Review The Bakery Publishing > > > > > Guidelines to understand why this article was deleted." > > > > > > Brilliant reviewer! Don't you think it would be a better to tell me > > > > > what is the exact problem so that I can correct it. According to > > > > > guidelines I do get 60 days. Right! > > > > > > So, what is it? The reviewers just do not care, are plain lazy or > > just > > > > > purely arrogant. > > > > > > If cakePHP has grown to such as level that it cannot handle the > > bakery > > > > > and breeds arrogance then I suggest that you get rid of it. > > > > > > Check out the new CakePHP Questions > > sitehttp://cakeqs.organdhelpotherswith their CakePHP related questions. > > > > > > You received this message because you are subscribed to the Google > > Groups "CakePHP" group. > > > > > To post to this group, send email to cake-php@googlegroups.com > > > > > To unsubscribe from this group, send email to > > > > > cake-php+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.c > > > > > om>For more options, visit this group athttp:// > > groups.google.com/group/cake-php?hl=en > > > > > Check out the new CakePHP Questions sitehttp://cakeqs.organdhelpothers > > with their CakePHP related questions. > > > > > You received this message because you are subscribed to the Google > > Groups "CakePHP" group. > > > > To post to this group, send email to cake-php@googlegroups.com > > > > To unsubscribe from this group, send email to > > > > cake-php+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.c > > > > om>For more options, visit this group athttp:// > > groups.google.com/group/cake-php?hl=en > > > > Check out the new CakePHP Questions sitehttp://cakeqs.organdhelp others > > with their CakePHP related questions. > > > > You received this message because you are subscribed to the Google Groups > > "CakePHP" group. > > > To post to this group, send email to cake-php@googlegroups.com > > > To unsubscribe from this group, send email to > > > cake-php+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.c > > > om>For more options, visit this group athttp:// > > groups.google.com/group/cake-php?hl=en > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others > > with their CakePHP related questions. > > > You received this message because you are subscribed to the Google Groups > > "CakePHP" group. > > To post to this group, send email to cake-php@googlegroups.com > > To unsubscribe from this group, send email to > > cake-php+unsubscr...@googlegroups.com<cake-php%2bunsubscr...@googlegroups.c > > om>For more options, visit this group at > >http://groups.google.com/group/cake-php?hl=en > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others with > their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > athttp://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
