Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.
Reinis
On Tue, Mar 12, 2013 at 9:35 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
To that end, we would like to know which of our Avogadro contributors
agree to relicensing their contributions under the 3-clause BSD
license, linked below,The 3-Clause BSD License – Open Source Initiative
If you contributed code to Avogadro, please reply to this email with
either one of the following statements (adapted from the Eigen
relicensing effort led by Benoit),
Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.
Egon
–
Dr E.L. Willighagen
Postdoctoral Researcher
Department of Bioinformatics - BiGCaT
Maastricht University (http://www.bigcat.unimaas.nl/)
Homepage: http://egonw.github.com/
LinkedIn: http://se.linkedin.com/in/egonw
Blog: http://chem-bla-ics.blogspot.com/
PubList: http://www.citeulike.org/user/egonw/tag/papers
Dear Avogadro developers,
Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.
Also, I would suggest moving to Eigen 3 if you haven’t already: it is now
MPL2-licenced, which is closer to the 3-clause BSD license than Eigen2’s
licensing options are.
Cheers,
Benoit
2013/3/12 Marcus D. Hanwell mhanwell@gmail.com
Hi,
We have talked about this offline, and at times on the list. As many
of you already know we are working on a rewrite of Avogadro, and we
are preparing to make an initial alpha release. It features many great
new features, but does not yet have feature parity with Avogadro 1.x.
Avogadro 2 is a rewrite and re-architecture of Avogadro using a
simpler, more liberal 3-clause BSD license. A lot of the API has
changed, and we invite community participation. For some background to
the project please see,http://wiki.openchemistry.org/
The Open Chemistry Project | PPTYou can see the latest version make use of obabel command line tools
for file translation, geometry optimization, and other pieces using a
qprocess to manage execution. We are also looking at using this
approach to run Python and Java in a more loosely coupled form, and we
have ported most of the input generators to use a much simpler
scripting framework where the addition of scripts can add new
generators to the GUI using pure Python, or other languages.To that end, we would like to know which of our Avogadro contributors
agree to relicensing their contributions under the 3-clause BSD
license, linked below,The 3-Clause BSD License – Open Source Initiative
If you contributed code to Avogadro, please reply to this email with
either one of the following statements (adapted from the Eigen
relicensing effort led by Benoit),Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.or
No, I do not agree.
Anything other than the above “Yes” sentence will mean “No”. Without
your agreement we will make no attempt to port your contribution to
Avogadro 2’s code base, we would also love input from our contributors
on Avogadro 2, and have made every attempt to address many of the
shortcomings we perceived in Avogadro.Thanks,
Marcus
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options
Also, I would suggest moving to Eigen 3 if you haven’t already: it is now MPL2-licenced, which is closer to the 3-clause BSD license than Eigen2’s licensing options are.
Yes, if you’ve seen, there’s a separate thread about porting Avogadro 1 to Eigen 3, and I believe Marcus’s Avogadro v2 repository already uses Eigen 3.x.
Thanks,
-Geoff
On Mon, Mar 18, 2013 at 11:30 AM, Benoit Jacob jacob.benoit.1@gmail.com wrote:
Dear Avogadro developers,
Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.Also, I would suggest moving to Eigen 3 if you haven’t already: it is now
MPL2-licenced, which is closer to the 3-clause BSD license than Eigen2’s
licensing options are.
Thanks, you may have recognized the relicensing email text which I
modeled on your emails 
Avogadro 2 is already using Eigen 3, and
there is possibly a patch to do most of this a contributor sent to me
recently - I need to take a look at it and assess the impact of it.
Thanks,
Marcus
Thanks Marcus and Geoff for the replies.
Just FYI there is a carefully documented Eigen2->Eigen3 porting path. Even
if you already have a patch doing most of the porting, it is still worth
taking a look at, as it lists some known pitfalls.
The main page is
http://eigen.tuxfamily.org/dox/Eigen2ToEigen3.html
and the detailed careful porting path (needed for nontrivial portings) is
http://eigen.tuxfamily.org/dox/Eigen2SupportModes.html
Benoit
2013/3/18 Marcus D. Hanwell mhanwell@gmail.com
On Mon, Mar 18, 2013 at 11:30 AM, Benoit Jacob jacob.benoit.1@gmail.com
wrote:Dear Avogadro developers,
Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.Also, I would suggest moving to Eigen 3 if you haven’t already: it is now
MPL2-licenced, which is closer to the 3-clause BSD license than Eigen2’s
licensing options are.Thanks, you may have recognized the relicensing email text which I
modeled on your emails
there is possibly a patch to do most of this a contributor sent to me
recently - I need to take a look at it and assess the impact of it.Thanks,
Marcus
Hi,
Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.
Michael
On Tue, Mar 12, 2013 at 04:35:43PM -0400, Marcus D. Hanwell wrote:
We have talked about this offline, and at times on the list. As many
of you already know we are working on a rewrite of Avogadro, and we
are preparing to make an initial alpha release. It features many great
new features, but does not yet have feature parity with Avogadro 1.x.
Avogadro 2 is a rewrite and re-architecture of Avogadro using a
simpler, more liberal 3-clause BSD license. A lot of the API has
changed, and we invite community participation. For some background to
the project please see,http://wiki.openchemistry.org/
The Open Chemistry Project | PPTYou can see the latest version make use of obabel command line tools
for file translation, geometry optimization, and other pieces using a
qprocess to manage execution. We are also looking at using this
approach to run Python and Java in a more loosely coupled form, and we
have ported most of the input generators to use a much simpler
scripting framework where the addition of scripts can add new
generators to the GUI using pure Python, or other languages.To that end, we would like to know which of our Avogadro contributors
agree to relicensing their contributions under the 3-clause BSD
license, linked below,The 3-Clause BSD License – Open Source Initiative
If you contributed code to Avogadro, please reply to this email with
either one of the following statements (adapted from the Eigen
relicensing effort led by Benoit),Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.or
No, I do not agree.
Anything other than the above “Yes” sentence will mean “No”. Without
your agreement we will make no attempt to port your contribution to
Avogadro 2’s code base, we would also love input from our contributors
on Avogadro 2, and have made every attempt to address many of the
shortcomings we perceived in Avogadro.Thanks,
Marcus
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options
On Mon, Mar 18, 2013 at 11:30 AM, Benoit Jacob jacob.benoit.1@gmail.com wrote:
Also, I would suggest moving to Eigen 3 if you haven’t already: it is now
MPL2-licenced, which is closer to the 3-clause BSD license than Eigen2’s
licensing options are.
The other thing to remember, at least as far as Avogadro 1.x is
concerned, is the Open Babel 2 library which is GPLv2 only (along with
the incompatibility with GPLv3 and Apache v2 licenses). So there is no
point migrating to Eigen 3 from a licensing perspective as Open Babel
would be a far larger effort (that will likely never relicense).
I think it is important to note that the Avogadro library/application
in 1.x will likely always be GPLv2 only due to the Open Babel
dependency. This is not the case in the Avogadro 2 code base where
obabel is called as a utility executable in a separate process.
Marcus