4 ms·

? why did you put it on github then? Are you sure you're not proud instead? :)

• the_mitsuhiko 14y ago
  > why did you put it on github then? For other people to learn, as an example of how to use rstblog, easy way to contribute fixes for typos and my horrible grammar. Also the actual texts after publishing are creative commons licensed (which however is not an open source license). It comes with strings attached. > Are you sure you're not proud instead? :) I am proud that people like it to the extend that they reuse it. I am proud and happy that people generally seem to like what I am doing. However I have an internal conflict with myself how much of that open source spirit applies to visual design, trademarks, logos and more. I spend a lot of time to figure something out for the Flask project and the styles that go with Flask and extensions. There I have them under a full open source license with the added wish to the license to be a nice person and only use the style for Flask projects, however this is not binding because that would make it hard to get the project into debian.
  • lucian1900 14y ago
    The Artistic License 2.0 does try maintain creative control to some extent and is a free software license. Afaik, debian are ok with it. It's possibly too much trouble to use a comparatively obscure license.