Note that it says:kgschlosser wrote:what i can do is a search for the GNU-GPL in the header of a plugin anf if it is not found omit it from the list unless we were able to obtain written consent from the author. but from this step forward i do believe the traditional EG header is a mandate in a plugin and upon adding it to the repo if it is not there then it will kick it back. i think that the GNU actually should be located in a separate file called license.txt and a balloon statement for all files located within the contents of the .egtree file are apart of the GNU-GPLthis should be added either as a file or a comment in the compression.
so the GPL license is not required. For example, I like to use the MIT license on my code because it seems to be the more permissive license but that license is GPL-compatible so I could use that license in an EventGhost plugin without being in violation of EventGhost's license.This means you must license the plug-in under the GPL or a GPL-compatible free software license
I think it would be really nice to have all versions in the database, default to installing the most recent but allow the user to install or roll back/forwards to any available version of the plugin. Sometimes bugs are introduced in the new version and it's very useful to be able to roll back to check if using an older version will make an issue go away. As you said, future EG versions may require changes in plugins that will break backwards compatibility with previous EG versions. If the user has other unmaintained plugins installed that aren't compatible with the new EG version then they may not be able to upgrade their EG and thus can't use the new plugin versions that aren't backwards compatible.kgschlosser wrote:are we going to provide all versions of a plugin available??? or just the most up to date.. the reason why i ask this is because of the possibility of a new version of a plugin not being compatible with an older version of EG.
On a related note, there is a good discussion about adding version compatibility metadata to the plugins here: https://github.com/EventGhost/EventGhost/issues/89, which would be a very useful feature for the Plugin Manager.