ISSUE #2443: Complete community page in the new docusaurus website

Descriptions of the changes in this PR:

This PR introduces changes to complete the community page of the new up-coming docusaurus based website.

### Motivation

The #2426 Pull Request introduced the changes for new docuasurus based website, However few of the pages like community and project were incomplete. This PR introduces the changes to complete the community page.

### Changes

I have added the markdown files for the following web-pages - 
* bookkeeper-proposals
* coding-guide
* community-meetings
* contributing
* issue-report-guide
* mailing-lists
* papers-and-presentations
* release-guide
* release-management
* testing-guide

I have also updated the code in community.js to refactor the way tables for PMC and committers is getting generated, So that we get the best out of the react based framework.

### Testing Details - 

I have build the changes locally and have verified that all the links are rendering properly or not. Here is the screenshot of the new community web-page.

![Screenshot 2020-10-19 at 18 36 34](https://user-images.githubusercontent.com/17764661/96454852-11be0100-123a-11eb-8a8f-ca49ec663d7b.png)


Master Issue: #2443 


Reviewers: Anup Ghatage <ghatage@apache.org>

This closes #2447 from Abhey/Issue-2443, closes #2443
10 files changed
tree: e3f8067ca13c0f77e35fcfd9c1683573acb59b83
  1. .github/
  2. .test-infra/
  3. bin/
  4. bookkeeper-benchmark/
  5. bookkeeper-common/
  6. bookkeeper-common-allocator/
  7. bookkeeper-dist/
  8. bookkeeper-http/
  9. bookkeeper-proto/
  10. bookkeeper-server/
  11. bookkeeper-stats/
  12. bookkeeper-stats-providers/
  13. buildtools/
  14. circe-checksum/
  15. conf/
  16. cpu-affinity/
  17. deploy/
  18. dev/
  19. docker/
  20. metadata-drivers/
  21. microbenchmarks/
  22. shaded/
  23. site/
  24. site2/
  25. stats/
  26. stream/
  27. tests/
  28. tools/
  29. .gitignore
  30. Jenkinsfile
  31. LICENSE
  32. NOTICE
  33. pom.xml
  34. README.md
README.md

Build Status Build Status Coverage Status Maven Central

Apache BookKeeper

Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.

It is suitable for being used in following scenarios:

  • WAL (Write-Ahead-Logging), e.g. HDFS NameNode.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Getting Started to setup BookKeeper to write logs.

Documentation

Developers

You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.

Administrators

Contributors

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.

Need Help?

Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.

Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.

Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.

Contributing

We feel that a welcoming open community is important and welcome contributions.

Contributing Code

  1. See Developer Setup to get your local environment setup.

  2. Take a look at our open issues: JIRA Issues Github Issues.

  3. Review our coding style and follow our pull requests to learn about our conventions.

  4. Make your changes according to our contribution guide.

Improving Website and Documentation

  1. See Building the website and documentation on how to build the website and documentation.