From: Petr Lautrbach <plautrba@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Petr Lautrbach <plautrba@redhat.com>, selinux@vger.kernel.org
Subject: Re: [PATCH] Add CONTRIBUTING
Date: Fri, 31 May 2019 19:45:09 +0200 [thread overview]
Message-ID: <pjdo93iv7q2.fsf@redhat.com> (raw)
In-Reply-To: <CAHC9VhQcuQ8+eoxXXqtEL4+PyxrWdpVvgMG9FDKnmr_XfaBsiA@mail.gmail.com>
Paul Moore <paul@paul-moore.com> writes:
> On Wed, May 29, 2019 at 12:05 PM Paul Moore <paul@paul-moore.com> wrote:
>> On Wed, May 29, 2019 at 12:03 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>> >
>> > Based on https://github.com/SELinuxProject/selinux/wiki/Contributing
>> >
>> > Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>> > ---
>> > CONTRIBUTING | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 1 file changed, 60 insertions(+)
>> > create mode 100644 CONTRIBUTING
>>
>> I would suggest updating the wiki to point to this file if/when it is
>> merged upstream.
>
> Sorry, one more thing: you might consider adding the ".md" suffix so
> that GitHub and others will treat it as Markdown. I know that GitHub
> also treats the CONTRIBUTING.md file in a special way and presents it
> to users in various parts of the web UI, for example it show up in the
> sidebar when creating new issues.
Using Contributing.md in code would mean that it could be directly
copied to wiki.
When you say include DCO directly in Contributing, do you mean something
like
https://github.com/bachradsusi/SELinuxProject-selinux/wiki/Contributing
?
Petr
next prev parent reply other threads:[~2019-05-31 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 16:03 [PATCH] Add CONTRIBUTING Petr Lautrbach
2019-05-29 16:05 ` Paul Moore
2019-05-31 15:16 ` Paul Moore
2019-05-31 17:45 ` Petr Lautrbach [this message]
2019-05-31 17:54 ` Paul Moore
2019-05-31 20:19 ` [PATCH v2] Add CONTRIBUTING.md Petr Lautrbach
2019-05-31 21:01 ` Paul Moore
2019-06-14 19:00 ` Stephen Smalley
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=pjdo93iv7q2.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.