TT, Polling people at the time you want to make use of their work is a hassle to all concerned. My point is if they have a licence in their work and its permissive that is effectively them saying "OK to use my work". Smaller methods and macros without such licence should be considered available in my perspective because one can assume that the work is following tiddlywikis open source standard. Any more complex solutions without a licence should perhaps direct a question to the author and also asking them to document the licence. This is all as long as you acknowledge and do not pass off someone else's work as your own especially if it were for profit.
I remain open to other views. Regards Tony On Tuesday, December 31, 2019 at 2:47:30 AM UTC+11, TiddlyTweeter wrote: > > 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/7ecb3771-0f58-450b-8601-2c51d134ec88%40googlegroups.com.
