Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-03-30 Thread Kent Sølvsten
Great! Thanks! Regards, Kent Den 28/03/2008 kl. 15.53 skrev Trygve Laugstøl: Done. Raphaël Piéroni skrev: Any despot to give karma to the voted new comitter ? Regards, Raphaël 2008/3/27, Kent Sølvsten <[EMAIL PROTECTED]>: Hi hausmates. What does it take to add a plugin to the sandbox? I

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-03-28 Thread Trygve Laugstøl
Done. Raphaël Piéroni skrev: Any despot to give karma to the voted new comitter ? Regards, Raphaël 2008/3/27, Kent Sølvsten <[EMAIL PROTECTED]>: Hi hausmates. What does it take to add a plugin to the sandbox? I honestly believe the chronos plugin is a great concept of "continuous performan

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-03-28 Thread Raphaël Piéroni
Any despot to give karma to the voted new comitter ? Regards, Raphaël 2008/3/27, Kent Sølvsten <[EMAIL PROTECTED]>: > > Hi hausmates. > > What does it take to add a plugin to the sandbox? > > I honestly believe the chronos plugin is a great concept of "continuous > performancetesting", based on

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-03-27 Thread Kent Sølvsten
Hi hausmates. What does it take to add a plugin to the sandbox? I honestly believe the chronos plugin is a great concept of "continuous performancetesting", based on integrating performancetesting in maven builds. At my company we have used it in two projects so far, and hope others would

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-29 Thread Tomasz Pik
On Fri, Feb 29, 2008 at 10:55 AM, Raphaël Piéroni <[EMAIL PROTECTED]> wrote: > +1 to accept Kent Sølvsten +1 (non-binding) Tomek > > Raphaël > > > > 2008/2/29, Tomasz Pik <[EMAIL PROTECTED]>: > > > > On Fri, Feb 29, 2008 at 9:45 AM, Kent Sølvsten <[EMAIL PROTECTED]> wrote: > > > > > > It w

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-29 Thread Raphaël Piéroni
+1 to accept Kent Sølvsten Raphaël 2008/2/29, Tomasz Pik <[EMAIL PROTECTED]>: > On Fri, Feb 29, 2008 at 9:45 AM, Kent Sølvsten <[EMAIL PROTECTED]> wrote: > > > > It would be very great to get access to the sandbox. > > Is it access to the whole sandbox, thus allowing me to commit the code >

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-29 Thread Tomasz Pik
On Fri, Feb 29, 2008 at 9:45 AM, Kent Sølvsten <[EMAIL PROTECTED]> wrote: > > It would be very great to get access to the sandbox. > Is it access to the whole sandbox, thus allowing me to commit the code > myself, and possibly help out with some of the other plugins? > > Currently i am the only act

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-29 Thread Kent Sølvsten
It would be very great to get access to the sandbox. Is it access to the whole sandbox, thus allowing me to commit the code myself, and possibly help out with some of the other plugins? Currently i am the only active developer on the chronos performancetest code. The code was originally star

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-29 Thread Raphaël Piéroni
Hi, i am +0.999 to give access to new volunteers, but please give us names ;-). Regards, Raphaël 2008/2/25, Tomasz Pik <[EMAIL PROTECTED]>: > Hello, > > There's a Plugin Submission issue for Chronos plugin > (http://jira.codehaus.org/browse/MOJO-1030). > It looks very interesting and complex

Re: [mojo-dev] access for mojo-sandbox for chronos developers

2008-02-27 Thread Kent Sølvsten
A great idea :-) But of course, as one of the developers, I am not very objective on this matter :-) The code was originally developed by one of my colleagues while performancetesting a public service oriented infrastructure project. I am currently introducing it into a second project (regi

[mojo-dev] access for mojo-sandbox for chronos developers

2008-02-25 Thread Tomasz Pik
Hello, There's a Plugin Submission issue for Chronos plugin (http://jira.codehaus.org/browse/MOJO-1030). It looks very interesting and complex (it's not small plugin with 2 mojos and one config file). What about giving plugin developers access to mojo-sandbox so they may work there instead of addi