rusefi_documentation/Knowledge-best-practices-an...

33 lines
1.4 KiB
Markdown
Raw Permalink Normal View History

2023-01-03 02:53:11 -08:00
# Knowledge sharing and Channels
TL,DR: are you interested in any knowledge being indexed by google and are you interested in any knowledge outliving your rusEFI involvement? Are you interested in the social aspect of the rusEFI Discord lounge?
TL,DR: please post knowledge on forum and report issues at [https://github.com/rusefi/rusefi/issues](https://github.com/rusefi/rusefi/issues)
(do we have this somewhere already?)
We have too many channels.
2023-01-02 11:22:23 -08:00
* wiki
* github tickets [Vault-Of-Memes](Vault-Of-Memes)
* forum
* facebook
* discord
* slack
Universal long term car knowledge? probably wiki
I have a cool project, it's my own not universal knowledge? at least a summary on the forum
## Q: I need help?
A: Please start on the forum, please go to slack after first back and forth, please post summary on the forum. Know what you are doing? Please start with a github issue instead of forum post.
2023-01-02 11:22:23 -08:00
## Q: I have exciting valuable data I really want to dump it into slack RIGHT NOW
2023-01-02 11:22:23 -08:00
A: Please do not. Please help by not offloading data preservation on someone else. Please start on the forum or github. Slack communications are only good for clarification and discussion *AFTER* context is nicely established on forum or github.
## Q: Should I pile everything together?
A: Please do not mix unrelated things together. For instance, let's not troubleshoot Mercedes vehicles on BMW build threads :)