Skip to content

Commit 54c5816

Browse files
authored
Remove Gitter from README.md (aws#947)
1 parent f5bafd4 commit 54c5816

File tree

1 file changed

+6
-9
lines changed

1 file changed

+6
-9
lines changed

Diff for: README.md

+6-9
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# AWS libcrypto (AWS-LC)
22

3-
[![Join the chat at https://gitter.im/awslabs/aws-lc](https://badges.gitter.im/awslabs/aws-lc.svg)](https://gitter.im/awslabs/aws-lc?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
4-
53
AWS-LC is a general-purpose cryptographic library maintained by the AWS Cryptography
64
team for AWS and their customers. It іs based on code from the Google BoringSSL project
75
and the OpenSSL project.
@@ -31,7 +29,7 @@ ls *
3129
```
3230
See [Building.md](https://github.com/aws/aws-lc/blob/main/BUILDING.md) for more
3331
information about required dependencies and build options. If you’re interested in
34-
getting involved open an Issue to discuss your plan or talk to us on Gitter.
32+
getting involved [open an issue](https://github.com/aws/aws-lc/issues/new/choose) to discuss your plan.
3533
[Contributing.md](https://github.com/aws/aws-lc/blob/main/CONTRIBUTING.md) has
3634
info for how to specifically make the change and get it reviewed by AWS-LC maintainers.
3735
If you just want to use AWS-LC see our existing documentation in the public header
@@ -52,7 +50,7 @@ other libcrypto projects.
5250

5351
AWS-LC is compatible with the majority of OpenSSL’s APIs to make it easy to use with
5452
existing applications. We’re open to discussing adding missing functionality and
55-
understanding your use case in an Issue or on Gitter.
53+
understanding your use case in an [issue](https://github.com/aws/aws-lc/issues/new/choose).
5654

5755
### Compiler, OS, and CPU support
5856

@@ -104,12 +102,11 @@ verified on certain platforms with caveats include:
104102

105103
## Have a Question?
106104

107-
If you have any questions about Submitting PR's, Opening Issues, AWS-LC API usage or
108-
any similar topic, we have a public chatroom available here to answer your questions
109-
on [Gitter](https://gitter.im/awslabs/aws-lc).
105+
We use [GitHub Issues](https://github.com/aws/aws-lc/issues) for managing feature requests,
106+
bug reports, or questions about AWS-LC API usage.
110107

111-
Otherwise, if you think you might have found a security impacting issue, please instead
112-
follow our Security Notification Process.
108+
If you think you might have found a security impacting issue, please instead
109+
follow our [Security Notification Process](#security-issue-notifications).
113110

114111
## Security issue notifications
115112

0 commit comments

Comments
 (0)