# NumPy at PyData Global 2022 **Sprint mentors:** Rohit Goswami(@HaoZeke), Ganesh Kathiresan (@ganesh-k13), Mukulika Pahari (@Mukulikaa), Inessa Pawson (@inessapawson) **Code of Conduct** The NumPy Steering Council has made a strong commitment to creating an open, inclusive, and positive community. All attendees of NumPy community events must adhere to the NumPy Code of Conduct (https://numpy.org/code-of-conduct/). ### Helpful resources* - [Contributing to NumPy](https://numpy.org/devdocs/dev/index.html) - [Using gitpod for NumPy development](https://numpy.org/devdocs/dev/development_gitpod.html) - [Building from source](https://numpy.org/devdocs/user/building.html#building-locally) - [Building the documentation](https://numpy.org/devdocs/dev/howto_build_docs.html) **Help us improve these resources by submitting your suggestions in a corresponding issue tracker.* ### Choosing an issue * Comment on the issue that you are working on to avoid multiple people taking on the same issue. Feel free to work in groups on the same issue. * There are *a lot of* issues!:sweat: The selection labelled `sprintable` is focused on beginner-to-intermediate-friendly issues that are actionable and should be doable today. They are a good starting point for learning your way through NumPy building and bug fixing. [Click here to see the list of all the `sprintable` issues.](https://github.com/numpy/numpy/labels/sprintable) * If you would like to take on something a little more challenging, there are a lot of issues in the [main NumPy repository](https://github.com/numpy/numpy) to choose from. We recommend choosing issues that (from the title or labels) seem to be bugs, don't have more than 5 comments, and are no more than 6 months old - those are most likely to be actionable. ### Contributing to the NumPy documentation - [How to contribute to the NumPy documentation](https://numpy.org/devdocs/dev/howto-docs.html) - [Building the documentation](https://numpy.org/devdocs/dev/howto_build_docs.html) *Important:* If you are working on the NumPy documentation, remember to check against https://numpy.org/devdocs/index.html. This is the version of the documentation corresponding to the latest development version (aka what is merged on the main branch on GitHub). ### Writing a commit message Commit messages should follow a few basic rules that are outlined [here](https://numpy.org/doc/stable/dev/development_workflow.html#writing-the-commit-message). ### How to co-author commits If you worked in a pair/group, it's a good idea to acknowledge everyone's contribution in a commit message. Refer to the GitHub documentation on how to do it [here.](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) ________ ### Recommended resources about contributing to open source - [Talk *Sphinx for Python documentation*](https://youtu.be/tXWscUSYdBs) by Melissa Mendonça - [Guide to making open source contributions, for first-timers and veterans](https://opensource.guide/how-to-contribute/) - [Guide to pair programming](https://medium.com/@weblab_tech/pair-programming-guide-a76ca43ff389) - [Mentored Sprints Community Handbook](https://mentored-sprints.netlify.app/) ________ ### Let's connect and keep the conversation going! Join the NumPy contributor community **Slack workspace**: https://join.slack.com/t/numpy-team/shared_invite/zt-1gokbq56s-bvEpo10Ef7aHbVtVFeZv2w Attend a community event: [Numpy community events calendar](https://scientific-python.org/calendars/) Sign up to the NumPy **mailing list**: mail.python.org/mailman/listinfo/numpy-discussion Subscribe to the NumPy **YouTube** channel: https://www.youtube.com/c/NumPy_team Follow us on **Twitter**: [@numpy_team](https://twitter.com/numpy_team) Follow us on **LinkedIn**: https://www.linkedin.com/company/numpy/