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 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/20181203133023.wtlco2lddk2nxw5n%40platonas.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: PGP signature

Reply via email to