search

Slevinski / signwriting_2010_tools

Tools for creating TrueType fonts for written sign language in the SignWriting script based on the ISWA 2010
MIT License
3 stars 0 forks source link

Packaging / Automated building needs #1

Open lanodan opened 6 years ago

lanodan commented 6 years ago

Hi, Gentoo ~user here, I would like to make a ebuild for SignWriting tools and fonts but as there is no archives or tags, only commits (and non-atomized ones btw) it’s making writing an ebuild less easy as I basically can’t currently use your releases (only the repository) unless I ~fork your projects to make tags+archives or host tarballs.

Also would appreciate having the license(s) the tools are under in the README or similar.

Note: This also goes to signwriting_2010_fonts, sorry but I don’t really see the separation between them other than signwriting_2010_tools to generate signwriting_2010_fonts, which I think is really bad practice as git is meant for atomised commits of code (so no binairies like .ttf) and versionized branches/tags and releases done with archiving the tags. The place where you can put binairies is in dedicated files of the releases. See https://github.com/eosrei/emojione-color-font (font) and https://github.com/eosrei/scfbuild (tool used) as a good/nice example.

Too Long; Didn’t Read / Summary

I would like this for signwriting_2010_tools and signwriting_2010_fonts:

Slevinski commented 6 years ago

Thanks for the comments and suggestions. I will take a look at the projects you referenced.

Early January 2018, I will cleanup this project for licenses in the README and add project tags and downloads.

Currently the scripts in this project are released under the GPL 2 or later, but I will be moving this project to the MIT license.

lanodan commented 6 years ago

Ok, great :D I guess I’ll have the fonts in ~/.fonts for now, if you have any questions feels free to ask anything.

Slevinski commented 6 years ago

Due to existing dependancies, the tools project and the fonts project will remain separate. I understand your point though.

The tools project is now released under the MIT license. Github is properly recognizing this.

The fonts project is released under the OFL license. Github is not recognizing this. I'm not sure why. I simplified the license and readme files, but Github still isn't auto detecting the license.

I've tagged the latest releases in both projects.

I still need to add downloads to the releases.

lanodan commented 6 years ago

Due to existing dependancies, the tools project and the fonts project will remain separate.

It’s totally fine as long as I can get the sources in archive(s) or at least tags, also I’d prefer to avoid downloading the generated fonts (which could be in the releases tab instead).

Github is properly recognizing this. Github is not recognizing this.

The README and LICENSE files works, and most packages/recipes (debian, gentoo, …) have license information in them, I think it matters more than undocumented things done by github that might change/break in the future.