On 04/02/2013 05:07, Christian Grobmeier wrote:
On Sun, Feb 3, 2013 at 8:10 AM, Eric Charles <e...@apache.org> wrote:
As stated before, I am convinced that we must provide small, modular
modules.
+1
However, I just want to ensure that we don't finish at the end with so many
micro modules that reviewer and users don't take time to become they could
think they are too fragmented.
Currently I only think on the users. In future (I mean after
graduation) we will be our own reviewers and well, we have to deal
with our own things then. I would like to build packages which make
technical sense, not ones which is easy to vote on (if both can be
achieved, good).
Actually we should think in this case if it makes sense to make jar
files for a single class. Or if we should just provide a single jar.
+1
When I said 'reviewer' or 'user', I meant 'non-onami-developer'.
I must makes technical sense to make a jar, but IMHO it must also makes
sense to *all* 'non-onami-developer'.
Thx, Eric
In the particular case of the incubator vote, we should provided the link to
the source jar.
For my particular use case, I hope the future 'all' module I would like to
use will for example provide transparently the src-jar so when I browse in
Eclipse, I have the source automatically downloaded from the repo and can
see it in the editor.
+1
Thx, Eric
[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201302.mbox/%3C510D82CF.7020706%40apache.org%3E
--
http://www.grobmeier.de
https://www.timeandbill.de
