And, as is usual when the issue of the apachecon website comes up, this has become more complicated than I thought it would be.

Those of you who are maintaining a current Apache event website (ie, me, Myrle, and Trevor) might want to track this ticket over the coming days. Or I will send periodic updates until the can of worms is reclosed.


On 5/17/19 9:39 AM, Rich Bowen wrote:
I have created the following Jira ticket: https://issues.apache.org/jira/browse/COMDEV-320

The request is as follows:


 >>
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 is more FYI than asking for advice, comments, input, whatever. However, if there are any large concerns around this, please speak up. I expect, however, that this is obvious and uncontroversial.

Thanks.



--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to