Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Welcome Contributors #1084

Closed
anushkrishnav opened this issue Sep 24, 2020 · 1 comment
Closed

Welcome Contributors #1084

anushkrishnav opened this issue Sep 24, 2020 · 1 comment

Comments

@anushkrishnav
Copy link
Contributor

anushkrishnav commented Sep 24, 2020

Hello, Everyone βœ¨πŸ™Œ

Thanks for showing your interest in being a part of this ever-growing community πŸ’₯

We are super delighted to have you on board for your Contributions on NeoAlgo πŸ™Œ

Project Maintainers:

Name πŸ“› Social Media #️⃣ Github πŸ±β€πŸ’»
Aanisha Bhattacharyyai LinkedIn Github
Abhinav Anand LinkedIn Github
Ankit Aggarwal Linkedln Github
AnushKrishnav Website Github
Harsh Bardhan Mishra Website Github
Rajiv Ranjan Singh LinkedIn Github
Ricardo Prins Website Github
Syed Farhan Ahmad LinkedIn Github
Vijaya Gajanan Buddha LinkedIn Github

Events :

Here are some 12 Rules, you should be following while working on an Open-Source to have a great experience during the whole process:

  • Be Nice, Be Respectful (BNBR)
  • Check if the Issue you created, exists or not.
  • Make proper commit messages and document your PR well.
  • Always add Comments in your Code and explain it at points if possible add Doctest.
  • Dynamic Input is always preferred over static Driver Code.
  • Squash your commits before you push them.
  • Always create a Pull Request from a Branch; Never from the Master.
  • Follow proper Code conventions. Using I, j in Loops shows a poor understanding of Code Quality. Use proper Variable, Function Names.
  • Issues would be served on a "First Come, First Serve" basis.
  • Issues would be tagged as Easy, Medium, Hard. Scores would be assigned to the difficulty of the Issue you solve.
  • Code would be reviewed by Maintainers before they are merged. Every PR requires 3 Reviews.
  • No person can take up more than 2 Issues at a single point of time.

Regards,
Team TesseractCoding πŸ€—

@iamrajiv iamrajiv pinned this issue Sep 25, 2020
@github-actions github-actions bot closed this as completed Dec 4, 2020
@iamrajiv iamrajiv reopened this Dec 5, 2020
@bhav09 bhav09 unpinned this issue Mar 10, 2021
@bhav09 bhav09 pinned this issue Mar 10, 2021
Repository owner deleted a comment from github-actions bot Mar 19, 2021
@github-actions
Copy link

Please reopen this issue once you add more information and updates here. If this is not the case and you need some help, feel free to seek help from our Telegram or ping one of the reviewers. Thank you for your contributions!

Repository owner locked and limited conversation to collaborators May 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants