Ineiev wrote: > Another thing you should get used to is to identify > the licensing conditions of programs clearly, e.g. there is no "BSD" > license, https://www.gnu.org/licenses/bsd.html; "GPL", "GPLv2" > "GPL version 2 or (at your option) any later version)" are different > licensing terms---some of them are acceptable for Savannah, other > are not https://www.gnu.org/licenses/identify-licenses-clearly.html. > Using license names from https://www.gnu.org/l/license-list.html is > highly recommended.
Thanks for the reminder. Both OpenToonz and Tahoma2D are under the 3 Clause BSD license (also known as BSD New or Revised BSD License). Nothing additional added to the license terms other than notice of third party licenses that doesn't apply to OpenToonz or Tahoma2D itself. And I'll also start to make a habit of specifying if when referring to the GPL or LGPL as a specific version. > It isn't necessary for a package to work, Savannah hosting > requirements don't contain such criterion. What we need is > an amount of data sufficient to see that the maintainer > follows our rules (in particular, that the package isn't > simplistic, that it has no nonfree dependencies, and so on). Thanks also for this. If by simplistic you mean trivial, no its that. Regardless if I go with C or C++ (Because I'm not entirely sure if its necessary to go that low level. I can achieve a lot of GLSL shaders + already existing nodes), it will be a very useful program that can't be on par with hello world. OpenToonz is also packaged up for fedora and arch distros, so that removes any concern it may have a non free component or requirement with it or at least something easy to run into. > Hope that helps. It certainly did. I'll give things a matter of time to decide if I do decide to submit to savannah after all. Thank you. ________________________________________ From: savannah-users-bounces+loonecanne=outlook....@gnu.org on behalf of Ineiev Sent: Tuesday, October 8, 2024 10:03 PM To: Matthew Polk Cc: savannah-users@gnu.org Subject: Re: How complete of a prototype do I require before submitting to savannah? On Tue, Oct 08, 2024 at 05:18:27PM +0000, Matthew Polk wrote: > I'm not entirely sure how to word this, because I don't want to > jump the gun or get too far ahead of myself on an idea I've got. I > want to toy with experimenting with plugins for opentoonz (A BSD > licensed animation program used by ghibli heavily) and its slight > fork (Just more frequent releases and some newer features) called > Tahoma2D. I know open isn't allowed on savannah as stated in the > rules, so I will not call the plugin project open* unless I'm > referring to the parent program. I'm glad you've carefully read Savannah documentation on its hosting requirements. Another thing you should get used to is to identify the licensing conditions of programs clearly, e.g. there is no "BSD" license, https://www.gnu.org/licenses/bsd.html; "GPL", "GPLv2" "GPL version 2 or (at your option) any later version)" are different licensing terms---some of them are acceptable for Savannah, other are not https://www.gnu.org/licenses/identify-licenses-clearly.html. Using license names from https://www.gnu.org/l/license-list.html is highly recommended. > How plugins work is that you can make plugins most notably in two > different ways. One is GLSL shaders with OpenGL and the other is > in C or C++ (Despite being a C++ program, it was designed to allow > for C usage) so I thought (Just pondering over, seeing what works > and what doesn't) with gobject + libvips. The question is: How > much do I have to have completed before I can submit it for > review? 2-3 plugins showing it works? It isn't necessary for a package to work, Savannah hosting requirements don't contain such criterion. What we need is an amount of data sufficient to see that the maintainer follows our rules (in particular, that the package isn't simplistic, that it has no nonfree dependencies, and so on). Hope that helps.
