Jakub, This is a great idea, and in line with the first unconference discussion (Stefan's community-building topic) a few of us had at Symfony Live.
If you're all collaborating in person, the easiest way to coordinate on Github might be to make a public organization with a fork of Symfony2, and you can all collaborate there. If everyone had access to the organization's fork repository, it should preserve all of the authorship and make it easier to combine efforts (vs using personal forks and having to add each other as remote repositories). You could even submit pull requests from the organization's fork. After everything is accepted, you could wipe the organization account to keep from littering Github :) Also, here's a good (and short) blog post from Bernhard on deciding how to prioritize test coverage: http://webmozarts.com/2010/03/15/why-not-to-want-100-code-coverage/ On Fri, Mar 11, 2011 at 9:21 AM, ryan weaver <[email protected]> wrote: > Hey Jakub! > > I somehow didn't actually meet you in Paris - a shame, let's fix that next > year! I can answer some of your questions, someone correct me if I'm > off-base: > > 1. Each test or group of tests that represent one tested "feature" should > probably be committed on their own branch and sent as their own pull request > to core. So, if 10 developers all write tests for 2 "features" each, then > each developer would have created 2 new branches on their fork and Fabien > would have 20 beautiful pull requests to merge in. > > 2. Can someone else answer this more intelligently than I can? > > 3. Depends. If you can fix the bug, then I'd put it in the same pull > request. If you can't, but your sure that the test is really revealing a > bug, I still think that should be sent as a pull request. In that PR, you > could say that this test exposes a bug, but fixing it was beyond some > developer's scope (I've done this before for the ODM). > > 4. In theory, yes! If others want to organize local test fests, then you > can all organize together. But even if nobody else speaks up now, a > successful test fest in Poland will set a great tone and others will follow > your lead. We talked a little about this at the conference - if you can > organize something small quickly, it's better than organizing something > *huge* that might take months to really get moving. > > Cheers Jakub! > > Ryan Weaver > Lead Programmer - iostudio - Nashville, TN > http://www.iostudio.com > http://www.thatsquality.com > Twitter: @weaverryan > > > > On Fri, Mar 11, 2011 at 7:38 AM, Jakub Zalas <[email protected]> wrote: > >> Hi, >> >> I came out with an idea of creating a Symfony TestFest at my location >> (Gdańsk/Poland). The aim is to improve the test coverage of Symfony2. >> Initial date of the event is 25th of March. >> >> I have some questions/comments regarding the organization. >> >> 1. What's the best way for core developers to merge the tests later? >> For example: should we create a branch for each meeting or for each >> file under test? >> >> 2. It would be good to know which components should get higher >> priority so we could take care of them in the first place. >> >> 3. What about potential changes in code? What if adding tests reveals >> bugs? What's advised approach? >> >> 4. Anyone else interested in participating? I think it would be great >> to arrange a global TestFest. Of course that requires some more >> organization. We would probably need to "reserve" components each >> group wants to take care of. >> >> During Hacking Day on Symfony Live in Paris I learned that creating >> tests can be fun and knowledgeable process. There's something in >> making that red becomes green ;) >> >> >> -- >> 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 >> > > -- > 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 > -- jeremy mikola -- 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
