Please include a license file (repo + PyPI) about codon-usage-tables HOT 8 CLOSED

I've done it now, PyPI has the latest version: https://pypi.org/project/python-codon-tables/0.1.11

from codon-usage-tables.

@veghp wanted to echo what @sugatoray is mentioning. Also, there are bots that help keep the conda-forge-distributed packages up-to-date with the PyPI releases, so the maintenance level actually drops to near-zero. In any case, I'm happy to be the maintainer of the recipe with @sugatoray, thereby keeping your inboxes free of clutter, if that's preferable to you. 😄

from codon-usage-tables.

What kind of license would it be?

cc: @veghp @Zulko

Examples:

• CC0: https://spdx.org/licenses/CC0-1.0.html
• SAX-PD: https://spdx.org/licenses/SAX-PD.html

from codon-usage-tables.

This is related to another PR: conda-forge/staged-recipes#17283

from codon-usage-tables.

@veghp and @Zulko can I ask, just as @sugatoray mentioned above, for the Public Domain license, would CC0 work? I am getting inspiration from this url.

We're eager to get SeqLike up on conda-forge, and since it depends on codon-usage-tables, we'd like to get this package up on conda-forge as well because that's a requirement for conda-forge packages (that all packages be conda installable).

from codon-usage-tables.

Hi, thanks for the interest in this package. It was released into the public domain, hence no license. This is one of the valid license specifications for PyPI, is that not suitable for conda also?

In any case I merged the license PR.

As for the package being on conda, perhaps we'd prefer it to be named something else than codon-usage-tables or python_codon_tables (perhaps with a little added note), so that it's clear we are not the maintainers of the package. Would that be suitable?

from codon-usage-tables.

Thank you, for merging the PR. "Public Domain" alone could be a little open to interpretation. So, it's safe and better to provide a license file and package that with the software.

About the package name, python-codon-tables is preferable as the source of the conda-forge package is the source you maintain at PyPI. It's understood that you may not be maintaining the conda-forge recipe and you can mention that in the readme in this repository (making it clear that it is not maintained by you).

However, given how minimal effort is necessary typically in maintaining the conda-forge package (once it is created), you could also push a PR to update the package there, and the maintainer of the conda-forge feedstock will merge it. You only have to may be change a few fields in a YAML file. That's it.

from codon-usage-tables.

@veghp Did you push the LICENSE file to PyPI as well?

from codon-usage-tables.