Re: [DISCUSS] "add" permissions for comdev confluence space to all ASF committers?
On 04/09/2019 17:12, John Andrunas wrote: > * Does the committers group really just contain all committers? > the committers group in confluence is from LDAP so it should only > contain ASF members No. It contains all committers which is a larger set than all members. > * Do we have enough experience to be able to say we can trust all of > the people in this group to not spam confluence? Yes. > * Are there any potential side effects of allowing all committers to > add and edit comdev pages that I haven't thought of and that we should > be aware of? > Confluence keeps versions of all edits, and deleted pages can be > recovered (though you didn't mention delete permissions), so if > someone vandalized a page an earlier version could be recovered. A committer isn;t going to do that. > Other than someone causing additional work to recover/remove spam I > wouldn't expect anything unexpected (except maybe the Spanish > Inquisition, no one ever expects that). There may be specific pages > you want to add additional restrictions on though. I doubt it. Unless it is something that needs to be PMC private which is unlikely. Mark > > > On Wed, Sep 4, 2019 at 8:22 AM Myrle Krantz wrote: >> >> Hey all, >> >> I'd like us to use the comdev confluence in order to help organize the >> hackathon for ApacheCon Europe 2019. I'd like people participating in the >> hackathon to be able to enter their own projects. >> >> However a problem with this approach occurred to me: if I have to enter each >> interested user in the permissions table in confluence, it's not really >> self-organizing any more. >> >> I had a look at the confluence permissions table though, and one potential >> solution occurred to me: Perhaps I can enter the committers group and give >> them permissions to add pages and comments. I already experimentally added >> the committers group to the permissions table (and discovered I couldn't >> figure out how to delete them again). >> >> So here come my questions: >> * Does the committers group really just contain all committers? >> * Do we have enough experience to be able to say we can trust all of the >> people in this group to not spam confluence? >> * Are there any potential side effects of allowing all committers to add and >> edit comdev pages that I haven't thought of and that we should be aware of? >> >> If those questions have the answers I hope they have, then I'll come back >> here, and ask the comdev PMC if there are any objections to allowing >> committers edit access to the comdev wiki. Depending on the answers, we may >> also wish to consider giving all committers access to only certain parts of >> the comdev space. Let's see how the discussion goes. >> >> Best Regards, >> Myrle > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] "add" permissions for comdev confluence space to all ASF committers?
* Does the committers group really just contain all committers? the committers group in confluence is from LDAP so it should only contain ASF members * Do we have enough experience to be able to say we can trust all of the people in this group to not spam confluence? I'm new so I can't really answer this question based on evidence but I suspect that we can trust our users * Are there any potential side effects of allowing all committers to add and edit comdev pages that I haven't thought of and that we should be aware of? Confluence keeps versions of all edits, and deleted pages can be recovered (though you didn't mention delete permissions), so if someone vandalized a page an earlier version could be recovered. Other than someone causing additional work to recover/remove spam I wouldn't expect anything unexpected (except maybe the Spanish Inquisition, no one ever expects that). There may be specific pages you want to add additional restrictions on though. On Wed, Sep 4, 2019 at 8:22 AM Myrle Krantz wrote: > > Hey all, > > I'd like us to use the comdev confluence in order to help organize the > hackathon for ApacheCon Europe 2019. I'd like people participating in the > hackathon to be able to enter their own projects. > > However a problem with this approach occurred to me: if I have to enter each > interested user in the permissions table in confluence, it's not really > self-organizing any more. > > I had a look at the confluence permissions table though, and one potential > solution occurred to me: Perhaps I can enter the committers group and give > them permissions to add pages and comments. I already experimentally added > the committers group to the permissions table (and discovered I couldn't > figure out how to delete them again). > > So here come my questions: > * Does the committers group really just contain all committers? > * Do we have enough experience to be able to say we can trust all of the > people in this group to not spam confluence? > * Are there any potential side effects of allowing all committers to add and > edit comdev pages that I haven't thought of and that we should be aware of? > > If those questions have the answers I hope they have, then I'll come back > here, and ask the comdev PMC if there are any objections to allowing > committers edit access to the comdev wiki. Depending on the answers, we may > also wish to consider giving all committers access to only certain parts of > the comdev space. Let's see how the discussion goes. > > Best Regards, > Myrle - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[DISCUSS] "add" permissions for comdev confluence space to all ASF committers?
Hey all, I'd like us to use the comdev confluence in order to help organize the hackathon for ApacheCon Europe 2019. I'd like people participating in the hackathon to be able to enter their own projects. However a problem with this approach occurred to me: if I have to enter each interested user in the permissions table in confluence, it's not really self-organizing any more. I had a look at the confluence permissions table though, and one potential solution occurred to me: Perhaps I can enter the committers group and give them permissions to add pages and comments. I already experimentally added the committers group to the permissions table (and discovered I couldn't figure out how to delete them again). So here come my questions: * Does the committers group really just contain all committers? * Do we have enough experience to be able to say we can trust all of the people in this group to not spam confluence? * Are there any potential side effects of allowing all committers to add and edit comdev pages that I haven't thought of and that we should be aware of? If those questions have the answers I hope they have, then I'll come back here, and ask the comdev PMC if there are any objections to allowing committers edit access to the comdev wiki. Depending on the answers, we may also wish to consider giving all committers access to only certain parts of the comdev space. Let's see how the discussion goes. Best Regards, Myrle
Re: Please add Apache Cassandra logo to RedBubble
Pada Rab, 4 Sep 2019 5:19 PTG Mark Thomas menulis: > As requested off-list, updated logo to use version with "Apache Cassandra" > > Mark > > > On 03/09/2019 21:35, Nate McCall wrote: > > Thanks, Mark! > > > > On Wed, Sep 4, 2019 at 8:23 AM Mark Thomas wrote: > > > >> On 03/09/2019 21:10, Nate McCall wrote: > >>> Hi folks, > >>> Per subject, hi-rez version can be found here: > >>> http://svn.apache.org/repos/asf/cassandra/logo/apache-cassandra.pdf > >> > >> Happy shopping: > >> > >> > >> > https://www.redbubble.com/people/comdev/works/40954574-apache-cassandra?asc=u > >> > >> Mark > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Please add Apache Cassandra logo to RedBubble
As requested off-list, updated logo to use version with "Apache Cassandra" Mark On 03/09/2019 21:35, Nate McCall wrote: > Thanks, Mark! > > On Wed, Sep 4, 2019 at 8:23 AM Mark Thomas wrote: > >> On 03/09/2019 21:10, Nate McCall wrote: >>> Hi folks, >>> Per subject, hi-rez version can be found here: >>> http://svn.apache.org/repos/asf/cassandra/logo/apache-cassandra.pdf >> >> Happy shopping: >> >> >> https://www.redbubble.com/people/comdev/works/40954574-apache-cassandra?asc=u >> >> Mark >> > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Booth Volunteers Needed for ApacheCon EU Berlin
Hi Sharan, I'll let you know if I will be there. I hope to have good news soon :) Cheers, PJ Il giorno mer 28 ago 2019 alle ore 21:15 Sharan Foga ha scritto: > Hi All > > ApacheCon EU will be running from 22nd - 24th October 2019 in Berlin and > we will be continuing the Apache 20th anniversary celebrations. > > We are looking for volunteers to help out with the setup and staffing of > the Apache booth during ApacheCon. The booth is a great place to be and is > always full of people and activity. It is a general hub and central meeting > point for attendees. > > As a booth volunteer, your main tasks will be talking to attendees and > handing out stickers, leaflets and other giveaways. If you’d like to spend > some time on the booth talking to attendees to about your project to help > grow your own project community then please let us know. Remember that even > 30 minutes or an hour of your time will be very welcome. > > The greater variety of people and projects we have on the booth, the > greater the chance of perhaps recruiting new contributors as we always have > people wanting to talk about specific projects. > > If you are only available to help with setup and tear down then that is > fine too. > > I’ve started drafting a wiki page to help with the booth planning. > > https://s.apache.org/6m3a0 > > If you are interested in helping out then please either respond to this > thread or add your details to the wiki page. > > Thanks > Sharan > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- Piergiorgio
[jira] [Resolved] (COMDEV-329) AtOmXpLuS
[ https://issues.apache.org/jira/browse/COMDEV-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KORAY DURGUT resolved COMDEV-329. -- Resolution: Fixed Everything in AtOmXpLuS.CoM > AtOmXpLuS > - > > Key: COMDEV-329 > URL: https://issues.apache.org/jira/browse/COMDEV-329 > Project: Community Development > Issue Type: Bug >Reporter: KORAY DURGUT >Priority: Major > Labels: Everything > > Everything in AtOmXpLuS.CoM -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-329) AtOmXpLuS
[ https://issues.apache.org/jira/browse/COMDEV-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KORAY DURGUT updated COMDEV-329: - Description: Everything in AtOmXpLuS.CoM > AtOmXpLuS > - > > Key: COMDEV-329 > URL: https://issues.apache.org/jira/browse/COMDEV-329 > Project: Community Development > Issue Type: Bug >Reporter: KORAY DURGUT >Priority: Major > Labels: Everything > > Everything in AtOmXpLuS.CoM -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-329) AtOmXpLuS
[ https://issues.apache.org/jira/browse/COMDEV-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] KORAY DURGUT updated COMDEV-329: - Labels: Everything (was: ) > AtOmXpLuS > - > > Key: COMDEV-329 > URL: https://issues.apache.org/jira/browse/COMDEV-329 > Project: Community Development > Issue Type: Bug >Reporter: KORAY DURGUT >Priority: Major > Labels: Everything > -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-329) AtOmXpLuS
KORAY DURGUT created COMDEV-329: Summary: AtOmXpLuS Key: COMDEV-329 URL: https://issues.apache.org/jira/browse/COMDEV-329 Project: Community Development Issue Type: Bug Reporter: KORAY DURGUT -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
