From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-07-21
Date: Tue, 9 Jul 2019 11:02:38 +0200 [thread overview]
Message-ID: <20190709090238.GA28475@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <w6gzhlptzf0.fsf@kph.uni-mainz.de>
[2019-07-07 21:30:59+0200] Ulrich Mueller:
> In two weeks from now, the newly elected Council will have its
> constituent meeting. This is the time to raise and prepare items that
> the Council should put on the agenda to discuss or vote on.
>
> Please respond to this message with agenda items. Do not hesitate to
> repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).
>
> The agenda for the meeting will be sent out on Sunday 2019-07-14.
>
> Please reply to the gentoo-project list.
>
> Ulrich
Not sure if as a non-developer I can call for an agenda item but as it
has been in other threads by developers I think there should be a
removal of the "legal name"[1] part of GLEP-76.
It's been driving at least two active contributors away, with a least
one other person having their name outed, which is a seriously bad
flag. (I don't have the link right now to it but could find it at a
later time. And I think it would be better to not send it publicly
anyway)
Which is also the reason to why I wouldn't have trust in a
proxy/compromise similar such as having the real name known by
so-called "trustees".
1: Which is very vague as depending on the jurisdiction you can quite
easily change your name either with a bit of money for the paperwork
or having testimony from people that they know you under this name.
--
Haelwenn (lanodan) Monnier
next prev parent reply other threads:[~2019-07-09 9:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 19:30 [gentoo-project] Call for agenda items - Council meeting 2019-07-21 Ulrich Mueller
2019-07-07 20:51 ` Michał Górny
2019-07-07 21:00 ` Michał Górny
2019-07-08 4:43 ` Ulrich Mueller
2019-07-08 5:36 ` Michał Górny
2019-07-08 13:50 ` Rich Freeman
2019-07-09 9:58 ` Ulrich Mueller
2019-07-12 19:56 ` Andreas K. Huettel
2019-07-21 0:22 ` Andrew Savchenko
2019-07-09 9:28 ` Lars Wendler
2019-07-10 13:55 ` William Hubbs
2019-07-10 14:07 ` Michael Everitt
2019-07-10 15:48 ` William Hubbs
2019-07-20 23:57 ` Andrew Savchenko
2019-07-20 23:48 ` Andrew Savchenko
2019-07-21 1:11 ` Raymond Jennings
2019-07-21 6:28 ` Michał Górny
2019-07-21 11:25 ` Andrew Savchenko
2019-07-21 11:52 ` Raymond Jennings
2019-07-21 13:33 ` Michael Orlitzky
2019-07-09 9:02 ` Haelwenn (lanodan) Monnier [this message]
2019-07-13 7:39 ` Ulrich Mueller
2019-07-13 10:53 ` Haelwenn (lanodan) Monnier
2019-07-13 3:28 ` desultory
2019-07-13 4:11 ` Matthew Thode
2019-07-13 6:56 ` Michał Górny
2019-07-13 7:09 ` Ulrich Mueller
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=20190709090238.GA28475@cloudsdale.the-delta.net.eu.org \
--to=contact@hacktivis.me \
--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