[
https://issues.apache.org/jira/browse/COMDEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842235#comment-16842235
]
Richard Bowen commented on COMDEV-320:
--------------------------------------
It has been suggested by [~humbedooh] that the way to accomplish this is to
move to Git, and allow these "outsider" contributors to commit via GitHub. If
that works, let's do it. I'm not interested in changing policy or creating
difficulty - just in getting stuff done.
> 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: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
