From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] GitHub and free software
Date: Thu, 2 Mar 2017 19:28:53 +0100 [thread overview]
Message-ID: <20170302182853.GA19829@archie.localdomain> (raw)
In-Reply-To: <20170302173542.53tlp4qb4w2zbudm@pengutronix.de>
Hi,
On Thu, Mar 02, 2017 at 06:35:42PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Mar 02, 2017 at 05:17:41PM +0100, Clemens Gruber wrote:
> > But if you are interested I could send a few patches or create a GitHub
> > repo to work on it.
> INAL etc pp. I didn't even read the updated GitHub TOS, but you might
> want to read through
>
> https://www.mirbsd.org/permalinks/wlog-10_e20170301-tg.htm
>
> and then judge for yourself if you can and want to still push stuff there.
Thanks for sharing this blog post. The new ToS do indeed sound
problematic.
Hopefully the FSF will soon release a statement about this and clarify
for us non-lawyers if this is problematic for code under copyleft
licenses and if they recommend against using GitHub for free software
projects from now on.
Regards,
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-02 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 17:36 [ptxdist] ptxdist with iMX6 Guillermo Rodriguez Garcia
2017-03-01 21:03 ` Alexander Dahl
2017-03-02 14:50 ` Guillermo Rodriguez Garcia
2017-03-02 16:17 ` Clemens Gruber
2017-03-02 17:35 ` [ptxdist] GitHub and free software Uwe Kleine-König
2017-03-02 18:17 ` Guillermo Rodriguez Garcia
2017-03-02 18:19 ` Guillermo Rodriguez Garcia
2017-03-02 18:28 ` Clemens Gruber [this message]
2017-03-16 15:53 ` Clemens Gruber
2017-03-17 20:50 ` Roland Hieber
2017-03-18 6:01 ` Robert Schwebel
2017-03-02 16:31 ` [ptxdist] ptxdist with iMX6 Alexander Dahl
2017-03-08 10:34 ` Michael Olbrich
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=20170302182853.GA19829@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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