public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Cc: gyakovlev@gentoo.org, xen0n@gentoo.org, rust@gentoo.org
Subject: [gentoo-dev] Pseudo up-for-grabs: dev-lang/rust, dev-lang/rust-bin, virtual/rust
Date: Thu, 25 Jan 2024 04:56:46 +0000	[thread overview]
Message-ID: <871qa6j9aq.fsf@gentoo.org> (raw)

Hi all,

rust@ is essentially empty as gyakovlev is long-term away and
dev-lang/rust, dev-lang/rust-bin, virtual/rust, sys-devel/rust-std,
etc all need _at least one_ maintainer.

xen0n has been doing some of the bumps but he's only really doing
so drive-by (although with best-effort review) and isn't AFAIK
interested in maintaining Rust full-time.

gyakovlev had some notes at
https://wiki.gentoo.org/wiki/User:GYakovlev/Rust_bump on bumping Rust,
might be that xen0n can improve that a little bit to improve handover if
necessary.

Ultimately, Rust needs an active maintainer who is on-top of the
ecosystem and able to handle the regular bumps every 6 weeks.

We already have a package needing not-in-tree rust-1.75.0
(https://bugs.gentoo.org/922880) which was only released 3-4 weeks
ago.

Please consider stepping forward if you rely on Rust. There's more
than enough advocates for it, there should be someone who is able
to then handle the packaging side.

thanks,
sam


             reply	other threads:[~2024-01-25  5:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  4:56 Sam James [this message]
2024-01-26  0:12 ` [gentoo-dev] Pseudo up-for-grabs: dev-lang/rust, dev-lang/rust-bin, virtual/rust Randy Barlow
2024-01-26  9:15   ` Sam James
2024-01-29 23:37 ` Randy Barlow
2024-01-30 15:40   ` Pascal Jäger
2024-01-31  1:49     ` Randy Barlow

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=871qa6j9aq.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gyakovlev@gentoo.org \
    --cc=rust@gentoo.org \
    --cc=xen0n@gentoo.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