infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18394) Split apachecon.com svn repo from comdev acl
Date Sat, 18 May 2019 04:06:00 GMT

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

Greg Stein commented on INFRA-18394:
------------------------------------

ACLs have been simplified.

We're in "Waiting For User", awaiting the ICLA now. Lemme know ...


> Split apachecon.com svn repo from comdev acl
> --------------------------------------------
>
>                 Key: INFRA-18394
>                 URL: https://issues.apache.org/jira/browse/INFRA-18394
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Website
>            Reporter: Richard Bowen
>            Assignee: Greg Stein
>            Priority: Major
>
> Having the apachecon website svn rep tied to the comdev acl is causing difficulties.
Specifically, we have to make someone a comdev committer for them to edit a web page, and
that's broken.
> I would like to split apachecon.com svn repo from the comdev repo, and create a new acl
where we can have "committers" for that repo who are not asf committers (think event producers)
and who probably haven't signed CLAs (because why would they?). Is this a thing we can do?
Are there policy considerations, or can we JFDI?



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

Mime
View raw message