Sun May 26 22:51:50 2024
EVENTS
 FREE
SOFTWARE
INSTITUTE

POLITICS
JOBS
MEMBERS'
CORNER

MAILING
LIST

NYLXS Mailing Lists and Archives
NYLXS Members have a lot to say and share but we don't keep many secrets. Join the Hangout Mailing List and say your peice.

DATE 2018-11-01

HANGOUT

2024-05-26 | 2024-04-26 | 2024-03-26 | 2024-02-26 | 2024-01-26 | 2023-12-26 | 2023-11-26 | 2023-10-26 | 2023-09-26 | 2023-08-26 | 2023-07-26 | 2023-06-26 | 2023-05-26 | 2023-04-26 | 2023-03-26 | 2023-02-26 | 2023-01-26 | 2022-12-26 | 2022-11-26 | 2022-10-26 | 2022-09-26 | 2022-08-26 | 2022-07-26 | 2022-06-26 | 2022-05-26 | 2022-04-26 | 2022-03-26 | 2022-02-26 | 2022-01-26 | 2021-12-26 | 2021-11-26 | 2021-10-26 | 2021-09-26 | 2021-08-26 | 2021-07-26 | 2021-06-26 | 2021-05-26 | 2021-04-26 | 2021-03-26 | 2021-02-26 | 2021-01-26 | 2020-12-26 | 2020-11-26 | 2020-10-26 | 2020-09-26 | 2020-08-26 | 2020-07-26 | 2020-06-26 | 2020-05-26 | 2020-04-26 | 2020-03-26 | 2020-02-26 | 2020-01-26 | 2019-12-26 | 2019-11-26 | 2019-10-26 | 2019-09-26 | 2019-08-26 | 2019-07-26 | 2019-06-26 | 2019-05-26 | 2019-04-26 | 2019-03-26 | 2019-02-26 | 2019-01-26 | 2018-12-26 | 2018-11-26 | 2018-10-26 | 2018-09-26 | 2018-08-26 | 2018-07-26 | 2018-06-26 | 2018-05-26 | 2018-04-26 | 2018-03-26 | 2018-02-26 | 2018-01-26 | 2017-12-26 | 2017-11-26 | 2017-10-26 | 2017-09-26 | 2017-08-26 | 2017-07-26 | 2017-06-26 | 2017-05-26 | 2017-04-26 | 2017-03-26 | 2017-02-26 | 2017-01-26 | 2016-12-26 | 2016-11-26 | 2016-10-26 | 2016-09-26 | 2016-08-26 | 2016-07-26 | 2016-06-26 | 2016-05-26 | 2016-04-26 | 2016-03-26 | 2016-02-26 | 2016-01-26 | 2015-12-26 | 2015-11-26 | 2015-10-26 | 2015-09-26 | 2015-08-26 | 2015-07-26 | 2015-06-26 | 2015-05-26 | 2015-04-26 | 2015-03-26 | 2015-02-26 | 2015-01-26 | 2014-12-26 | 2014-11-26 | 2014-10-26 | 2014-09-26 | 2014-08-26 | 2014-07-26 | 2014-06-26 | 2014-05-26 | 2014-04-26 | 2014-03-26 | 2014-02-26 | 2014-01-26 | 2013-12-26 | 2013-11-26 | 2013-10-26 | 2013-09-26 | 2013-08-26 | 2013-07-26 | 2013-06-26 | 2013-05-26 | 2013-04-26 | 2013-03-26 | 2013-02-26 | 2013-01-26 | 2012-12-26 | 2012-11-26 | 2012-10-26 | 2012-09-26 | 2012-08-26 | 2012-07-26 | 2012-06-26 | 2012-05-26 | 2012-04-26 | 2012-03-26 | 2012-02-26 | 2012-01-26 | 2011-12-26 | 2011-11-26 | 2011-10-26 | 2011-09-26 | 2011-08-26 | 2011-07-26 | 2011-06-26 | 2011-05-26 | 2011-04-26 | 2011-03-26 | 2011-02-26 | 2011-01-26 | 2010-12-26 | 2010-11-26 | 2010-10-26 | 2010-09-26 | 2010-08-26 | 2010-07-26 | 2010-06-26 | 2010-05-26 | 2010-04-26 | 2010-03-26 | 2010-02-26 | 2010-01-26 | 2009-12-26 | 2009-11-26 | 2009-10-26 | 2009-09-26 | 2009-08-26 | 2009-07-26 | 2009-06-26 | 2009-05-26 | 2009-04-26 | 2009-03-26 | 2009-02-26 | 2009-01-26 | 2008-12-26 | 2008-11-26 | 2008-10-26 | 2008-09-26 | 2008-08-26 | 2008-07-26 | 2008-06-26 | 2008-05-26 | 2008-04-26 | 2008-03-26 | 2008-02-26 | 2008-01-26 | 2007-12-26 | 2007-11-26 | 2007-10-26 | 2007-09-26 | 2007-08-26 | 2007-07-26 | 2007-06-26 | 2007-05-26 | 2007-04-26 | 2007-03-26 | 2007-02-26 | 2007-01-26 | 2006-12-26 | 2006-11-26 | 2006-10-26 | 2006-09-26 | 2006-08-26 | 2006-07-26 | 2006-06-26 | 2006-05-26 | 2006-04-26 | 2006-03-26 | 2006-02-26 | 2006-01-26 | 2005-12-26 | 2005-11-26 | 2005-10-26 | 2005-09-26 | 2005-08-26 | 2005-07-26 | 2005-06-26 | 2005-05-26 | 2005-04-26 | 2005-03-26 | 2005-02-26 | 2005-01-26 | 2004-12-26 | 2004-11-26 | 2004-10-26 | 2004-09-26 | 2004-08-26 | 2004-07-26 | 2004-06-26 | 2004-05-26 | 2004-04-26 | 2004-03-26 | 2004-02-26 | 2004-01-26 | 2003-12-26 | 2003-11-26 | 2003-10-26 | 2003-09-26 | 2003-08-26 | 2003-07-26 | 2003-06-26 | 2003-05-26 | 2003-04-26 | 2003-03-26 | 2003-02-26 | 2003-01-26 | 2002-12-26 | 2002-11-26 | 2002-10-26 | 2002-09-26 | 2002-08-26 | 2002-07-26 | 2002-06-26 | 2002-05-26 | 2002-04-26 | 2002-03-26 | 2002-02-26 | 2002-01-26 | 2001-12-26 | 2001-11-26 | 2001-10-26 | 2001-09-26 | 2001-08-26 | 2001-07-26 | 2001-06-26 | 2001-05-26 | 2001-04-26 | 2001-03-26 | 2001-02-26 | 2001-01-26 | 2000-12-26 | 2000-11-26 | 2000-10-26 | 2000-09-26 | 2000-08-26 | 2000-07-26 | 2000-06-26 | 2000-05-26 | 2000-04-26 | 2000-03-26 | 2000-02-26 | 2000-01-26 | 1999-12-26

Key: Value:

Key: Value:

MESSAGE
DATE 2018-11-08
FROM From: "Donald Robertson, III, FSF"
SUBJECT Subject: [Hangout - NYLXS] Recent licensing updates
From hangout-bounces-at-nylxs.com Thu Nov 8 21:18:08 2018
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id 5344A16113A;
Thu, 8 Nov 2018 21:18:06 -0500 (EST)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id D6FA5161134; Thu, 8 Nov 2018 21:18:01 -0500 (EST)
Resent-From: Ruben Safir
Resent-Date: Thu, 8 Nov 2018 21:18:01 -0500
Resent-Message-ID: <20181109021801.GA20078-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from eggs.gnu.org (eggs.gnu.org [208.118.235.92])
by mrbrklyn.com (Postfix) with ESMTP id 393C5161132
for ; Thu, 8 Nov 2018 17:04:35 -0500 (EST)
Received: from crmserver2p.fsf.org ([208.118.235.223]:59284)
by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
(Exim 4.71)
(envelope-from )
id 1gKsPT-0002kO-O6
for ruben-at-mrbrklyn.com; Thu, 08 Nov 2018 17:04:26 -0500
Received: from localhost ([127.0.0.1] helo=my.fsf.org)
by crmserver2p.fsf.org with esmtp (Exim 4.86_2)
(envelope-from )
id 1gKsPS-00040l-Gl
for ruben-at-mrbrklyn.com; Thu, 08 Nov 2018 17:04:19 -0500
MIME-Version: 1.0
From: "Donald Robertson, III, FSF"
job_id: 157651
To: Ruben Safir
Precedence: bulk
X-CiviMail-Bounce: crmmailer+b.157651.38293026.59e4e2ab4839e927-at-fsf.org
Date: Thu, 08 Nov 2018 17:04:18 -0500
Message-Id:
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
Subject: [Hangout - NYLXS] Recent licensing updates
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.17
Reply-To: "Donald Robertson, III, FSF"
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,

List-Post:
List-Help:
List-Subscribe: ,

Content-Type: multipart/mixed; boundary="===============1441279329=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"

--===============1441279329==
Content-Type: multipart/alternative;
boundary="=_276482f677d5835a0635178a01efe841"

--=_276482f677d5835a0635178a01efe841
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read and share online: *


Dear Ruben Safir,

We recently published a number of updates to our licensing
materials. While we generally post individual announcements for these
types of important changes, there were so many in such a short span
that we needed to combine them all in one place. We recently added two
licenses to our list of [Various Licenses and Comments about Them][0],
updated our article on [License Compatibility and Relicensing][1], and
added a new entry to the [Frequently Asked Questions about the GNU
Licenses][2]. What follows is a brief rundown on those changes, and
how you can learn more about free software licensing.

[0]: https://www.gnu.org/licenses/license-list.html
[1]: http://www.gnu.org/licenses/license-compatibility.html
[2]: https://www.gnu.org/licenses/gpl-faq.html

# Commons Clause

We added the [Commons Clause][3] to our list of nonfree licenses. Not
a stand-alone license in and of itself, it is meant to be added to an
existing free license to prevent using the work commercially,
rendering the work nonfree. It's particularly nasty given that the
name, and the fact that it is attached to pre-existing free licenses,
may make it seem as if the work is still free software.

[3]: https://www.gnu.org/licenses/license-list.html#comclause

If a previously existing project that was under a free license adds
the Commons Clause, users should work to fork that program and
continue using it under the free license. If it isn't worth forking,
users should simply avoid the package. We are glad to see that in the
case of Redis modules using the Commons Clause, people are [stepping
up to maintain free versions][4].

[4]: https://goodformcode.com/

# The Fraunhofer FDK AAC license

We recently added the [Fraunhofer FDK AAC][5] license to our list of
licenses. This is a free license, incompatible with any version of the
GNU General Public License (GNU GPL), but also contains a potential
trap. While Fraunhofer provides a copyright license here, they
explicitly decline to grant any patent license. In fact, they direct
users to contact them to obtain a patent license. Users should act
with caution in determining whether they feel comfortable using works
under this license.

[5]: https://www.gnu.org/licenses/license-list.html#fdk

# License Compatibility

In September we added a new section to our article on [License
Compatibility and Relicensing][1], addressing combinations of
code. This new section helps you to simplify the picture when dealing
with a project that combines code under multiple compatible
licenses. If complying with one license necessarily means compliance
with the other, then you can reduce the question of complying with
both in the following manner:

"[Y]ou start with a list of all the pertinent licenses. Then you can
delete from the list any license which is subsumed by another in the
list.

"We say that license A subsumes license B when compliance with license
A implies compliance with license B."

The updated section then goes on to list various examples of this in
action. The list may be expanded in the future to cover more cases.

# Translated Code

Finally, there is a new addition to our Frequently Asked Questions
about the GNU Licenses, with an entry explaining [what the GNU GPL
says about translating code into another programming language][6]. In
short, since copyright law treats a translation as a modified version
of a work, translating a program into another programming language has
the same consequences as creating a modified version.

[6]: https://www.gnu.org/licenses/gpl-faq.html#TranslateCode

# How to learn more

These updates touch upon quite a few different resources that we make
available, but that's only the start of the materials we provide that
can help you to understand free software licensing. For an overview of
the resources available, visit us at ,
or if you have questions, you can ask the Compliance Lab directly by
emailing . The Compliance Lab is our resource on
free software licensing, providing materials and expertise to free
software users and developers everywhere. Please help us keep this
vital program going strong: help more users keep informed by asking
them to sign up for the [Free Software Supporter][7].

[7]: https://www.fsf.org/fss

Sincerely,

Donald Robertson
Licensing & Compliance Manager
--
* Follow us on GNU social at , on Diaspora at , and on Twitter at .
* Read about why we use Twitter, but only with caveats at .
* Subscribe to our RSS feeds at .
* Join us as an associate member at .
* Read our Privacy Policy at .

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=157651&qid=38293026&h=59e4e2ab4839e927.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=157651&qid=38293026&h=59e4e2ab4839e927.
--=_276482f677d5835a0635178a01efe841
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







Read and share online: https://www.fsf.org/blogs/licensing/recent-licensing-updates





Dear Ruben Safir,



We recently published a number of updates to our licensing
materials. While we generally post individual announcements for these
types of important changes, there were so many in such a short span
that we needed to combine them all in one place. We recently added two
licenses to our list of Various Licenses and Comments about Them,
updated our article on License Compatibility and Relicensing, and
added a new entry to the Frequently Asked Questions about the GNU
Licenses
. What follows is a brief rundown on those changes, and
how you can learn more about free software licensing.



Commons Clause



We added the Commons Clause to our list of nonfree licenses. Not
a stand-alone license in and of itself, it is meant to be added to an
existing free license to prevent using the work commercially,
rendering the work nonfree. It's particularly nasty given that the
name, and the fact that it is attached to pre-existing free licenses,
may make it seem as if the work is still free software.



If a previously existing project that was under a free license adds
the Commons Clause, users should work to fork that program and
continue using it under the free license. If it isn't worth forking,
users should simply avoid the package. We are glad to see that in the
case of Redis modules using the Commons Clause, people are stepping
up to maintain free versions
.



The Fraunhofer FDK AAC license



We recently added the Fraunhofer FDK AAC license to our list of
licenses. This is a free license, incompatible with any version of the
GNU General Public License (GNU GPL), but also contains a potential
trap. While Fraunhofer provides a copyright license here, they
explicitly decline to grant any patent license. In fact, they direct
users to contact them to obtain a patent license. Users should act
with caution in determining whether they feel comfortable using works
under this license.



License Compatibility



In September we added a new section to our article on License
Compatibility and Relicensing
, addressing combinations of
code. This new section helps you to simplify the picture when dealing
with a project that combines code under multiple compatible
licenses. If complying with one license necessarily means compliance
with the other, then you can reduce the question of complying with
both in the following manner:



"[Y]ou start with a list of all the pertinent licenses. Then you can
delete from the list any license which is subsumed by another in the
list.



"We say that license A subsumes license B when compliance with license
A implies compliance with license B."



The updated section then goes on to list various examples of this in
action. The list may be expanded in the future to cover more cases.



Translated Code



Finally, there is a new addition to our Frequently Asked Questions
about the GNU Licenses, with an entry explaining what the GNU GPL
says about translating code into another programming language
. In
short, since copyright law treats a translation as a modified version
of a work, translating a program into another programming language has
the same consequences as creating a modified version.



How to learn more



These updates touch upon quite a few different resources that we make
available, but that's only the start of the materials we provide that
can help you to understand free software licensing. For an overview of
the resources available, visit us at https://www.fsf.org/licensing,
or if you have questions, you can ask the Compliance Lab directly by
emailing licensing@fsf.org. The Compliance Lab is our resource on
free software licensing, providing materials and expertise to free
software users and developers everywhere. Please help us keep this
vital program going strong: help more users keep informed by asking
them to sign up for the Free Software Supporter.



Sincerely,



Donald Robertson
Licensing & Compliance Manager






--=_276482f677d5835a0635178a01efe841--

--===============1441279329==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1441279329==--

--===============1441279329==
Content-Type: multipart/alternative;
boundary="=_276482f677d5835a0635178a01efe841"

--=_276482f677d5835a0635178a01efe841
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=utf-8

*Read and share online: *


Dear Ruben Safir,

We recently published a number of updates to our licensing
materials. While we generally post individual announcements for these
types of important changes, there were so many in such a short span
that we needed to combine them all in one place. We recently added two
licenses to our list of [Various Licenses and Comments about Them][0],
updated our article on [License Compatibility and Relicensing][1], and
added a new entry to the [Frequently Asked Questions about the GNU
Licenses][2]. What follows is a brief rundown on those changes, and
how you can learn more about free software licensing.

[0]: https://www.gnu.org/licenses/license-list.html
[1]: http://www.gnu.org/licenses/license-compatibility.html
[2]: https://www.gnu.org/licenses/gpl-faq.html

# Commons Clause

We added the [Commons Clause][3] to our list of nonfree licenses. Not
a stand-alone license in and of itself, it is meant to be added to an
existing free license to prevent using the work commercially,
rendering the work nonfree. It's particularly nasty given that the
name, and the fact that it is attached to pre-existing free licenses,
may make it seem as if the work is still free software.

[3]: https://www.gnu.org/licenses/license-list.html#comclause

If a previously existing project that was under a free license adds
the Commons Clause, users should work to fork that program and
continue using it under the free license. If it isn't worth forking,
users should simply avoid the package. We are glad to see that in the
case of Redis modules using the Commons Clause, people are [stepping
up to maintain free versions][4].

[4]: https://goodformcode.com/

# The Fraunhofer FDK AAC license

We recently added the [Fraunhofer FDK AAC][5] license to our list of
licenses. This is a free license, incompatible with any version of the
GNU General Public License (GNU GPL), but also contains a potential
trap. While Fraunhofer provides a copyright license here, they
explicitly decline to grant any patent license. In fact, they direct
users to contact them to obtain a patent license. Users should act
with caution in determining whether they feel comfortable using works
under this license.

[5]: https://www.gnu.org/licenses/license-list.html#fdk

# License Compatibility

In September we added a new section to our article on [License
Compatibility and Relicensing][1], addressing combinations of
code. This new section helps you to simplify the picture when dealing
with a project that combines code under multiple compatible
licenses. If complying with one license necessarily means compliance
with the other, then you can reduce the question of complying with
both in the following manner:

"[Y]ou start with a list of all the pertinent licenses. Then you can
delete from the list any license which is subsumed by another in the
list.

"We say that license A subsumes license B when compliance with license
A implies compliance with license B."

The updated section then goes on to list various examples of this in
action. The list may be expanded in the future to cover more cases.

# Translated Code

Finally, there is a new addition to our Frequently Asked Questions
about the GNU Licenses, with an entry explaining [what the GNU GPL
says about translating code into another programming language][6]. In
short, since copyright law treats a translation as a modified version
of a work, translating a program into another programming language has
the same consequences as creating a modified version.

[6]: https://www.gnu.org/licenses/gpl-faq.html#TranslateCode

# How to learn more

These updates touch upon quite a few different resources that we make
available, but that's only the start of the materials we provide that
can help you to understand free software licensing. For an overview of
the resources available, visit us at ,
or if you have questions, you can ask the Compliance Lab directly by
emailing . The Compliance Lab is our resource on
free software licensing, providing materials and expertise to free
software users and developers everywhere. Please help us keep this
vital program going strong: help more users keep informed by asking
them to sign up for the [Free Software Supporter][7].

[7]: https://www.fsf.org/fss

Sincerely,

Donald Robertson
Licensing & Compliance Manager
--
* Follow us on GNU social at , on Diaspora at , and on Twitter at .
* Read about why we use Twitter, but only with caveats at .
* Subscribe to our RSS feeds at .
* Join us as an associate member at .
* Read our Privacy Policy at .

Sent from the Free Software Foundation,

51 Franklin St, Fifth Floor
Boston, Massachusetts 02110-1335
United States


You can unsubscribe from this mailing list by visiting

https://my.fsf.org/civicrm/mailing/unsubscribe?reset=1&jid=157651&qid=38293026&h=59e4e2ab4839e927.

To stop all email from the Free Software Foundation, including Defective by Design,
and the Free Software Supporter newsletter, visit

https://my.fsf.org/civicrm/mailing/optout?reset=1&jid=157651&qid=38293026&h=59e4e2ab4839e927.
--=_276482f677d5835a0635178a01efe841
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

































Free Software Foundation







Read and share online: https://www.fsf.org/blogs/licensing/recent-licensing-updates





Dear Ruben Safir,



We recently published a number of updates to our licensing
materials. While we generally post individual announcements for these
types of important changes, there were so many in such a short span
that we needed to combine them all in one place. We recently added two
licenses to our list of Various Licenses and Comments about Them,
updated our article on License Compatibility and Relicensing, and
added a new entry to the Frequently Asked Questions about the GNU
Licenses
. What follows is a brief rundown on those changes, and
how you can learn more about free software licensing.



Commons Clause



We added the Commons Clause to our list of nonfree licenses. Not
a stand-alone license in and of itself, it is meant to be added to an
existing free license to prevent using the work commercially,
rendering the work nonfree. It's particularly nasty given that the
name, and the fact that it is attached to pre-existing free licenses,
may make it seem as if the work is still free software.



If a previously existing project that was under a free license adds
the Commons Clause, users should work to fork that program and
continue using it under the free license. If it isn't worth forking,
users should simply avoid the package. We are glad to see that in the
case of Redis modules using the Commons Clause, people are stepping
up to maintain free versions
.



The Fraunhofer FDK AAC license



We recently added the Fraunhofer FDK AAC license to our list of
licenses. This is a free license, incompatible with any version of the
GNU General Public License (GNU GPL), but also contains a potential
trap. While Fraunhofer provides a copyright license here, they
explicitly decline to grant any patent license. In fact, they direct
users to contact them to obtain a patent license. Users should act
with caution in determining whether they feel comfortable using works
under this license.



License Compatibility



In September we added a new section to our article on License
Compatibility and Relicensing
, addressing combinations of
code. This new section helps you to simplify the picture when dealing
with a project that combines code under multiple compatible
licenses. If complying with one license necessarily means compliance
with the other, then you can reduce the question of complying with
both in the following manner:



"[Y]ou start with a list of all the pertinent licenses. Then you can
delete from the list any license which is subsumed by another in the
list.



"We say that license A subsumes license B when compliance with license
A implies compliance with license B."



The updated section then goes on to list various examples of this in
action. The list may be expanded in the future to cover more cases.



Translated Code



Finally, there is a new addition to our Frequently Asked Questions
about the GNU Licenses, with an entry explaining what the GNU GPL
says about translating code into another programming language
. In
short, since copyright law treats a translation as a modified version
of a work, translating a program into another programming language has
the same consequences as creating a modified version.



How to learn more



These updates touch upon quite a few different resources that we make
available, but that's only the start of the materials we provide that
can help you to understand free software licensing. For an overview of
the resources available, visit us at https://www.fsf.org/licensing,
or if you have questions, you can ask the Compliance Lab directly by
emailing licensing@fsf.org. The Compliance Lab is our resource on
free software licensing, providing materials and expertise to free
software users and developers everywhere. Please help us keep this
vital program going strong: help more users keep informed by asking
them to sign up for the Free Software Supporter.



Sincerely,



Donald Robertson
Licensing & Compliance Manager






--=_276482f677d5835a0635178a01efe841--

--===============1441279329==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout

--===============1441279329==--

  1. 2018-11-02 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] FWIW
  2. 2018-11-02 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter Issue 127, November 2018
  3. 2018-11-01 Hadar Shochat <hadar-at-mindu.co.il> Subject: [Hangout - NYLXS] Visibility Engineer (can#72318)
  4. 2018-11-02 From: "Free Software Foundation" <info-at-fsf.org> Subject: [Hangout - NYLXS] Free Software Supporter Issue 127, November 2018
  5. 2018-11-01 Moishe Bane <alerts-at-ounetwork.org> Subject: [Hangout - NYLXS] On Pittsburgh - Message from the President of the
  6. 2018-11-01 From: "IEEE Spectrum Tech Alert" <reply-at-media.ieee.org> Subject: [Hangout - NYLXS] Roboticist Rodney Brooks' Rules of Thumb for
  7. 2018-11-05 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] OReilly on humblebundle
  8. 2018-11-06 From: "Molly de Blanc" <info-at-fsf.org> Subject: [Hangout - NYLXS] LibrePlanet Call for Sessions to close THIS FRIDAY
  9. 2018-11-06 From: "IEEE The Institute Alert" <reply-at-media.ieee.org> Subject: [Hangout - NYLXS] Would You Quit a Tech Project Over Ethical
  10. 2018-11-05 From: "American Museum of Natural History" <GilderCenter-at-amnh.org> Subject: [Hangout - NYLXS] Gilder Center Project Update
  11. 2018-11-04 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #380 - What after Hacktoberfest?
  12. 2018-11-07 Ruben Safir <ruben.safir-at-my.liu.edu> Subject: [Hangout - NYLXS] Fwd: Tuesday: Join us at "NYLUG Open Hacker Hours"
  13. 2018-11-08 Naomi for Congress <naomi-at-naomiforcongress.com> Subject: [Hangout - NYLXS] Thank You
  14. 2018-11-07 James E Keenan <jkeenan-at-pobox.com> Subject: [Hangout - NYLXS] Nov 07 NYCBUG/NY.PM tech meeting: slides
  15. 2018-11-08 From: "Donald Robertson, III, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Recent licensing updates
  16. 2018-11-08 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Bash and Biocomputations
  17. 2018-11-11 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] complex
  18. 2018-11-11 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] How to hate and do it well
  19. 2018-11-12 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #381 - What is the name of my Perl?
  20. 2018-11-12 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #381 - What is the name of my Perl?
  21. 2018-11-13 The Billie Holiday Theatre <info-at-thebillieholiday.org> Subject: [Hangout - NYLXS] Last Chance, ruben - See DOT
  22. 2018-11-16 From: "Ruben.Safir" <ruben.safir-at-my.liu.edu> Subject: [Hangout - NYLXS] Fwd: Absolute copy number analysis from
  23. 2018-11-16 From: "Mancini, Sabin (DFS)" <Sabin.Mancini-at-dfs.ny.gov> Re: [Hangout - NYLXS] Fwd: Tuesday: Join us at "NYLUG Open Hacker
  24. 2018-11-18 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Fwd: Tuesday: Join us at "NYLUG Open Hacker
  25. 2018-11-18 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] my brain hurts
  26. 2018-11-19 Gabor Szabo <gabor-at-szabgab.com> Subject: [Hangout - NYLXS] [Perlweekly] #382 - London Perl Workshop 2018
  27. 2018-11-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] [mothur] mothur v1.41.0
  28. 2018-11-20 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Jewish Europe
  29. 2018-11-21 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Sex Slaves and women in captivity
  30. 2018-11-21 Ruben Safir <ruben-at-mrbrklyn.com> Re: [Hangout - NYLXS] Sex Slaves and women in captivity
  31. 2018-11-22 mrbrklyn <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] Fwd: Tuesday: Join us at "Next Generation
  32. 2018-11-24 Ron Guerin <ron-at-vnetworx.net> Re: [Hangout - NYLXS] Fwd: Tuesday: Join us at "NYLUG Open Hacker
  33. 2018-11-24 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: Give the gift of freedom this year!
  34. 2018-11-26 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: [Perlweekly] #383 - To CGI or not to CGI?
  35. 2018-11-26 Liz Freedman Fowler <eafreedman-at-gmail.com> Subject: [Hangout - NYLXS] [dinosaur] Conference Invitation: Cretaceous &
  36. 2018-11-27 NYOUG <execdir-at-nyoug.org> Subject: [Hangout - NYLXS] Upcoming Events for Oracle Professionals
  37. 2018-11-28 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] The relentless push to destory your rights - DMCA
  38. 2018-11-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Mexico loves Jared Kusner?
  39. 2018-11-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Trump has gone to pot?
  40. 2018-11-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] One can only hope...
  41. 2018-11-28 From: "Andrew Engelbrecht, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Help the FSF tech team build the future of free
  42. 2018-11-28 From: "Andrew Engelbrecht, FSF" <info-at-fsf.org> Subject: [Hangout - NYLXS] Help the FSF tech team build the future of free
  43. 2018-11-29 Ruben Safir <ruben.safir-at-my.liu.edu> Subject: [Hangout - NYLXS] Fwd: New York Artificial Intelligence In
  44. 2018-11-29 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] UN rants
  45. 2018-11-30 From: "Ruben.Safir" <ruben.safir-at-my.liu.edu> Subject: [Hangout - NYLXS] Fwd: EMBS News and Events
  46. 2018-11-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: Help the FSF tech team build the future of
  47. 2018-11-30 Ruben Safir <mrbrklyn-at-panix.com> Subject: [Hangout - NYLXS] =?utf-8?q?Fwd=3A_Immediate_Opening_=E2=80=93_Cl?=
  48. 2018-11-30 Ruben Safir <ruben-at-mrbrklyn.com> Subject: [Hangout - NYLXS] Fwd: EMBS News and Events

NYLXS are Do'ers and the first step of Doing is Joining! Join NYLXS and make a difference in your community today!