[
https://issues.apache.org/jira/browse/COMDEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842214#comment-16842214
]
Shane Curcuru commented on COMDEV-320:
--------------------------------------
To (I hope) better define the problem: The ApacheCon website has many
time-specific demands for updating, and with our current model, various
producers of events (here I believe event staff at Virtual - people not
otherwise involved in our communities) will be making those updates. They need
to modify content here:
[https://svn.apache.org/repos/infra/apachecon/www.apachecon.com]
And they will need the source there to be auto-published to the live
apachecon.com site as it already is.
----
Historically, we have had very firm policies that committer accounts enabling
write access to our repos are only given out to individuals who sign an ICLA.
# The simplest solution from the ASF point of view is to ask those event staff
to sign an ICLA, which hopefully is non-controversial (but I understand may not
be from their point of view).
# The other solution is for Infra to figure out how to differentiate "special
accounts that can commit to ApacheCon SVN only" from "committer accounts". I
don't know if this is practical for infra. But ensuring that people without an
ICLA can't commit to any project repo (among other places) is critical to our
legal policies.
> 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]
