hitsz-ids/duetector

[Good First Issue] Guide for New Contributors

wunder957 opened this issue Β· 2 comments

In order to get more people into the program faster, we came up with this Issue. Thank you for clicking on this issue and thinking about how you can contribute to our project. πŸŽ‰

🍰 What is Good First Issue?

Good First Issues empowers first-time contributors of open-source software.

We have three levels of difficulty for you:

πŸš… How to pick a task?

Participation in a project that has already been assigned is also encouraged, but you must be aware that it will require more effort to get up.

  • πŸ‘€ Browse the issues you are interested in
  • πŸ™‹β€ Comment below the issue you want to participate in
  • πŸ“§ After further communication with the maintainer, issue will be assigned to you
  • πŸ”§ A Maintainer will be your mentor and will continue to work with you on issue resolution
  • πŸš… Read our contributing guidelines and commit code to your fork.
  • βœ” After PR, Code review, Request changes, Approve..., your code will be merged into the master branch and you will become one of our developers!

❓ Need help?

When you have some problems and want to ask for help:

⭐New ideas?

If you have any new ideas, including Feature Requests, feel free to raise an issue as a good first issue, and the maintainer will analyze the problem and evaluate the difficulty with you.

πŸ‘¨β€πŸ”§Technical support

There are currently two maintainers responsible for maintaining this project:

Hi, I would like to take on this issue.

@Lymah123 Please read this issue carefully and find an issue that interests you from it.

We have three levels of difficulty for you:

Easy
Medium
Hard

πŸš… How to pick a task?
Participation in a project that has already been assigned is also encouraged, but you must be aware that it will require more effort to get up.

πŸ‘€ Browse the issues you are interested in
πŸ™‹β€ Comment below the issue you want to participate in
πŸ“§ After further communication with the maintainer, issue will be assigned to you
πŸ”§ A Maintainer will be your mentor and will continue to work with you on issue resolution
πŸš… Read our contributing guidelines and commit code to your fork.
βœ” After PR, Code review, Request changes, Approve..., your code will be merged into the master branch and you will become one of our developers!