Public source control

Home Forums Welcome! Pre-Sales Questions Public source control

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #929766
    Marc
    Participant

    Hello,

    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!

    #930131
    Brian
    Member

    Hi,

    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?

    #930307
    Marc
    Participant

    Great, thanks Brian.

    Can you give me a link to the license terms where it says this so I can pass this on?

    Cheers

    #930511
    Rob
    Member

    Hi 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!

    #930792
    Marc
    Participant

    Hi Rob, that’s great — that’s the answer I was looking for. I’ll look into a private repo or submodule somehow!

    Cheers

    #930850
    Brian
    Member

    Great, 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!

Viewing 6 posts - 1 through 6 (of 6 total)
  • The topic ‘Public source control’ is closed to new replies.