Welcome Mike! Yes, go ahead fork the git repository on github and start hacking on your personal branch tracking the javelin branch.
Regards. On 14-Dec-2012, at 9:35 AM, Mike Tutkowski <[email protected]> wrote: > Thanks for the info, David! > > I have joined #cloudstack-dev now, so that should help, as well. > > Also, I can fork > https://github.com/apache/incubator-cloudstack/incubator-cloudstack.git and > work from it. > > Sounds like any work I do should be performed on the javelin branch, true? > > Thanks again!! > > > On Thu, Dec 13, 2012 at 11:04 PM, David Nalley <[email protected]> wrote: > >>> >>> My first question is, where do I start? :) >> >> Welcome! >> You've done a good job starting by subscribing to the list and sending >> this mail. >> >> >>> >>> I've gotten an account on GitHub. I've forked the repo and cloned it >>> locally to my development computer. I have Eclipse in place and am >> trying >>> to get the code to build under the storagerefactor branch. >> >> So while github will work (assuming you are using this repo: >> https://github.com/apache/incubator-cloudstack ) I don't see much >> reason not to use the official one here: >> https://github.com/apache/incubator-cloudstack/incubator-cloudstack.git >> It will be updated faster, etc. Various CloudStack branches can be >> rather fast paced and makes the mirroring slow to keep up. >> >> Pull requests can be submitted, but are a bit out of norm. - just push >> your patches to reviews.apache.org >> >>> >>> During an e-mail exchange with Edison today, it sounded like I should >>> instead be on the javelin branch. Did I understand that correctly? >> >> Feel free to bring those conversations to the list. We'll all benefit >> and learn from the discussions. >> >> Couple of other things - many of us hang out in #cloudstack-dev on >> freenode, feel free to join us. >> >> --David >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: [email protected] > o: 303.746.7302 > Advancing the way the world uses the cloud <http://bit.ly/ToRxAV>*™*
