public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Subject: Second year of sponsorship
Date: Tue, 10 Feb 2026 00:52:50 +0100	[thread overview]
Message-ID: <aYprOnLo5WSP8Ljh@devuan> (raw)

[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]

Hi!

A few days ago, we signed the contract for the second year of
sponsorship of the project, for the period 2025-11..2026-10.

Some links to context, in case anyone wasn't aware of this:
<https://lwn.net/Articles/989215/>
<https://lwn.net/Articles/997193/>
<https://www.linux.com/news/celebrating-the-second-year-of-linux-man-pages-maintenance-sponsorship/?hss_channel=lcp-208777>

We've lost a couple of sponsors this time, which means we're below what
would be okay for a sustainable amount.  However, I understand the
global situation is how it is, and agreed to continue for this period.
But the cost of living rises, so for having a sustainable project we
need more companies (or foundations --cough, LF, cough--) joining the
sponsorship of the project.

Anyway, I'd like to thank the two sponsors that helped me through last
year which couldn't continue this year.  Your help was very much
appreciated!

And of course, I'd also like to thank the three sponsors that continue
this year!  Your help was and is very much appreciated!

	$ cat SPONSORS;
	Google               <https://opensource.google/>
	Hudson River Trading <https://www.hudsonrivertrading.com/>
	Meta                 <https://www.meta.com/>

Now that the EU is interested in tech sovereignty, it might be
interested in funding projects that it needs, which might help this and
other projects.  <https://lwn.net/Articles/1053107/>.  In order to help
people know which projects they depend upon --possibly unknowingly--,
I've documented all the dependencies of this project (this might help
anyone needing to produce an SBOM).  See the file <README.d/deps> in
the git repository.  You can find it here:
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/README.d/deps>
I know for a fact that more than one of those projects would benefit of
some funding.

In the following days, I'll publish a new release of the manual pages.
This one is going to be huge.  :)

I've been too overloaded in the past few weeks with quite a few things,
including renewing the contract, a meeting of the C Committee (and its
preparation), and preparing this release.  Sorry if I didn't respond.
I hope you'll enjoy the new release!


Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2026-02-09 23:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=aYprOnLo5WSP8Ljh@devuan \
    --to=alx@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