Re: Biopython 1.69 plans - late January / early February?
Peter Cock <[email protected]> Thu, 26 Jan 2017 17:20:56 +0000
| Newsgroups | gmane.comp.python.bio.devel |
|---|---|
| Message-ID | <CAKVJ-_5UDxVhqeTousPpKsEWJj9iXb_S00Rt+ouXycYZYsfAtQ@mail.gmail.com> |
Thinking about this, I intend to merge this pull request for including in Biopython 1.69. We will need something in the NEWS file, my initial suggestion is: We have started have begun to dual-license Biopython under both our original liberal "Biopython License Agreement", and the very similar but more commonly used "3-Clause BSD License". In this release a small number of the Python files are explicitly available under either license, but most of the code remains under the "Biopython License Agreement". See the LICENSE file for more details. The release announcement will also highlight this, and should help with tracking down the remaining contributors who have yet to formally agree to dual license the contributions. Peter On Wed, Jan 25, 2017 at 2:51 PM, Peter Cock <[email protected]> wrote: > > > Is it worth starting the BSD dual licensing with this > release, i.e. merging this pull request? > > https://github.com/biopython/biopython/pull/904 > > Peter