[vtk-developers] Driving away your existing developers

Sean McBride sean at rogue-research.com
Fri Sep 26 12:01:09 EDT 2014


On Tue, 2 Sep 2014 09:38:21 -0400, Brad King said:

>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

Brad,

Thanks for pointing this out.  I subscribed immediately, but wanted to experience it a bit before replying.

It's decent, but I find the subject line really not useful.  They are always of the form:

[Vtk-commit] Visualization Toolkit branch, master, updated. v6.1.0-1718-g5ad494c

Only the last bit ever changes, meaning you really need to look at the body of the email.

Much more useful would be something like on the clang commits list, ex:

r218482 - Fix PR20886 - enforce CUDA target match in method calls

There you can lurk on the list and have an idea of what's changing just from scanning the subjects.  For me anyway, that'd be perfect.

Cheers,

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada





More information about the vtk-developers mailing list