[
https://issues.apache.org/jira/browse/COMDEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842213#comment-16842213
]
Richard Bowen commented on COMDEV-320:
--------------------------------------
Yeah, sorry for the missing detail.
I'm not sure what repo you're looking at, but, to be more precise, I'm talking
about
[https://svn.apache.org/repos/infra/apachecon/www.apachecon.com]
There's also
[https://svn.apache.org/repos/infra/apachecon/archive.apachecon.com]
which, I suppose, it would be useful to do as well, since we (inconsistently)
archive past events there.
> Split apachecon.com svn repo from comdev acl
> --------------------------------------------
>
> Key: COMDEV-320
> URL: https://issues.apache.org/jira/browse/COMDEV-320
> Project: Community Development
> Issue Type: Task
> Components: Website
> Reporter: Richard Bowen
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
