I personally use GitHub since it’s so easy to use.
Regarding the structure and if you keep it locally or not depends on the project for me. For the most though, I develop all projects locally and then just push to GitHub as it progresses.
For example, I might have a project under development at localhost/project/. I just make that a github repository and push all changes made as it goes along.
If I was in your place, i’d probably set up repositories locally either of different wordpress versions or theme versions vise. For example, localhost/wp.x.x.x/ or for themes: localhost/themes/3.x/ etc etc.
In this case, it would be easy to just make the changes in any of those themes and versions, and then just push it back to GitHub. It would also make it easy to lets say if you want to change your development computer or w/e, you can just clone the whole rep and you’re almost ready.
Anyway, that’s probably the way I would do it. I’m sure that it’s probably other ways to do it that might fit better just for you, I guess it’s a matter of personal opinion.
Good luck with it.
Keep in mind that it is not allowed to use any other license check apart from the envato api. So you are not allowed to implement a own license system which does not connect directly to the Envato api.
The Envato API will also be included in the validation of checking a license.
Great! What would you think about it being a SaaS application? It would probably be the easiest software to use due to the flexibility of it being in the cloud instead of a stand alone installation for each “product holder”. Could be pretty sweet and hassle free in my opinnion.
I am thinking about developing a SaaS application for preventing illegal use of wordpress themes and all other web related products.
Would anyone be interested in trying it out?
Thanks in advance, Daniel