From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [RFC] CONTRIBUTING.md
Date: Sat, 19 Aug 2017 09:55:26 -0400 [thread overview]
Message-ID: <e2e8183d-9563-3300-4d2f-0cdc8d23523f@siemens.com> (raw)
In-Reply-To: <20170808100752.GA5314@yssyq.radix50.net>
On 2017-08-08 06:07, Baurzhan Ismagulov wrote:
> Hello,
>
> as discussed, I've added CONTRIBUTING.md. Comments and suggestions welcome.
I think it wasn't on the list, was it?
I would strongly recommend avoiding fast-lane commits to master in the
future. Should be clarified in that file as well. That doesn't change
the role of the maintainer, just makes the work more transparent and
gives people a chance to comment prior to the application.
BTW, who is maintainer of the day? Do you announce that when you rotate?
Having two at the same time can be at least confusing and is generally
not best-practice.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-08-19 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 10:07 Baurzhan Ismagulov
2017-08-19 13:55 ` Jan Kiszka [this message]
2017-08-21 8:58 ` Henning Schild
2017-08-21 9:35 ` Baurzhan Ismagulov
2017-08-21 23:47 ` Baurzhan Ismagulov
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=e2e8183d-9563-3300-4d2f-0cdc8d23523f@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/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