Jason Porter wrote:
I noticed a little bit ago Gradle is trying to make Git it's official repo, maybe that's complete now, not sure. I'm wondering how best to go about contributing. I spent a few hours last night trying to understand how to create a plugin and a task for that notifier plugin I spoke about a few weeks back. Is the correct way now to ask for a clone or a fork of the git repo then merge back? Or should I still be working off of the svn repo and submit patches? I guess I should have read http://docs.codehaus.org/display/GRADLE/How+to+contribute+a+patch+to+Gradle first :) I'll follow the directions there. Though it may be good for the community to hear the "official" answer to this as the wiki details many ways of contributing.
I don't have an 'official' answer. Personally, I prefer to review changes using git, but svn is completely fine as well. It depends on the size of the change - I think git is easier for everyone for large changes (like a new plugin, for example).
Adam --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
