From f7a12a4ecd2b2015019b5b6de6a406d5965d08f1 Mon Sep 17 00:00:00 2001 From: Elliott Sales de Andrade Date: Thu, 25 Aug 2022 14:57:27 -0400 Subject: [PATCH] Backport PR #23639: Adding the new contributor meeting --- doc/devel/contributing.rst | 75 +++++++++++++++++++++++++++----------- 1 file changed, 54 insertions(+), 21 deletions(-) diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst index dfdc03d0eeef..2743424423d3 100644 --- a/doc/devel/contributing.rst +++ b/doc/devel/contributing.rst @@ -12,19 +12,52 @@ is expected to abide by our The project is hosted on https://github.com/matplotlib/matplotlib -Contributor incubator -===================== +Get Connected +============= + +Do I really have something to contribute to Matplotlib? +------------------------------------------------------- -If you are interested in becoming a regular contributor to Matplotlib, but -don't know where to start or feel insecure about it, you can join our non-public -communication channel for new contributors. To do so, please go to `gitter -`_ and ask to be added to '#incubator'. -This is a private gitter room moderated by core Matplotlib developers where you can -get guidance and support for your first few PRs. This is a place you can ask questions -about anything: how to use git, github, how our PR review process works, technical questions -about the code, what makes for good documentation or a blog post, how to get involved involved -in community work, or get "pre-review" on your PR. +100% yes. There are so many ways to contribute to our community. +When in doubt, we recommend going together! Get connected with our community of +active contributors, many of whom felt just like you when they started out and +are happy to welcome you and support you as you get to know how we work, and +where things are. Take a look at the next sections to learn more. + +Contributor incubator +--------------------- + +The incubator is our non-public communication channel for new contributors. It +is a private gitter room moderated by core Matplotlib developers where you can +get guidance and support for your first few PRs. It's a place you can ask +questions about anything: how to use git, github, how our PR review process +works, technical questions about the code, what makes for good documentation +or a blog post, how to get involved in community work, or get +"pre-review" on your PR. + +To join, please go to our public `gitter +`_ community channel, and ask to be +added to '#incubator'. One of our core developers will see your message and will +add you. + +New Contributors meeting +------------------------ + +Once a month, we host a meeting to discuss topics that interest new +contributors. Anyone can attend, present, or sit in and listen to the call. +Among our attendees are fellow new contributors, as well as maintainers, and +veteran contributors, who are keen to support onboarding of new folks and +share their experience. You can find our community calendar link at the +`Scientific Python website `_, and +you can browse previous meeting notes on `github +`_. +We recommend joining the meeting to clarify any doubts, or lingering +questions you might have, and to get to know a few of the people behind the +GitHub handles 😉. You can reach out to @noatamir on `gitter +`_ for any clarifications or +suggestions. We <3 feedback! .. _new_contributors: @@ -32,20 +65,20 @@ Issues for new contributors --------------------------- While any contributions are welcome, we have marked some issues as -particularly suited for new contributors by the label -`good first issue `_ -These are well documented issues, that do not require a deep understanding of -the internals of Matplotlib. The issues may additionally be tagged with a -difficulty. ``Difficulty: Easy`` is suited for people with little Python experience. -``Difficulty: Medium`` and ``Difficulty: Hard`` require more programming experience. -This could be for a variety of reasons, among them, though not necessarily all at -the same time: +particularly suited for new contributors by the label `good first issue +`_. These +are well documented issues, that do not require a deep understanding of the +internals of Matplotlib. The issues may additionally be tagged with a +difficulty. ``Difficulty: Easy`` is suited for people with little Python +experience. ``Difficulty: Medium`` and ``Difficulty: Hard`` require more +programming experience. This could be for a variety of reasons, among them, +though not necessarily all at the same time: - The issue is in areas of the code base which have more interdependencies, or legacy code. - It has less clearly defined tasks, which require some independent - exploration, making suggestions, or follow-up discussions to clarify a good path - to resolve the issue. + exploration, making suggestions, or follow-up discussions to clarify a good + path to resolve the issue. - It involves Python features such as decorators and context managers, which have subtleties due to our implementation decisions.