infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Bowen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18255) Discuss options for GDrive permission granularity
Date Tue, 23 Apr 2019 19:32:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824460#comment-16824460
] 

Richard Bowen commented on INFRA-18255:
---------------------------------------

Still waiting to hear back from our friends at Virtual. Will ping again.


> Discuss options for GDrive permission granularity
> -------------------------------------------------
>
>                 Key: INFRA-18255
>                 URL: https://issues.apache.org/jira/browse/INFRA-18255
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: LDAP
>            Reporter: Richard Bowen
>            Priority: Minor
>
> The ApacheCon GDrive is divided into years, and then subdivided into events. Each event
has (may have) its own producer, who SHOULD NOT have access to the other events, where we
have financials, vendor info, sponsor info, and so on.
> The current situation, where we add everyone to the top-level directory, relies on trust.
Which is mostly fine. We trust these people. But we already have instances of people going
on fishing expeditions into the other directories, and the lack of granular permissions make
them think this is ok. I'd rather not have that confusion.
> On the other hand, having per-event GDrives would be *awful* from the perspective of
those of us who actually need to oversee all events.
> What are our options?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message