From b939d1a0b6b375ea5bae54d83a1cb89eb888c75a Mon Sep 17 00:00:00 2001 From: gcontini <1121667+gcontini@users.noreply.github.com> Date: 周六, 21 3月 2020 20:57:47 +0800 Subject: [PATCH] update docs --- README.md | 24 ++++++++++++------------ 1 files changed, 12 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index e0a832d..8124392 100644 --- a/README.md +++ b/README.md @@ -10,25 +10,25 @@ [](https://codecov.io/gh/open-license-manager/open-license-manager) [](http://github.com/open-license-manager/open-license-manager/issues) -It allows to protect the software you develop from unauthorized copies, -limit the usage in time, to a specific set of machines, or prevent the usage in -virtualized environments. It is an Open License Manager that helps to keep your -software closed :smirk: . A comprehensive [list of features](https://github.com/open-license-manager/open-license-manager/wiki/features), and their status is available in the project wiki. +Protect the software you develop from unauthorized copies, limit the usage in time, to a specific set of +machines, or prevent the usage in virtualized environments. It is an Open License Manager that helps to keep your +software closed :smirk: . Among other features if it runs on a "real hardware" it can generate a signature of that hardware and report if the signature doesn't match. + +A comprehensive [list of features](https://github.com/open-license-manager/open-license-manager/wiki/features), and their status is available in the project wiki. + +If you plan to use this library or part of it remember to show us your appreciation giving it a +<a class="github-button" href="https://github.com/open-license-manager/open-license-manager" data-icon="octicon-star" aria-label="Star open-license-manager/open-license-manager on GitHub">star</a> here on GitHub. ## License The project is donated to the community. It comes with a very large freedom of use for everyone, and it will always be. It uses a [BSD 3 clauses](https://opensource.org/licenses/BSD-3-Clause) licensing schema, that allows free modification and inclusion in commercial software. ## Project Structure -The software is made by 2 main sub-components: +The software is made by 3 main sub-components: - a C++ library with a nice C api, `licensecc` with minimal (or no) external dependencies (the part you have to integrate in your software) that is the project you're currently in. -- a license generator lcc-license-generator `lcc` for customizing the library and generate the licenses. +- a license debugger `lcc-inspector` to be sent to the final customer when there are licensing problems or for calculating the pc hash before issuing the license. +- a license generator (github project [lcc-license-generator](https://github.com/open-license-manager/lcc-license-generator)) `lcc` for customizing the library and generate the licenses. -The following modules are planned... -- a license [backoffice](../../issues/7) in php (in order to handle multiple licenses). -- a license debugger to be sent to the final customer when there are licensing problems. -- a [log descriptor](../../issues/8) in order to decrypt logs generated by the license system. - ## How to build Below an overview of the basic build procedure, you can find detailed instructions for [linux](https://github.com/open-license-manager/open-license-manager/wiki/Build-the-library) or [windows](https://github.com/open-license-manager/open-license-manager/wiki/Build-the-library-windows) in the wiki. @@ -91,5 +91,5 @@ ## How to contribute -The project is not dead but we take our time to answer. The best interaction you can have with us is through the issue system. Have a look to the [contribution guidelines](CONTRIBUTING.md) +The easiest way you can solve your problems or ask help is through the [forum](https://groups.google.com/forum/#!forum/licensecc), otherwise if you think there is a problem you can open an issue in the [issue system](https://github.com/open-license-manager/open-license-manager/issues). Have a look to the [contribution guidelines](CONTRIBUTING.md) before reporting. We use [GitFlow](https://datasift.github.io/gitflow/IntroducingGitFlow.html) (or at least a subset of it). Remember to install the gitflow git plugin and use `develop` as default branch for your pull requests. -- Gitblit v1.9.1