communications info (#44)

This commit is contained in:
coreglitch 2020-08-24 23:08:32 +06:00 committed by GitHub
parent 1759787334
commit f999b9ef28
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 3 deletions

View File

@ -13,7 +13,8 @@ Separating roles and channels in this way:
* Staff — people working in-house * Staff — people working in-house
* Admins — staff members who can manage permissions * Admins — staff members who can manage permissions
### Channels ### Channels
Right now I just separate contributors from everyone, to prevent a flood. Later we can create more voice and text channels for firmware/hardware/creative department. Right now I just separate contributors from everyone, to prevent a flood. Later we can create more voice and text channels for firmware/hardware/creative department.
![image](https://user-images.githubusercontent.com/774290/90881195-6536de80-e3b2-11ea-8b14-c7ac5b69c10c.png) ![image](https://user-images.githubusercontent.com/774290/90881195-6536de80-e3b2-11ea-8b14-c7ac5b69c10c.png)

View File

@ -9,7 +9,7 @@ If you are just beginning in Flipper, **Read the [wiki](https://github.com/Flipp
## General Tips and principles ## General Tips and principles
* **Ask around for help!** If you have any questions, feel free to create an [`need help` issue](https://github.com/Flipper-Zero/flipperzero-firmware-community/issues/new?assignees=&labels=need+help&template=need-help.md&title=) or send an email to devel@flipperdevices.com. The earlier you check your feature design with other people, the less likely it is that it is denied during the review process. * **Ask around for help!** If you have any questions, feel free to create an [`need help` issue](https://github.com/Flipper-Zero/flipperzero-firmware-community/issues/new?assignees=&labels=need+help&template=need-help.md&title=), send an email to devel@flipperdevices.com or use our [Discord server](https://flipperzero.one/discord) ([read more about discord](Communication)). The earlier you check your feature design with other people, the less likely it is that it is denied during the review process.
* **Verify your concept early!** If you work on your own until the code looks good enough to show publicly, you might miss some design flaws others might have spotted earlier. * **Verify your concept early!** If you work on your own until the code looks good enough to show publicly, you might miss some design flaws others might have spotted earlier.
* **Keep it simple!** Try to use what is already there and don't change existing APIs if not absolutely necessary. * **Keep it simple!** Try to use what is already there and don't change existing APIs if not absolutely necessary.
* **State your intentions** Create issue before you start your work. It will prevent a very frustrating situation where several people are doing the same job the same time. * **State your intentions** Create issue before you start your work. It will prevent a very frustrating situation where several people are doing the same job the same time.

View File

@ -1,6 +1,9 @@
### For quick communication and voice calls we use Discord: [flipperzero.one/discord](https://flipperzero.one/discord) ### For quick communication and voice calls we use Discord: [flipperzero.one/discord](https://flipperzero.one/discord)
(please ask for `Contributor` role to use developers channels in Discord) (please ask for `Contributor` role to use developers channels in Discord)
[read more about discord](Communication)
Community forum: [forum.flipperzero.one](https://forum.flipperzero.one) Community forum: [forum.flipperzero.one](https://forum.flipperzero.one)
Project website: [flipperzero.one](https://flipperzero.one) Project website: [flipperzero.one](https://flipperzero.one)