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

[Luis Ibanez]

Perhaps one way to approach the discussion is to actually
draw a map of the the paths that new code can take in the
current ITK landscape. Different types of code would follow
different paths.

Then we can better evaluate whether the workflows are
appropriate, and whether we need to refine the tools that
go with them.

I agree with Brad K, in that what we first need to address
the governance of code flow, and then we will have a
better perspective for discussing the actual mechanisms.

Creating a Contrib group, doesn't quite address the more
fundamental issue that we need to recruit more volunteers
developers to actually review and improve code.

We already have the backlog of the Review directory...


      Luis



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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20140116/e0c59b03/attachment.html>