| | |
|---|
| | | * Windows server 1809 (MSVC 2017, boost 1.71) |
|---|
| | | * Windows 7-10 (MSVC 2019, boost 1.71) |
|---|
| | | |
|---|
| | | Tests are carried out automatically every commit. You can see the current build status on [travis-ci](https://travis-ci.org/open-license-manager/open-license-manager). |
|---|
| | | Tests are carried out automatically every commit. You can see the current build status on [travis-ci](https://travis-ci.org/open-license-manager/licensecc). |
|---|
| | | |
|---|
| | | If you can't get it compiling: |
|---|
| | | |
|---|
| | |
|---|
| | | ## Project statuss |
|---|
| | | |
|---|
| | | ### Project general context (is the project still maintained?) |
|---|
| | | This project started as a week-end project in 2014, donated and almost forgotten. This doesn't necessarily meant bad. It was "functional". Thanks to the effort of some people that are using it, and to the help of many of you it has been kept up to date (2020). Now it has got a _refresh_ due to some project having interest in it.. |
|---|
| | | This project started as a week-end project in 2014, donated and almost forgotten. This doesn't necessarily meant bad. It was "functional". Thanks to the effort of some people that are using it, and to the help of many of you it has been kept up to date (2020). Now it has got a _refresh_ due to some project having interest in it and |
|---|
| | | this year has seen a lot of new features mostly linked to virtualization detection and new environment support. |
|---|
| | | |
|---|
| | | ### Is it production ready? |
|---|
| | | Let's be honest It is still in alhpa  |
|---|
| | | stage. This means it's usable with some effort. Some companies are actively using it in production to issue demo licenses and few production licenses. |
|---|
| | | If you plan to use it in a scenario where you need to issue hundreds of licenses plan some maintaining effort, or better use a more mature or commercial licensing software. |
|---|
| | | Let's be honest it is still in a very  |
|---|
| | | stage. This means: it's usable with some effort. Some companies are actively using it in production to issue demo licenses and few production licenses. |
|---|
| | | If you plan to use it in a scenario where you need to issue hundreds of licenses plan some maintaining effort, |
|---|
| | | or better use a more mature/commercial licensing software. |
|---|
| | | |
|---|
| | | ### Challenges. |
|---|
| | | The most challenging aspect is the number of environment/libraries we must work with. |
|---|
| | | We've set up automated tests on Travis CI in about 10 different configurations to help contributors to verify their code automatically in conditions they've not thought about. |
|---|
| | | If you plan to contribute you can quickly check your pull requests are compiling before notifying us by visiting the [travis-ci website](https://travis-ci.org/open-license-manager/open-license-manager). |
|---|
| | | If you plan to contribute you can quickly check your pull requests are compiling before notifying us by visiting the [travis-ci website](https://travis-ci.org/open-license-manager/licensecc). |
|---|
| | | |
|---|
| | | ### Open License Manager and "the community" |
|---|
| | | Open License Manager has a very strange relationship with "the community", its aim is to protect proprietary software |
|---|
| | | ### Licensecc and "the community" |
|---|
| | | `Licensecc` has a very controversal relationship with "the community", its aim is to protect proprietary software |
|---|
| | | from copy and unintended usage. But out there, there are people that think that all the software should be licensed as AGPL... |
|---|
| | | StackOverflow and its fellow sites turned out to be not such a collaborative place to talk about software protection. |
|---|
| | | Remember to choose your questions carefully. :speak_no_evil: |
|---|
