From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] trace_clock_update() spinning
Date: Fri, 5 Feb 2010 10:57:02 -0500 [thread overview]
Message-ID: <20100205155701.GA5264@Krystal> (raw)
In-Reply-To: <20100205154810.GN12001@hansolo.jdub.homelinux.org>
* Josh Boyer (jwboyer at gmail.com) wrote:
> On Fri, Feb 05, 2010 at 10:16:13AM -0500, Mathieu Desnoyers wrote:
> >Hi Mike,
> >- Would you agree for me to integrate it in the lttng project and transfer
> > non-exclusive relicensing rights to the LTTng maintainer ? Basically, the idea
> > is to release it under dual GPLv2/LGPLv2.1 licenses, but I start to think that
> > it might be just easier to use the gdb approach for LTTng contributions, where
> > the project maintainers have the freedom to decide license changes. This way
> > we would not have to ask permission from everyone if we need to do a license
> > change for the LTTng project overall.
>
> That's called copyright assignment, and I think you might want to discuss what
> is really needed from a legal perspective with someone if you wish to go that
> route. The FSF has paperwork you have to have on-file with them for contributions.
> I would expect something similar is needed (though I am certainly not a lawyer
> and this is not legal advice).
>
> josh
Thanks for the hint. Well then maybe it's easier to just ask for GPLv2/LGPLv2.1
licensing. I am trying to find out what can be the easiest way to proceed both
for now and for the future.
Thanks,
Mathieu
next prev parent reply other threads:[~2010-02-05 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 18:52 Mike McTernan
2010-02-02 19:42 ` Mathieu Desnoyers
2010-02-02 21:12 ` Mike McTernan
2010-02-05 9:37 ` Mike McTernan
2010-02-05 15:16 ` Mathieu Desnoyers
2010-02-05 15:48 ` Josh Boyer
2010-02-05 15:57 ` Mathieu Desnoyers [this message]
2010-02-05 17:27 ` Mike McTernan
2010-02-09 0:30 ` Mathieu Desnoyers
2010-02-09 10:19 ` Mike McTernan
2010-02-09 14:42 ` Mathieu Desnoyers
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=20100205155701.GA5264@Krystal \
--to=mathieu.desnoyers@efficios.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