[Insight-developers] [ITK Community] A Contrib group?

[Bill Lorensen]

I think remote modules should be used for "special purpose" or limited
application contributions. For example, the Lesion Sizing Toolkit.  Or
the Skull Stripper that I am about to submit as a remote module.

Something like the STL Reader/Writer is appropriate for inclusion into
the toolkit.

Of course these are subjective decisions and should be dictated by the
community.

We have a process in place for Remote Modules, although we don't
always follow it:
http://www.itk.org/Wiki/ITK/Policy_and_Procedures_for_Adding_Remote_Modules

Bill

On Thu, Jan 16, 2014 at 10:51 AM, Bradley Lowekamp
<blowekamp at mail.nih.gov> wrote:
> Brad K, Bill,
>
> It's not clear from your(s) comments if you are in favor of using remote modules for all new modules or not?
>
> Or if small new contribution like a single class should be added as separate module or integrated into the appropriate existing module?
>
> Thanks for the clarification,
> Brad
>
> On Jan 16, 2014, at 10:38 AM, Brad King <brad.king at kitware.com> wrote:
>
>> On 01/16/2014 10:18 AM, Bradley Lowekamp wrote:
>>> these contributed modules are not reviewable in gerrit, are no
>>> automatically tested in gerrit, and are not tested in the dashboard.
>>
>> That is a limitation of the review/testing infrastructure that should
>> be overcome by technical means rather than worked around with means
>> known to fail in the past.  Just look back at the Review directory
>> prior to modularization.  It was huge and barely maintained.
>>
>>> Additionally, the other other goal it to have users have sense of ownership
>>> and responsibility for the code contributed and reduce the limited
>>> maintenance resources.
>>
>> How does labeling something "contrib" (a second-class designation) give
>> a contributor a sense of acceptance into the community?  We should
>> encourage contributors to maintain their work as first-class
>> participants.
>>
>>> Also, everyone things there code is great and thinks it should get into ITK.
>>> With the current nebulous Community lead approach no direction or editorial
>>> leadership can occur.
>>
>> This is a problem best solved by refining the governance model.
>>
>> -Brad K
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.php
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/community



-- 
Unpaid intern in BillsBasement at noware dot com