<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I wanted to comment that your gerrit work flow is great. I like the
organization by topic branches and that dashboard runs are
automatically triggered on new pushes. Also the reviews by folks on
your side have been very helpful in improving the submitted code. It
would be nice to see a diff between successive review/recommit
iterations.<br>
<br>
I don't know how much the work flow is turning off new developers, a
knee jerk reaction is that it feels like overkill, but all of the
things that you ask folks to do make a lot of sense and help keep
VTK solid. It sure is rewarding to see how solid VTK is and see it's
continual improvement and to be a part of that! As a developer the
high quality of the resulting product outs weigh my desire to work
with fun tools.<br>
<br>
I recently made some commits to a KDE component project. Their
workflow uses svn+reviewboard. The lack of topic branches made
iteration cumbersome. Once the patches were approved merging was not
as easy as it is in your gerrit workflow where it's done with a
simple button click on a web page.<br>
<br>
I would think that modernization is more of an issue in attracting
developers. Ancient OpenGL infrastructure is a really big one.
Things like having to use SafeDownCast instead of dynamic_cast and
the other baggage of supporting ancient compilers are also a big
turnoff. A full c++11 port would be very exciting. All these are
things you are working on but are harder and take longer to
change...<br>
<br>
<div class="moz-cite-prefix">On 08/25/2014 04:47 PM, Berk Geveci
wrote:<br>
</div>
<blockquote
cite="mid:CAE32kpUgLsM9KdwvHACqwAzDxcD0iiQ42ETrNHYdGr4rB+ujfA@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Bill,
<div><br>
</div>
<div>The goal is not to have more process. It is to implement a
workflow with fun-to-use tools such that we can continue to
attract developers to VTK. VTK development is lively. We have
done a lot of great stuff last year, both new development and
maintenance, and we have great things coming next year.</div>
<div><br>
</div>
<div>In my humble opinion, what we are doing poorly is
attracting new developers. I think toolchain and workflow play
a role in this. Not communicating well is another part. I'd
like to attract more people to contribute code and more people
to do reviews. Also, our bug tracker is collecting dust. Lots
of bug reports are going in but it gets very little attention.
I can't even remember when I looked at it last.</div>
<div>
<div><br>
</div>
<div>Here are some statistics from <a moz-do-not-send="true"
href="http://openhub.net">openhub.net</a> (website
formerly known as ohloh):</div>
<div><br>
</div>
<div>
<div>
<div><font face="arial, sans-serif">VTK:</font></div>
<div>
<font face="arial, sans-serif">
<div>
<br>
</div>
<div>30 Day Summary</div>
<div>Jul 21 2014 — Aug 20 2014</div>
<div>152 Commits</div>
<div>19 Contributors</div>
<div><br>
</div>
<div>12 Month Summary</div>
<div>Aug 20 2013 — Aug 20 2014</div>
<div>2393 Commits</div>
<div>
Down -965 (28%) from previous 12 months</div>
<div>64 Contributors</div>
<div>Down -6 (8%) from previous 12 months</div>
<div><br>
</div>
<div>Still a lot of commits but going down.</div>
<div><br>
</div>
<div>So I'd like to see us slowly migrating towards
tools that are more attractive and facilitate
collaboration with the larger community.</div>
<div><br>
</div>
<div>Frankly, I believe that our current set of tools
get in the way. First of all, they all require
creating accounts to do anything. An account for bug
tracker, another for Gerrit, another for Wiki,
another 2 for the mailing lists. We should have
presence where people already hang out and don't
have to create new accounts. Github, stackoverflow,
Google+ etc. Second of all, they are all clunky at
best. Usability does matter to people. Finally,
there are a lot new resources available out there
and we are not tapping into it as best as we can. We
should be using Travis and Jenkins in addition to
CDash and CDash @ Home for example.</div>
<div><br>
</div>
<div>So I don't think that this conversation is
overkill. These discussions have a natural tendency
to go on forever, I agree. So let's try to keep to
the point and make some decisions soon.</div>
<div>
<br>
</div>
<div>Best,</div>
<div>-berk</div>
<div><br>
</div>
<div><br>
</div>
</font></div>
</div>
<div><br>
</div>
</div>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Aug 25, 2014 at 4:54 PM, Bill
Lorensen <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:bill.lorensen@gmail.com" target="_blank">bill.lorensen@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">BTW the
new gerrit UI is a bit prettier:<br>
<a moz-do-not-send="true"
href="https://android-review.googlesource.com/#/q/status:open"
target="_blank">https://android-review.googlesource.com/#/q/status:open</a><br>
<br>
I'm a little concerned that we spend too much time on
process and not<br>
enough time on improving VTK. But, I'll go with the
consensus of the<br>
people who still work for a living. If the new process is
too<br>
difficult for an old guy like me, I'll just spend my extra
time with<br>
ITK.<br>
<span class="HOEnZb"><font color="#888888"><br>
Bill<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On Mon, Aug 25, 2014 at 4:45 PM, Sean McBride <<a
moz-do-not-send="true"
href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>>
wrote:<br>
> On Mon, 25 Aug 2014 15:50:59 -0400, David Cole via
vtk-developers said:<br>
><br>
>>A fantasy feature for me would be that the
system injects a step<br>
>>1.5/2.5 in the developer workflow, and
automatically chooses 3-5<br>
>>reviewers for you based on reviewers "signing
up" for reviewing certain<br>
>>modules, or perhaps based on recent-ish commits
in the same files...<br>
><br>
> That would be a great addition. I often don't know
who to add as a reviewer, and I've been tinkering with
VTK for years. Imagine a newbie! A person can use 'git
log' and 'git blame' to get some guesses, and that could
be automated. Of course, sometimes that results in
suggesting someone no longer involved with VTK or the
infamous 'VTK developers', but still it would help to
automate it.<br>
><br>
> Cheers,<br>
><br>
> --<br>
>
____________________________________________________________<br>
> Sean McBride, B. Eng <a
moz-do-not-send="true"
href="mailto:sean@rogue-research.com">sean@rogue-research.com</a><br>
> Rogue Research <a
moz-do-not-send="true"
href="http://www.rogue-research.com" target="_blank">www.rogue-research.com</a><br>
> Mac Software Developer Montréal,
Québec, Canada<br>
><br>
><br>
</div>
</div>
<div class="HOEnZb">
<div class="h5">>
_______________________________________________<br>
> Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/vtk-developers"
target="_blank">http://public.kitware.com/mailman/listinfo/vtk-developers</a><br>
><br>
<br>
<br>
<br>
--<br>
Unpaid intern in BillsBasement at noware dot com<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/vtk-developers">http://public.kitware.com/mailman/listinfo/vtk-developers</a>
</pre>
</blockquote>
<br>
</body>
</html>