> > On the other hand oksvg is completely de novo, so I can slap whatever > license I want on that package. I take it people here prefer the Go > license? Can anyone briefly describe the difference? I will definitely > change it if someone can give me a good reason. I just want to make it as > convenient and useful as possible for everyone.
Don’t consider golang-nuts for professional advice. Here’s my understanding: GPL requires that if the code is distributed or included in a distributed application (source or binary) then the entirety of the source code is also distributed and the license remains. “Viral” is a term associated with GPL, if you use a GPL library then your entire project must become GPL compliant. For Go you may want to consider the AGPL which also requires any network app to provide its source code. These GNU licenses are from the Free Software Foundation which has a traditionally radical philosophy toward computers: https://www.gnu.org/licenses/why-affero-gpl.en.html So far I personally like the AGPL approach. My understanding is the source inclusion is only in effect in distribution. If you give your program to a person then that doesn’t require you to post it all on GitHub, but if you have a website where anybody can download your app then you have to make the source code available to all of those people. Note that GitHub also has a default license applied to your work which allows people to fork it and view it on GitHub. I usually see the MIT, BSD, Apache licenses here. These give you permission to use the code without requiring you distribute the source code. There may be attribution requirements and usually the license says something about no warranty or support provided. If you want your library used here you’ll probably want one of these. Matt On Monday, April 23, 2018 at 7:19:59 PM UTC-5, Steven Wiley wrote: > > Thanks for the compliments, everyone. > > I will check out the vector package and further test SVG examples are > welcome. If I have isolated concepts as well as I hope I have, re-writing > the Scanner to use the vector package might not be too hard. Gradients are > also near the top of the to-do list, because they are just so darn pretty. > > As for the license part of it...(snnzz......, huh, what?) Oh yes, the > rasterx package has parts that are straight copies, and parts that are > somewhat modified from the freetype raster package, as well as parts that > are completely new. So, I think I need to stay within the terms of the > freetype license for that bit. Apparently, freetype wants derivatives to > use their license, or GPL 2.0 or higher, so I just selected the highest > GPL open on github, and also kept around a copy of their terms. > > On the other hand oksvg is completely *de novo*, so I can slap whatever > license I want on that package. I take it people here prefer the Go > license? Can anyone briefly describe the difference? I will definitely > change it if someone can give me a good reason. I just want to make it as > convenient and useful as possible for everyone. > > On Monday, April 23, 2018 at 3:42:55 PM UTC-7, Nigel Tao wrote: >> >> Nice! >> >> >> On Mon, Apr 23, 2018 at 3:41 AM, Steven Wiley <steven...@gmail.com> >> wrote: >> >>> I refactored and enhanced the raster package from the golang >>> translation of freetype, <https://github.com/golang/freetype> >>> >> >> It'd be a bunch of work, but you might consider basing off of >> golang.org/x/image/vector instead: >> >> 1. Its technique is based on "Inside the fastest font renderer in the >> world" at >> https://medium.com/@raphlinus/inside-the-fastest-font-renderer-in-the-world-75ae5270c445 >> >> although rasterizing SVG images might perform differently than rasterizing >> font glyphs. Both are vector graphics, but SVG images often have multiple, >> overlapping shapes while font glyphs are typically simpler. >> >> There's also >> https://github.com/golang/exp/blob/master/shiny/iconvg/internal/gradient/gradient.go. >> >> It's currently pretty slow, as I wanted to get the API right before >> optimizing the implementation, then haven't really had the free time to >> work on it since. But you might find it (and IconVG in general) interesting. >> >> 2. Its license is the Go license (i.e. BSD-like, >> https://github.com/golang/image/blob/master/LICENSE), not the >> Freetype-or-GPL2+ license ( >> https://github.com/golang/freetype/blob/master/LICENSE). OTOH, if you >> really want GPL3, then perhaps golang/freetype is a better foundation. >> Disclaimer: I am not a laywer, this is not legal advice, etc. >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
