Sent from my [rhymes with tryPod] ;-)
On 26 Sep 2009, at 18:58, Albert Kurucz <albert.kur...@gmail.com> wrote:
Very nice idea to measure the quality.
But sorry Tamas, 50% corrupt or 90% corrupt does not make a
difference for me.
Especially not, when I have feeling that it is possible to maintain a
100% clean repo with the right automation tools.
yes this is possible, but it will be missing so many of the "ok"
artifacts that everyone needs as to make it useful. if you set the
bar too high, nobody will try to jump it.
let's start by setting the bar a little higher than it currently is,
and with deprecation metadata we can start flagging those artifacts
which would not make it over the bar at its new height
central it just too useful... it has gathered critical mass whereby it
is nearly a right of passage for new java projects to get hosted on
central... hosting on central becomes one of those things projects are
asked to do... if we move the goalposts too far or too fast we will
kill the critical mass we have now, and the whole thing will end up a
dead duck
If Sonatype's goal is to sell these tools only for paying customers I
don't have a bad feeling about that.
I don't get that impression
I get the impression that paying customers will get the features
first, but, the impression I have is that Jason feels good artifacts
in central help sonatype make money more than providing commercial
tools to try and filter out the bad from central ever could
Everyone has to make a living.
But I hope sometime similar tools and a clean repo will be available
for the open public.
I hope OSS developers will recognize the need for quality (and a high
quality repo).
On Sat, Sep 26, 2009 at 11:22 AM, Hervé BOUTEMY <herve.bout...@free.
fr> wrote:
Le samedi 26 septembre 2009, Tamás Cservenák a écrit :
I think we all need some clarification, since we all talk about
"quality"
(we all agreed upon the basic things unanimously).
What is the "quality" of a maven repository (in general)? Can we
measure
it? Can we define it?
A wiki page with piled up (even personal) opinions would be good --
don't hesitate to start one on MAVENUSER Wiki [1]
whatever they are -- and later we should cherry-pick the most
relevant ones
to build some tooling to build these metric. And then, we could
"measure"
the quality of different reposes (like central) and have a list of
reposes
that do meet certain "level of quality" and list publicly the
others that
does not.
[1] http://docs.codehaus.org/display/MAVENUSER/Home
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
