Contributor approval for 3-clause BSD relicensing (YOUR ACTION NEEDED)

Yes, I agree to have all the code that I contributed to Avogadro relicensed to the 3-clause BSD license.

Donald

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/

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Thanks,

Marcus

On Tue, Mar 12, 2013 at 4:35 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license!

(For the sake of clarity, I’ll point out that the XtalOpt extension code is
to remain GPLv2+ unless otherwise noted in the source files – my
relicensing permission extends only to code which I have directly
contributed to the Avogadro repository.).

Dave

On Tue, Mar 12, 2013 at 4:35 PM, Marcus D. Hanwell <
mhanwell@gmail.com> wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

On Tue, Mar 12, 2013 at 9:35 PM, Marcus D. Hanwell <
mhanwell@gmail.com> wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Yes, I agree to have all the code that I contributed to Avogadro relicensed to the 3-clause BSD license.

-Geoffrey Hutchison

On Mar 12, 2013, at 4:35 PM, “Marcus D. Hanwell” mhanwell@gmail.com wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.comwrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Hi,

Thanks to everyone who responded so far. In less than a day we have
responses from (which already covers a large portion of the code
base),

Marcus D. Hanwell
Casper Steinmann
David Lonie
Geoffrey Hutchison
Jens Thomas
Matthew Kennedy

This leaves the following people (added to CC from emails found in git
log). If they are no longer subscribed to the list we could make the
list open for a few days as Eigen did (although it opened them up to
quite a bit of spam too). The list below is crudely de-duplicated by
me and roughly sorted by number of lines changed. I have not yet
analyzed exactly what those lines were, but would certainly appreciate
responses from all contributors.

Tim Vandermeersch
Konstantin Tokarev
Donald Ephraim Curtis
Eric Brown
Michael Banck
Jogvan Magnus Olsen
Albert DeFusco
Benoit Jacob
Carsten Niehaus
James Bunt
Naomi Fox
Raimondas Galvelis
Ross Braithwaite
Jordan Mantha
Shahzad Ali
Simon Ochsenreither
Gary Kedziora
Kristof Bal
Reinis Danne
Egon Willighagen

The full email is included below, with the most important part being a
response (to the Avogadro development list),

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.

Thanks,

Marcus

On Wed, Mar 13, 2013 at 5:11 AM, Jens linucks42@gmail.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.com
wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Eric Brown

On Mar 13, 2013, at 10:42 AM, “Marcus D. Hanwell” mhanwell@gmail.com wrote:

Hi,

Thanks to everyone who responded so far. In less than a day we have
responses from (which already covers a large portion of the code
base),

Marcus D. Hanwell
Casper Steinmann
David Lonie
Geoffrey Hutchison
Jens Thomas
Matthew Kennedy

This leaves the following people (added to CC from emails found in git
log). If they are no longer subscribed to the list we could make the
list open for a few days as Eigen did (although it opened them up to
quite a bit of spam too). The list below is crudely de-duplicated by
me and roughly sorted by number of lines changed. I have not yet
analyzed exactly what those lines were, but would certainly appreciate
responses from all contributors.

Tim Vandermeersch
Konstantin Tokarev
Donald Ephraim Curtis
Eric Brown
Michael Banck
Jogvan Magnus Olsen
Albert DeFusco
Benoit Jacob
Carsten Niehaus
James Bunt
Naomi Fox
Raimondas Galvelis
Ross Braithwaite
Jordan Mantha
Shahzad Ali
Simon Ochsenreither
Gary Kedziora
Kristof Bal
Reinis Danne
Egon Willighagen

The full email is included below, with the most important part being a
response (to the Avogadro development list),

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.

Thanks,

Marcus

On Wed, Mar 13, 2013 at 5:11 AM, Jens linucks42@gmail.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.com
wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

On Wed, Mar 13, 2013 at 10:53 AM, Eric Brown eric.c.brown@mac.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Eric Brown

On Mar 13, 2013, at 10:42 AM, “Marcus D. Hanwell” <
mhanwell@gmail.com> wrote:

Hi,

Thanks to everyone who responded so far. In less than a day we have
responses from (which already covers a large portion of the code
base),

Marcus D. Hanwell
Casper Steinmann
David Lonie
Geoffrey Hutchison
Jens Thomas
Matthew Kennedy

This leaves the following people (added to CC from emails found in git
log). If they are no longer subscribed to the list we could make the
list open for a few days as Eigen did (although it opened them up to
quite a bit of spam too). The list below is crudely de-duplicated by
me and roughly sorted by number of lines changed. I have not yet
analyzed exactly what those lines were, but would certainly appreciate
responses from all contributors.

Tim Vandermeersch
Konstantin Tokarev
Donald Ephraim Curtis
Eric Brown
Michael Banck
Jogvan Magnus Olsen
Albert DeFusco
Benoit Jacob
Carsten Niehaus
James Bunt
Naomi Fox
Raimondas Galvelis
Ross Braithwaite
Jordan Mantha
Shahzad Ali
Simon Ochsenreither
Gary Kedziora
Kristof Bal
Reinis Danne
Egon Willighagen

The full email is included below, with the most important part being a
response (to the Avogadro development list),

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.

Thanks,

Marcus

On Wed, Mar 13, 2013 at 5:11 AM, Jens linucks42@gmail.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro
relicensed

to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.com
wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Albert DeFusco, Ph.D.
Research Assistant Professor
Technical Director, Center for Simulation and Modeling
University of Pittsburgh
Pittsburgh, PA 15206
412-648-3094
http://www.sam.pitt.edu

On Mar 13, 2013, at 11:42 AM, Marcus D. Hanwell wrote:

Hi,

Thanks to everyone who responded so far. In less than a day we have
responses from (which already covers a large portion of the code
base),

Marcus D. Hanwell
Casper Steinmann
David Lonie
Geoffrey Hutchison
Jens Thomas
Matthew Kennedy

This leaves the following people (added to CC from emails found in git
log). If they are no longer subscribed to the list we could make the
list open for a few days as Eigen did (although it opened them up to
quite a bit of spam too). The list below is crudely de-duplicated by
me and roughly sorted by number of lines changed. I have not yet
analyzed exactly what those lines were, but would certainly appreciate
responses from all contributors.

Tim Vandermeersch
Konstantin Tokarev
Donald Ephraim Curtis
Eric Brown
Michael Banck
Jogvan Magnus Olsen
Albert DeFusco
Benoit Jacob
Carsten Niehaus
James Bunt
Naomi Fox
Raimondas Galvelis
Ross Braithwaite
Jordan Mantha
Shahzad Ali
Simon Ochsenreither
Gary Kedziora
Kristof Bal
Reinis Danne
Egon Willighagen

The full email is included below, with the most important part being a
response (to the Avogadro development list),

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.

Thanks,

Marcus

On Wed, Mar 13, 2013 at 5:11 AM, Jens linucks42@gmail.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.com
wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Hi,

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Keep up the good work!

Thanks and bye,

Simon

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

On Thu, Mar 14, 2013 at 4:42 AM, Marcus D. Hanwell <
mhanwell@gmail.com> wrote:

Hi,

Thanks to everyone who responded so far. In less than a day we have
responses from (which already covers a large portion of the code
base),

Marcus D. Hanwell
Casper Steinmann
David Lonie
Geoffrey Hutchison
Jens Thomas
Matthew Kennedy

This leaves the following people (added to CC from emails found in git
log). If they are no longer subscribed to the list we could make the
list open for a few days as Eigen did (although it opened them up to
quite a bit of spam too). The list below is crudely de-duplicated by
me and roughly sorted by number of lines changed. I have not yet
analyzed exactly what those lines were, but would certainly appreciate
responses from all contributors.

Tim Vandermeersch
Konstantin Tokarev
Donald Ephraim Curtis
Eric Brown
Michael Banck
Jogvan Magnus Olsen
Albert DeFusco
Benoit Jacob
Carsten Niehaus
James Bunt
Naomi Fox
Raimondas Galvelis
Ross Braithwaite
Jordan Mantha
Shahzad Ali
Simon Ochsenreither
Gary Kedziora
Kristof Bal
Reinis Danne
Egon Willighagen

The full email is included below, with the most important part being a
response (to the Avogadro development list),

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.

Thanks,

Marcus

On Wed, Mar 13, 2013 at 5:11 AM, Jens linucks42@gmail.com wrote:

Yes, I agree to have all the code that I contributed to Avogadro
relicensed
to the 3-clause BSD license.

Jens

On 12 March 2013 20:35, Marcus D. Hanwell mhanwell@gmail.com
wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

On Wed, Mar 13, 2013 at 7:49 PM, Simon Ochsenreither <simon@ochsenreither.de

wrote:

Hi,

Yes, I agree to have all the code that I contributed to Avogadro

relicensed to the 3-clause BSD license.

Keep up the good work!

Thanks and bye,

Simon

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Ross

On Wed, Mar 13, 2013 at 9:35 AM, Marcus D. Hanwell <
mhanwell@gmail.com> wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

That’s fine with me.

On Wed, Mar 13, 2013 at 12:15 PM, Tim Vandermeersch <
tim.vandermeersch@gmail.com> wrote:

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

On Wed, Mar 13, 2013 at 7:49 PM, Simon Ochsenreither <
simon@ochsenreither.de> wrote:

Hi,

Yes, I agree to have all the code that I contributed to Avogadro

relicensed to the 3-clause BSD license.

Keep up the good work!

Thanks and bye,

Simon


-Naomi

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.


Regards,
Konstantin

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Ross Braithwaite

On Wed, Mar 13, 2013 at 9:35 AM, Marcus D. Hanwell <
mhanwell@gmail.com> wrote:

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/
http://www.slideshare.net/cryos/the-open-chemistry-project

You 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,

http://opensource.org/licenses/BSD-3-Clause

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
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Yes, I agree to have all the code that I contributed to Avogadro
relicensed to the 3-clause BSD license.

Hi

Yes, I agree to have all the code that I contributed to Avogadro relicensed
to the 3-clause BSD license.

Carsten NIehaus