From af28f0b5d11ebb763d914ec7f1ba9f9b9676b06c Mon Sep 17 00:00:00 2001 From: noatamir <6564007+noatamir@users.noreply.github.com> Date: Tue, 16 Aug 2022 18:47:48 +0200 Subject: [PATCH 1/3] adding the new contributor meeting --- doc/devel/contributing.rst | 41 ++++++++++++++++++++++++++++++-------- 1 file changed, 33 insertions(+), 8 deletions(-) diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst index 578cf8f28f58..026532fdbbb7 100644 --- a/doc/devel/contributing.rst +++ b/doc/devel/contributing.rst @@ -12,19 +12,44 @@ is expected to abide by our The project is hosted on https://github.com/matplotlib/matplotlib +Do I really have something to contribute to Matplotlib? +------------------------------------------------------- +1,000% 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 section to learn more. + + +Get Connected +============= + Contributor incubator -===================== - -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 +--------------------- +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 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: From 9e1bfa8599287f03ecb815b71acd9cd68c917dc7 Mon Sep 17 00:00:00 2001 From: noatamir <6564007+noatamir@users.noreply.github.com> Date: Wed, 24 Aug 2022 23:45:22 +0200 Subject: [PATCH 2/3] Fixed rst spacing + review feedback. --- doc/devel/contributing.rst | 78 +++++++++++++++++++++----------------- 1 file changed, 43 insertions(+), 35 deletions(-) diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst index 026532fdbbb7..d7c7433d9534 100644 --- a/doc/devel/contributing.rst +++ b/doc/devel/contributing.rst @@ -12,44 +12,50 @@ is expected to abide by our The project is hosted on https://github.com/matplotlib/matplotlib +Get Connected +============= + Do I really have something to contribute to Matplotlib? ------------------------------------------------------- -1,000% 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 section to learn more. +100% yes. There are so many ways to contribute to our community. -Get Connected -============= +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 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. +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! +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: @@ -58,19 +64,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: +`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. @@ -610,3 +617,4 @@ example code you can load it into a file handle with:: import matplotlib.cbook as cbook fh = cbook.get_sample_data('mydata.dat') + From ff9b0af784e4057b5923d8d6e3db81833eaa06f2 Mon Sep 17 00:00:00 2001 From: noatamir <6564007+noatamir@users.noreply.github.com> Date: Thu, 25 Aug 2022 11:16:27 +0200 Subject: [PATCH 3/3] review feedback on links --- doc/devel/contributing.rst | 40 +++++++++++++++++++------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst index d7c7433d9534..7d3a58d55d61 100644 --- a/doc/devel/contributing.rst +++ b/doc/devel/contributing.rst @@ -36,9 +36,10 @@ 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. +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 ------------------------ @@ -49,13 +50,14 @@ 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! +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: @@ -63,15 +65,14 @@ 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. @@ -617,4 +618,3 @@ example code you can load it into a file handle with:: import matplotlib.cbook as cbook fh = cbook.get_sample_data('mydata.dat') -