Not only is the original chair not available, neither is a quorum of the 
proposed PMC.  Why are you pushing this?  I, for one, am perfectly content to 
keep Math here and see if those who have expressed interest in helping out 
actually do and if others are attracted to fill in the gaps.

Ralph

> On Jun 10, 2016, at 11:54 AM, James Carman <ja...@carmanconsulting.com> wrote:
> 
> We already voted to make it go TLP and it passed.  The original chair of
> the new project isn't available any more.  Gilles, are you willing to chair
> the new project?  Is anyone else willing to help Gilles perhaps take Math
> through the incubator to gather more momentum?  Can we perhaps reach out to
> the incubator PMC and ask them for guidance on if this is even a good idea?
> 
> 
> 
> On Fri, Jun 10, 2016 at 2:22 PM Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
> 
>> 
>>> On Jun 10, 2016, at 11:00 AM, Jörg Schaible <joerg.schai...@gmx.de>
>> wrote:
>>> 
>>> Hi Gary,
>>> 
>>> Gary Gregory wrote:
>>> 
>>>> I agree with Jörg's email below. Furthermore, to me, the best chance
>>>> [math] has a shot to survive and prosper (I'm a glass-half-full kinda
>> guy)
>>>> is to stay in Commons in its current single module form (KISS)
>> _because_ a
>>>> bunch of [math] developer's have left. We have a bunch of people in
>>>> Commons that are smart and _can_ fix _some_ of the problems, can
>>>> _shepherd_ patches, and _mentor_ newcomers; all of which could not
>> happen
>>>> in a new TLP unless all Commons committers came along.
>>> 
>>> 
>>> For me, we have two options: Either keep it as one component that
>> contains
>>> all of the current stuff or go TLP and split it into individual
>> components.
>>> 
>>> Gilles cannot live with the former and we do not have a community left
>> for
>>> the latter. Catch-22.
>>> 
>> 
>> There is no catch-22. Gilles can move Commons Math to a TLP and split it
>> up once he has enough of a community to move it.  Until then he can work on
>> whatever portions of the code he wants or not as he chooses.
>> 
>> If there is a catch-22 it is that the community that gets built up around
>> the current code may not want to split it up.
>> 
>> Ralph
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to