Michael Jakl wrote: > Hi! > > Since I do not have committer access, how would you suggest to get the big > feature improvement into the code? > > Currently I would make JIRA tasks (as soon as JIRA has moved) and upload > patches. This way Bernd can have a second look at the code.
The idea is that everybody, not just me can have a look. Although, some folks might to choose to review only commits and speak up then (search for '"commit-then-review" +site:apache.org'). > I think the extension is mostly separate from the Vysper core, so a few bigger > patches in the integration phase might also work. Unfortunately this way > nobody > else can have a look at the code until it is migrated... . -1, because of the reason you already give. This won't work. > Personally I use git to track my work (and git-svn to communicate with the > Vysper repository along with the stock subversion client). I think staying up > to date and making coherent patches from many small changes should be no big > problem. > > I'm sure you have some good ideas or suggestions how you would tackle this - > please tell me ;) >From my PoV, it is absolutely crucial to have small patches, as often as possible. The thing is, here at Apache, we have a very strict regime on code provenance. It must be absolutely trackable where the code comes from. That makes working with git problematic. ASF relies on its svn repository. It's our brain for everything. Everyone here knows svn from their hearts. This pretty much rules out introducing git for collaboration (at least for this summer). If you want to use git locally though, that's perfectly fine. So, I propose to attach patches to JIRA (more than one patch per JIRA, where appropriate) for the time being. At some point you may gain committership (that's not my call, but the MINA PMCs, so I can be open about that), but that's probably some month of work away. What do you think? Bernd
