Ciao Tony Good points in your post. Tx.
I was more looking for* "OK to use MY work!" *from a few authors. I know that in a "LegoKit" you should acknowledge the component authors. I was looking I guess, for *enthusiasm* for the idea of more freely using other people's work. Its a an issue HERE that we don't have that many people, so I rarely can form a definitive idea. Not from lack of interest, just lack of numbers. Best wishes TT On Sunday, 29 December 2019 23:29:37 UTC+1, TonyM wrote: > > TT > > So thoughts > > Each plugin should specify its licence but typically they are so open you > can modify and redistribute. The only fair limitation is to not pass one > plugin off as someone else's with changes as this can undermine the authors > version control. Bundled plugins have typically being distributed as > editions but I see no reason not to bundle plugins perhaps in a json > bundle. I think the key is to list and acknowledge what you have used and > included if for no other reason than informing the user however I think a > key approach is to respect others work. > > If publishing a bundle modifications or additions that impact the core or > another's plugin macro should be documented so no one seeks support from > the author when its your mods breaking something. > > When bundling others work unaltered check the source is documented so > should an update be required say with a core update then people can source > the latest version. The danger of a repackage can be components age. > > Regards > Tony > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9c2edca8-1875-4e1f-a290-cb4a5e9f2a02%40googlegroups.com.
