Re: [eigen] Bugs on bugzilla

[Matthew Brett <matthew.brett@xxxxxxxxx>]

Hi,

On Wed, Jun 4, 2014 at 2:13 AM, Gael Guennebaud
<gael.guennebaud@xxxxxxxxx> wrote:
>
> Hi,
>
> so basically we are facing three interconnected problems:
> - we have to better structure our community,
> - attract more contributors,
> - deal with the numerous bug entries.
>
> Regarding the structuration of the community, we could try to lean towards
> something like:
> - a small steering committee taking the major decisions on the evolution of
> Eigen,
> - assign one person in charge for each module of Eigen, each platform, etc.
> (from regular Eigen's developers)
> - assign a release manager taking care of the progress of each feature
> planed for the next release.
> - a pool of reviewers to review novel features (do not need to be an Eigen's
> developer)
>
> However, I'm not sure that currently we have enough man power to go to such
> a formal structure.
> As Christoph suggested, identifying active contributors with their domain of
> expertise would already be a good step. Here I'm thinking about
> "contributors" and "expertise" in a very general way, not only code!
>
> This last remark leads me to the second item (attract more contributors) for
> which I'd like to emphasise that there are many way to contribute to Eigen
> without knowing its internal:
> - documentation,
> - support to other users,
> - unit testing,
> - fix compiler/platform specific issues,
> - discuss API,
> - etc.
>
> What about adding a "How to contribute?" page developing these items on the
> web site? Any volunteers?
>
> Then we need a way to keep track and easily spot these 'junior jobs" which
> could be addressed without requiring any knowledge on Eigen's internals.
> So instead of adding a voting system to the bug tracker, I'd rather add a
> such a field.