Hi guys! On the documentation front, one thing that's been happening at least somewhat commonly is at least creating a ticket on symfony/symfony-docs for the new feature. This doesn't raise the barrier of entry for getting PR's accepted, but makes sure that we (the docs team) are aware of all of the changes that need to be doc'ed (which is very important). I think this works well and should be encouraged. We're not quite keeping up with those changes at the moment (despite some heroic efforts from people like drak), but that's a separate issue.
Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Sat, Mar 24, 2012 at 10:50 AM, Lukas Kahwe Smith <m...@pooteeweet.org>wrote: > > On Mar 24, 2012, at 11:46 , DlSnIpEr wrote: > > > Hi, > > > > > > In regards to the problem the requiring documentation I don't think it > would be that bad as it sounds. If everyone would just write even simple > bootstraps like : The feature X has been updated/changed in order to > perform more cool stuff and you can do that by adding/changing this and > that into the existing/new code then I believe it wouldn't be a problem > even for someone else to pickup and extend that documentation. > > well we already have the CHANGELOG/UPGRADING doc for that > > > As for people being afraid to do PRs. Indeed, some of them might be. > Others could be just lazy, but I think for the most part, the lack of a > guideline for each components, their scope and how they should be > used/extended/what's expected from them pushes them away, along with the > how to use them documentation as well. For me it's really hard to do a PR > because sometimes I don't know what should I do about the Configuration > component part of something, or about how the component itself should work > in the end and given the fact that my schedule is pretty tight at times I > might abandon doing a PR just because I'd need to look at a ton of source > code before doing anything. Plus even if I do a PR, it might not be in the > Symfony2 way of doing it, see the lack of general direction I was talking > about. > > Just to clarify, I wasnt talking about people being afraid of creating > PR's, I was talking about people not realizing that its totally legitimate > to fork the code from another PR to continue it in case the original author > isnt reacting. > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org > > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > 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 > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
