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

# 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 involvment? Are you interested in the social aspect of the rusEFI Slack 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.

* wiki
* github tickets [Vault-Of-Memes](Vault-Of-Memes)
* forum
* facebook
* slack

We do not pay for Slack history - Slack history is purged.

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.

## Q: I have exciting valuable data I really want to dump it into slack RIGHT NOW

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.
fix md syntax and hierarchy 2023-01-03 02:53:11 -08:00			`# Knowledge sharing and Channels`

Updated Knowledge best practices and Channels (markdown) 2022-08-10 09:14:18 -07:00			`TL,DR: are you interested in any knowledge being indexed by google and are you interested in any knowledge outliving your rusEFI involvment? Are you interested in the social aspect of the rusEFI Slack lounge?`
Updated Knowledge best practices and Channels (markdown) 2022-08-10 09:11:40 -07:00
convert some links using script, and fix some manually 2022-01-24 17:21:25 -08:00			`TL,DR: please post knowledge on forum and report issues at [https://github.com/rusefi/rusefi/issues](https://github.com/rusefi/rusefi/issues)`
Updated Knowledge best practices and Channels (markdown) 2021-11-11 20:09:05 -08:00
Created Knowledge best practices and Channels (markdown) 2021-07-26 08:32:29 -07:00			`(do we have this somewhere already?)`

			`We have too many channels.`
automated md lint fixes 2023-01-02 11:22:23 -08:00
Created Knowledge best practices and Channels (markdown) 2021-07-26 08:32:29 -07:00			`* wiki`
Updated Knowledge best practices and Channels (markdown) 2023-03-15 10:57:26 -07:00			`* github tickets [Vault-Of-Memes](Vault-Of-Memes)`
Updated Knowledge best practices and Channels (markdown) 2022-08-10 09:19:17 -07:00			`* forum`
Created Knowledge best practices and Channels (markdown) 2021-07-26 08:32:29 -07:00			`* facebook`
			`* slack`
Updated Knowledge best practices and Channels (markdown) 2022-08-10 09:19:17 -07:00
Created Knowledge best practices and Channels (markdown) 2021-07-26 08:32:29 -07:00			`We do not pay for Slack history - Slack history is purged.`

			`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`

Updated Knowledge best practices and Channels (markdown) 2021-09-27 13:33:28 -07:00			`## 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.`
Updated Knowledge best practices and Channels (markdown) 2021-08-11 05:33:42 -07:00
automated md lint fixes 2023-01-02 11:22:23 -08:00			`## Q: I have exciting valuable data I really want to dump it into slack RIGHT NOW`
Updated Knowledge best practices and Channels (markdown) 2021-08-11 05:33:42 -07:00
automated md lint fixes 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.`