Looking for sincere maintainers

[abhpd]

Dated: Oct 1st 2021

Maintainers are most welcome to help us handle the large amount of PRs and helping beginners.

Hacktoberfest now also has rewards for maintainers.

Responsibilities of a maintainer will include the following

1. Handle PRs

1. Make sure the PR adds something new/improved/fixed then mark them "hacktoberfest-accepted ". If it’s spam, mark "invalid" and "spam".
2. PR should clearly mention what it is doing along with any issues if it applies.
3. PR file locations should match the hierarchy of the repository.
4. PR should have a proper commented explanation in the code file of the implementation and details.
5. If it follows all the above criteria, approved it to be merged.
6. If it needs change, review the code and add proper details of what needs to be changed and mark the PR changes requested and add tag "changes-needed", so it will be easier to track with a bunch of PRs.
7. Give preference to the PR on a first come first serve basis. that means if two PRs work on the same Algorithm like binary search, give preference to the first PR made.

2. Create Issues

1. Create issues for bugs, improvements, and hierarchy correction.
2. Make sure you provide details for the issue clearly mentioning what to do.

3. Help Everyone

After all this repository is mainly aimed to help people new to open-source.
Be generous to small PRs like documentation update or grammar correction.

4. Growth of Repository

If you know anyone who would love to help people new to open-source feel free to refer them for maintainers.

[internall]

Here I am, ready to help :)

[abhpd]

Here I am, ready to help :)

Okay 👍🏼

[adi-mohan]

I can help you with this!

[abhpd]

@adi-mohan Added 👍🏼

[adi-mohan]

Thanks @abhpd ! It would be great to point-out the responsibilities of a maintainer to the repo too . Like how much documentation you expect to be covered in a PR. I found that there are some anomalies in project structure too, so should I raise the issue, or you want to keep it that way.

[abhpd]

Dated: Oct 16 2020
Responsibilities of a maintainer will include the following

1. Handle PRs

1. Make sure the PR adds something new/improved/fixed then mark them "hacktoberfest-accepted ". If it’s spam, mark "invalid" and "spam".
2. PR should clearly mention what it is doing along with any issues if it applies.
3. PR file locations should match the hierarchy of the repository.
4. PR should have a proper commented explanation in the code file of the implementation and details.
5. If it follows all the above criteria, approved it to be merged.
6. If it needs change, review the code and add proper details of what needs to be changed and mark the PR changes requested and add tag "changes-needed", so it will be easier to track with a bunch of PRs.
7. Give preference to the PR on a first come first serve basis. that means if two PRs work on the same Algorithm like binary search, give preference to the first PR made.

2. Create Issues

1. Create issues for bugs, improvements, and hierarchy correction.
2. Make sure you provide details for the issue clearly mentioning what to do.

3. Help Everyone

After all this repository is mainly aimed to help people new to open-source.
Be generous to small PRs like documentation update or grammar correction.

4. Growth of Repository

If you know anyone who would love to help people new to open-source feel free to refer them for maintainers.

[abhpd]

@internall @adi-mohan

[abhpd]

@internall check your email for the invite. ✨

[0ne0rZer0]

Hey I am ready to help!

[internall]

@internall check your email for the invite. ✨

Thanks for the invite.
Unfortunately, I just saw it and now it's expired, could you re-send one?

[abhpd]

Hey I am ready to help!

@0ne0rZer0 Alright, Welcome.

[abhpd]

@internall check your email for the invite. ✨

Thanks for the invite.
Unfortunately, I just saw it and now it's expired, could you re-send one?

@internall sure!

[abhpd]

Dated: Oct 16 2020
Responsibilities of a maintainer will include the following

1. Handle PRs

1. Make sure the PR adds something new/improved/fixed then mark them "hacktoberfest-accepted ". If it’s spam, mark "invalid" and "spam".
2. PR should clearly mention what it is doing along with any issues if it applies.
3. PR file locations should match the hierarchy of the repository.
4. PR should have a proper commented explanation in the code file of the implementation and details.
5. If it follows all the above criteria, approved it to be merged.
6. If it needs change, review the code and add proper details of what needs to be changed and mark the PR changes requested and add tag "changes-needed", so it will be easier to track with a bunch of PRs.
7. Give preference to the PR on a first come first serve basis. that means if two PRs work on the same Algorithm like binary search, give preference to the first PR made.

1. Create Issues

1. Create issues for bugs, improvements, and hierarchy correction.
2. Make sure you provide details for the issue clearly mentioning what to do.

1. Help Everyone

After all this repository is mainly aimed to help people new to open-source.
Be generous to small PRs like documentation update or grammar correction.

1. Growth of Repository

If you know anyone who would love to help people new to open-source feel free to refer them for maintainers.

@0ne0rZer0 @internall

[NyorJa]

count me in

[abhpd]

@NyorJa Welcome! 🎉

[rudradave1]

I want to help!

[abhpd]

@rudradave1 Welcome, make sure to go through the Maintainer's responsibility I mentioned in the issue description once.

[pranjal021]

Happy to help!

[abhpd]

Welcome! @pranjal021 Please read through the description of this issue.

[CuriousRadhika]

Would love to help maintain this repository :)

[Aashish-cyber]

ready to help!

[anonymous372]

@abhpd, I wanna help as maintainer

[iam-monu]

@abhpd, I want to help!

[Itashamodi]

I can take up the responsibility of being a maintainer! @abhpd :)

[abhpd]

@CuriousRadhika @Aashish-cyber @anonymous372 @iam-monu @Itashamodi Thank you so much for showing interest. I Will surely consider you guys my first go-to if I need to replace any of our current maintainers or if I need to have more. For now, I'm figuring out the issue of our excluded project so merging PR is not my first concern.

[shubhamhere]

@abhpd I will be happy to take this responsibility : )

[ayushisingla]

I'll be happy to help!

[coderAbhik]

I got 8 years experience as developer, I can be a supporting hand as a reviewer. let me know. Thanks.

[SyedFasiuddin]

I have got 2 years of experience as a web developer. I think I can help you with this, Let me know.