On Mar 21, 2012, at 14:48 , DlSnIpEr wrote: > Hello, > > After a chat with vicb I've decided to open this thread. > Basically I see two major flaws in the current way Symfony2 community is > organized and I believe if these would be covered the we could drive the > framework to something even better. > Since both of the issues are on the same grade of the relevance I'll just > list them in a random order:
i agree that there is room for improvement and the 2 topics you mention. > a) the lack of documentation when a BIG change is done; i am not sure if mandating documentation is the way to go. as a matter of fact it might worsen the issue you note in b). but we just need to get more people involved. in general the barrier to entry is ridiculously low to help on the docs. heck you dont even need to really understand git thanks to the online PR creation via the edit button on github.com > b) the time it sometime takes for a PR to be either merged or rejected. vicb has improved the feedback end of things quite a lot in the short time since he was hired to work on this. i also think that on the "push" side too many fellow developers are too shy to "fork" PR's and push them forward. aka just fork the repo that the PR originated from, take the branch and continue the work. then either send a PR to the repo that originally send the PR or create a new PR referencing the old PR. the original commits will be around, so its not like someone would be taking credit for other peoples work. regards, Lukas Kahwe Smith [email protected] -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
