Contributor Onboarding

Welcome to the Community

If you are new to this community you are advised to introduce yourself in the discussion section section, you may use the following context for your introduction purpose

1. Introduction of new Participants

Give a basic intro about yourself A clear and concise description of yourself [...]

Describe your tech expertise A clear and concise description of the domains in which you have worked on (just make bullet points please don't provide information about each and every stack you can mention your previous projects but not necessary).

You may mention your Social Links such that we can connect with you (Optional) Add as many as you can

• Website
• Github
• Twitter...etc

Getting Help

Got a problem? Ask your mentors, ask other students, or ask the community.

Our community is not so large so we value each and every persons and want to enlarge the community. Everyone else you talk with may be a non-mentor.

Students should keep in mind that some people are non-mentors, and cannot see the contest progress, dates, or information about students. When communicating widely, be sure to;

• Introduce yourself, the first time,
• Talk about the task as if you want to do it yourself, not because of the contest,
• Defend your technical decisions without using the contest as a defense,
• Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

Community etiquette

Everyone in the community has to be polite and respectful, and consider everyone else a member of a team and not a competitor.

One should be considerate to everyone else's time. We would like to have quality discussions, and not answer questions that are already documented, or available on stackoverflow. This doesn't mean you can't ask questions, but a clueless user and a lazy developer are two different things.

Tell things as you see them. Be polite, but don't sugar coat it. You don't have to apologize everytime you make a mistake; but avoid repeating it again ;-)

We are ready to hear from you for any suggestions will help us, Please feel free to open an issue