From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jeff Elsloo <jeff.elsloo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Contribution Question
Date: Wed, 26 Oct 2016 09:27:47 +0200 [thread overview]
Message-ID: <dfc7de1a-eb91-2c56-8afc-871e9d1951fa@redhat.com> (raw)
In-Reply-To: <CABjXaGv8B9eK5ucw6H436oAWTNwTpB__snrCFGv1UDwnMb48yg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 13.10.2016 19:12, Jeff Elsloo wrote:
> Hi all,
>
> I've been working on a small enhancement for dracut and unfortunately
> before I'm able to make a contribution, my company's legal team has a
> licensing question. Is the project strictly governed by the terms of
> the GPLv2, or are there additional requirements such as a Contributor
> License Agreement (CLA)? I looked around at the project and various
> sites/docs and didn't see anything about a CLA, but I still need to
> confirm.
>
> Additionally I'm curious about the contribution process in general. Do
> you prefer pull requests via GitHub, or a discussion of the proposed
> feature (and patch?) on the list? I'm expecting that the enhancement
> might need some work to fit within the framework properly.
>
> Any insight is appreciated!
>
> Thanks,
> Jeff
No CLA needed.
If you want a wider discussion use the mailing list.
Pull requests via GitHub are possible though.
You can also mention the github PR in the poster mail of the patchset to the mailing list.
prev parent reply other threads:[~2016-10-26 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 17:12 Contribution Question Jeff Elsloo
[not found] ` <CABjXaGv8B9eK5ucw6H436oAWTNwTpB__snrCFGv1UDwnMb48yg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-26 7:27 ` Harald Hoyer [this message]
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=dfc7de1a-eb91-2c56-8afc-871e9d1951fa@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jeff.elsloo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).