Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Buildroot ML <buildroot@buildroot.org>
Subject: [Buildroot] Resigning as a maintainer
Date: Sun, 13 Oct 2024 10:59:56 +0200	[thread overview]
Message-ID: <ZwuMDPcgFOLNVRqn@landeda> (raw)

Hello All,

Events and changes, more or less recent, both organisational and
technical, have made me reconsider whether I should continue
contributing, interacting with the community, and being a maintainer.

I've thought about it quite a bit, for quite some time now, and I
see now that merely asking the question begs only one possible
answer: no.

As a consequence, I have resigned from my position as a maintainer. The
other maintainers have been informed of my decision a few days ago now.

As for contributing, I don't see how the time I will regain from no
longer being a maintainer, could be applied to bring in evolutions to
Buildroot given the circumstances.

For the time being, I have no idea what will replace the many hours
a week I was spending on Buildroot on my own time; maybe a future
personal project will require that I use Buildroot again, but until
then, I will no longer be an active contributor either.

I will still keep my entries in the DEVELOPERS file for a while, so that
I can at least try and help fix the mess I leave behind me.

I am grateful to all the contributors, past and present, for the many
years we've been all together working toward making Buildroot better,
and building a great community; I've learned a lot along the ride.
I wish you all the best with your continued use of Buildroot and your
future contributions!

Peter, Thomas, Arnout, Romain: I wish you all the best in your future
endeavours with Buildroot maintenance.

So long, and thanks for all the fish.

Regards,
Yann E. MORIN.

P.S. To avoid any future confusion: this is my own personal position and
decision, and has no connection to my professional activities that may
be related to Buildroot.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-10-13  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-13  8:59 Yann E. MORIN [this message]
2024-10-24 20:39 ` [Buildroot] Resigning as a maintainer Thomas Petazzoni via buildroot
2024-10-25 21:19 ` Michael Nazzareno Trimarchi
2024-10-27 16:39 ` Dario Binacchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZwuMDPcgFOLNVRqn@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox