Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/berty/community
Berty Planning, Management & Coordination threads
https://github.com/berty/community
berty community
Last synced: 3 months ago
JSON representation
Berty Planning, Management & Coordination threads
- Host: GitHub
- URL: https://github.com/berty/community
- Owner: berty
- License: mit
- Created: 2019-07-05T13:52:47.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-07-12T12:05:54.000Z (over 2 years ago)
- Last Synced: 2024-05-02T21:52:36.241Z (6 months ago)
- Topics: berty, community
- Language: Shell
- Homepage: https://berty.tech/community
- Size: 335 KB
- Stars: 41
- Watchers: 15
- Forks: 9
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
README
Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
---
> General discussions and documentation on community practices
## About
Welcome to Berty Community!
At Berty, we have a true emphasis on our community. You are the driving force behind the project. We are more than ever grateful for the investment of time and effort you have made and will make.
Help us to fight censorship and mass surveillance because everyoneβs privacy matters.
Please never underestimate your contribution. Little + Little = Big. We do believe in the butterfly effect.
The Berty team.
## Berty Technologies
We are an NGO based in Paris that defends privacy and fights against censorship and surveillance.
If these topics speak to you and your values correspond to ours, we would very much like you to join our community!
> Learn more on our website: https://berty.tech## Security
As a privacy-protective NGO, we really care about security. Please read this: [SECURITY.md](https://github.com/berty/community/blob/master/SECURITY.md).
## π Getting Started
The hardest part is always getting started, and a lot of people are wondering where to start. The answer is very simple: each little thing matters, so just do it!
Here are **5 quick and easy steps** before digging in that will help us a lot:
* Follow [@berty](https://twitter.com/berty) on Twitter.
* Star Berty on [Github](https://github.com/berty).
* Join the community on [Discord](https://crpt.fyi/berty-discord).
* Read our [blog posts](https://berty.tech/blog) and [latest news](https://berty.tech/newsletter).
* Check how to contribute (see below).## Community Rules
### Code of Conduct
This repository falls under the Berty [Code of Conduct](https://github.com/berty/community/blob/master/CODE_OF_CONDUCT.md).
### Language
We use the English language to spread widely the project!
### Membership
You can spontaneously decide to become a member. We really encourage all members to become a contributor in any way (see below). We aim to grow an active, healthy community of contributors, reviewers, and code owners.
## Contributing
![Contribute to Berty](https://assets.berty.tech/files/contribute-contribute_v2--Contribute-berty-ultra-light.gif)
We really welcome contributions. Your input is the most precious material. We're well aware of that and we thank you in advance. Everyone is encouraged to look at what they can do on their own scale; no effort is too small.
There are plenty of ways to get involved and act for our community. It has been divided into two distinct parts: everything that is related to the code and everything that is not.
To put it very simply:
* Code-related = Github
* Not code-related = Open taskEverything on contribution is sum up here: [CONTRIBUTING.MD](https://github.com/berty/community/blob/master/CONTRIBUTING.md)
### Code
As you may know, all Berty's code is [open-source](https://berty.tech/blog/open-source/) and available on [Github](https://github.com/berty). The code is yours: `Own it, Use it, Test it, Fix it`.
To facilitate and centralize contributions, we rely only on Github for code contributions. We use `issues` as a discussion forum and contributions can be done in a pull request.
If you're looking for something to get your feet wet working on Berty, take a look at the GitHub issues tagged [`good first issue`](https://github.com/berty/berty/labels/good%20first%20issue) or [`help wanted`](https://github.com/berty/berty/labels/help%20wanted).
Here is a bunch of contribution ideas:
* Answer the questions from the community on issues.
* Fix bugs reported on issues.
* Send us a pull request.
* Review the existing pull request.
* Improve the documentation.
* Check out the architecture and review it.
* Hack on Berty.
* Contribute to the projects of the Berty ecosystem (mostly IPFS-related).
* Any other form of contribution that is not mentioned above. π¬See [README](https://github.com/berty/berty) for details on submitting patches and the contribution workflow.
> Haven't found any inspiration above? Got stuck? Don't know how to start? Please send an email to let us know, and we will be pleased to help you!
>### Open Tasks
There are lots of ways to help on the creative side. We can channel our creative energies!
#### Design
* π¨ Draw a logo for social networks, blog, newsletter...
* π Create a new design for our merch
* πΌβUpdate our [portfolio](https://assets.berty.tech/)
* βοΈ Produce illustrations for technical documentation
* βοΈ Improve graphic guidelines
* π Design a Berty mantra
* πβMake a virtual greeting card#### Sound
* π·Create a sound notification
* ποΈConduct an interview of Berty users or team members### Street Art
* ποΈ We bootstrap a street art project on whistleblowers called '[Berty Priv-art](https://berty.tech/art)'. Help us make it concrete!
> Find inspiration: https://assets.berty.tech
### Translation
As you may guess, we don't know every language. However, we want Berty to be accessible to as many people as possible. That's why we need as much material as possible translated into as many languages as possible.
This can be the documentation, the app, the support, a blog post, even this page, or another section on the site.
### Bugs and Report
We use GitHub issues for tracking requests and bugs. Please post the questions directly there using the 'bug' tag.
If you've got questions or issues with using Berty, check out our support page and be sure to connect to our community, where there's always someone ready to help.
### Support
For Berty to benefit as many people as possible, it is important to have the most comprehensive documentation available. If you have a question and the answer is not in the documentation/support page, please help us to update this section.
Remember, if you have asked yourself the question, someone else will do the same.
> To help us improve our support page, reach @Camille.
### Website & Blog
Having a good website helps make the Berty project as accessible as possible. So if you have any ideas for improvement (SEO, for example), let us know. We'll be happy to adjust!Or maybe you have an idea of how to use Berty and you want to share it with the community? Write a nice blog post about your idea, and what it will change for you and your community. We'll be happy to spread the word!
## How To Support Berty?
Berty Technologies runs only on donations. This is why we need your help, including financial support.There are many small things you can do to help us. Each contribution will be highlighted on our site as a thank you.
### Berty Store
When you [shop at our store](https://shop.berty.tech/), you'll find great items that are not only cool but also allow Berty to exist!
Support the team and rock a new shirt on the next event π
Do you have an idea of a Berty-related design that would be cool to wear? Feel free to suggest it, and if it's added to the store, we'll send you a sample!
## People
### Maintainers
The [berty-staff](https://github.com/orgs/berty/teams/staff) team.
### Sponsors and Backers
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor](https://github.com/sponsors/berty)
Thank you to all our backers! π [Become a backer]
## π Events
We will organize events to bring the community together π». Please let us know if you wish to create local events. We will send you goodies (stickers, T-shirts...), slide kits presenting the project, and relay the info! This applies both for IRL and online events.
> **Note:** If you have other ideas to improve this section, or want to set up an event, go to [Discord](https://crpt.fyi/berty-discord) and ping us!
## π© How To Contact Us
Contact: https://berty.tech/contact
## π Useful Links
* Twitter: https://twitter.com/berty
* Discord: https://crpt.fyi/berty-discord
* Documentation: https://berty.tech/docs#
* Github: https://github.com/berty (don't forget to click on the βοΈ button π)
* Blog: https://berty.tech/blog
* Newsletter: https://berty.tech/news
* Shop: https://shop.berty.tech### Berty GitHub Repo
* [Main Repo](https://github.com/berty/Berty)
* [Assets](https://github.com/berty/assets)
* [Website](https://github.com/berty/www.berty.tech)## Swag
_TODO_
## License
This repository is mainly for documents. All of these are licensed under the [CC-BY 3.0](https://creativecommons.org/licenses/by/3.0/us/) license.
Β© [Berty Technologies](https://berty.tech). Any code is under an [MIT](./LICENSE).