Re: Open up incubator wiki to all committers

2019-10-10 Thread Justin Mclean
Hi,

> I don’t think this step is documented for new, graduated and retired podlings.

No it's not document anywhere, but it's on my list of things to do, we only 
moved to the new wiki / LDAP authentication recently.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Dave Fisher
Hi Justin,

I don’t think this step is documented for new, graduated and retired podlings.

For example you still have zipkin in the list.

Regards,
Dave

> On Oct 10, 2019, at 4:18 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Yes, I saw that which is why I edited directly in the board whimsy.  Sorry
>> for being late.  ApacheCon and the board have been keeping me quite busy.
>> : o)  But I diid want to sync the incubator version up with my edits.
> 
> Not sure it needs to sync up. The reason I make the report page read only the 
> report is submitted is so that people don’t edit it and those edits miss 
> making it into the real board report. This has happened in the past.
> 
>> You don't actually explain why you're opposed to allowing committers
>> access.  You do say how things are currently, but vetoes should be
>> accompanied by an explanation of what you see wrong with the proposal.
>> What are you worried might happen?
> 
> Reports are created by PPMC members not committers. It encourages podlings to 
> keep their PPMC information up to date. It's only this section of the wiki 
> that is restricted to PPMCs, the rest of the wiki (in general) has the 
> default permission restrictions.
> 
> Thanks,
> Justin
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Justin Mclean
Hi,

> Yes, I saw that which is why I edited directly in the board whimsy.  Sorry
> for being late.  ApacheCon and the board have been keeping me quite busy.
> : o)  But I diid want to sync the incubator version up with my edits.

Not sure it needs to sync up. The reason I make the report page read only the 
report is submitted is so that people don’t edit it and those edits miss making 
it into the real board report. This has happened in the past.

> You don't actually explain why you're opposed to allowing committers
> access.  You do say how things are currently, but vetoes should be
> accompanied by an explanation of what you see wrong with the proposal.
> What are you worried might happen?

Reports are created by PPMC members not committers. It encourages podlings to 
keep their PPMC information up to date. It's only this section of the wiki that 
is restricted to PPMCs, the rest of the wiki (in general) has the default 
permission restrictions.

Thanks,
Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Myrle Krantz
Hi Justin,

On Thu, Oct 10, 2019 at 2:36 PM Justin Mclean 
wrote:

> HI,
>
> > I just checked the Weex report for October, and while doing so, I
> realized
> > that I do not have edit rights to the incubator wiki.
>
> I think might what have happen here is that the page has been made read
> only as the report has been submitted to the board. Note the "FINAL FINAL
> FINAL - SUBMITTED TO BOARD - DO NOT EDIT” message at the top of the page :-)
>

Yes, I saw that which is why I edited directly in the board whimsy.  Sorry
for being late.  ApacheCon and the board have been keeping me quite busy.
: o)  But I diid want to sync the incubator version up with my edits.

You don't actually explain why you're opposed to allowing committers
access.  You do say how things are currently, but vetoes should be
accompanied by an explanation of what you see wrong with the proposal.
What are you worried might happen?

Note that confluence is version controlled.  As long as we don't allow
committers to delete, then any mistake anyone might make is reversible.  As
as I've said, we've had absolutely no problems with this over at ComDev.
It has been quite nice to just, for example, ask those who want to
participate in the hackathon to enter themselves, and not have to worry
about becoming a bottleneck for them.

Best Regards,
Myrle


Re: Open up incubator wiki to all committers

2019-10-10 Thread Justin Mclean
HI,

> I just checked the Weex report for October, and while doing so, I realized
> that I do not have edit rights to the incubator wiki.  

I think might what have happen here is that the page has been made read only as 
the report has been submitted to the board. Note the "FINAL FINAL FINAL - 
SUBMITTED TO BOARD - DO NOT EDIT” message at the top of the page :-)

Thanks,
Justin



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Justin Mclean
Hi,

Myrle given you are on the incubator PMC I’m not sure why you couldn’t edit 
that page.

Here is the list of groups who can currently edit that page, note that both 
incubator-pmc and weex-pmc have permission to edit that page.

amaterasu-pmc
annotator-pmc   
batchee-pmc 
brpc-pmc
crail-pmc   
Can edit
daffodil-pmc
Can edit
datasketches-pmc
dlab-pmc
dolphinscheduler-pmc
doris-pmc
druid-pmc
dubbo-pmc
echarts-pmc
edgent-pmc
flagon-pmc
gobblin-pmc 
heron-pmc
hivemall-pmc
hudi-pmc
iceberg-pmc
incubator-pmc   
iotdb-pmc
livy-pmc
marvin-pmc
milagro-pmc
mxnet-pmc
myriad-pmc
nemo-pmc
omid-pmc
openwhisk-pmc   
pagespeed-pmc
pinot-pmc   
ponymail-pmc
ratis-pmc   
rya-pmc 
s2graph-pmc 
samoa-pmc   
sdap-pmc
shardingsphere-pmc  
singa-pmc   
spot-pmc
superset-pmc
tamaya-pmc  
taverna-pmc 
tephra-pmc  
toree-pmc   
training-pmc
tuweni-pmc  
tvm-pmc 
warble-pmc
weex-pmc
zipkin-pmc  

Thanks,
Justin


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Justin Mclean
Hi,

Sorry but -1 form me.

The report section is open to podling PPMC members, each PPMC is added manually 
and for one reason or another there may be a couple of podlings who have not 
been added. They can just ask to be added. I don’t think we should open it up 
to all committers.

On occasions where people have asked to add to the report areas I’ve added them 
as needed, in some cases they have not been committers.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Greg Stein
Generally/all: please stick to committers ... NOT confluence-users. The
latter will bring down the spam.

Thx,
Greg
InfraAdmin, ASF


On Thu, Oct 10, 2019 at 4:40 AM Myrle Krantz  wrote:

> Hey all,
>
> I just checked the Weex report for October, and while doing so, I realized
> that I do not have edit rights to the incubator wiki.  Rather than request
> them now, I'd like to make a different suggestion:
>
> We should add the group "committers" with RW access (but not delete) to the
> entire INCUBATOR space.
>
> We have, historically, spent rather a lot of time granting people access to
> our wiki.
>
> But our recently implemented confluence-LDAP integration makes that
> unnecessary. I made the COMDEV confluence space writable for all
> committers.  So far this has had several advantages and no disadvantages.
> It's made it possible for committers of any project to enter themselves for
> the ApacheCon EU hackathon without having to ask for permissions, and I
> haven't seen any spamming of our spaces from this.
>
> Do you all see any reason we can't do the same for the incubator confluence
> space?
>
> Best Regards,
> Myrle
>


Re: Open up incubator wiki to all committers

2019-10-10 Thread Nick Burch

On Thu, 10 Oct 2019, Myrle Krantz wrote:

We should add the group "committers" with RW access (but not delete) to the
entire INCUBATOR space.

We have, historically, spent rather a lot of time granting people access to
our wiki.


Makes sense to me. We'd still need to grant permissions to people wanted 
to make/edit new proposals, but most of the requests from mentors / 
potential mentors would no longer be needed


Nick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Open up incubator wiki to all committers

2019-10-10 Thread Kevin Ratnasekera
+1

On Thu, Oct 10, 2019 at 4:44 PM York Shen  wrote:

> +1
>
> Great idea. It could save everyone’s time in this mailing list, IMO.
>
> BTW, I just add RW access to all committers in Weex Wiki space.
>
> Best Regards,
> York Shen
>
> 申远
>
> > 2019年10月10日 17:40,Myrle Krantz  写道:
> >
> > Hey all,
> >
> > I just checked the Weex report for October, and while doing so, I
> realized
> > that I do not have edit rights to the incubator wiki.  Rather than
> request
> > them now, I'd like to make a different suggestion:
> >
> > We should add the group "committers" with RW access (but not delete) to
> the
> > entire INCUBATOR space.
> >
> > We have, historically, spent rather a lot of time granting people access
> to
> > our wiki.
> >
> > But our recently implemented confluence-LDAP integration makes that
> > unnecessary. I made the COMDEV confluence space writable for all
> > committers.  So far this has had several advantages and no disadvantages.
> > It's made it possible for committers of any project to enter themselves
> for
> > the ApacheCon EU hackathon without having to ask for permissions, and I
> > haven't seen any spamming of our spaces from this.
> >
> > Do you all see any reason we can't do the same for the incubator
> confluence
> > space?
> >
> > Best Regards,
> > Myrle
>
>


Re: Open up incubator wiki to all committers

2019-10-10 Thread York Shen
+1

Great idea. It could save everyone’s time in this mailing list, IMO.

BTW, I just add RW access to all committers in Weex Wiki space.

Best Regards,
York Shen

申远

> 2019年10月10日 17:40,Myrle Krantz  写道:
> 
> Hey all,
> 
> I just checked the Weex report for October, and while doing so, I realized
> that I do not have edit rights to the incubator wiki.  Rather than request
> them now, I'd like to make a different suggestion:
> 
> We should add the group "committers" with RW access (but not delete) to the
> entire INCUBATOR space.
> 
> We have, historically, spent rather a lot of time granting people access to
> our wiki.
> 
> But our recently implemented confluence-LDAP integration makes that
> unnecessary. I made the COMDEV confluence space writable for all
> committers.  So far this has had several advantages and no disadvantages.
> It's made it possible for committers of any project to enter themselves for
> the ApacheCon EU hackathon without having to ask for permissions, and I
> haven't seen any spamming of our spaces from this.
> 
> Do you all see any reason we can't do the same for the incubator confluence
> space?
> 
> Best Regards,
> Myrle



Open up incubator wiki to all committers

2019-10-10 Thread Myrle Krantz
Hey all,

I just checked the Weex report for October, and while doing so, I realized
that I do not have edit rights to the incubator wiki.  Rather than request
them now, I'd like to make a different suggestion:

We should add the group "committers" with RW access (but not delete) to the
entire INCUBATOR space.

We have, historically, spent rather a lot of time granting people access to
our wiki.

But our recently implemented confluence-LDAP integration makes that
unnecessary. I made the COMDEV confluence space writable for all
committers.  So far this has had several advantages and no disadvantages.
It's made it possible for committers of any project to enter themselves for
the ApacheCon EU hackathon without having to ask for permissions, and I
haven't seen any spamming of our spaces from this.

Do you all see any reason we can't do the same for the incubator confluence
space?

Best Regards,
Myrle