Alright, Thanks Mark and John. What I'm going to do now is give edit and add permissions for all committers to the comdev space. I recognize that I haven't given much time for discussion/objections. But this is a reversible step that enables contributions we need. I'm happy to change things back if objections come up, or if we discover something that causes us to rethink.
I am not giving full permissions to the comdev space to the committers. So for example, committers won't be able to delete pages or edit permissions to the space. Best Regards, Myrle On Wed, Sep 4, 2019 at 6:16 PM Mark Thomas <ma...@apache.org> wrote: > 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 <my...@apache.org> 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 > >
