Home › Forums › Welcome! › Pre-Sales Questions › Public source control
- This topic has 5 replies, 3 voices, and was last updated 11 years, 3 months ago by
Brian.
-
AuthorPosts
-
January 7, 2015 at 2:47 am #929766
Marc
ParticipantHello,
Can’t see anything in the Terms; is it permitted to check purchased licensed plugins into public source control, e.g. Github? You’re not allowing public downloads (so far as I can see), wondering whether there’s a reason you’re restricting the availability of code before purchase — whether it’s vulnerable to be modified to work without a license key, or you’re counting downloads from your own sources, etc.
Don’t want to unintentionally breach a bought a license.
Thanks!
January 7, 2015 at 3:29 pm #930131Brian
MemberHi,
Thanks for the interest.
You can purchase the coding and modify it.
However, you are not allowed to publish the coding in the public.
Does that answer your question?
January 8, 2015 at 2:20 am #930307Marc
ParticipantGreat, thanks Brian.
Can you give me a link to the license terms where it says this so I can pass this on?
Cheers
January 8, 2015 at 10:22 am #930511Rob
MemberHi there Marc! Thanks for the note here. I wanted to follow-up with some information for you after Brian brought this thread to my attention today.
The most of what we’ve got on the documentation front regarding licenses is what you saw in the Licensing section of the terms – basically, that we release under GNU – and then this overview of what the license does and does not do: https://theeventscalendar.com/knowledgebase/what-does-buying-a-license-get-me/.
The point you touched on, regarding whether the plugin is vulnerable to work without a license code: this is close to the reality. In fact, the plugin as it stands works 100% without a license plugged in…which is the main reason we don’t make it available to the public via GitHub and instead keep it as a private repo. Buying a license doesn’t unlock new functionality…but it does grant access to automatic updates within the plugin when a new build is released, and provides forum access for support. But if someone got their hands on a copy of the code elsewhere, they would be able to run it so long as they understood they wouldn’t get help or future updates.
Does this help shed light on things? Let me know if not, or if there was another answer you were looking for here. Thanks in advance!
January 9, 2015 at 1:30 am #930792Marc
ParticipantHi Rob, that’s great — that’s the answer I was looking for. I’ll look into a private repo or submodule somehow!
Cheers
January 9, 2015 at 6:46 am #930850Brian
MemberGreat, glad it helps, I am going to go ahead and close this ticket, but if you need help on this or something else please post a new ticket.
Thanks!
-
AuthorPosts
- The topic ‘Public source control’ is closed to new replies.
