Hi, thank you. Its working now.
Greetings, Thomas Am Samstag, 8. Dezember 2018 00:48:06 UTC+1 schrieb Oleg Nenashev: > > Hi, > > It should be fixed now. > It seems we have an issue with the ChatOps bot OR with the developer group. > It had read-only permissions due to whatever reason > > BR, Oleg > > On Fri, Dec 7, 2018 at 4:56 PM Thomas Döring <[email protected] > <javascript:>> wrote: > >> Hi Oleg again, >> >> maybe a stupid question: The write access is setup for the GitHub user >> "thomas-dee" (https://github.com/thomas-dee), right? Or do I have to >> login with another account? >> >> Greetings, >> Thomas >> >> Am Freitag, 7. Dezember 2018 14:48:14 UTC+1 schrieb Oleg Nenashev: >>> >>> Hi Thomas, >>> >>> Once you accept the invitation to the jenkinsci org, everybody should be >>> set. >>> Please check your inbox, you should have received it on Dec 4 >>> >>> BR, Oleg >>> >>> >>> On Fri, Dec 7, 2018 at 2:46 PM Thomas Döring <[email protected]> wrote: >>> >>>> Hi Olge, >>>> >>>> is there anything else I need to do to get write permissions for the >>>> embeddable-build-status-plugin? >>>> >>>> Greetings, >>>> Thomas >>>> >>>> Am Mittwoch, 5. Dezember 2018 07:53:34 UTC+1 schrieb Oleg Nenashev: >>>>> >>>>> Thanks for the response, Marius! >>>>> >>>>> Hi Thomas, >>>>> >>>>> I have granted you the write permissions to the repo and made you a >>>>> default assignee in JIRA. >>>>> Thanks again for your interest, and welcome aboard! >>>>> >>>>> To get the release permissions, please submit a pull request to >>>>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-embeddable-build-status.yml >>>>> >>>>> Best regards, >>>>> Oleg >>>>> >>>>> On Tuesday, December 4, 2018 at 3:39:45 PM UTC+1, Thomas Döring wrote: >>>>>> >>>>>> >>>>>> Oh. I forgot: My GitHub username is "thomas-dee". My Jenkins-ID is >>>>>> "thomas_dee". >>>>>> >>>>>> Am Montag, 3. Dezember 2018 20:13:26 UTC+1 schrieb Thomas Döring: >>>>>>> >>>>>>> Hello again, >>>>>>> >>>>>>> Well then: I hereby request adoption for the >>>>>>> embeddable-build-status-plugin. >>>>>>> And Marius: There will be no new release until January. >>>>>>> >>>>>>> Greetings, >>>>>>> Thomas. >>>>>>> >>>>>>> Am Montag, 3. Dezember 2018 14:30:30 UTC+1 schrieb Marius Gedminas: >>>>>>>> >>>>>>>> Hi! >>>>>>>> >>>>>>>> I have no interest in maintaining embeddable-build-status-plugin, >>>>>>>> so if >>>>>>>> my opinion matters, anyone else is welcome to step up! >>>>>>>> >>>>>>>> (I have some slight interest in having the plugin continue working, >>>>>>>> and >>>>>>>> in having it produce badges in the common shields.io style, until >>>>>>>> end of >>>>>>>> December, when I plan to shut down my Jenkins instance.) >>>>>>>> >>>>>>>> On Mon, Dec 03, 2018 at 08:39:08AM +0100, Oleg Nenashev wrote: >>>>>>>> > Added [1]Marius Gedminas to Cc. >>>>>>>> > Since Jesse Glick says he is not a maintainer, Marius is the last >>>>>>>> contributor >>>>>>>> > to release 2 versions of the plugin before Jesse. >>>>>>>> > >>>>>>>> > Let's set a standard 2-week timeout. >>>>>>>> > >>>>>>>> > BR, Oleg >>>>>>>> > >>>>>>>> > >>>>>>>> > On Mon, Dec 3, 2018 at 8:13 AM Thomas Döring <[2][email protected]> >>>>>>>> wrote: >>>>>>>> > >>>>>>>> > Is there any way to "adopt" the plugin if there is no current >>>>>>>> maintainer >>>>>>>> > (since I can ask no one to approve). >>>>>>>> > >>>>>>>> > Am Freitag, 30. November 2018 16:01:58 UTC+1 schrieb Jesse >>>>>>>> Glick: >>>>>>>> > >>>>>>>> > On Thu, Nov 29, 2018 at 3:33 PM Oleg Nenashev < >>>>>>>> [email protected]> >>>>>>>> > wrote: >>>>>>>> > > I will ask the maintainers >>>>>>>> > >>>>>>>> > I do not know if there _are_ any maintainers. Not me. >>>>>>>> >>>>>>>> Marius Gedminas >>>>>>>> -- >>>>>>>> Q: How many IBM CPU's does it take to execute a job? >>>>>>>> A: Four; three to hold it down, and one to rip its head off. >>>>>>>> >>>>>>> -- >>>> 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/BXZUKKEQWQk/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/d76ec08a-9937-4340-8203-12c925d5d94e%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d76ec08a-9937-4340-8203-12c925d5d94e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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/BXZUKKEQWQk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/f91d7b9e-7877-413c-a564-8cc3b1087ed2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/f91d7b9e-7877-413c-a564-8cc3b1087ed2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1a2ed5f4-2908-4c03-9546-7ffecea3596f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
