Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Thu, 17 Aug 2017 16:42:17 +0200
From: Gilles <gilles@harfang.homelinux.org>
To: <dev@commons.apache.org>
Subject: Re: [All][Math] New component: "Commons =?UTF-8?Q?Geometry=22=3F?=
In-Reply-To: <782E7B47-A587-47AE-BE41-ED28743FE490@apache.org>
References: <715027bee0b4681d76bd15328fad2415@scarlet.be>
 <782E7B47-A587-47AE-BE41-ED28743FE490@apache.org>
Message-ID: <dd1aae97f95b816785b535239acac706@scarlet.be>
User-Agent: Scarlet Webmail
X-DCC-scarlet.be-Metrics: eir; whitelist
X-Virus-Scanned: clamav-milter 0.98.1-exp at eir
X-Virus-Status: Clean
archived-at: Thu, 17 Aug 2017 14:42:29 -0000

Hi Benedikt.

On Thu, 17 Aug 2017 15:48:45 +0200, Benedikt Ritter wrote:
> Hello Gilles,
>
>> Am 15.08.2017 um 16:26 schrieb Gilles 
>> <gilles@harfang.homelinux.org>:
>>
>> Hello.
>>
>> [Time for a new episode in our "Ripping CM" series.]
>>
>> How about creating "Commons Geometry"?
>>
>> The rationale is comprised of the usual suspects:
>> * Smaller and more focused component, hence:
>>   - Consistent development and maintenance.
>>   - Consistent release schedule, not encumbered by
>>     changes (and endless discussions) in _totally_
>>     unrelated code.
>>   - Potential for attracting contributors not
>>     interested in maintaining the (growing) backlog
>>     of CM.
>> * Self-contained: 96.3% of the "o.a.c.math4.geometry"
>>   package have no dependency except:
>>   - 4 classes now in "Commons Numbers".
>>   - 2 methods and 1 constant in "MathUtils".
>>   - CM exceptions. [Creating alternatives for those
>>     will probably be the most time-consuming part of
>>     the porting work.]
>>
>> Moreover, none of the code in the "o.a.c.math4.geometry"
>> package is used by another package of CM.
>>
>> A new component would give the "geometry" codes a much
>> better chance of being (confidently[1]) released, since
>> CM is "stuck" for the foreseeable future.[2]
>>
>> WDYT?
>
> I want to see the initial release of Commons Numbers before breaking
> more components out of CM.

+1
I'm among those who most want to see that release rather sooner
than later.  [IIRC, I posted regularly to inquire about the status
of the pending issues.  Is there more *I* can do at this point?]

I've no problem with serializing the "CM ripping[1]" project.

However, I wish to know what people think of the purely technical,
code-oriented, arguments which I've put forward above.

My suggestion would be to have a "beta" release of the new component
in order to let a community of expert/interested users voice its
opinion on the expected API.  [I think there is a lot of good and
broadly useful code in the "geometry" package (otherwise I wouldn't
ask for a new component) but I also suspect that the API can be
improved.]

Regards,
Gilles

[1] For its own good, and ours. ;-)

> Regards,
> Benedikt
>
>>
>> Gilles
>>
>> [1] There seems to be only one issue reported in JIRA
>>    that pertains to "geometry".
>> [2] 54 issues yet to be fixed before the 4.0 release;
>>    which, at the current rate, would lead to after 2025
>>    (a very rough guess, I admit).
>>


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