On Mon, 30 Jan 2017 12:30:20 +0100, Emmanuel Bourg wrote:
Le 30/01/2017 à 12:08, Gilles a écrit :
Ideally, it should be another light-weight component (because
solvers
are used in so many areas).
This thread is about if (and how) we can try and stretch the scope a
little, so as to group several basic utilities in a single
component.
I'd prefer creating [math] sub modules than independent components.
Either you or I have misunderstood the consensus that CM cannot
provide (what I'd call) "partial" releases (I had proposed that
currently unsupported code[1] will not be released anymore).
The consequence is that the date of the next release of CM was
likely to be: never.
The consequence of which is that valuable _and_ supported code
must be moved to other components (that would also become a
good opportunity to get rid of obsolete stuff, and redesign
without backwards compatibility burdens) in order to be useful
to a larger audience.
Otherwise what will be left in [math] once you are done slicing it?
Good question.
Development can be viewed from the [Math] component POV (removing
stuff) or from each of the new components' view (what's in scope?).
The former POV leads to project death.[2]
The latter is being worked on, and in the end, the goal is that
CM will loose nothing[3]: it will depend on other components where
the "removed" functionality has been transferred.
A big component like Commons Math is a nightmare to manage; as
we've seen, it simply did not work (reasons, according to me, have
been already amply exposed on this ML).
Small components are more agile.
The proposed roadmap increases the chances to attract enough
contributors so that eventually the huge task of supporting
the whole of CM can be considered again.
In the meantime, more focused components can attract contributors
who will not have to wait years to see their work released
officially.
This IMO is actually more community-building stuff than clinging
onto an old component, full of good code[4] but an empty shell,
community-wise.
Gilles
Emmanuel Bourg
[1] Unsupported = nobody knows the code enough to timely follow up
on reports about it.
[2] Visible symptom is: nobody works on reports piling up in JIRA.
[3] Of course, there will backwards incompatible changes, but that
fact was agreed on several years ago, when the then current
development branch was aimed at releasing the next major version.
[4] But also containing outdated things to be revamped or thrown away.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
