From: Fotios Valasiadis <fvalasiad@gmail.com>
To: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: Linux man-pages project maintenance
Date: Tue, 05 Nov 2024 14:06:00 +0200 [thread overview]
Message-ID: <AE38F6CA-0886-4C23-BD16-0B275071699E@gmail.com> (raw)
In-Reply-To: <4d7tq6a7febsoru3wjium4ekttuw2ouocv6jstdkthnacmzr6x@f2zfbe5hs7h5>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Hello Alex,
I too am thankful for your work, manpages were the only doc I had as a low level dev writing tools utilizing some of linux's niche system calls, literally wouldn't have managed without them.
I see you are somewhat active again, out of curiosity, did you find funding, or are you contributing some patches voluntarily once more?
Mind you I ain't assuming you are back as a maintainer just because you got some patches handled.
Thanks!
Fotis
On September 6, 2024 4:02:02 PM GMT+03:00, Alejandro Colomar <alx@kernel.org> wrote:
>Hi all,
>
>As you know, I've been maintaining the Linux man-pages project for the
>last 4 years as a voluntary. I've been doing it in my free time, and no
>company has sponsored that work at all. At the moment, I cannot sustain
>this work economically any more, and will temporarily and indefinitely
>stop working on this project. If any company has interests in the
>future of the project, I'd welcome an offer to sponsor my work here; if
>so, please let me know.
>
>Have a lovely day!
>Alex
>
>--
><https://www.alejandro-colomar.es/>
-- fvalasiad --
next prev parent reply other threads:[~2024-11-05 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 13:02 Alejandro Colomar
2024-09-06 16:22 ` Michael Kerrisk (man7.org)
2024-09-09 8:28 ` Stefan Puiu
2024-10-28 10:58 ` AW: " Walter Harms
2024-11-05 12:06 ` Fotios Valasiadis [this message]
2024-11-05 23:42 ` Alejandro Colomar
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=AE38F6CA-0886-4C23-BD16-0B275071699E@gmail.com \
--to=fvalasiad@gmail.com \
--cc=alx@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).