From: Gary Thomas <gary@mlbassoc.com>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: [Fwd: FSF Releases Fiduciary License Agreement]
Date: Mon, 12 Feb 2007 21:05:00 -0000 [thread overview]
Message-ID: <45D0D69C.1060007@mlbassoc.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
Does this have any effect on our negotiations with the FSF?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
[-- Attachment #2: FSF Releases Fiduciary License Agreement --]
[-- Type: message/rfc822, Size: 2434 bytes --]
From: SlashZot <dj@delorie.com>
To: slashzot@delorie.com
Subject: FSF Releases Fiduciary License Agreement
Date: Mon, 12 Feb 2007 16:00:08 -0500
Message-ID: <200702122100.l1CL08oU006438@delorie.com>
FSF Releases Fiduciary License Agreement
[1]lisah writes "FSF Europe announced this week that it has released
its [2]Fiduciary License Agreement (FLA), which is being touted as an
'assignment of copyright.' The goal of the FLA is to allow free
software projects to place their copyright under the control of a
single group or trustee, though its usefulness is being debated
throughout the open source community since it only address the
authorship rights of a project, not the more intangible moral rights.
Furthermore, the agreement seems to have been created without the
involvement of a lot of lawyers and some members of the community
worry that the FLA might have unintended consequences if adopted
without sound legal advice."
Linux.com and Slashdot are both owned by OSTG.
References
<URL:http://slashdot.org/article.pl?sid=07/02/12/1944203>
[1] <REF:mailto:lisahoover@gmail.com>
[2] <REF:http://enterprise.linux.com/article.pl?sid=07/02/09/1735247&from=rss>
This is an automated posting to slashzot@delorie.com
See http://www.delorie.com/listserv/ to be removed.
reply other threads:[~2007-02-12 21:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45D0D69C.1060007@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@ecos.sourceware.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).