MAINTAINER GUIDELINES

We are excited to have you onboard and hope this experience will help you get great contributions and new contributors! Here are a few guidelines to help you out with the ODHack.

Content sharing (communication)

• In order for us to share with the community that you will be participating in the ODHack, please provide us with:
  • Description of the project and/or repo
  • What you are looking for in contributions (skills and experience)
  • Twitter handle so that we can tag you and for you to equally share it with your community
• We will also do community calls before the event day to showcase the project. Please be available. They tend to happen at 5 PM CET.

Issues

• Preparation: Have a number of open issues ready for D-Day (so in this case by December 12st CET 3:00 PM), with a good number being "good first issues." This helps in onboarding new contributors and ensuring there's a task for everyone.
  • We highly recommend having AT LEAST 10-15 ISSUES.

• Labeling and Visibility: Please make sure that issues are labeled in order of difficulty and tagged ODHack10 for better visibility.

It’s also important that issues have enough description to guide contributors effectively.

<aside> ⚠️ IMPORTANT: You must have the label ODHack10 on the issues. This way everything is centralized on the **hackathon page** where contributors can look at the available issues an apply accordingly.

For the one December 12st, it must be labeled ODHack11.

</aside>

<aside> ⚠️ You can have a look here at best practices for maintainers!

</aside>

<aside> ⚠️ I have added other examples at the very bottom!

</aside>

Communication guidelines & channels