From 8d405b265285c368df2e9cf1c14acee7532e0ee7 Mon Sep 17 00:00:00 2001 From: nancy.liao <huihui.liao@greentest.com.cn> Date: ćšć, 29 5æ 2025 18:14:38 +0800 Subject: [PATCH] Merge branch 'develop' of http://139.9.88.116:3000/r/module/open-license-manager into develop --- README.md | 11 +++++------ 1 files changed, 5 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index b0c9df2..cbe5f0d 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,6 @@ [](https://www.codacy.com/gh/open-license-manager/licensecc/dashboard?utm_source=github.com&utm_medium=referral&utm_content=open-license-manager/licensecc&utm_campaign=Badge_Grade) [](https://codecov.io/gh/open-license-manager/licensecc) [](http://github.com/open-license-manager/licensecc/issues) -[](https://groups.google.com/d/forum/licensecc) 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 source license manager that helps to keep your @@ -18,20 +17,20 @@ A comprehensive [list of features](http://open-license-manager.github.io/licensecc/analysis/features.html), and their status is available in the project site. -If you're experiencing problems, or you just need informations you can't find in the [documentation](http://open-license-manager.github.io/licensecc) please contact us on the [user forum](https://groups.google.com/forum/#!forum/licensecc) (hosted on Google), we'll be happy to help. +If you're experiencing problems, or you just need informations you can't find in the [documentation](http://open-license-manager.github.io/licensecc) please contact us on [github discussions](https://github.com/open-license-manager/licensecc/discussions), we'll be happy to help. Remember to show your appreciation giving us a <a class="github-button" href="https://github.com/open-license-manager/licensecc" data-icon="octicon-star" aria-label="Star open-license-manager/licensecc 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. +The project is donated to the community. It comes with freedom of use for everyone, and it always will be. +It has a [BSD 3 clauses](https://opensource.org/licenses/BSD-3-Clause) licensing schema, that allows free modification and use in commercial software. ## Project Structure The software is made by 4 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 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)) `lccgen` for customizing the library and generate the licenses. -- Usage [examples](hhttps://github.com/open-license-manager/examples) to simplify the integration in your project. +- Usage [examples](https://github.com/open-license-manager/examples) to simplify the integration in your project. ## How to build Below an overview of the basic build procedure, you can find detailed instructions for [Linux](http://open-license-manager.github.io/licensecc/development/Build-the-library.html) @@ -95,7 +94,7 @@ ## How to contribute -The easiest way you can solve your problems or ask help is through the [forum](https://groups.google.com/forum/#!forum/licensecc) (hosted on Google), otherwise if you think there is a problem you can open an issue in the [issue system](https://github.com/open-license-manager/licensecc/issues). +The easiest way you can solve your problems or ask help is through the [discussions tab](https://github.com/open-license-manager/licensecc/discussions) above, otherwise if you think there is a problem you can open an issue in the [issue system](https://github.com/open-license-manager/licensecc/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