> ... >> 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.
We can look at the wocommunity fork as a "staging" fork, a place where we can try out new stuff or fixes without having to build the forks of everyone who is providing fixes or new features. As for issues, we can remove the Issues tab in the wocommunity fork so that issues would be only created on the wolips master repository. For pull requests, they could be done in the wocommunity fork, and when we know that everything is good, we do a pull request into the wolips master repository. For me, my goals are to make it easier to new developers to get in WOLips. That's why I want to add a ERRest template and that I removed the "WebObjects" templates from File -> New so that we have less confusion (a new user will not understand the differences between a "WebObjects Application" and a "Wonder Application" (the WebObjects templates are still available from File -> New -> Other). _______________________________________________ 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]
