-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update plugin-fitnesse.yml #653
Update plugin-fitnesse.yml #653
Conversation
Ideally @lessonz would also confirm this here, just to be sure. Do you still need commit access to the GitHub repo as well? |
I will indeed need access to the GitHub repo as well. |
I'm not sure if this was directed at me. If so, I do NOT still need commit
access.
Cheers
…On Thu, Mar 29, 2018 at 2:39 PM Daniel Beck ***@***.***> wrote:
Ideally @lessonz <https://github.com/lessonz> would also confirm this
here, just to be sure.
Do you still need commit access to the GitHub repo as well?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#653 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADw6ds5R2B3M8P77LW0oinEFCwdYAvTYks5tjUaTgaJpZM4TAwA5>
.
|
@lessonz Thanks! That part wasn't directed at you, sorry about that. Would still appreciate explicit overall approval of this addition to the plugin releasers / owners though. |
Okay, if the approval request is aimed at me, I approve. |
jenkinsci/fitnesse-plugin#35 is in the scope, I'd guess. Rhanks @lessonz ! |
@daniel-beck The only thing missing seems to be the GitHub repo access. Thanks |
@CSLTech Done, you should have been added to the repo, or gotten an invitation to the jenkinsci GitHub org. |
Description
Taking over for maintenance of fitnesse plugin. Plugin can be found at: https://github.com/jenkinsci/fitnesse-plugin
@lessonz approved change at https://groups.google.com/forum/#!msg/jenkinsci-dev/II-ishc_xfU/xq2rrChDAAAJ;context-place=forum/jenkinsci-dev
Refered by issue: https://issues.jenkins-ci.org/browse/HOSTING-532
Submitter checklist for changing permissions
Always
For a newly hosted plugin only
For a new permissions file only
permissions/
directoryartifactId
(pom.xml) is used forname
(permissions YAML file).groupId
/artifactId
(pom.xml) are correctly represented inpath
(permissions YAML file)plugin-${artifactId}.yml
for pluginsWhen adding new uploaders (this includes newly created permissions files)
@
mention an existing maintainer to confirm the permissions request, if applicable