You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by nicolas de loof <ni...@apache.org> on 2008/01/15 17:28:27 UTC
component suggest : commons-monitoring
Hello,
I just asked for an apache lab for a java monitoring component
(
http://labs.markmail.org/search/list:org.apache.labs.labs#query:list%3Aorg.apache.labs.labs+page:1+mid:bkztzg2rmceuopvq+state:results
)
One year ago I've created a sourceforge project (www.jmonit.org) with same
idea in mind, and used it @work, but did not yet create a community around
this project that could make it eligible to the apache incubator.
As an alternative to apache labs, the apache.commons sandbox seems to be the
best place to create such a component, and to get feedback from the wide and
talentuous apache developers community.
What is the "apache.commons" way for such contribution request ?
Nico.
Re: component suggest : commons-monitoring
Posted by nicolas de loof <ni...@apache.org>.
The current jmonit code base is more an experiment, or a "proof of concept",
than a stable codebase ready for incubation.
My intention is to start a new component from scratch, taking benefict from
this first attempt.
That is the reason why I do not take incubator as first option.
Nico.
We have a policy that any ASF committer can start something in our
> Sandbox. Usually though this is people starting out from scratch, not
> importing an existing code base from outside the ASF (and Apache Labs
> is similar). For importing an existing code base then at a minimum we
> would probably need to at least use the Incubator IP Clearance check
> list (the Mantissa contribution to Commons Math did this a while back,
> so the archives may give you some pointers).
>
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> So I think its really down to you on the route you want to take -
> whether here or elsewhere
>
> Niall
>
> > Nico.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: component suggest : commons-monitoring
Posted by nicolas de loof <ni...@apache.org>.
I've found the example proposal in the sandbox/project-template.
I'll publish one soon.
2008/1/16, Rahul Akolkar <ra...@gmail.com>:
>
> On 1/16/08, nicolas de loof <ni...@apache.org> wrote:
> > I'm ok with the graduate rule.
> >
> > Could you please grant me access to the sandbox SVN ?
> >
> > Is there some rule to follow for documentation, to best fit with other
> > commons ?
> >
> <snip/>
>
> In addition to what Hen said, IMO its good to have a slightly more
> formal [PROPOSAL] thread, with some more details (this can actually be
> helpful because it requires some thinking about the scope, this gets
> communicated to the list etc. and can also produce feedback from
> others).
>
> There are some docs and a template in the old charter [1], but here is
> an example [2]. There could be better examples, but this one is
> easiest for me to find ;-)
>
> -Rahul
>
> [1] http://commons.apache.org/oldcharter.html
> [2] http://markmail.org/message/kpfukwihmw273yj4
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: component suggest : commons-monitoring
Posted by Rahul Akolkar <ra...@gmail.com>.
On 1/16/08, nicolas de loof <ni...@apache.org> wrote:
> I'm ok with the graduate rule.
>
> Could you please grant me access to the sandbox SVN ?
>
> Is there some rule to follow for documentation, to best fit with other
> commons ?
>
<snip/>
In addition to what Hen said, IMO its good to have a slightly more
formal [PROPOSAL] thread, with some more details (this can actually be
helpful because it requires some thinking about the scope, this gets
communicated to the list etc. and can also produce feedback from
others).
There are some docs and a template in the old charter [1], but here is
an example [2]. There could be better examples, but this one is
easiest for me to find ;-)
-Rahul
[1] http://commons.apache.org/oldcharter.html
[2] http://markmail.org/message/kpfukwihmw273yj4
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: component suggest : commons-monitoring
Posted by nicolas de loof <ni...@apache.org>.
>
> > Could you please grant me access to the sandbox SVN ?
>
> Done.
Thanks
> > Is there some rule to follow for documentation, to best fit with other
> > commons ?
>
> You'll know when you break them ;)
>
> Generally (new) components are using m2 for the build system and JDK
> 1.5 dependent now; or planning a move to those. That helps keep the
> websites generally similar (there's a parent pom to reference in the
> sandbox).
I plan to code for java 5 and provided a (retrotranslator) backported
version for java 1.3/1.4
> If you're not using the Sun standard code style, then state the style
> you're using.
>
> Use the JIRA Sandbox project for your issues. I've added a Monitoring
> component.
>
> Don't release.
> Otherwise, the usual Apache stuff.
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: component suggest : commons-monitoring
Posted by Henri Yandell <fl...@gmail.com>.
On Jan 16, 2008 12:13 AM, nicolas de loof <ni...@apache.org> wrote:
> I'm ok with the graduate rule.
>
> Could you please grant me access to the sandbox SVN ?
Done.
> Is there some rule to follow for documentation, to best fit with other
> commons ?
You'll know when you break them ;)
Generally (new) components are using m2 for the build system and JDK
1.5 dependent now; or planning a move to those. That helps keep the
websites generally similar (there's a parent pom to reference in the
sandbox).
If you're not using the Sun standard code style, then state the style
you're using.
Use the JIRA Sandbox project for your issues. I've added a Monitoring component.
Don't release.
Otherwise, the usual Apache stuff.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: component suggest : commons-monitoring
Posted by nicolas de loof <ni...@apache.org>.
I'm ok with the graduate rule.
Could you please grant me access to the sandbox SVN ?
Is there some rule to follow for documentation, to best fit with other
commons ?
Nico.
2008/1/15, Rahul Akolkar <ra...@gmail.com>:
>
> On 1/15/08, Niall Pemberton <ni...@gmail.com> wrote:
> > On Jan 15, 2008 4:28 PM, nicolas de loof <ni...@apache.org> wrote:
> > > Hello,
> > >
> > > I just asked for an apache lab for a java monitoring component
> > > (
> > >
> http://labs.markmail.org/search/list:org.apache.labs.labs#query:list%3Aorg.apache.labs.labs+page:1+mid:bkztzg2rmceuopvq+state:results
> > > )
> > >
> <big-snip/>
> >
> > So I think its really down to you on the route you want to take -
> > whether here or elsewhere
> >
> <snap/>
>
> Indeed. The Commons Sandbox is available, but does require some
> interest from the community to graduate out of (specifically, a
> promotion vote is needed before anything can be released).
>
> -Rahul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: component suggest : commons-monitoring
Posted by Rahul Akolkar <ra...@gmail.com>.
On 1/15/08, Niall Pemberton <ni...@gmail.com> wrote:
> On Jan 15, 2008 4:28 PM, nicolas de loof <ni...@apache.org> wrote:
> > Hello,
> >
> > I just asked for an apache lab for a java monitoring component
> > (
> > http://labs.markmail.org/search/list:org.apache.labs.labs#query:list%3Aorg.apache.labs.labs+page:1+mid:bkztzg2rmceuopvq+state:results
> > )
> >
<big-snip/>
>
> So I think its really down to you on the route you want to take -
> whether here or elsewhere
>
<snap/>
Indeed. The Commons Sandbox is available, but does require some
interest from the community to graduate out of (specifically, a
promotion vote is needed before anything can be released).
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: component suggest : commons-monitoring
Posted by Niall Pemberton <ni...@gmail.com>.
On Jan 15, 2008 4:28 PM, nicolas de loof <ni...@apache.org> wrote:
> Hello,
>
> I just asked for an apache lab for a java monitoring component
> (
> http://labs.markmail.org/search/list:org.apache.labs.labs#query:list%3Aorg.apache.labs.labs+page:1+mid:bkztzg2rmceuopvq+state:results
> )
>
> One year ago I've created a sourceforge project (www.jmonit.org) with same
> idea in mind, and used it @work, but did not yet create a community around
> this project that could make it eligible to the apache incubator.
Actually theres no community requirement to *enter* the incubator -
just to exit it. Thats one of the main purposes of incubation -
creating a community. The real requirment is gathering mentors and
pursuading the incubator folks (or other sponsoring PMC) that its a
good idea.
> As an alternative to apache labs, the apache.commons sandbox seems to be the
> best place to create such a component, and to get feedback from the wide and
> talentuous apache developers community.
>
> What is the "apache.commons" way for such contribution request ?
We have a policy that any ASF committer can start something in our
Sandbox. Usually though this is people starting out from scratch, not
importing an existing code base from outside the ASF (and Apache Labs
is similar). For importing an existing code base then at a minimum we
would probably need to at least use the Incubator IP Clearance check
list (the Mantissa contribution to Commons Math did this a while back,
so the archives may give you some pointers).
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
So I think its really down to you on the route you want to take -
whether here or elsewhere
Niall
> Nico.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org