1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: AreaDetector stream encoding |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Daykin, Evan" <daykin at frib.msu.edu> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Wed, 26 May 2021 17:45:54 +0000 |
Hi Evan,
First: IANAL, TINLA (I am not a lawyer, this is not Legal Advice), but what follows is my understanding of the licensing situation here. You should discuss this with your management and/or legal department though before releasing any code.
Your link [3] points to a patent license, which operates in parallel with AOM's copyright license (BSD 2-Clause) as it allows licensees to do things with their code that the patent laws would otherwise prohibit. Some patent licenses may be incompatible
with the GPLv3, but this one certainly looks to be compatible with the EPICS Open License which Asyn uses, and should be with many other Open Source licenses too.
If you include the AOM code in anything you publish you should be sure you follow the fairly simple requirements in [3] section 1.2.1 (a), and/or possibly (b) if you distribute it in binary form. I don’t see any major problems with your doing that as long
as you do what they ask there, and don’t go removing any legal notices from their code.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|