www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12208) openoffice-security group additions
Date Tue, 05 Jul 2016 06:59:11 GMT

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

Dennis E. Hamilton commented on INFRA-12208:
--------------------------------------------

I guess the problem is that the tools we are given for this don't handle this particular kind
of group and it is a mystery.  Perhaps the best answer is to arrange it so that the projects
can actually self-manage this without having to know what infra knows?  That seems like the
win-win to me.

If it means pull requests for these, so be it.  Now however, I am on a project that is all
SVN based, so that's a problem too.

But to make every project have to know how to do what infra does for maintaining these odd
groups might relieve infra, and I don't object to that.  The question is how does that transfer
of knowledge and *reliability* happen.  Or is there need for a better tool in this instance?

And where should we hold this conversation?


> openoffice-security group additions
> -----------------------------------
>
>                 Key: INFRA-12208
>                 URL: https://issues.apache.org/jira/browse/INFRA-12208
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Subversion
>            Reporter: Dennis E. Hamilton
>            Assignee: Daniel Takamori
>            Priority: Minor
>
> Please add cmarcum and kschenk to the pit-authorization:openoffice-security group.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message