public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: abebeos <lazaridis.com+abebeos@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [GOVERNANCE] Where to file complaints re project-maintainers?
Date: Sat, 8 May 2021 18:49:10 +0300	[thread overview]
Message-ID: <CADWdT=wsQSPyDmGTvkGP_=hvbUugqFahj_y+eq7vNc51+F7nZw@mail.gmail.com> (raw)

(failed to join gcc, so posting here)

Is there any private email where one can file complaints re
project-maintainers (or "those who are supervising the maintainers") ?

Is there any information about the process for such complaints?

Related Issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100480

(please note that this complaint will most possibly escalate up to the
person(s) who are responsible for policies/rules)

             reply	other threads:[~2021-05-08 15:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 15:49 abebeos [this message]
2021-05-09  2:06 ` Ian Lance Taylor
2021-05-09 15:33   ` abebeos
2021-05-09 17:32     ` Koning, Paul
2021-05-09 21:28       ` abebeos
2021-05-09 22:42         ` Eric Botcazou
2021-05-10 13:51           ` abebeos
2021-05-10  2:48     ` Ian Lance Taylor
2021-05-10  9:19       ` Jakub Jelinek
2021-05-10 13:52         ` abebeos
2021-05-10 20:32           ` Ian Lance Taylor
2021-05-10 21:45             ` abebeos
2021-05-10 22:35               ` Ian Lance Taylor
2021-05-11  2:35                 ` abebeos
2021-05-10 22:43               ` Jeff Law
2021-05-11  2:36                 ` abebeos
2021-05-14 13:15           ` Georg-Johann Lay
2021-05-14 14:47             ` abebeos
2021-05-23 16:02               ` Mike Stump
2021-05-24 18:14                 ` abebeos
2021-05-10 21:44       ` abebeos
2021-05-13 21:30 ` abebeos

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='CADWdT=wsQSPyDmGTvkGP_=hvbUugqFahj_y+eq7vNc51+F7nZw@mail.gmail.com' \
    --to=lazaridis.com+abebeos@gmail.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).