public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Дилян Палаузов" <dilyan.palauzov@aegee.org>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	       Joseph Myers	 <joseph@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Make clear, when contributions will be ignored
Date: Sun, 10 Feb 2019 14:45:00 -0000	[thread overview]
Message-ID: <a7f5412515a1698e47c006703519e490c7522047.camel@aegee.org> (raw)
In-Reply-To: <20190206124401.GO14180@gate.crashing.org>

Hello,

thanks to Serger and Joseph for the feedback.

Acting primary upon reminders is a general phenomenon in the society, nothing specific to software teams.  Think on
public administration: it acts sometimes much more collaboratively, if a public/private/famous media reports on the
workflows of the public administration.  Public administration also reacts sometimes only, if reminders are sent.

Not surprizing is, that talking with a public administration, about their policy on acting only after receiving a
reminder, leads to nowhere, as making progress on this discussion with such an administration, needs a lot of reminders.
In summary, such public administrations insist on their right to receive reminders before acting.

Do you share the opinion, that whatever can be done after receiving a reminder, can be arranged also without reminder? 
If yes, how do you propose to proceed, so that a no-reminders-are-necessary-state is reached?

I read in the answer of Segher, that the purpose of reminding is not only to ping, but also to filter the ones who are
pernetrant and sending manually reminders is the means to verify, that the persons really want to make progress.  It was
certainly not intentionally meant this way, but this is a possible reading.

Let me repeat, that the topic is not anyhow GCC specific, nor do I offend the society anyhow.  To make things better,
first the causes for the current state have to be understood.

Raising the topic on GNU Tools Cauldron is a very good idea, but it likely approaches less people than on this mailing
list, I am not that much inside the GCC processes and I do not know, whether I can visit the next meeting.

Regards
  Дилян

On Wed, 2019-02-06 at 06:44 -0600, Segher Boessenkool wrote:
> On Fri, Dec 07, 2018 at 10:55:11AM +0000, Дилян Палаузов wrote:
> > will it help, if Bugzilla is reprogrammed to send automatically weekly
> > reminders on all patches, that are not integrated yet?
> 
> No, that will not help.
> 
> If an interested party sends a friendly ping, that is of course welcome.
> But automated pings are spam: unwanted bulk mail.
> 
> > The patch I proposed on 27th Oct was first submitted towards GDB and
> > then I was told to send it to GCC.  Here I was told to sent it to GDB. 
> > What shall happen to quit the loop?
> 
> You can cc: both sides of the discussion.  Either also gdb-patches, or also
> whoever told you to send it to GCC instead, or both.  And include a link to
> the mailing list archive of your thread on gdb-patches in your mail to
> gcc-patches, so that all parties can see the relevant context.  Make it
> easy for people to help you!
> 
> 
> Segher

  reply	other threads:[~2019-02-10 14:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  7:36 Make claer, " Дилян Палаузов
2018-12-05 17:13 ` Segher Boessenkool
2018-12-05 17:37   ` Joseph Myers
2018-12-07 10:55     ` Make clear, " Дилян Палаузов
2018-12-21  8:08       ` +reminder+ " Дилян Палаузов
2019-02-05 13:36       ` Дилян Палаузов
2019-02-05 23:10         ` Joseph Myers
2019-02-06 12:46       ` Segher Boessenkool
2019-02-10 14:45         ` Дилян Палаузов [this message]
2019-02-10 20:59           ` Segher Boessenkool
2019-02-11 12:44             ` Дилян Палаузов
2019-02-11 14:01               ` Segher Boessenkool
2019-02-11 14:16                 ` Дилян Палаузов
2019-02-11 16:27                   ` Segher Boessenkool
2019-02-17 17:00                     ` Дилян Палаузов
2019-02-17 19:13                       ` Segher Boessenkool
2019-02-17 19:47                         ` Дилян Палаузов
2018-12-05 17:17 ` Make claer, " Maciej W. Rozycki

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=a7f5412515a1698e47c006703519e490c7522047.camel@aegee.org \
    --to=dilyan.palauzov@aegee.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=segher@kernel.crashing.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).