[vtk-developers] Driving away your existing developers

[David E DeMarle]

One thing we can hope to do better next time to not alienate the old timers
(including myself).

* The transition from CVS to today's gerrit workflow was necessarily long,
but there were frequent adjustments along the way as we learned and built
up the infrastructure. Every change in the process meant retraining all of
the (self interested and busy) contributors.

Whatever our end goal is with the new infrastructure - we need to work
harder to minimize the number of changes to the commit process, to keep the
contribution process as dead simple as it can be, and to describe the
mechanics clearly and loudly.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Tue, Sep 2, 2014 at 9:38 AM, Brad King <brad.king at kitware.com> wrote:

> On 08/28/2014 11:07 AM, Sean McBride wrote:
> > 1) a 'commits' email list, like other projects.  Where you get an
> > email for every merge into master.
>
> We've had one of these since CVS days:
>
>  http://www.vtk.org/mailman/listinfo/vtk-commit
>
> It still works.
>
> -Brad
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20140903/288610e7/attachment-0002.html>