infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafa Haro (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17442) Admin Access to Project at Jira and Job at Jenkins
Date Fri, 21 Dec 2018 09:23:00 GMT

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

Rafa Haro commented on INFRA-17442:
-----------------------------------

Hi [~humbedooh], as I explained in the ticket, current chair is not active in the project
because of lack of time. After discussing with members of the board, they told me that other
PMC members can eventually perform typical chairs' tasks. We have voted a new committer and
a new PMC member but I don't have permissions at whimsy to add them. That's the reason I'm
asking

Please let me know if I have to open a new ticket for this because I doubt we can count on
the current chair right now

Thanks and apologise 

> Admin Access to Project at Jira and Job at Jenkins
> --------------------------------------------------
>
>                 Key: INFRA-17442
>                 URL: https://issues.apache.org/jira/browse/INFRA-17442
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins, JIRA, LDAP
>            Reporter: Rafa Haro
>            Assignee: Gavin
>            Priority: Major
>
> Hi,
> As PMC member of Apache Stanbol, I would like to have admin access to the project at
Jira and to the Job configured at Jenkins. Current members with access to both are becoming
less active and I need this for maintaining both.
> Not sure yet if I also need access to LDAP in order to update it when new comitters and
PMC members are invited to join
> My apache nickname is rharo. Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message