On Monday, January 28, 2013 6:56:52 PM UTC+1, Larry Garfield wrote: > > On 1/28/13 11:13 AM, Victor Berchet wrote: > > > Anyway, my impression of doc updates is pretty favourable. IIRC the > > code > > contribution process for changes and new features requires[1] > > contributors to > > modify UPGRADE, CHANGELOG, and to link to a corresponding pull > > request on the > > documentation repository. That's already a pretty tall order. > > > > > > My reply is more about cookbook (/technical) articles that are not > > triggered by code changes. There are a lot of blog posts that will tell > > you how to better use the DI or the security component, ... > > But it also true that core devs (myself included) do often not take time > > to write cookbook articles when introducing new features. This is why > > those blog posts could be valuable when added to the documentation. > > They could be, sure. I'd certainly find that valuable as a relative > Symfony newbie, as things like the symblog tutorial are already out of > date and it would be great to be able to locate articles to send to > people other than trying to remember who tweeted them. > > But I'd also advise making such a section actively curated, rather than > just a place people can copy articles from their blog and forget about > them. That would turn it into a docs dumping ground, and our experience > with that model from Drupal suggests that you really don't want to do > that. :-) (Drupal.org has a ridiculously huge amount of > documentation... that is beyond the ability of our docs team to manage.) > > That of course takes committed resources to curate, coordinate, update, > deprecate, and so forth. >
Larry, Could you please give some more details on why it doesn't work for Drupal ? Is there some kind of review for added articles or can anybody just post them ? If the articles get reviewed why do you end with low quality ? the number ? There are missing info in the Symfony doc I think - May be the Form, Security and DI components could be a good focus to start with. Of course we would only accept valuable articles and review them on PRs submission. If this help decreaseing the amount of support (and "support" issues), the ROI might be worth the time spent. I would personnally volunteer to review (and reject when needed) such PRs. Thanks for your valuable feedback, Victor > > > I reckon we'll be fine as long as we keep Ryan well fed and watered > :) > > You may need some cloning pods, too. We've been trying to add that > feature to our Docs team for some time. ;-) > > -- -- If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en --- You received this message because you are subscribed to the Google Groups "Symfony developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to symfony-devs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
