Ben told me that officially it is Brett who is responsible to create Mojo
projects.
Brett, are you always monitoring these tasks ?
On Fri, Sep 5, 2014 at 11:18 AM, Arnaud Héritier
wrote:
> I just checked and there are very few admins around Ben Walding to manage
> administrative tasks
> * Bob M
I just checked and there are very few admins around Ben Walding to manage
administrative tasks
* Bob McWhirter
* Brett Porter
* Olivier Gaudin
* Stephen Connolly
* and me
Perhaps this is something to discuss with Ben about Codehaus systems
management ?
Perhaps he may need some help if we consider
Hi,
If you compare the differences between Apaches PMC and teammembers, then
the difference between a Codehaus despot and teammember is much smaller.
Teammembers already have a lot of rights for the infrastructure[1],
there's no such thing as binding votes. Main difference between a despot
H Dan,
On 9/3/14 7:47 PM, Dan Tran wrote:
Arnaud just confirmed with me that I should have 'nagged' him since
sometimes he misses the email:-) Now we know how to proceed
my apology for the confusion
No need for this...we should discuss things like this from time to
timeand it shouldn't
Arnaud just confirmed with me that I should have 'nagged' him since
sometimes he misses the email:-) Now we know how to proceed
my apology for the confusion
-D
On Wed, Sep 3, 2014 at 10:10 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
>
> On 9/3/14 9:39 AM, Anders Hammar wrote:
>
>> One problem is
Hi,
On 9/3/14 9:39 AM, Anders Hammar wrote:
One problem is that the JIRA URL is on the produced mojo site, so
creating the JIRA project after the release requires a new release to
update the site.
/Anders
I have the same opinion as Anders
so i would vote against this kind of relaxing...
There is something to take care. Being despot doesn't give us the jira
administration privilege required to create new projects.
The thing to do is to ask to Ben if we could have more Jira admins to
create these projects.
(And yes +1 to have more despots too)
On Wed, Sep 3, 2014 at 6:20 PM, Dan
+1 for more Depots
I have been with this project since beginning, will be glad helping out
Thanks
-D
On Wed, Sep 3, 2014 at 9:16 AM, Baptiste Mathus
wrote:
> I think that if this discussion is raised only because it's difficult to
> have a despot create the project in jira, then we may just
I think that if this discussion is raised only because it's difficult to
have a despot create the project in jira, then we may just want to have
more despots. Changing the release process not because it's having an issue
in itself seems wrong to me.
Like Arnaud, I also think it's a wee bit better
I would prefer to have a jira project per mojo when they are stable
AFAIK I'm always despot + jira administrator and can create projects if you
need but don't hesitate to ping me directly because I'm not reading all
mojo MLs threads
On Wed, Sep 3, 2014 at 9:39 AM, Anders Hammar wrote:
> One pro
One problem is that the JIRA URL is on the produced mojo site, so creating
the JIRA project after the release requires a new release to update the
site.
/Anders
On Wed, Sep 3, 2014 at 9:31 AM, Dan Tran wrote:
> Correct
>
> -Dan
>
>
> On Tuesday, September 2, 2014, Anders Hammar wrote:
>
>> No
Correct
-Dan
On Tuesday, September 2, 2014, Anders Hammar wrote:
> Not sure what you mean. Do you want to make a 1.0 release without a mojo
> specific JIRA project?
>
> /Anders
>
>
> On Wed, Sep 3, 2014 at 8:29 AM, Dan Tran > wrote:
>
>> Currently in order for a component to become 1.0, it jus
12 matches
Mail list logo
