License

[josemendez]

I have the same question.

I manage a group of student projects at my university, where we are developing a virtual science lab in which school students can train to perform the experiments prescribed in their textbooks.

It's early days yet, but given the huge and exploding population of the country, the potential number of users is very high!

In order to ensure that this work does not get stuck behind paywalls, we are working in open-source mode. However, we would, of course, not want to cause financial damage to Obi/VirtualMethod. Hence, before we proceed, we would like to know what it would be ok to share in our public repositories and what we should not?

Thanks!

Hi there,

Generally speaking, assets in the store operate under a pay once/use in as many projects as you want kind of deal. This makes sense for small developers, as they don't have large budgets, and most of their projects never actually see the light of day.

Larger companies however, tend to make much more $$ and have lots of seats with the asset installed. Some workers probably will just copy the asset and take it home from work. We deliberately take a hit here to benefit small developers and allow the asset to expand.

Open source projects however have the potential to expose the asset to a much higher amount of people. For this reason I think it makes sense to refrain from sharing the asset in your public repos, listing it as a dependency instead, since Obi itself is not open source.

If this is not possible for whatever reason, we can work to find a reasonable solution.