[Insight-developers] Adding David Doria as ITK Developer
Matt McCormick
matt.mccormick at kitware.com
Wed Dec 21 17:41:19 EST 2011
Yes, David should certainly be triggering robot builds. I added him
to the list.
-------------
I think it would be good for the project to adopt a set of policies so
there is a clear pathway for contributors to get access to resources
like this.
What the Qt project did recently is a good example of a meritocratic process:
http://wiki.qt-project.org/Qt_Contribution_Guidelines
http://wiki.qt-project.org/The_Qt_Governance_Model
The title-seeking aspects would likely be harmful to a community,
encouraging people to claim rank instead of technical justification on
issues. But, a clear, merit-based, well defined way for contributors
to obtain the resources they need would be good.
-------------
David started on patches to move the wiki examples into the repository.
http://review.source.kitware.com/#change,3555
This is an outstanding effort, and the examples are a valuable
resource. I think we should consider adding an example as a
requirement to the new class contribution process:
http://www.itk.org/Wiki/ITK_Release_4/New_Code_Contribution_Process
Matt
On Wed, Dec 21, 2011 at 10:48 AM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> I agree.
>
>
> On Wed, Dec 21, 2011 at 10:46 AM, Arnaud Gelas
> <arnaud_gelas at hms.harvard.edu> wrote:
>> Hi all,
>>
>> For the last past year, David has shown his dedication to open source
>> projects (VTK and ITK).
>> He regularly submits patches to gerrit which fixes bug, enhances the
>> documentation or contributes useful examples to illustrate typical usage of
>> a class.
>>
>> I think it would be quite useful for him and for the community at a whole,
>> if David was granted the same right level as other ITK Developer; i.e. when
>> he submits one patch to gerrit, it should trigger an experimental build.
>>
>> Would it be possible to proceed, please?
>>
>> Thanks,
>> Arnaud
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
More information about the Insight-developers
mailing list