Hi Sean,
Yes, it also took me awhile and a few false starts to make commits via Gerrit. Still have not sorted out the best process for reviewing pending changes (including yours).
I also started working on Maven config yesterday, primarily by reviewing pom files for Papyrus, including how our build can be run on Eclipse Hudson nightly and push the update site to Eclipse server. Need to compare notes on that. I want to get the complete automated nightly build working asap.
Looking at other Eclipse projects on git, and experience with others over the years on cvs and svn, all appear to use 'master' for current development. Branches are created for maintenance of prior releases and sometimes for significant enhancement changes to review. I don't see a need for 'develop' branch. The way you've been using github, was master the most recent release? As we sync with the eclipse release train, our master build should use latest milestone of Neon. See:
Regarding use of org.openhealthtools, I'm certain this needs IP review and approval, and likely an agreement with HL7, as they now own this trademark. At EclipseCon next month, I am in the process of scheduling a face-to-face meeting with the IP team for our project.
Also, please install and test the Mylyn integration with Gerrit. I looked at the Gerrit changes for Papyrus and UML2, and always saw a bugzilla for each commit. Mylyn makes this relatively easy with Gerrit. See the bugs I've created for MDHT work. Mylyn + Gerrit will automatically add a comment for each commit. While looking at your Gerrit change, there are actually 2-3 different groups of changes, not only the Maven config.
In the list of Gerrit changes for MDHT most include a bugzilla ID. You can click the bugzilla link from within the Gerrit change to see description/discussion of the change. I'd like to adopt this as part of MDHT agile sprint planning.
I should be able to make the dev call tomorrow at 4:30 ET to discuss.
Dave
