FYI- I thought this exchange, and the idea, are interesting.<div><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Julien Jomier</b> <span dir="ltr"><<a href="mailto:julien.jomier@kitware.com">julien.jomier@kitware.com</a>></span><br>
Date: Wed, Aug 18, 2010 at 3:15 AM<br>Subject: Re: Modifying VTK Journal to allow git branches<br>To: David Doria <<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>><br>Cc: Will Schroeder <<a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a>>, Luis Ibanez <<a href="mailto:luis.ibanez@kitware.com">luis.ibanez@kitware.com</a>><br>
<br><br>David,<br>
<br>
Great minds think alike :)<br>
<br>
Luis and I actually discussed this idea a couple weeks ago for the Insight Journal. We wrote exactly what you mentioned in a proposal to NIH. If everything goes well, we should have some funding available to implement this feature in the near future (September/October). There is a fair amount of work to make this work but it would definitely be a very nice addition to the journal.<br>
<br>
We are always taking feedback and new ideas so feel free to keep them coming!<br><font color="#888888">
<br>
Julien</font><div><div></div><div class="h5"><br>
<br>
<br>
On 8/17/2010 1:04 PM, David Doria wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Julien and Will,<br>
<br>
I have really been enjoying working in the new git framework. Creating<br>
git hub VTK branches have made it amazingly easy to work on projects<br>
with collaborators and perform code reviews.<br>
<br>
It seems like a natural addition to the VTK Journal to allow code to<br>
be published as a VTK branch on github (or elsewhere). The workflow<br>
for the developer becomes extremely easy - simply provide the journal<br>
a link to the repository and the name of the branch. The workflow for<br>
the user is also extremely easy - simply clone and checkout the<br>
branch. The user should be presented with a link to a "snapshot" of<br>
when the code was published (a known working version) as well as a<br>
"live" link where they can see new work. I have modified the code for<br>
many of my projects after my original Journal submission. It has been<br>
awkward each time (so much so that I stopped doing it!) to have to<br>
shuffle the files to stand on their own (the biggest issue by far),<br>
zip them and re-upload them to the journal. In my suggested method, a<br>
simple 'git push' would do the job.<br>
<br>
The beauty of this is that there is nothing special that needs to be<br>
done on the Journal side except allow the developer to select "upload<br>
code" or "publish a git repository". Then two new fields would need to<br>
be added to each publication to store the two github links mentioned<br>
above.<br>
<br>
A second benefit is that when people go through the submissions<br>
deciding if anything is worth adding to the mainstream toolkit (which<br>
I don't think actually happens at the moment), they can work directly<br>
on the files (after the original submitter gives them write access)<br>
and then simply perform a merge with VTK HEAD.<br>
<br>
A spin off idea is that you could maintain and distribute a<br>
"VTK-NextGen" branch that has all of the VTK Journal submissions<br>
merged into a branch. Maybe this would encourage developers to work on<br>
and with each others code.<br>
<br>
What do you think?<br>
<br>
Thanks,<br>
<br>
David Doria<br>
<br>
</blockquote>
</div></div></div><br><br clear="all"><br>-- <br>William J. Schroeder, PhD<br>Kitware, Inc.<br>28 Corporate Drive<br>Clifton Park, NY 12065<br><a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a><br>
<a href="http://www.kitware.com">http://www.kitware.com</a><br>(518) 881-4902<br>
</div>