From: Jeff Gazso <jeff.gazso@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: chromium@gentoo.org
Subject: Re: [gentoo-dev] www-client/chromium needs a new maintainer
Date: Wed, 7 Jun 2023 09:09:50 -0400 [thread overview]
Message-ID: <CAAxvVDgj7uYePc6acx5_r0fmfw2vRqFkRd6K6bNAiPmtTwsFbQ@mail.gmail.com> (raw)
In-Reply-To: <87pm67o7lh.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
I'm in the process of getting Gentoo dev status. I'm willing to consider
maintaining www-client/chromium. I have a high core count rack server that
should be able to handle the build process quite well. Can you give me a
list
of common pain points? If that is a long conversation feel free to email me
directly.
~Jeff
On Wed, Jun 7, 2023 at 7:06 AM Sam James <sam@gentoo.org> wrote:
>
> Alexe Stefan <stefanalexe48@gmail.com> writes:
>
> > My finger slipped in my last mail.
> > How do you see how many people are using a package?
>
> Bug reports, mentions on forums, mentions on the mailing list, mentions
> on IRC, etc.
>
> Or, to put it another way: when you break it, enough people
> shout. Gentoo doesn't have telemetry so we have to go off things like
> this.
>
[-- Attachment #2: Type: text/html, Size: 1229 bytes --]
next prev parent reply other threads:[~2023-06-07 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:59 [gentoo-dev] www-client/chromium needs a new maintainer Mike Gilbert
2023-06-07 10:54 ` Sam James
2023-06-07 10:58 ` Alexe Stefan
2023-06-07 11:00 ` Alexe Stefan
2023-06-07 11:04 ` Sam James
2023-06-07 13:09 ` Jeff Gazso [this message]
2023-06-07 14:12 ` Toralf Förster
2023-06-07 14:20 ` Sam James
2023-06-07 14:31 ` Ionen Wolkens
2023-06-07 17:45 ` Mike Gilbert
2023-06-07 18:38 ` Maciej Barć
2023-06-07 19:25 ` Jeff Gazso
2023-06-07 19:31 ` Sam James
2023-06-07 19:48 ` Mike Gilbert
2023-06-07 22:11 ` Alexe Stefan
2023-06-08 7:31 ` Joonas Niilola
2023-06-08 10:08 ` Alexe Stefan
2023-06-08 10:19 ` Joonas Niilola
2023-06-08 13:49 ` Sam James
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=CAAxvVDgj7uYePc6acx5_r0fmfw2vRqFkRd6K6bNAiPmtTwsFbQ@mail.gmail.com \
--to=jeff.gazso@gmail.com \
--cc=chromium@gentoo.org \
--cc=gentoo-dev@lists.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