Like the title says, for plugin devs that give stuff away/rely on a shareware model (like my “Karma-Ware” plugins)… please sync your plugins to GitHub so they are forkable. I ran into a situation today with @ZeroqodeSupport@ZeroqodeTeam 's “Search & Autocorrect” free plugin where I would have forked and made a custom version to get around this problem, but it’s not forkable so I’m not gonna bother.
This is so annoying that I went thru and made sure even my jokey-joke open source plugins are forkable this evening. I advise the rest of y’all to do this too. (I wouldn’t expect every update to be synced, but it’s good practice, so – you know – just go do it and try to remember to sync those open source plugs to GitHub when you publish an update.)
Yep, @rico.trevisan, it only syncs when you tell it to. If the Bubble side is ahead of the GitHub side, it updates GitHub. If GitHub is ahead of the Bubble side (because you’ve made changes in GitHub) it updates Bubble.
If you don’t use or understand GitHub… well, I don’t know where to point you, but play around with it.
The point is that if you’ve never synced to GitHub, nobody can fork your plugin and get a fresh copy and make changes easily.
I don’t expect zerocode to do that, but those of us that provide useful open source plugins should.
FYI: if a plugin started its life as a private plugin and you synced with Github, that repository will be marked private. I just made the Tiptap one public: https://github.com/RicoTrevisan/Tiptap-for-Bubble.
