Skip to content
This repository has been archived by the owner on Jul 6, 2022. It is now read-only.

How to better raise questions and corresponding rules #2

Open
Diana316613 opened this issue Jun 28, 2022 · 0 comments
Open

How to better raise questions and corresponding rules #2

Diana316613 opened this issue Jun 28, 2022 · 0 comments

Comments

@Diana316613
Copy link

Diana316613 commented Jun 28, 2022

The original intention of Tapdata community is to grow together with developers and create unlimited possibilities. Here, we can speak freely and help each other solve problems.

In the world of hackers, when you throw out a technical question, whether you can finally get a useful answer often depends on the way you ask and ask. The wisdom of asking questions teaches you how to ask questions correctly to get your satisfactory answers. Here are some excerpts to share with you.

【Before asking questions】
Before you are ready to ask technical questions through groups or forums, please try to search the answers by various means, and try not to often ask some questions that can be solved by search. Including but not limited to:

  • [Tapdata Technical Manual]
  • Tapdata GitHub problem search
  • Search on Baidu, Google and related technology communities

If the above behavior still does not solve your problem, please indicate that you have made the above efforts when asking others for advice and questions; This will help establish that you are not a questioner who gets something for nothing and wastes other people's time. Asking questions or initiating discussions on relevant technical topics in the community is encouraged, but asking questions is also an art that needs to be grasped by the questioner.

【When asking questions】

  1. Maintain a friendly and polite attitude
    No one is obliged to answer your question, especially the answer to this question may take the other party's time / energy, so we need to be polite when asking questions. It is suggested that when asking questions, we first introduce ourselves and politely express our problems. No matter whether the problems are really solved or not, we should thank each other to show our proper bearing and demeanor.
  2. When asking questions, try to describe your questions in detail, clearly, correctly and concisely; The person being asked will be more likely to give a more comprehensive answer to your question.
  3. Try to use specific words and sentences that others can understand when asking questions.

【after questioning】

  1. Express gratitude to the responders.
  2. If your problem has not been solved, please continue to ask and feed back the problems you encounter. It is best to attach operation tips or screenshots.

【Say no to the following actions】
In fact, participating in community interaction is also a social activity, which requires individuals to grasp social propriety and abide by basic social etiquette. Unacceptable participant behaviors include but are not limited to:

  1. Discussion issues rise to personal attacks, provocative, insulting or derogatory comments;
  2. Public or private harassment;
  3. Release private information of others without permission;
  4. Publish advertisements or other bad information without permission;
  5. Brush the screen and post without reason, thus occupying public resources, etc.

Reference source for community code development:
Original website of the wisdom of asking questions: http://www.catb.org/~esr/faqs/smart-questions.html
The English version is copyrighted by Eric S. Raymond, Rick Moen.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant