Linux-Sparse Archive mirror
 help / color / mirror / Atom feed
From: Chris Li <sparse@chrisli.org>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Sparse maintainership
Date: Thu, 18 Sep 2025 08:44:47 -0700	[thread overview]
Message-ID: <CACePvbXDO1ZybDu3RaFhED9D-9gC6LTMpWrxoh5xD+ZO5SLdzA@mail.gmail.com> (raw)

Very sorry that I disappeared from the project for a very long time.

I was the sparse maintainer until someone really wanted the sparse
project maintenance and fought me over it.

I was deeply wounded at that time and felt sick of the situation. I
pulled the plug completely, I stopped caring.

I was afraid to click on the sparse mailing list folder, even though I
am still subscribed to it, like a wounded puppy afraid to lick the
wound. I can observe the number of unread emails in the sparse folder
is growing, I assume the project is doing great with the new
maintainer. I am afraid to look inside.

I accidentally clicked on this folder today. To my surprise  the
project seems unmaintained.
That breaks my heart, again.

I would like to get some clarification on the mailing list:
Is the sparse project still maintained? I really don't want to step on
anybody's toe.

If not, does anyone mind if I slowly resume some maintainer duty at a
very very slow pace?

I have much less capacity in hobby projects than I used to nowadays.
If I ever pick up again, I can't promise any capacity or SLO. It will
be my own very slow peace. I just feel sad to see the project I used
to care so much got unmaintained.

If there are any objections, please let me know in the mail list or privately.

Thanks and sorry about the disappearance. At least I feel brave enough
to click on the sparse folder now.

Chris

             reply	other threads:[~2025-09-18 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 15:44 Chris Li [this message]
2025-09-18 15:57 ` Sparse maintainership Derek M Jones
2025-09-18 17:04 ` Ben Dooks
2025-09-18 18:28 ` Linus Torvalds
2025-09-21 20:24   ` Chris Li

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=CACePvbXDO1ZybDu3RaFhED9D-9gC6LTMpWrxoh5xD+ZO5SLdzA@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).