Collect technical questions and solutions via Github. #51
Replies: 1 comment
-
Sure, we encourage members of the community to propose their ideas/questions on GitHub, which is actively maintained by our team. Actually, GitHub is the primary channel we're in, while other channels are for non-technical members. By doing so, these discussions can be archived and accessible to the community. These discussions/solutions will also be concluded and subscribed to by our troubleshooting page(Magickbase/neuron-public-issues#99) to utilize the power of algolia(https://www.algolia.com/), which is more powerful than the search of GitHub/Google, and easy to visit for non-technical members. Besides, Q&A on other channels will be recorded on GitHub too, if they are frequently asked, to make the library(GitHub issues) robust. And all these issues will be referenced if similar questions appear on other channels. |
Beta Was this translation helpful? Give feedback.
-
I have noticed that various members of the community are collecting Questions and Answers/Solutions that often occur on Discord and other platforms. I think it is a very good idea and has a number of important advantages:
Here some examples:
Using Q/A from the discussion section:
How to translate godwoken_short_address to eth_address? godwokenrises/godwoken#1069
Using an issue:
How to import the next Lumos version? ckb-js/lumos#513
Using Nervos Talk:
What’s the max size and max cycles of a CKB block? https://talk.nervos.org/t/whats-the-max-size-and-max-cycles-of-a-ckb-block/7166
This comes up from a series of questions from a developer on the Magickbase discord:
https://discord.com/channels/956765352514183188/959384192859389983/1108895398803800134
Beta Was this translation helpful? Give feedback.
All reactions