You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Amey Jadiye <am...@gmail.com> on 2017/11/30 18:15:45 UTC

Re: [All][Math] New component: "Commons Geometry"?

Pardon me for pulling this thread up again, I havent read anything about
"Commons Geometry" since long (or may be I missed any other disscussion? ).
is someone working on this ? what is the final decision ? I'm having good
amount of time to spend on this now, appreciate If someone direct me to
correct disscussion thread I think I can help here.
It took me half hour to read all old mails but dont see final verdict,
though I was in favour with Maven modules but after reading all again  I
think Gilles approch is more practicle here and If no one is working I can
submit something to review.

Regards,
Amey

On Wed, Sep 13, 2017 at 4:44 AM, Gilles <gi...@harfang.homelinux.org>
wrote:

> On Tue, 12 Sep 2017 13:07:24 +0200, Jochen Wiedmann wrote:
>
>> On Sat, Sep 2, 2017 at 12:50 AM, Gilles <gi...@harfang.homelinux.org>
>> wrote:
>>
>> Because of "Commons" rules, it is not "equivalent": There was
>>> a long thread concluding that all modules must be released
>>> _together_, and with the same top-level package name and version
>>> number.
>>> It is very "maintainer(s)-unfriendly" because of the quite
>>> different subject matters that coexist in CM.
>>>
>>
>> I wouldn't count that rule "*all* modules must be released" as a mantra:
>>
>
> I found the idea attractive, but Stian (link to older discussion
> in a previous post) advised that maven would not easily "support"
> it.
>
> Has that changed since the discussion took place (10 months ago)?
>
> a) In case of an emergency release (fixing a CVE, for example), I'd
>> clearly consider pushing out the module as more important than waiting
>> for a full release. (Of course, one must be careful to maintain
>> compatibility when pushing out just a module, but that goes without
>> saying.)
>> b) I'd like to hear others experiences on that topic (maybe VFS).
>> Anyways, my personal experiences with Rat are clear: Releasing *all*
>> together is causing nothing but pain, and tends to defer releases
>> indefinitely. OTOH, releasing a submodule can be done at all times,
>> and without overly much preparation.
>>
>> In conclusion, I'd definitely support the release of a single
>> submodule, if the need would arise.
>>
>
> How can one reconcile what you say here with what was said in
> that old thread?
>
> Would the PMC accept that a component contains independent modules
> (where "independent" means that each module can have its own version
> number, irrespective of the component's version)?
>
> Arguably (cf. thread referred to above), a "Commons" component
> should be simple enough that multiple versions are not necessary.
> [Chorus:] This is not the case with "Commons Math", hence separate
> components for independent contents (such as "Geometry", "RNG",
> "Numbers" and "SigProc") is the simplest solution.
>
> Gilles
>
> Jochen
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org

For additional commands, e-mail: dev-help@commons.apache.org

Re: [All][Math][Numbers] Refactoring "Commons Math" (Was: [...] "Commons Geometry"?)

Posted by Martijn Verburg <ma...@gmail.com>.
Hi Gilles,

That sounds eminently sensible to me as an end user.  I'd like my 3rd party
deps to be as small as possible, so a modularised Math is good for me.

Cheers,
Martijn

On 7 December 2017 at 17:05, Gilles <gi...@harfang.homelinux.org> wrote:

> Hi Martijn.
>
> On Tue, 5 Dec 2017 23:45:43 +0000, Martijn Verburg wrote:
>
>> Can this project be forked to a new domain over on GitHub (under the
>> existing Apache license),
>>
>
> It is allowed, of course.  However, I think that it is the
> last option to consider, because it will further dilute the
> community that has an interest in the "Commons Math" codebase.
> For developers and for users, there are practical advantages
> in keeping the spin-off projects within "Commons".
> It is even a more appropriate place than a TLP!
> [In this evaluation, I of course do not account for the
> negative stance of part of the PMC.]
>
> split up and then continued in that case?
>>
>
> The work had started.
> Did you have a look at "Commons RNG"[1] and "Commons Numbers"[2]?
> Both were spun off the development version of "Commons Math"[3].
>
> IMO, current priority is to have an initial (beta?) release of
> "Commons Numbers". There is a list of issues in the bug-tracking
> system:
>   https://issues.apache.org/jira/projects/NUMBERS
>
> An important test must pass (before a release can make sense):
> All the code that was "moved" (to "Numbers") must be removed
> from "Math", and functionalities of the latter must be adapted
> to depend on "Numbers".
>
> Afterwards, a probably easy task would be to create another
> generally useful component out of the "o.a.c.math4.geometry"
> package (no other part of CM depends on it and it has almost
> no dependencies on any other CM class).
> Another easy move would be the code in package "o.a.c.math4.ml"
> (zero cross-dependencies). [Although developer and user of that
> package, I admit that the functionality might currently be too
> limited to warrant a component.]
> Less easy (but quite useful) would be a component based on a
> selection of the functionalities in package "o.a.c.math4.analysis"
> (root solver, interpolation, integration).
>
> The rest of CM is either too advanced or with cross-dependencies
> not easy to untangle and/or too many issues to solve, in order
> to create good components, given the scarce human resources...
>
> Next, we can tackle tasks on CM itself:
> - make modules for functionality that is free of issues and
>   supported, and
> - make a "legacy" module for everything else.
> Then, we head toward a long-overdue release.
>
> Opinions on the plan is appreciated, and help to make progress
> (forward!) is most welcome.
>
> Regards,
> Gilles
>
> [1] https://git1-us-west.apache.org/repos/asf?p=commons-rng.git
> [2] https://git1-us-west.apache.org/repos/asf?p=commons-numbers.git
> [3] https://git1-us-west.apache.org/repos/asf?p=commons-math.git
>
>
>> Cheers,
>> Martijn
>>
>> On 3 December 2017 at 11:51, Gilles <gi...@harfang.homelinux.org> wrote:
>>
>> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>>>
>>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org>
>>>> wrote:
>>>>
>>>> There hasn't been any progress towards a decision.
>>>>
>>>>> There isn't even a consensus on one of the central tenets of
>>>>> Apache ("Those who do the work..."): how sad/strange (?).
>>>>>
>>>>>
>>>> Those who do the work are welcome to decide on their own, if they do
>>>> not involve others.
>>>>
>>>>
>>> The conditional is not part of the well-known mantra.
>>>
>>> The issue here is to answer the question of what to do with
>>> a non-trivial code base.  My stance is to try and fix the
>>> problem(s), a.o. difficult management, by rooting out its
>>> main cause: CM has become an aggregate of components with
>>> completely different subject matters, scopes, designs,
>>> efficiencies, provisions for extension, etc.
>>> [An array of issues which "maven" modules will not solve.]
>>>
>>> We are seemingly faced with a choice between:
>>> 1. Maintain CM as the huge library that it is now.
>>> 2. Incrementally create maintainable components.
>>>
>>> A long time has passed since these alternatives were first
>>> exposed, only proving that none of the people who informally
>>> chose option(1) invested work to make it a reality.
>>>
>>> Refusing option (2) not only "involves others"; it is harming
>>> them (very real people, having done a lot of work here, on
>>> that code base).
>>>
>>> Establishing a new commons component doesn't
>>>
>>>> qualify, IMO.
>>>>
>>>>
>>> True; that's why we are stalled, despite that a majority
>>> of the PMC did not explicitly oppose option (2).
>>>
>>> A handful of PMC people prefer to let the code base become
>>> "dormant" rather than give any chance to an alternate view.
>>> [If, say, you looked at the "Commons RNG" project, and
>>> concluded that, decidedly, this is not how a component
>>> should look like, then I could perhaps fathom out where
>>> those reservations come from.]
>>>
>>> Gilles
>>>
>>>
>>> Jochen
>>>>
>>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

[All][Math][Numbers] Refactoring "Commons Math" (Was: [...] "Commons Geometry"?)

Posted by Gilles <gi...@harfang.homelinux.org>.
Hi Martijn.

On Tue, 5 Dec 2017 23:45:43 +0000, Martijn Verburg wrote:
> Can this project be forked to a new domain over on GitHub (under the
> existing Apache license),

It is allowed, of course.  However, I think that it is the
last option to consider, because it will further dilute the
community that has an interest in the "Commons Math" codebase.
For developers and for users, there are practical advantages
in keeping the spin-off projects within "Commons".
It is even a more appropriate place than a TLP!
[In this evaluation, I of course do not account for the
negative stance of part of the PMC.]

> split up and then continued in that case?

The work had started.
Did you have a look at "Commons RNG"[1] and "Commons Numbers"[2]?
Both were spun off the development version of "Commons Math"[3].

IMO, current priority is to have an initial (beta?) release of
"Commons Numbers". There is a list of issues in the bug-tracking
system:
   https://issues.apache.org/jira/projects/NUMBERS

An important test must pass (before a release can make sense):
All the code that was "moved" (to "Numbers") must be removed
from "Math", and functionalities of the latter must be adapted
to depend on "Numbers".

Afterwards, a probably easy task would be to create another
generally useful component out of the "o.a.c.math4.geometry"
package (no other part of CM depends on it and it has almost
no dependencies on any other CM class).
Another easy move would be the code in package "o.a.c.math4.ml"
(zero cross-dependencies). [Although developer and user of that
package, I admit that the functionality might currently be too
limited to warrant a component.]
Less easy (but quite useful) would be a component based on a
selection of the functionalities in package "o.a.c.math4.analysis"
(root solver, interpolation, integration).

The rest of CM is either too advanced or with cross-dependencies
not easy to untangle and/or too many issues to solve, in order
to create good components, given the scarce human resources...

Next, we can tackle tasks on CM itself:
- make modules for functionality that is free of issues and
   supported, and
- make a "legacy" module for everything else.
Then, we head toward a long-overdue release.

Opinions on the plan is appreciated, and help to make progress
(forward!) is most welcome.

Regards,
Gilles

[1] https://git1-us-west.apache.org/repos/asf?p=commons-rng.git
[2] https://git1-us-west.apache.org/repos/asf?p=commons-numbers.git
[3] https://git1-us-west.apache.org/repos/asf?p=commons-math.git

>
> Cheers,
> Martijn
>
> On 3 December 2017 at 11:51, Gilles <gi...@harfang.homelinux.org> 
> wrote:
>
>> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>>
>>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles 
>>> <gi...@harfang.homelinux.org>
>>> wrote:
>>>
>>> There hasn't been any progress towards a decision.
>>>> There isn't even a consensus on one of the central tenets of
>>>> Apache ("Those who do the work..."): how sad/strange (?).
>>>>
>>>
>>> Those who do the work are welcome to decide on their own, if they 
>>> do
>>> not involve others.
>>>
>>
>> The conditional is not part of the well-known mantra.
>>
>> The issue here is to answer the question of what to do with
>> a non-trivial code base.  My stance is to try and fix the
>> problem(s), a.o. difficult management, by rooting out its
>> main cause: CM has become an aggregate of components with
>> completely different subject matters, scopes, designs,
>> efficiencies, provisions for extension, etc.
>> [An array of issues which "maven" modules will not solve.]
>>
>> We are seemingly faced with a choice between:
>> 1. Maintain CM as the huge library that it is now.
>> 2. Incrementally create maintainable components.
>>
>> A long time has passed since these alternatives were first
>> exposed, only proving that none of the people who informally
>> chose option(1) invested work to make it a reality.
>>
>> Refusing option (2) not only "involves others"; it is harming
>> them (very real people, having done a lot of work here, on
>> that code base).
>>
>> Establishing a new commons component doesn't
>>> qualify, IMO.
>>>
>>
>> True; that's why we are stalled, despite that a majority
>> of the PMC did not explicitly oppose option (2).
>>
>> A handful of PMC people prefer to let the code base become
>> "dormant" rather than give any chance to an alternate view.
>> [If, say, you looked at the "Commons RNG" project, and
>> concluded that, decidedly, this is not how a component
>> should look like, then I could perhaps fathom out where
>> those reservations come from.]
>>
>> Gilles
>>
>>
>>> Jochen
>>>



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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Martijn Verburg <ma...@gmail.com>.
Can this project be forked to a new domain over on GitHub (under the
existing Apache license), split up and then continued in that case?

Cheers,
Martijn

On 3 December 2017 at 11:51, Gilles <gi...@harfang.homelinux.org> wrote:

> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>
>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org>
>> wrote:
>>
>> There hasn't been any progress towards a decision.
>>> There isn't even a consensus on one of the central tenets of
>>> Apache ("Those who do the work..."): how sad/strange (?).
>>>
>>
>> Those who do the work are welcome to decide on their own, if they do
>> not involve others.
>>
>
> The conditional is not part of the well-known mantra.
>
> The issue here is to answer the question of what to do with
> a non-trivial code base.  My stance is to try and fix the
> problem(s), a.o. difficult management, by rooting out its
> main cause: CM has become an aggregate of components with
> completely different subject matters, scopes, designs,
> efficiencies, provisions for extension, etc.
> [An array of issues which "maven" modules will not solve.]
>
> We are seemingly faced with a choice between:
> 1. Maintain CM as the huge library that it is now.
> 2. Incrementally create maintainable components.
>
> A long time has passed since these alternatives were first
> exposed, only proving that none of the people who informally
> chose option(1) invested work to make it a reality.
>
> Refusing option (2) not only "involves others"; it is harming
> them (very real people, having done a lot of work here, on
> that code base).
>
> Establishing a new commons component doesn't
>> qualify, IMO.
>>
>
> True; that's why we are stalled, despite that a majority
> of the PMC did not explicitly oppose option (2).
>
> A handful of PMC people prefer to let the code base become
> "dormant" rather than give any chance to an alternate view.
> [If, say, you looked at the "Commons RNG" project, and
> concluded that, decidedly, this is not how a component
> should look like, then I could perhaps fathom out where
> those reservations come from.]
>
> Gilles
>
>
>> Jochen
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Re: [All][Math] New component: "Commons Geometry"?

Posted by Stephen Colebourne <sc...@joda.org>.
Frankly, as an observer, this issue seems to be handled pretty poorly.
Commons-Math is currently dead. There are people willing to put in
effort to work on parts of it, but they are blocked at every turn.
Various options are put forward, but nothing ever happens.

In technical terms, if Commons-Math were a TLP, it would no doubt
release multiple separate releases, just like commons does. Thus,
separate commons projects seems like a good model.

Commons-VFS is not a good comparator, as it is a single "narrow and
deep" library with plugins. Commons-Math is a "broad and shallow"
library by comparison [1]. Subdivisions of a "broad and shallow"
library are best managed with separate release cycles, as each part is
independent of the others. (commons [lang], [collections] and [io] are
not forced to be multi-module simply because they all release to the
java.base module).

Anyway, the original rules for Commons [2] required a majority
approval vote (more +1 than -1) to create a new component, which has
already happended AFAICT. So, I think those that want to create a new
component should JFDI.

Stephen


[1] https://marc.info/?l=jakarta-commons-dev&m=108601577728628&w=2
[2] http://commons.apache.org/oldcharter.html (item 15)



On 6 December 2017 at 12:59, Gilles <gi...@harfang.homelinux.org> wrote:
> Hi Ralph.
>
> On Tue, 5 Dec 2017 22:38:06 -0700, Ralph Goers wrote:
>>
>> I don’t know
>
>
> Then please _read_ the ML archive.
>
>> why you are ignoring
>
>
> I do not (willingly) "ignore" any proposal. [Gentle
> reminders are welcome if/when I lost track of a pending
> issue that is waiting for my input.]
>
> It's rather the opposite: a few PMC people keep turning
> a blind eye to arguably constructive proposals (see below
> and ML archive).
>
>> option 3, which is what many have
>> suggested many times.
>
>
> With strings attached. See ML archive.
>
>> 3) Modify CM to be a multi-module project
>
>
> See below; what don't you understand in "issues which
> maven modules will not solve"?
> [See ML archive for a many times reiterated detailed
> description of the CM problems, the difference between
> CM and other components (modular or not), here and
> elsewhere, and how we do not have (never had) the human
> resources to correctly handle such a large and diverse
> code base.]
>
>> that contains only the
>> modules you want to support.
>
>
> That condition was explicitly rejected  when *I* first
> evoked it (see ML archive).
>
> Later discussions (see ML archive) clarified (?!) that
> modularizing CM would certainly not suffice to revive
> the project.
>
> Other options were (see ML archive)
> 4. create an Apache TLP (proposed by James Carman),
> 5. go through the Incubator.
>
> Either one required the PMC to relinquish the code base
> (no internal fork allowed IIUC), which it refused (see ML
> archive).
>
> The now visible consequences of renewed obstruction to
> the refactoring of CM were not difficult to predict (see
> ML archive).
>
> Gilles
>
>
>
>> Ralph
>>
>>> On Dec 3, 2017, at 4:51 AM, Gilles <gi...@harfang.homelinux.org> wrote:
>>>
>>> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>>>>
>>>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org>
>>>> wrote:
>>>>
>>>>> There hasn't been any progress towards a decision.
>>>>> There isn't even a consensus on one of the central tenets of
>>>>> Apache ("Those who do the work..."): how sad/strange (?).
>>>>
>>>>
>>>> Those who do the work are welcome to decide on their own, if they do
>>>> not involve others.
>>>
>>>
>>> The conditional is not part of the well-known mantra.
>>>
>>> The issue here is to answer the question of what to do with
>>> a non-trivial code base.  My stance is to try and fix the
>>> problem(s), a.o. difficult management, by rooting out its
>>> main cause: CM has become an aggregate of components with
>>> completely different subject matters, scopes, designs,
>>> efficiencies, provisions for extension, etc.
>>> [An array of issues which "maven" modules will not solve.]
>>>
>>> We are seemingly faced with a choice between:
>>> 1. Maintain CM as the huge library that it is now.
>>> 2. Incrementally create maintainable components.
>>>
>>> A long time has passed since these alternatives were first
>>> exposed, only proving that none of the people who informally
>>> chose option(1) invested work to make it a reality.
>>>
>>> Refusing option (2) not only "involves others"; it is harming
>>> them (very real people, having done a lot of work here, on
>>> that code base).
>>>
>>>> Establishing a new commons component doesn't
>>>> qualify, IMO.
>>>
>>>
>>> True; that's why we are stalled, despite that a majority
>>> of the PMC did not explicitly oppose option (2).
>>>
>>> A handful of PMC people prefer to let the code base become
>>> "dormant" rather than give any chance to an alternate view.
>>> [If, say, you looked at the "Commons RNG" project, and
>>> concluded that, decidedly, this is not how a component
>>> should look like, then I could perhaps fathom out where
>>> those reservations come from.]
>>>
>>> Gilles
>>>
>>>>
>>>> Jochen
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Gilles <gi...@harfang.homelinux.org>.
Hi Ralph.

On Tue, 5 Dec 2017 22:38:06 -0700, Ralph Goers wrote:
> I don’t know

Then please _read_ the ML archive.

> why you are ignoring

I do not (willingly) "ignore" any proposal. [Gentle
reminders are welcome if/when I lost track of a pending
issue that is waiting for my input.]

It's rather the opposite: a few PMC people keep turning
a blind eye to arguably constructive proposals (see below
and ML archive).

> option 3, which is what many have
> suggested many times.

With strings attached. See ML archive.

> 3) Modify CM to be a multi-module project

See below; what don't you understand in "issues which
maven modules will not solve"?
[See ML archive for a many times reiterated detailed
description of the CM problems, the difference between
CM and other components (modular or not), here and
elsewhere, and how we do not have (never had) the human
resources to correctly handle such a large and diverse
code base.]

> that contains only the
> modules you want to support.

That condition was explicitly rejected  when *I* first
evoked it (see ML archive).

Later discussions (see ML archive) clarified (?!) that
modularizing CM would certainly not suffice to revive
the project.

Other options were (see ML archive)
4. create an Apache TLP (proposed by James Carman),
5. go through the Incubator.

Either one required the PMC to relinquish the code base
(no internal fork allowed IIUC), which it refused (see ML
archive).

The now visible consequences of renewed obstruction to
the refactoring of CM were not difficult to predict (see
ML archive).

Gilles


> Ralph
>
>> On Dec 3, 2017, at 4:51 AM, Gilles <gi...@harfang.homelinux.org> 
>> wrote:
>>
>> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles 
>>> <gi...@harfang.homelinux.org> wrote:
>>>
>>>> There hasn't been any progress towards a decision.
>>>> There isn't even a consensus on one of the central tenets of
>>>> Apache ("Those who do the work..."): how sad/strange (?).
>>>
>>> Those who do the work are welcome to decide on their own, if they 
>>> do
>>> not involve others.
>>
>> The conditional is not part of the well-known mantra.
>>
>> The issue here is to answer the question of what to do with
>> a non-trivial code base.  My stance is to try and fix the
>> problem(s), a.o. difficult management, by rooting out its
>> main cause: CM has become an aggregate of components with
>> completely different subject matters, scopes, designs,
>> efficiencies, provisions for extension, etc.
>> [An array of issues which "maven" modules will not solve.]
>>
>> We are seemingly faced with a choice between:
>> 1. Maintain CM as the huge library that it is now.
>> 2. Incrementally create maintainable components.
>>
>> A long time has passed since these alternatives were first
>> exposed, only proving that none of the people who informally
>> chose option(1) invested work to make it a reality.
>>
>> Refusing option (2) not only "involves others"; it is harming
>> them (very real people, having done a lot of work here, on
>> that code base).
>>
>>> Establishing a new commons component doesn't
>>> qualify, IMO.
>>
>> True; that's why we are stalled, despite that a majority
>> of the PMC did not explicitly oppose option (2).
>>
>> A handful of PMC people prefer to let the code base become
>> "dormant" rather than give any chance to an alternate view.
>> [If, say, you looked at the "Commons RNG" project, and
>> concluded that, decidedly, this is not how a component
>> should look like, then I could perhaps fathom out where
>> those reservations come from.]
>>
>> Gilles
>>
>>>
>>> Jochen


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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Ralph Goers <ra...@dslextreme.com>.
I don’t know why you are ignoring option 3, which is what many have suggested many times.
3) Modify CM to be a multi-module project that contains only the modules you want to support.

Ralph

> On Dec 3, 2017, at 4:51 AM, Gilles <gi...@harfang.homelinux.org> wrote:
> 
> On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
>> On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org> wrote:
>> 
>>> There hasn't been any progress towards a decision.
>>> There isn't even a consensus on one of the central tenets of
>>> Apache ("Those who do the work..."): how sad/strange (?).
>> 
>> Those who do the work are welcome to decide on their own, if they do
>> not involve others.
> 
> The conditional is not part of the well-known mantra.
> 
> The issue here is to answer the question of what to do with
> a non-trivial code base.  My stance is to try and fix the
> problem(s), a.o. difficult management, by rooting out its
> main cause: CM has become an aggregate of components with
> completely different subject matters, scopes, designs,
> efficiencies, provisions for extension, etc.
> [An array of issues which "maven" modules will not solve.]
> 
> We are seemingly faced with a choice between:
> 1. Maintain CM as the huge library that it is now.
> 2. Incrementally create maintainable components.
> 
> A long time has passed since these alternatives were first
> exposed, only proving that none of the people who informally
> chose option(1) invested work to make it a reality.
> 
> Refusing option (2) not only "involves others"; it is harming
> them (very real people, having done a lot of work here, on
> that code base).
> 
>> Establishing a new commons component doesn't
>> qualify, IMO.
> 
> True; that's why we are stalled, despite that a majority
> of the PMC did not explicitly oppose option (2).
> 
> A handful of PMC people prefer to let the code base become
> "dormant" rather than give any chance to an alternate view.
> [If, say, you looked at the "Commons RNG" project, and
> concluded that, decidedly, this is not how a component
> should look like, then I could perhaps fathom out where
> those reservations come from.]
> 
> Gilles
> 
>> 
>> Jochen
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> 



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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Gilles <gi...@harfang.homelinux.org>.
On Sun, 3 Dec 2017 11:18:18 +0100, Jochen Wiedmann wrote:
> On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org> 
> wrote:
>
>> There hasn't been any progress towards a decision.
>> There isn't even a consensus on one of the central tenets of
>> Apache ("Those who do the work..."): how sad/strange (?).
>
> Those who do the work are welcome to decide on their own, if they do
> not involve others.

The conditional is not part of the well-known mantra.

The issue here is to answer the question of what to do with
a non-trivial code base.  My stance is to try and fix the
problem(s), a.o. difficult management, by rooting out its
main cause: CM has become an aggregate of components with
completely different subject matters, scopes, designs,
efficiencies, provisions for extension, etc.
[An array of issues which "maven" modules will not solve.]

We are seemingly faced with a choice between:
1. Maintain CM as the huge library that it is now.
2. Incrementally create maintainable components.

A long time has passed since these alternatives were first
exposed, only proving that none of the people who informally
chose option(1) invested work to make it a reality.

Refusing option (2) not only "involves others"; it is harming
them (very real people, having done a lot of work here, on
that code base).

> Establishing a new commons component doesn't
> qualify, IMO.

True; that's why we are stalled, despite that a majority
of the PMC did not explicitly oppose option (2).

A handful of PMC people prefer to let the code base become
"dormant" rather than give any chance to an alternate view.
[If, say, you looked at the "Commons RNG" project, and
concluded that, decidedly, this is not how a component
should look like, then I could perhaps fathom out where
those reservations come from.]

Gilles

>
> Jochen


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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Jochen Wiedmann <jo...@gmail.com>.
On Fri, Dec 1, 2017 at 2:26 PM, Gilles <gi...@harfang.homelinux.org> wrote:

> There hasn't been any progress towards a decision.
> There isn't even a consensus on one of the central tenets of
> Apache ("Those who do the work..."): how sad/strange (?).

Those who do the work are welcome to decide on their own, if they do
not involve others. Establishing a new commons component doesn't
qualify, IMO.

Jochen


-- 
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Amey Jadiye <am...@gmail.com>.
On Fri, Dec 1, 2017 at 7:23 PM, Amey Jadiye <am...@gmail.com> wrote:

>
>
> On Fri, Dec 1, 2017 at 6:56 PM, Gilles <gi...@harfang.homelinux.org>
> wrote:
>
>> Hello Amey.
>
>
> Hi Gilles,
>
>>
>>
>> On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
>>
>>> Pardon me for pulling this thread up again, I havent read anything about
>>> "Commons Geometry" since long
>>>
>>
>> Thanks for your renewed interest.
>>
>> (or may be I missed any other disscussion? ).
>>>
>>
>> Probably not.
>>
>> is someone working on this ?
>>>
>>
>> It would be a surprise.
>>
>> what is the final decision ?
>>>
>>
>> There hasn't been any progress towards a decision.
>>
>
> I'm not sure if "Lazy Consensus" works in these matters ? better take help
> of it, its fast and easy.
>
>
>> There isn't even a consensus on one of the central tenets of
>> Apache ("Those who do the work..."): how sad/strange (?).
>>
>> I'm having good
>>> amount of time to spend on this now, appreciate If someone direct me to
>>> correct disscussion thread
>>>
>>
>> IIRC, the one below is where we left off...
>>
>> I think I can help here.
>>>
>>
>> Thanks for the offer!
>>
>> It took me half hour to read all old mails but dont see final verdict,
>>> though I was in favour with Maven modules but after reading all again I
>>> think Gilles approch is more practicle here and If no one is working I
>>> can
>>> submit something to review.
>>>
>>
>> IMHO, the priority would be to review the status of "Numbers"
>> (i.e. what is preventing a first release?).
>>
>
> Ok, If commons number is priority let me check that first, I will chime in
> here after that release.
> last numbers release I see on 22/4/17,
>

apologies, that date belongs to site publish and SNAPSHOT, not the alpha
release.

and total open jiras are 18, what are min expectation here ?
> I will open another thread If want advise., let this thread alive for
> o.a.c.geometry.
>
> Regards,
> Amey
>
>
>> Best regards,
>> Gilles
>>
>>
>>
>> Regards,
>>> Amey
>>>
>>> On Wed, Sep 13, 2017 at 4:44 AM, Gilles <gi...@harfang.homelinux.org>
>>> wrote:
>>>
>>> On Tue, 12 Sep 2017 13:07:24 +0200, Jochen Wiedmann wrote:
>>>>
>>>> On Sat, Sep 2, 2017 at 12:50 AM, Gilles <gi...@harfang.homelinux.org>
>>>>> wrote:
>>>>>
>>>>> Because of "Commons" rules, it is not "equivalent": There was
>>>>>
>>>>>> a long thread concluding that all modules must be released
>>>>>> _together_, and with the same top-level package name and version
>>>>>> number.
>>>>>> It is very "maintainer(s)-unfriendly" because of the quite
>>>>>> different subject matters that coexist in CM.
>>>>>>
>>>>>>
>>>>> I wouldn't count that rule "*all* modules must be released" as a
>>>>> mantra:
>>>>>
>>>>>
>>>> I found the idea attractive, but Stian (link to older discussion
>>>> in a previous post) advised that maven would not easily "support"
>>>> it.
>>>>
>>>> Has that changed since the discussion took place (10 months ago)?
>>>>
>>>> a) In case of an emergency release (fixing a CVE, for example), I'd
>>>>
>>>>> clearly consider pushing out the module as more important than waiting
>>>>> for a full release. (Of course, one must be careful to maintain
>>>>> compatibility when pushing out just a module, but that goes without
>>>>> saying.)
>>>>> b) I'd like to hear others experiences on that topic (maybe VFS).
>>>>> Anyways, my personal experiences with Rat are clear: Releasing *all*
>>>>> together is causing nothing but pain, and tends to defer releases
>>>>> indefinitely. OTOH, releasing a submodule can be done at all times,
>>>>> and without overly much preparation.
>>>>>
>>>>> In conclusion, I'd definitely support the release of a single
>>>>> submodule, if the need would arise.
>>>>>
>>>>>
>>>> How can one reconcile what you say here with what was said in
>>>> that old thread?
>>>>
>>>> Would the PMC accept that a component contains independent modules
>>>> (where "independent" means that each module can have its own version
>>>> number, irrespective of the component's version)?
>>>>
>>>> Arguably (cf. thread referred to above), a "Commons" component
>>>> should be simple enough that multiple versions are not necessary.
>>>> [Chorus:] This is not the case with "Commons Math", hence separate
>>>> components for independent contents (such as "Geometry", "RNG",
>>>> "Numbers" and "SigProc") is the simplest solution.
>>>>
>>>> Gilles
>>>>
>>>> Jochen
>>>>
>>>>>
>>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
>
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>
> For additional commands, e-mail: dev-help@commons.apache.org
>



-- 

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org

For additional commands, e-mail: dev-help@commons.apache.org

Re: [All][Math] New component: "Commons Geometry"?

Posted by Gilles <gi...@harfang.homelinux.org>.
Hi.

On Sat, 2 Dec 2017 20:40:38 +0000, Martijn Verburg wrote:
> Has the PMC and the active developers met over a video call to try 
> and hash
> this out?

The ML archive is replete with discussions.
A few PMC members voiced their agreement with the Apache mantra.
A few oppose trying an approach that would break the status quo,
even as it has stalled development (the next major release is
nowhere in sight, almost 3 years after work started on it).

> It would be a shame to see this library fall into disuse.

The library can be used but is virtually unmaintained.

IMO, the question is why the loss of continuity is being preferred
over a proposal that costs only to those who are willing to put
work in it.
The asymmetry of the situation should be obvious...

> I'd also argue with Jigsaw being the heart of Java 9+ that more 
> modular
> libs now make sense.

+1 to a separation of concerns that allows for clear and independent
lines of development.

Regards,
Gilles

> Cheers,
> Martijn
>
> On 1 December 2017 at 14:56, Gilles <gi...@harfang.homelinux.org> 
> wrote:
>
>> On Fri, 1 Dec 2017 19:23:57 +0530, Amey Jadiye wrote:
>>
>>> On Fri, Dec 1, 2017 at 6:56 PM, Gilles 
>>> <gi...@harfang.homelinux.org>
>>> wrote:
>>>
>>> Hello Amey.
>>>>
>>>
>>>
>>> Hi Gilles,
>>>
>>>
>>>>
>>>> On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
>>>>
>>>> Pardon me for pulling this thread up again, I havent read anything 
>>>> about
>>>>> "Commons Geometry" since long
>>>>>
>>>>>
>>>> Thanks for your renewed interest.
>>>>
>>>> (or may be I missed any other disscussion? ).
>>>>
>>>>>
>>>>>
>>>> Probably not.
>>>>
>>>> is someone working on this ?
>>>>
>>>>>
>>>>>
>>>> It would be a surprise.
>>>>
>>>> what is the final decision ?
>>>>
>>>>>
>>>>>
>>>> There hasn't been any progress towards a decision.
>>>>
>>>>
>>> I'm not sure if "Lazy Consensus" works in these matters ? better 
>>> take help
>>> of it, its fast and easy.
>>>
>>
>> By definition, it does not apply when people voice their opinion:
>> Some did it one way, others did it in another (non-compatible way).
>>
>> The strange thing here is that some PMC members seem to prefer
>> moving Commons Math to "dormant" rather than let the few remaining
>> active developers do some cleanup in the hope to revivify some of
>> the code base in a more modern Java eco-system.
>>
>> Gilles
>>
>> [...]
>>>


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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Martijn Verburg <ma...@gmail.com>.
Has the PMC and the active developers met over a video call to try and hash
this out?

It would be a shame to see this library fall into disuse.

I'd also argue with Jigsaw being the heart of Java 9+ that more modular
libs now make sense.

Cheers,
Martijn

On 1 December 2017 at 14:56, Gilles <gi...@harfang.homelinux.org> wrote:

> On Fri, 1 Dec 2017 19:23:57 +0530, Amey Jadiye wrote:
>
>> On Fri, Dec 1, 2017 at 6:56 PM, Gilles <gi...@harfang.homelinux.org>
>> wrote:
>>
>> Hello Amey.
>>>
>>
>>
>> Hi Gilles,
>>
>>
>>>
>>> On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
>>>
>>> Pardon me for pulling this thread up again, I havent read anything about
>>>> "Commons Geometry" since long
>>>>
>>>>
>>> Thanks for your renewed interest.
>>>
>>> (or may be I missed any other disscussion? ).
>>>
>>>>
>>>>
>>> Probably not.
>>>
>>> is someone working on this ?
>>>
>>>>
>>>>
>>> It would be a surprise.
>>>
>>> what is the final decision ?
>>>
>>>>
>>>>
>>> There hasn't been any progress towards a decision.
>>>
>>>
>> I'm not sure if "Lazy Consensus" works in these matters ? better take help
>> of it, its fast and easy.
>>
>
> By definition, it does not apply when people voice their opinion:
> Some did it one way, others did it in another (non-compatible way).
>
> The strange thing here is that some PMC members seem to prefer
> moving Commons Math to "dormant" rather than let the few remaining
> active developers do some cleanup in the hope to revivify some of
> the code base in a more modern Java eco-system.
>
> Gilles
>
> [...]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Re: [All][Math] New component: "Commons Geometry"?

Posted by Gilles <gi...@harfang.homelinux.org>.
On Fri, 1 Dec 2017 19:23:57 +0530, Amey Jadiye wrote:
> On Fri, Dec 1, 2017 at 6:56 PM, Gilles <gi...@harfang.homelinux.org> 
> wrote:
>
>> Hello Amey.
>
>
> Hi Gilles,
>
>>
>>
>> On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
>>
>>> Pardon me for pulling this thread up again, I havent read anything 
>>> about
>>> "Commons Geometry" since long
>>>
>>
>> Thanks for your renewed interest.
>>
>> (or may be I missed any other disscussion? ).
>>>
>>
>> Probably not.
>>
>> is someone working on this ?
>>>
>>
>> It would be a surprise.
>>
>> what is the final decision ?
>>>
>>
>> There hasn't been any progress towards a decision.
>>
>
> I'm not sure if "Lazy Consensus" works in these matters ? better take 
> help
> of it, its fast and easy.

By definition, it does not apply when people voice their opinion:
Some did it one way, others did it in another (non-compatible way).

The strange thing here is that some PMC members seem to prefer
moving Commons Math to "dormant" rather than let the few remaining
active developers do some cleanup in the hope to revivify some of
the code base in a more modern Java eco-system.

Gilles

> [...]


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


Re: [All][Math] New component: "Commons Geometry"?

Posted by Amey Jadiye <am...@gmail.com>.
On Fri, Dec 1, 2017 at 6:56 PM, Gilles <gi...@harfang.homelinux.org> wrote:

> Hello Amey.


Hi Gilles,

>
>
> On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
>
>> Pardon me for pulling this thread up again, I havent read anything about
>> "Commons Geometry" since long
>>
>
> Thanks for your renewed interest.
>
> (or may be I missed any other disscussion? ).
>>
>
> Probably not.
>
> is someone working on this ?
>>
>
> It would be a surprise.
>
> what is the final decision ?
>>
>
> There hasn't been any progress towards a decision.
>

I'm not sure if "Lazy Consensus" works in these matters ? better take help
of it, its fast and easy.


> There isn't even a consensus on one of the central tenets of
> Apache ("Those who do the work..."): how sad/strange (?).
>
> I'm having good
>> amount of time to spend on this now, appreciate If someone direct me to
>> correct disscussion thread
>>
>
> IIRC, the one below is where we left off...
>
> I think I can help here.
>>
>
> Thanks for the offer!
>
> It took me half hour to read all old mails but dont see final verdict,
>> though I was in favour with Maven modules but after reading all again I
>> think Gilles approch is more practicle here and If no one is working I can
>> submit something to review.
>>
>
> IMHO, the priority would be to review the status of "Numbers"
> (i.e. what is preventing a first release?).
>

Ok, If commons number is priority let me check that first, I will chime in
here after that release.
last numbers release I see on 22/4/17, and total open jiras are 18, what
are min expectation here ?
I will open another thread If want advise., let this thread alive for
o.a.c.geometry.

Regards,
Amey


> Best regards,
> Gilles
>
>
>
> Regards,
>> Amey
>>
>> On Wed, Sep 13, 2017 at 4:44 AM, Gilles <gi...@harfang.homelinux.org>
>> wrote:
>>
>> On Tue, 12 Sep 2017 13:07:24 +0200, Jochen Wiedmann wrote:
>>>
>>> On Sat, Sep 2, 2017 at 12:50 AM, Gilles <gi...@harfang.homelinux.org>
>>>> wrote:
>>>>
>>>> Because of "Commons" rules, it is not "equivalent": There was
>>>>
>>>>> a long thread concluding that all modules must be released
>>>>> _together_, and with the same top-level package name and version
>>>>> number.
>>>>> It is very "maintainer(s)-unfriendly" because of the quite
>>>>> different subject matters that coexist in CM.
>>>>>
>>>>>
>>>> I wouldn't count that rule "*all* modules must be released" as a mantra:
>>>>
>>>>
>>> I found the idea attractive, but Stian (link to older discussion
>>> in a previous post) advised that maven would not easily "support"
>>> it.
>>>
>>> Has that changed since the discussion took place (10 months ago)?
>>>
>>> a) In case of an emergency release (fixing a CVE, for example), I'd
>>>
>>>> clearly consider pushing out the module as more important than waiting
>>>> for a full release. (Of course, one must be careful to maintain
>>>> compatibility when pushing out just a module, but that goes without
>>>> saying.)
>>>> b) I'd like to hear others experiences on that topic (maybe VFS).
>>>> Anyways, my personal experiences with Rat are clear: Releasing *all*
>>>> together is causing nothing but pain, and tends to defer releases
>>>> indefinitely. OTOH, releasing a submodule can be done at all times,
>>>> and without overly much preparation.
>>>>
>>>> In conclusion, I'd definitely support the release of a single
>>>> submodule, if the need would arise.
>>>>
>>>>
>>> How can one reconcile what you say here with what was said in
>>> that old thread?
>>>
>>> Would the PMC accept that a component contains independent modules
>>> (where "independent" means that each module can have its own version
>>> number, irrespective of the component's version)?
>>>
>>> Arguably (cf. thread referred to above), a "Commons" component
>>> should be simple enough that multiple versions are not necessary.
>>> [Chorus:] This is not the case with "Commons Math", hence separate
>>> components for independent contents (such as "Geometry", "RNG",
>>> "Numbers" and "SigProc") is the simplest solution.
>>>
>>> Gilles
>>>
>>> Jochen
>>>
>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org

For additional commands, e-mail: dev-help@commons.apache.org

Re: [All][Math] New component: "Commons Geometry"?

Posted by Gilles <gi...@harfang.homelinux.org>.
Hello Amey.

On Thu, 30 Nov 2017 23:45:45 +0530, Amey Jadiye wrote:
> Pardon me for pulling this thread up again, I havent read anything 
> about
> "Commons Geometry" since long

Thanks for your renewed interest.

> (or may be I missed any other disscussion? ).

Probably not.

> is someone working on this ?

It would be a surprise.

> what is the final decision ?

There hasn't been any progress towards a decision.
There isn't even a consensus on one of the central tenets of
Apache ("Those who do the work..."): how sad/strange (?).

> I'm having good
> amount of time to spend on this now, appreciate If someone direct me 
> to
> correct disscussion thread

IIRC, the one below is where we left off...

> I think I can help here.

Thanks for the offer!

> It took me half hour to read all old mails but dont see final 
> verdict,
> though I was in favour with Maven modules but after reading all again 
> I
> think Gilles approch is more practicle here and If no one is working 
> I can
> submit something to review.

IMHO, the priority would be to review the status of "Numbers"
(i.e. what is preventing a first release?).

Best regards,
Gilles


> Regards,
> Amey
>
> On Wed, Sep 13, 2017 at 4:44 AM, Gilles 
> <gi...@harfang.homelinux.org>
> wrote:
>
>> On Tue, 12 Sep 2017 13:07:24 +0200, Jochen Wiedmann wrote:
>>
>>> On Sat, Sep 2, 2017 at 12:50 AM, Gilles 
>>> <gi...@harfang.homelinux.org>
>>> wrote:
>>>
>>> Because of "Commons" rules, it is not "equivalent": There was
>>>> a long thread concluding that all modules must be released
>>>> _together_, and with the same top-level package name and version
>>>> number.
>>>> It is very "maintainer(s)-unfriendly" because of the quite
>>>> different subject matters that coexist in CM.
>>>>
>>>
>>> I wouldn't count that rule "*all* modules must be released" as a 
>>> mantra:
>>>
>>
>> I found the idea attractive, but Stian (link to older discussion
>> in a previous post) advised that maven would not easily "support"
>> it.
>>
>> Has that changed since the discussion took place (10 months ago)?
>>
>> a) In case of an emergency release (fixing a CVE, for example), I'd
>>> clearly consider pushing out the module as more important than 
>>> waiting
>>> for a full release. (Of course, one must be careful to maintain
>>> compatibility when pushing out just a module, but that goes without
>>> saying.)
>>> b) I'd like to hear others experiences on that topic (maybe VFS).
>>> Anyways, my personal experiences with Rat are clear: Releasing 
>>> *all*
>>> together is causing nothing but pain, and tends to defer releases
>>> indefinitely. OTOH, releasing a submodule can be done at all times,
>>> and without overly much preparation.
>>>
>>> In conclusion, I'd definitely support the release of a single
>>> submodule, if the need would arise.
>>>
>>
>> How can one reconcile what you say here with what was said in
>> that old thread?
>>
>> Would the PMC accept that a component contains independent modules
>> (where "independent" means that each module can have its own version
>> number, irrespective of the component's version)?
>>
>> Arguably (cf. thread referred to above), a "Commons" component
>> should be simple enough that multiple versions are not necessary.
>> [Chorus:] This is not the case with "Commons Math", hence separate
>> components for independent contents (such as "Geometry", "RNG",
>> "Numbers" and "SigProc") is the simplest solution.
>>
>> Gilles
>>
>> Jochen
>>>


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