infra-issues mailing list archives

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

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

Richard Bowen commented on INFRA-18394:
---------------------------------------

Thanks, Chris. That being the case, I'd really like to do the fast-and-dirty thing now, and
the long-term solution once we have a clearer idea of what all of the options are.

Daniel's solution felt like that right one, but would it mean we'd have to make Yet Another
Change a few weeks/months later? If so, I'd like to avoid.

I did very briefly speak with Greg about this yesterday - across a large room, with other
conversations going on at the same time - and he seemed to be saying that we can solve this
quickly and easily.

The apachecon website situation is untenable, and has been for *years*, but we are hampered
by the fact that any major change would be very disruptive, and nobody has time for the work
involved (on the apachecon side, that is).

Perhaps this needs more discussion before it's a ticket.

> 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