I think just for now add a command to the irc bot to invite the user to the org.
Make user a maintainer on team doesn't work unless the user is part of the org anyway... On Wed, 27 Oct 2021 at 12:18, '[email protected]' via Jenkins Developers < [email protected]> wrote: > > Hi all, > > So thanks Baptiste for creating the team which I now have maintainership > of so can add users. > > One issue I have is that users that are not currently a member of the > jenkinsci organisation can not be added to the team. > > I guess normally adding a user to a plugin group via IRC would also invite > them to the org, but as this is to be used outside of a plugin group not > sure what we should be doing? > > irc-bot has `jenkins-admin: Make USER a maintainer on TEAM` but we do not > want all members to be maintainers of the team. > > So my question is what would be the best cause of action here, or how > would we best onbaoard users into the jenkinsci org? > > I am open to extending irc-bot with a command like `jenkins-admin: invite > user to the organisation` or `jenkins-admin: Make USER a member on TEAM` if > that helps at all. > > /James > > > On Wednesday, October 27, 2021 at 10:58:51 AM UTC+1 [email protected] > wrote: > >> Thanks Tim for the confirmation. >> >> Yeah, not 100% of the naming either. >> But yep, given at this point it's only one + this part is manual, that's >> not a big deal yet. >> >> Le mer. 27 oct. 2021 à 11:50, Tim Jacomb <[email protected]> a écrit : >> >>> Sounds fine, not 100% sure company needs to be at the start but we can >>> also rationalise it later if we get more >>> >>> On Wed, 27 Oct 2021 at 10:42, Baptiste Mathus <[email protected]> wrote: >>> >>>> Hi all, >>>> >>>> FYI I've created this epic to track this: >>>> https://issues.jenkins.io/browse/INFRA-3111. >>>> >>>> I plan to manually do the creation of a GitHub team for CloudBees >>>> developers in the next hour or so if nobody objects. AFAICT from the >>>> discussion above, we have an agreement that it makes sense and is >>>> acceptable. >>>> I will name it "company-cloudbees-developers" so one can easily find >>>> all companies in the teams, using typically >>>> https://github.com/orgs/jenkinsci/teams?query=company- >>>> >>>> For the RPU part, I've created >>>> https://issues.jenkins.io/browse/INFRA-3113 to describe what we'd want >>>> to have. >>>> We (cloudbees team) plan to look into implementing this soon. Given >>>> this sounds reasonably simple, I think it can be done some time in November >>>> 2021. >>>> Any review on this enhancement proposal is welcome :-). >>>> >>>> Last, and important, thing: this feature is not only for CloudBees. The >>>> point is that any company/team willing to do this is welcome to ask. >>>> >>>> Cheers >>>> >>>> >>>> Le jeu. 21 oct. 2021 à 19:12, 'Daniel Beck' via Jenkins Developers < >>>> [email protected]> a écrit : >>>> >>>>> >>>>> >>>>> On Thu, Oct 21, 2021 at 3:47 PM Baptiste Mathus <[email protected]> >>>>> wrote: >>>>> >>>>>> Care to elaborate what you mean and how that would work? IIUC, what >>>>>> you're describing would quite entail refactoring all existing "xyz-plugin >>>>>> developer" groups on GitHub side? >>>>>> And as you know we currently have close to no notion of github on RPU >>>>>> side, like the names there are only artifactory's ones. >>>>>> >>>>> >>>>> Yup, these realms are independent so unless you find a way to have a >>>>> tamper-proof bi-directional mapping, there's no need to worry about GH >>>>> permissions while dealing with upload permissions. Note that I only >>>>> responded to the part around RPU. >>>>> >>>>> >>>>>> Do you mean we should improve RPU to better manage multi-modules? In >>>>>> that case, I don't disagree, but I think we should put it in a separate >>>>>> bucket so we can improve the situation iteratively. >>>>>> I think what James describes can be done in a very quick way (still >>>>>> clean), and what you describe here seems bigger. >>>>>> >>>>> >>>>> I am just pointing out that the use case goes beyond multiple plugins >>>>> maintained by the same group, and this change can also benefit others >>>>> while >>>>> the mentioned limitation exists. >>>>> >>>>> -- >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLs27A9ODjSe537Ar3pRwkTYNiFr8WHX88Kd7EQtvUSow%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLs27A9ODjSe537Ar3pRwkTYNiFr8WHX88Kd7EQtvUSow%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4prSBQsOx%3D2UmfqrjronEkn7j4qWWQvVk2WaGwS8ZPZA%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4prSBQsOx%3D2UmfqrjronEkn7j4qWWQvVk2WaGwS8ZPZA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> 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 [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicz862ZrAAx%2Bbjsb_E_6gTj8NkYk2x%3DNBZQvxNktLye3w%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicz862ZrAAx%2Bbjsb_E_6gTj8NkYk2x%3DNBZQvxNktLye3w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/97fdb78d-1275-4a4a-94c4-b1b9ce1b923an%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/97fdb78d-1275-4a4a-94c4-b1b9ce1b923an%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidQeq4w5eBJ63%3Dcy6a%2BormhpWoC2C1QQ29cbi9Getc7Xg%40mail.gmail.com.
