From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2024-04-14 - Call for agenda items
Date: Mon, 01 Apr 2024 06:00:35 +0200 [thread overview]
Message-ID: <62e4ec5f5d27d8e4943f8ac026d58f562a5108f7.camel@gentoo.org> (raw)
In-Reply-To: <5168903.5fSG56mABF@noumea>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Mon, 2024-04-01 at 00:34 +0200, Andreas K. Huettel wrote:
> The next Gentoo Council meeting is scheduled for 2024-04-14.
>
> Please respond to this message with agenda items. Also, please
> repeat your agenda item here in this thread with a pointer if
> you previously suggested one (since the last meeting).
>
> The final agenda will be sent out before the meeting.
>
> Please reply to the gentoo-project list.
>
I'd also like the Council to take a formal motion on the redundancy
problems within the Gentoo PR project [1].
Long story short, many of the official or semi-official Gentoo accounts
on social media platforms and alike are maintained by a single person.
Such people often have very low availability, and we're running a very
high risk of losing access (if it hasn't happened already).
I think as a baseline policy we need to have backup of all credentials
in Infra secret storage. We may also need to issue a call for
volunteers to take maintenance of our social media accounts.
[1] https://bugs.gentoo.org/925014
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2024-04-01 4:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 22:34 [gentoo-project] Council meeting 2024-04-14 - Call for agenda items Andreas K. Huettel
2024-04-01 3:56 ` Michał Górny
2024-04-01 4:00 ` Michał Górny [this message]
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=62e4ec5f5d27d8e4943f8ac026d58f562a5108f7.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-project@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