Clarify the licence that Trogon is released under

[davep]

As pointed out over on Discord, there is no licence file in the repository, it's not made clear in the README what the licence is, and by extension the presentation of the repo here on GitHub doesn't make clear the licence.

It is indicated in the project file but nowhere else.

[chrisjsewell]

Indeed, I would like to also distribute on conda-forge, in which case a license file is required in the source distribution

[kratsg]

Indeed, I would like to also distribute on conda-forge, in which case a license file is required in the source distribution

I would also like to have it on conda-forge too. https://twitter.com/kratsg/status/1669231846700511232

[datajoely]

Any update on this :) the same MIT licence that Textualize itself uses would be perfect

[TkTech]

@davep This can be closed with the LICENSE file committed today :)

[chrisjsewell]

Cheers!

[kratsg]

Is it possible for one of the maintainers (@davep ?) to do a patch release including the LICENSE?

[davep]

I don't personally have the ability to make a release. Do note though that doing so won't change the licence status.

[kratsg]

Do note though that doing so won't change the licence status.

Oh - but I do see it listed as an MIT license. Most places, such as conda, expect the LICENSE to be packaged up in the tarball on pypi so a release should include that. Fair enough. I'll just package from the GitHub repo for now and keep an eye out for a new release in the future.