Commit access to jenkinsci/SCTMExecutor-plugin

[Sebastian Kornexl]

Hi,

 

when the source was on SVN I already had permissions to commit.

 

Can I have these permission on GitHub too?

 

Rep: https://github.com/jenkinsci/SCTMExecutor-plugin

GitHub account: donkaes

 

Time for a new release of this plugin.

 

Thanks,

Sebastian

 

[Thomas Fürer]

Hi seb,

I'm wondering, because I'm not able to set ownership or commit rights on
this project, even I'm the maintainer and owner of this project.

So maybe one of the jenkins staff can help us.

Meanwhile I saw you allready forked the project, but I'm not sure if in
this case the release worflow will work?

thanks,
Thomas

> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[Oleg Nenashev]

In GitHub the right approach to the contribution is to create pull requests from forks to the master repo. In such case the plugin developers will be able to review and accept the pull request.

Anyway I've granted the commit permissions to Sebastian. He dhould get an invitation to the jenkinsci org soon.

BR, Oleg

суббота, 5 сентября 2015 г., 13:50:30 UTC+3 пользователь Thomas Fuerer написал:

Hi seb,

I'm wondering, because I'm not able to set ownership or commit rights on
this project, even I'm the maintainer and owner of this project.

So maybe one of the jenkins staff can help us.

Meanwhile I saw you allready forked the project, but I'm not sure if in
this case the release worflow will work?

thanks,
Thomas

Am 21.08.2015 um 12:23 schrieb Sebastian Kornexl:
> Hi,
>
>  
>
> when the source was on SVN I already had permissions to commit.
>
>  
>
> Can I have these permission on GitHub too?
>
>  
>
> Rep: https://github.com/jenkinsci/SCTMExecutor-plugin
>
> GitHub account: donkaes
>
>  
>
> Time for a new release of this plugin.
>
>  
>
> Thanks,
>
> Sebastian
>
>  
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-dev+unsub...@googlegroups.com>.

[Thomas Fürer]

Hi Oleg,

thanks for helping, but why do I not have permissions to change
settings. I'm the founder, owner an maintainer of this plugin? I also
have a different plugin for jenkins (thinbackup) and here I'm able to
change the settings.

Regards,
Thomas

> > an email to jenkinsci-de...@googlegroups.com <javascript:>
> > <mailto:jenkinsci-de...@googlegroups.com <javascript:>>.

> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com>
>
> >

> <https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email&utm_source=footer

> <https://groups.google.com/d/msgid/jenkinsci-dev/BDD6AE160CFA944A9A8A16488252F26C013466B7FD%40NWB-EXCHANGE2.microfocus.com?utm_medium=email&utm_source=footer>>.
>
> > For more options, visit https://groups.google.com/d/optout

> <https://groups.google.com/d/optout>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com

> <mailto:jenkinsci-de...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/e9ef07c6-c05d-4fd5-8293-ce64c9ab47b4%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Oleg Nenashev]

I have no permissions to check your permissions :(

CC'ed Daniel Beck, he should be able to do it.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/GxfNANOJ5IY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/55EC8C0A.8030508%40googlemail.com.

[Daniel Beck]

The permissions we have on GitHub are a complete mess.

We have the 'Everyone' group (which does _not_ contain everyone) that gives push access to almost every repo. This is basically the 'default' permission given by some project admins (my theory: the command requires less typing :-) ). So you may well have commit access to your plugin repo, like almost everyone else, but not be able to administer it (which is the case here). OTOH you also get commit access to a thousand repos you don't care about (and whose maintainers would well object to that). Cool, right?

Then we have per-repo 'foo-plugin Developers' groups, which gives admin access for the one repo. This is what I assign most of the time. Unfortunately, if you're given that permission, can use it to create new repos and completely mess up the repo/group permission system we use. (Also, most plugins probably shouldn't track their issues on GitHub when the users are expecting that to be on the Jenkins JIRA.)

With this explanation out of the way, I made Thomas a member of 'SCTMExecutor-plugin Developers'. Don't create new repos!

> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLA8w1ZsR3ubfDijoWebxQ8KCXOSvmHpGrDy7X2VUrWjxQ%40mail.gmail.com.

[Thomas Fürer]

thanks oleg and daniel,

I do not know how you want to do the permission stuff. however currently
I have no admin permissions to sctmexecutor but to thin-backup-plugin.
both repositories belongs to me!

Are you sure you add tofuatgit or tofuatjava to the admin group?

regards,
thomas

[Daniel Beck]

> On 07.09.2015, at 08:53, Thomas Fürer <tfuerer...@gmail.com> wrote:
>
> Are you sure you add tofuatgit or tofuatjava to the admin group?

I did, but this specific "admin" group only gave write permissions. m( Fixed now.

Did I mention permissions are a mess?

[Thomas Fürer]

you are my hero of the day,

godfather of permissions ;-)

thanks again,
thomas