infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18394) Split apachecon.com svn repo from comdev acl
Date Fri, 17 May 2019 15:37:00 GMT

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

Chris Lambertus commented on INFRA-18394:
-----------------------------------------

A large portion of 'why' is because these sites are so strongly tied to the CMS. If they were
not, we would have more options. Not saying we don't have options now, but I would strongly
suggest we use this as a catalyst to further enable a move off of the CMS to something more
maintainable by modern web/webdev standards.

> 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: Daniel Gruno
>            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