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.
signature.asc
Description: PGP signature
