Re: commit rights to ComDev non-community.a.o site resources

[Roman Shaposhnik]

On Mon, Mar 16, 2015 at 1:21 AM, Ulrich Stärk  wrote:
> One doesn't exclude the other. I'd first like us to establish whether 
> committership
> to the ComDev code is by invitation only or open to all existing Apache 
> committers
> (which I'd prefer).

+1

Re: commit rights to ComDev non-community.a.o site resources

[Rich Bowen]

+1

On 03/19/2015 01:27 PM, Ross Gardler (MS OPEN TECH) wrote:

+1 to lazy consensus - this is a reversible step

-Original Message-
From: Ulrich Stärk [mailto:u...@spielviel.de]
Sent: Thursday, March 19, 2015 10:08 AM
To: dev@community.apache.org
Subject: Re: commit rights to ComDev non-community.a.o site resources

Actually I just realized how dumb that question is.

So: I assume lazy consensus and will go ahead and modify the permissions if 
nobody objects within the next 72 hours.

Cheers,

Uli

On 2015-03-19 18:07, Ulrich Stärk wrote:

So shall we put this to a vote or may I assume lazy consensus?

If so I'd go ahead and modify the permissions accordingly.

Cheers,

Uli

On 2015-03-16 09:21, Ulrich Stärk wrote:

One doesn't exclude the other. I'd first like us to establish whether 
committership to the ComDev code is by invitation only or open to all existing 
Apache committers (which I'd prefer).

Cheers,

Uli


Am 15.03.2015 um 23:22 schrieb Pierre Smits :

Why not register the solution as a component of the COMDEV project
in JIRA, and do the same as any other ASF project does when it comes to code:
register and evaluate issues, have patches registered there and have
invited committers work from there.

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud-
Based Manufacturing, Professional Services and Retail & Trade
http://www.orrtiz.com


On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:

Heh.

When I put that sentence in the board report we didn't have
projects-new yet.

I don't see a reason why we shouldn't open up those two (or even
all of
/comdev) for all committers
as long as changes are first discussed on our lists.

What do others think?

Cheers,

Uli


On 2015-03-14 16:38, Hervé BOUTEMY wrote:
Hi,

I lately gave patches for projects-new that were not applied: it
seems

there

is a problem to determine who should do it (to avoid projects-new
to be a single-man affair).

Then I made some investigations: in the last board report for
ComDev

[1], I

think I found the cause:
"Since artifacts produced by ComDev are usually documentation on
our

website

which is writable for all Apache committers, we usually do not add

committers

to the ComDev project."

Then should projects(-new).apache.org become writeable for all
Apache committers too? Same for reporter.apache.org?

Regards,

Hervé

[1]
https://whimsy.apache.org/board/minutes/Community_Development.html





--
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

Re: commit rights to ComDev non-community.a.o site resources

[Bertrand Delacretaz]

On Thu, Mar 19, 2015 at 6:08 PM, Ulrich Stärk  wrote:
> ...I assume lazy consensus and will go ahead and modify the permissions if 
> nobody objects within
> the next 72 hours

Sure, thanks for doing that!
-Bertrand

RE: commit rights to ComDev non-community.a.o site resources

[Ross Gardler (MS OPEN TECH)]

+1 to lazy consensus - this is a reversible step

-Original Message-
From: Ulrich Stärk [mailto:u...@spielviel.de] 
Sent: Thursday, March 19, 2015 10:08 AM
To: dev@community.apache.org
Subject: Re: commit rights to ComDev non-community.a.o site resources

Actually I just realized how dumb that question is.

So: I assume lazy consensus and will go ahead and modify the permissions if 
nobody objects within the next 72 hours.

Cheers,

Uli

On 2015-03-19 18:07, Ulrich Stärk wrote:
> So shall we put this to a vote or may I assume lazy consensus?
> 
> If so I'd go ahead and modify the permissions accordingly.
> 
> Cheers,
> 
> Uli
> 
> On 2015-03-16 09:21, Ulrich Stärk wrote:
>> One doesn't exclude the other. I'd first like us to establish whether 
>> committership to the ComDev code is by invitation only or open to all 
>> existing Apache committers (which I'd prefer).
>>
>> Cheers,
>>
>> Uli
>>
>>> Am 15.03.2015 um 23:22 schrieb Pierre Smits :
>>>
>>> Why not register the solution as a component of the COMDEV project 
>>> in JIRA, and do the same as any other ASF project does when it comes to 
>>> code:
>>> register and evaluate issues, have patches registered there and have 
>>> invited committers work from there.
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- 
>>> Based Manufacturing, Professional Services and Retail & Trade 
>>> http://www.orrtiz.com
>>>
>>>> On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:
>>>>
>>>> Heh.
>>>>
>>>> When I put that sentence in the board report we didn't have 
>>>> projects-new yet.
>>>>
>>>> I don't see a reason why we shouldn't open up those two (or even 
>>>> all of
>>>> /comdev) for all committers
>>>> as long as changes are first discussed on our lists.
>>>>
>>>> What do others think?
>>>>
>>>> Cheers,
>>>>
>>>> Uli
>>>>
>>>>> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
>>>>> Hi,
>>>>>
>>>>> I lately gave patches for projects-new that were not applied: it 
>>>>> seems
>>>> there
>>>>> is a problem to determine who should do it (to avoid projects-new 
>>>>> to be a single-man affair).
>>>>>
>>>>> Then I made some investigations: in the last board report for 
>>>>> ComDev
>>>> [1], I
>>>>> think I found the cause:
>>>>> "Since artifacts produced by ComDev are usually documentation on 
>>>>> our
>>>> website
>>>>> which is writable for all Apache committers, we usually do not add
>>>> committers
>>>>> to the ComDev project."
>>>>>
>>>>> Then should projects(-new).apache.org become writeable for all 
>>>>> Apache committers too? Same for reporter.apache.org?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hervé
>>>>>
>>>>> [1] 
>>>>> https://whimsy.apache.org/board/minutes/Community_Development.html
>>>>

Re: commit rights to ComDev non-community.a.o site resources

[Ulrich Stärk]

Actually I just realized how dumb that question is.

So: I assume lazy consensus and will go ahead and modify the permissions if 
nobody objects within
the next 72 hours.

Cheers,

Uli

On 2015-03-19 18:07, Ulrich Stärk wrote:
> So shall we put this to a vote or may I assume lazy consensus?
> 
> If so I'd go ahead and modify the permissions accordingly.
> 
> Cheers,
> 
> Uli
> 
> On 2015-03-16 09:21, Ulrich Stärk wrote:
>> One doesn't exclude the other. I'd first like us to establish whether 
>> committership to the ComDev code is by invitation only or open to all 
>> existing Apache committers (which I'd prefer).
>>
>> Cheers,
>>
>> Uli
>>
>>> Am 15.03.2015 um 23:22 schrieb Pierre Smits :
>>>
>>> Why not register the solution as a component of the COMDEV project in JIRA,
>>> and do the same as any other ASF project does when it comes to code:
>>> register and evaluate issues, have patches registered there and have
>>> invited committers work from there.
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> *ORRTIZ.COM *
>>> Services & Solutions for Cloud-
>>> Based Manufacturing, Professional
>>> Services and Retail & Trade
>>> http://www.orrtiz.com
>>>
 On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:

 Heh.

 When I put that sentence in the board report we didn't have projects-new
 yet.

 I don't see a reason why we shouldn't open up those two (or even all of
 /comdev) for all committers
 as long as changes are first discussed on our lists.

 What do others think?

 Cheers,

 Uli

> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> Hi,
>
> I lately gave patches for projects-new that were not applied: it seems
 there
> is a problem to determine who should do it (to avoid projects-new to be a
> single-man affair).
>
> Then I made some investigations: in the last board report for ComDev
 [1], I
> think I found the cause:
> "Since artifacts produced by ComDev are usually documentation on our
 website
> which is writable for all Apache committers, we usually do not add
 committers
> to the ComDev project."
>
> Then should projects(-new).apache.org become writeable for all Apache
> committers too? Same for reporter.apache.org?
>
> Regards,
>
> Hervé
>
> [1] https://whimsy.apache.org/board/minutes/Community_Development.html

Re: commit rights to ComDev non-community.a.o site resources

[Ulrich Stärk]

So shall we put this to a vote or may I assume lazy consensus?

If so I'd go ahead and modify the permissions accordingly.

Cheers,

Uli

On 2015-03-16 09:21, Ulrich Stärk wrote:
> One doesn't exclude the other. I'd first like us to establish whether 
> committership to the ComDev code is by invitation only or open to all 
> existing Apache committers (which I'd prefer).
> 
> Cheers,
> 
> Uli
> 
>> Am 15.03.2015 um 23:22 schrieb Pierre Smits :
>>
>> Why not register the solution as a component of the COMDEV project in JIRA,
>> and do the same as any other ASF project does when it comes to code:
>> register and evaluate issues, have patches registered there and have
>> invited committers work from there.
>>
>> Best regards,
>>
>> Pierre Smits
>>
>> *ORRTIZ.COM *
>> Services & Solutions for Cloud-
>> Based Manufacturing, Professional
>> Services and Retail & Trade
>> http://www.orrtiz.com
>>
>>> On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:
>>>
>>> Heh.
>>>
>>> When I put that sentence in the board report we didn't have projects-new
>>> yet.
>>>
>>> I don't see a reason why we shouldn't open up those two (or even all of
>>> /comdev) for all committers
>>> as long as changes are first discussed on our lists.
>>>
>>> What do others think?
>>>
>>> Cheers,
>>>
>>> Uli
>>>
 On 2015-03-14 16:38, Hervé BOUTEMY wrote:
 Hi,

 I lately gave patches for projects-new that were not applied: it seems
>>> there
 is a problem to determine who should do it (to avoid projects-new to be a
 single-man affair).

 Then I made some investigations: in the last board report for ComDev
>>> [1], I
 think I found the cause:
 "Since artifacts produced by ComDev are usually documentation on our
>>> website
 which is writable for all Apache committers, we usually do not add
>>> committers
 to the ComDev project."

 Then should projects(-new).apache.org become writeable for all Apache
 committers too? Same for reporter.apache.org?

 Regards,

 Hervé

 [1] https://whimsy.apache.org/board/minutes/Community_Development.html
>>>

Re: commit rights to ComDev non-community.a.o site resources

[Pierre Smits]

+ 1

Best regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Mon, Mar 16, 2015 at 9:39 PM, Hervé BOUTEMY 
wrote:

> +1 (non-binding)
>
> Regards,
>
> Hervé
>
> Le dimanche 15 mars 2015 22:24:34 Ulrich Stärk a écrit :
> > Heh.
> >
> > When I put that sentence in the board report we didn't have projects-new
> > yet.
> >
> > I don't see a reason why we shouldn't open up those two (or even all of
> > /comdev) for all committers as long as changes are first discussed on our
> > lists.
> >
> > What do others think?
> >
> > Cheers,
> >
> > Uli
> >
> > On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> > > Hi,
> > >
> > > I lately gave patches for projects-new that were not applied: it seems
> > > there is a problem to determine who should do it (to avoid projects-new
> > > to be a single-man affair).
> > >
> > > Then I made some investigations: in the last board report for ComDev
> [1],
> > > I
> > > think I found the cause:
> > > "Since artifacts produced by ComDev are usually documentation on our
> > > website which is writable for all Apache committers, we usually do not
> > > add committers to the ComDev project."
> > >
> > > Then should projects(-new).apache.org become writeable for all Apache
> > > committers too? Same for reporter.apache.org?
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://whimsy.apache.org/board/minutes/Community_Development.html
>
>

Re: commit rights to ComDev non-community.a.o site resources

[Hervé BOUTEMY]

+1 (non-binding)

Regards,

Hervé

Le dimanche 15 mars 2015 22:24:34 Ulrich Stärk a écrit :
> Heh.
> 
> When I put that sentence in the board report we didn't have projects-new
> yet.
> 
> I don't see a reason why we shouldn't open up those two (or even all of
> /comdev) for all committers as long as changes are first discussed on our
> lists.
> 
> What do others think?
> 
> Cheers,
> 
> Uli
> 
> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> > Hi,
> > 
> > I lately gave patches for projects-new that were not applied: it seems
> > there is a problem to determine who should do it (to avoid projects-new
> > to be a single-man affair).
> > 
> > Then I made some investigations: in the last board report for ComDev [1],
> > I
> > think I found the cause:
> > "Since artifacts produced by ComDev are usually documentation on our
> > website which is writable for all Apache committers, we usually do not
> > add committers to the ComDev project."
> > 
> > Then should projects(-new).apache.org become writeable for all Apache
> > committers too? Same for reporter.apache.org?
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] https://whimsy.apache.org/board/minutes/Community_Development.html

Re: commit rights to ComDev non-community.a.o site resources

[Rich Bowen]

On 03/16/2015 04:21 AM, Ulrich Stärk wrote:

One doesn't exclude the other. I'd first like us to establish whether 
committership to the ComDev code is by invitation only or open to all existing 
Apache committers (which I'd prefer).


A while ago, the topic of "universal commit bit" was discussed at some 
length. I, and many of the people here, were very much in favor of this 
idea, but leaving the decision to the individual projects.


As ComDev, we should be setting an example for the Foundation, 
encouraging welcoming community behavior.


So, yeah, I'm +1 to a Universal Commit Bit on anything that ComDev works 
on, whether it's code or docs.


What's the worst that can happen? Someone commits something crappy, and 
we revert it. That's why we have revision control.


--Rich




Cheers,

Uli


Am 15.03.2015 um 23:22 schrieb Pierre Smits :

Why not register the solution as a component of the COMDEV project in JIRA,
and do the same as any other ASF project does when it comes to code:
register and evaluate issues, have patches registered there and have
invited committers work from there.

Best regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com


On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:

Heh.

When I put that sentence in the board report we didn't have projects-new
yet.

I don't see a reason why we shouldn't open up those two (or even all of
/comdev) for all committers
as long as changes are first discussed on our lists.

What do others think?

Cheers,

Uli


On 2015-03-14 16:38, Hervé BOUTEMY wrote:
Hi,

I lately gave patches for projects-new that were not applied: it seems

there

is a problem to determine who should do it (to avoid projects-new to be a
single-man affair).

Then I made some investigations: in the last board report for ComDev

[1], I

think I found the cause:
"Since artifacts produced by ComDev are usually documentation on our

website

which is writable for all Apache committers, we usually do not add

committers

to the ComDev project."

Then should projects(-new).apache.org become writeable for all Apache
committers too? Same for reporter.apache.org?

Regards,

Hervé

[1] https://whimsy.apache.org/board/minutes/Community_Development.html





--
Rich Bowen - rbo...@rcbowen.com - @rbowen
http://apachecon.com/ - @apachecon

Re: commit rights to ComDev non-community.a.o site resources

[Bertrand Delacretaz]

On Mon, Mar 16, 2015 at 9:21 AM, Ulrich Stärk  wrote:
> ...I'd first like us to establish whether committership to the ComDev code is 
> by invitation
> only or open to all existing Apache committers (which I'd prefer)

I'm +1 on opening to all Apache committers, making it clear (with a
README) that they are expected to discuss things here.

-Bertrand

Re: commit rights to ComDev non-community.a.o site resources

[Ulrich Stärk]

One doesn't exclude the other. I'd first like us to establish whether 
committership to the ComDev code is by invitation only or open to all existing 
Apache committers (which I'd prefer).

Cheers,

Uli

> Am 15.03.2015 um 23:22 schrieb Pierre Smits :
> 
> Why not register the solution as a component of the COMDEV project in JIRA,
> and do the same as any other ASF project does when it comes to code:
> register and evaluate issues, have patches registered there and have
> invited committers work from there.
> 
> Best regards,
> 
> Pierre Smits
> 
> *ORRTIZ.COM *
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
> 
>> On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:
>> 
>> Heh.
>> 
>> When I put that sentence in the board report we didn't have projects-new
>> yet.
>> 
>> I don't see a reason why we shouldn't open up those two (or even all of
>> /comdev) for all committers
>> as long as changes are first discussed on our lists.
>> 
>> What do others think?
>> 
>> Cheers,
>> 
>> Uli
>> 
>>> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
>>> Hi,
>>> 
>>> I lately gave patches for projects-new that were not applied: it seems
>> there
>>> is a problem to determine who should do it (to avoid projects-new to be a
>>> single-man affair).
>>> 
>>> Then I made some investigations: in the last board report for ComDev
>> [1], I
>>> think I found the cause:
>>> "Since artifacts produced by ComDev are usually documentation on our
>> website
>>> which is writable for all Apache committers, we usually do not add
>> committers
>>> to the ComDev project."
>>> 
>>> Then should projects(-new).apache.org become writeable for all Apache
>>> committers too? Same for reporter.apache.org?
>>> 
>>> Regards,
>>> 
>>> Hervé
>>> 
>>> [1] https://whimsy.apache.org/board/minutes/Community_Development.html
>> 

Re: commit rights to ComDev non-community.a.o site resources

[Pierre Smits]

Why not register the solution as a component of the COMDEV project in JIRA,
and do the same as any other ASF project does when it comes to code:
register and evaluate issues, have patches registered there and have
invited committers work from there.

Best regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Sun, Mar 15, 2015 at 10:24 PM, Ulrich Stärk  wrote:

> Heh.
>
> When I put that sentence in the board report we didn't have projects-new
> yet.
>
> I don't see a reason why we shouldn't open up those two (or even all of
> /comdev) for all committers
> as long as changes are first discussed on our lists.
>
> What do others think?
>
> Cheers,
>
> Uli
>
> On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> > Hi,
> >
> > I lately gave patches for projects-new that were not applied: it seems
> there
> > is a problem to determine who should do it (to avoid projects-new to be a
> > single-man affair).
> >
> > Then I made some investigations: in the last board report for ComDev
> [1], I
> > think I found the cause:
> > "Since artifacts produced by ComDev are usually documentation on our
> website
> > which is writable for all Apache committers, we usually do not add
> committers
> > to the ComDev project."
> >
> > Then should projects(-new).apache.org become writeable for all Apache
> > committers too? Same for reporter.apache.org?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://whimsy.apache.org/board/minutes/Community_Development.html
> >
>

Re: commit rights to ComDev non-community.a.o site resources

[Ulrich Stärk]

Heh.

When I put that sentence in the board report we didn't have projects-new yet.

I don't see a reason why we shouldn't open up those two (or even all of 
/comdev) for all committers
as long as changes are first discussed on our lists.

What do others think?

Cheers,

Uli

On 2015-03-14 16:38, Hervé BOUTEMY wrote:
> Hi,
> 
> I lately gave patches for projects-new that were not applied: it seems there 
> is a problem to determine who should do it (to avoid projects-new to be a 
> single-man affair).
> 
> Then I made some investigations: in the last board report for ComDev [1], I 
> think I found the cause:
> "Since artifacts produced by ComDev are usually documentation on our website 
> which is writable for all Apache committers, we usually do not add committers 
> to the ComDev project."
> 
> Then should projects(-new).apache.org become writeable for all Apache 
> committers too? Same for reporter.apache.org?
> 
> Regards,
> 
> Hervé
> 
> [1] https://whimsy.apache.org/board/minutes/Community_Development.html
> 

Re: commit rights to ComDev non-community.a.o site resources

[Antoine Levy Lambert]

Hello Benjamin,

thanks for contacting us. Contributions are welcome to the Apache Ant project.

One way of contributing is to look at the bug database, in the case of Ant it 
is in Bugzilla and picking one or several entries and try to either 
evaluate/update existing patches or to create a solution including code, test 
cases and documentation changes.

You can also come up with your own suggestions of improvement/extension/…

I am unfortunately these days not very active in Apache Ant, but the best 
contact points for Apache Ant are the distribution lists u...@ant.apache.org 
and d...@ant.apache.org.

If you are interested I also recommend that you try to help with Apache Ivy 
which is also part of the Apache Ant project.

Best regards,

Antoine

On Mar 14, 2015, at 2:11 PM, Benjamin Spero  wrote:

> Hi Antoine,
> 
> I’m new to java development.  I need more experience in writing java code.  I 
> read your background and I would like to help in the Apache Ant project.  I 
> would appreciate your advice.
> 
> Thank you,
> Ben
> 
> 
> On Mar 14, 2015, at 12:18 PM, Antoine Levy Lambert  wrote:
> 
>> Hi,
>> 
>> On Mar 14, 2015, at 11:38 AM, Hervé BOUTEMY  wrote:
>> 
>>> Hi,
>>> 
>>> I lately gave patches for projects-new that were not applied: it seems 
>>> there 
>>> is a problem to determine who should do it (to avoid projects-new to be a 
>>> single-man affair).
>>> 
>>> Then I made some investigations: in the last board report for ComDev [1], I 
>>> think I found the cause:
>>> "Since artifacts produced by ComDev are usually documentation on our 
>>> website 
>>> which is writable for all Apache committers, we usually do not add 
>>> committers 
>>> to the ComDev project."
>>> 
>>> Then should projects(-new).apache.org become writeable for all Apache 
>>> committers too? Same for reporter.apache.org?
>> +1
>> 
>> That makes sense to allow all the Apache committers to contribute.
>> 
>> Antoine
>>> 
>>> Regards,
>>> 
>>> Hervé
>>> 
>>> [1] https://whimsy.apache.org/board/minutes/Community_Development.html
>> 
> 

Re: commit rights to ComDev non-community.a.o site resources

[Benjamin Spero]

Hi Antoine,

I’m new to java development.  I need more experience in writing java code.  I 
read your background and I would like to help in the Apache Ant project.  I 
would appreciate your advice.

Thank you,
Ben


On Mar 14, 2015, at 12:18 PM, Antoine Levy Lambert  wrote:

> Hi,
> 
> On Mar 14, 2015, at 11:38 AM, Hervé BOUTEMY  wrote:
> 
>> Hi,
>> 
>> I lately gave patches for projects-new that were not applied: it seems there 
>> is a problem to determine who should do it (to avoid projects-new to be a 
>> single-man affair).
>> 
>> Then I made some investigations: in the last board report for ComDev [1], I 
>> think I found the cause:
>> "Since artifacts produced by ComDev are usually documentation on our website 
>> which is writable for all Apache committers, we usually do not add 
>> committers 
>> to the ComDev project."
>> 
>> Then should projects(-new).apache.org become writeable for all Apache 
>> committers too? Same for reporter.apache.org?
> +1
> 
> That makes sense to allow all the Apache committers to contribute.
> 
> Antoine
>> 
>> Regards,
>> 
>> Hervé
>> 
>> [1] https://whimsy.apache.org/board/minutes/Community_Development.html
> 

Re: commit rights to ComDev non-community.a.o site resources

[Antoine Levy Lambert]

Hi,

On Mar 14, 2015, at 11:38 AM, Hervé BOUTEMY  wrote:

> Hi,
> 
> I lately gave patches for projects-new that were not applied: it seems there 
> is a problem to determine who should do it (to avoid projects-new to be a 
> single-man affair).
> 
> Then I made some investigations: in the last board report for ComDev [1], I 
> think I found the cause:
> "Since artifacts produced by ComDev are usually documentation on our website 
> which is writable for all Apache committers, we usually do not add committers 
> to the ComDev project."
> 
> Then should projects(-new).apache.org become writeable for all Apache 
> committers too? Same for reporter.apache.org?
+1

That makes sense to allow all the Apache committers to contribute.

Antoine
> 
> Regards,
> 
> Hervé
> 
> [1] https://whimsy.apache.org/board/minutes/Community_Development.html

commit rights to ComDev non-community.a.o site resources

[Hervé BOUTEMY]

Hi,

I lately gave patches for projects-new that were not applied: it seems there 
is a problem to determine who should do it (to avoid projects-new to be a 
single-man affair).

Then I made some investigations: in the last board report for ComDev [1], I 
think I found the cause:
"Since artifacts produced by ComDev are usually documentation on our website 
which is writable for all Apache committers, we usually do not add committers 
to the ComDev project."

Then should projects(-new).apache.org become writeable for all Apache 
committers too? Same for reporter.apache.org?

Regards,

Hervé

[1] https://whimsy.apache.org/board/minutes/Community_Development.html