Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/hcl-tech-software/domino-license-analysis-utility-dlau

Utility to assist HCL Domino Administrators in determining your Authorized User Count
https://github.com/hcl-tech-software/domino-license-analysis-utility-dlau

domino

Last synced: 8 days ago
JSON representation

Utility to assist HCL Domino Administrators in determining your Authorized User Count

Awesome Lists containing this project

README

        


HCL DominoHCL Domino License Analysis Utility

# HCL Domino License Analysis Utility

This utility will assist HCL Domino Administrators in doing a health check based on deployment best practices and determining the Authorized User Count within an HCL Domino environment according to the CCB & CCX license model.

## Purpose
The purpose of this utility is to provide fast and accurate Authorized User counts for HCL Domino environments by aggregating information that a Domino Administrator would otherwise have to collect manually.

The DLAU automates the process by aggregating all the information that is needed to accurately determine the Authorized User counts in a fraction of the time.

___
## Documentation

Please refer to

[this page](https://opensource.hcltechsw.com/domino-license-analysis-utility-DLAU/)

___
## Change log

We will keep track of each release in the [CHANGE LOG](/docs/changelog.md)

___
## Code of Conduct

To understand our Code of Conduct and how we handle misuse, please read the following:
[CODE OF CONDUCT](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/blob/main/CODE_OF_CONDUCT.md).

___
## Contributing

Please read through our [Contributing Guidelines](https://github.com/HCL-TECH-SOFTWARE/domino-license-analysis-utility-DLAU/blob/main/Documentation/CONTRIBUTING.md). Included are directions for opening issues.

___
## Versioning

The HCL Domino License Analysis Utility will adhere to the following versioning guidelines as much as possible. Releases will be numbered with the following format:

`..`

* A release may update the design, look-and-feel, or branding of an existing version
* We will not intentionally release a `patch` version update that breaks previous functionality
* A `minor` or `patch` release will never remove functionality
* Bug fixes will be addressed as `patch` releases unless they change existing functionality, then they will be `minor` releases

___
## Copyright and License
By contributing your code, you agree to license your contribution under the terms of the the [Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0) for any contributions that are made open source as development progresses.