Am 15.01.2012 um 05:23 schrieb Q: > On 14/01/2012, at 2:50 AM, Ramsey Gurley wrote: >> On Jan 13, 2012, at 8:51 AM, Johann Werner wrote: >>> Am 09.01.2012 um 22:21 schrieb Pascal Robert: >>>> Le 2012-01-09 à 16:09, Johann Werner a écrit : >>>> >>>>> Btw who is able to do commits on wolips? It seems that the group of >>>>> people having the ability to check pull requests, create patches for >>>>> issues and commit changes is rather small in contrast to wonder. >>>> >>>> I think only the organization members (listed on the organization page at >>>> https://github.com/wolips) can do commits; >>> >>> Hm that's only two persons, effectively just Quinton doing all the work. >>> Wouldn't it be more reasonable to add some more commiters as for wonder? >> >> Well, it is Q's repo. I'm not sure he trusts us. Not sure I trust us >> either ;-) > > It's not so much that it's my repo, it's more like everyone else is gone and > for some time I've been the only one left to fight off the bugs, at least > until recently. > > Join the WOLips Infantry and save the Galaxy. Service guarantees citizenship. > Would you like to know more? > >> Having said that, with git, everyone is a committer. I can (and have) set >> up my own build for WOLips at home. I can fix any problem I have and use my >> changes right away. Pascal could easily clone the repo, set up a WOLips >> build at WOCommunity based on it, and add more committers there if he likes. >> Amazon cloud servers are free for a year too. A micro instance should be >> sufficient for a build server. So anyone can set up their own 'official' >> build. For better or worse, git frees you from the centralized authority of >> committers in SVN :-) > > This is very true, but this can also cause confusion of which build of what > repo people should be using, and where they should raise issues about bugs. > If everyone starts setting up their own builds from their own forks it's sort > of a step backwards.
That's exactly what I am thinking and what makes me hesitant to go for a "new official" fork. I had the same situation deciding on how to handle the wonder repository at work and came to the result to use only the official one instead of creating and patching an own fork which probably would diverge more and more over the time. > I have been away on leave recently and haven't had a chance to review > Johann's outstanding pull requests since getting back, but it will happen > soon. > > If you think you should be a committer for wolips, talk to me. I think it would be better to keep the wolips repository as the official fork, to prevent confusion (one point is that issues are related to a specific fork so there would be two places for issues) as well as having at least one experienced user (that is you ;) keep an eye on all those code changes. I made some pull request but only with minimalist changes and have not delved much into Eclipse plugin development yet so it is reassuring that there is someone who will comment (or even correct) bad mistakes or cumbersome code. I suppose that there aren't many active people who have a good understanding of the whole structure and details of all those wolips plugin parts (no, I am not asking if there exists any documentation ;) and we absolutely need more people working on that code and gaining experience so I would gladly ask for to be added as a committer. Even as there is way less change on wolips than on wonder it is unfair of the community to burden you with all that work as you too have to hold down a job. Though Pascal's suggestion to create a separate branch to test patches on a jenkins server and being some sort of wolips 'nightly' distribution sounds interesting. Just some thoughts, jw _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
