aries-bbssignatures 0.1.0

BBS+ signature support for Hyperledger Aries
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

## How to contribute

You are encouraged to contribute to the repository by **forking and submitting a pull request** signed by the contributor using the `git commit -s` command line option pursuant to the Developer's Certificate of Origin (DCO), available at [https://developercertificate.org](https://developercertificate.org), and licensed under the Apache License, version 2.0 (Apache-2.0). 

Contributions can be made and signed using the GitHub user interface by simply
editing one or more files. Such contributions MUST NOT be made to the `main`
branch, but rather to a fork.

For significant changes, please open an issue first to discuss the proposed
changes to avoid re-work.

(If you are new to GitHub, you might start with a [basic
tutorial](https://help.github.com/articles/set-up-git) and check out a more
detailed guide to [pull
requests](https://help.github.com/articles/using-pull-requests/).)

Pull requests will be evaluated by the repository maintainers on a schedule and
if deemed beneficial will be committed to the `main` branch. Pull requests
should have a descriptive name, include an summary of all changes made in the
pull request description, and include unit tests that provide good coverage of
the feature or fix. A Continuous Integration (CI) pipeline is executed on all
PRs before review and contributors are expected to address all CI issues
identified. Where appropriate, PRs that impact the end-user and developer demos
in the repo should include updates or extensions to those demos to cover the new
capabilities.

If you would like to propose a significant change, please open an issue first to
discuss the work with the community.

<!-- ## Development Tools

### Pre-commit

A configuration for [pre-commit](https://pre-commit.com/) may be included in this
repository. This is an optional tool to help contributors commit code that
follows the formatting requirements enforced by the CI pipeline. Additionally,
it can be used to help contributors write descriptive commit messages that can
be parsed by changelog generators.

On each commit, pre-commit hooks will run that verify the committed code
complies with flake8 and is formatted with black. To install the flake8 and
black checks:

```
$ pre-commit install
```

To install the commit message linter:

```
$ pre-commit install --hook-type commit-msg
``` -->