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

WIP: Contributor Journey Comics #600

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/en/contribute.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,23 @@ title: Contribute to NumPy
sidebar: false
---

# WIP for Draft PR: not final placement

**Markdown Image test:**
![A comic showing how people can start contributing to NumPy](/images/content_images/contribute_journey/Numpy_Adventure.png)

**Hugo image test:**
{{< figure src="/images/content_images/contribute_journey/Numpy_Adventure.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A comic showing how people can start contributing to NumPy" >}}

**Panel by panel breakdown**

| Panel | Image Description | Copy/Script |
|---|---|---|
| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_tracks.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing how different tracks in NumPy" width="500" >}}| A person excitedly holding up a sword. They are standing next to the NumPy logo and the various tracks in NumPy. The tracks are laid in a diverging tree-like pattern. The first track, the "Contributor Track", eventually unlocks the second track, the "Review Track", which unlocks the "Merge Track", which unlocks the last track, the "Maintainer Track". These tracks are represented by dots and the unlocking as keys. Each track is personified with a person wearing a hat. | Choose your adventure! Start as a contributor! Once you gain enough experience, you can become a reviewer! And perhaps with enough experience and mentorship, you can merge PRs. |
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_tracks.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing how different tracks in NumPy" width="500" >}}| A person excitedly holding up a sword. They are standing next to the NumPy logo and the various tracks in NumPy. The tracks are laid in a diverging tree-like pattern. The first track, the "Contributor Track", eventually unlocks the second track, the "Review Track", which unlocks the "Merge Track", which unlocks the last track, the "Maintainer Track". These tracks are represented by dots and the unlocking as keys. Each track is personified with a person wearing a hat. | Choose your adventure! Start as a contributor! Once you gain enough experience, you can become a reviewer! And perhaps with enough experience and mentorship, you can merge PRs. |
| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_tracks.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing how different tracks in NumPy" width="500" >}}| A person excitedly holding up a sword. They are standing next to the NumPy logo and the various tracks in NumPy. The tracks are laid in a diverging tree-like pattern. The first track, the "Contributor Track", eventually unlocks the second track, the "Review Track", which unlocks the "Merge Track", which unlocks the last track, the "Maintainer Track". These tracks are represented by dots and the unlocking as keys. Each track is personified with a person wearing a hat. | Choose your adventure! Start as a contributor! Once you gain enough experience, you can become a reviewer! And perhaps with enough experience and mentorship, you can merge Pull Requests (PRs). |

Our target audience, newcomers, may not know the acronym PRs.

| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_maintainers.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing the role and importance of maintainers." width="500" >}} | A contributor with merge permissions is kneeling down, using their torch to light a campfire. Around the campfire are two maintainers. One is excitedly waving their arms, the other watches on proud and serene. | If you feel that fire within you, to keep NumPy going, you can join as a maintainer! It's not a quick or easy path. But it's one worth having. Of course, not everyone should or wants to be a maintainer! You may decide to stay a regular contributor. Or review PRs every now and then. |
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe... we can add another illlustration to show how contributors can do different roles, represented by "wearing different hats"? So a contributor wearing the Reviewer bowler hat one panel, then wearing the Merger feather cap in the next panel!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something like this:
image
image
One person wearing multiple hats. And then switching them out.

| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_call_to_action.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing different calls to action." width="500" >}} | A person looking at a computer screen which shows a NumPy community call. An icon of Slack. | Your NumPy adventure is yours to choose! And the NumPy community wil be there with you every step of the way! Start your adventure by joining the NumPy Slack! Or join our community call (every 2 weeks, Wednesday at 6pm UTC). For calendars and links, check out: NumPy.org/community |
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_call_to_action.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing different calls to action." width="500" >}} | A person looking at a computer screen which shows a NumPy community call. An icon of Slack. | Your NumPy adventure is yours to choose! And the NumPy community wil be there with you every step of the way! Start your adventure by joining the NumPy Slack! Or join our community call (every 2 weeks, Wednesday at 6pm UTC). For calendars and links, check out: NumPy.org/community |
| {{< figure src="/images/content_images/contribute_journey/Numpy_Adventure_call_to_action.png" caption="**NumPy Contributor Journey: Choose Your Adventure!**" alt="A panel showing different calls to action." width="500" >}} | A person looking at a computer screen which shows a NumPy community call. An icon of Slack. | Your NumPy adventure is yours to choose! And the NumPy community wil be there with you every step of the way! Start your adventure by joining the NumPy Slack! Or join our NumPy NewComer Hour, every other Thursday, 2pm UTC. For calendars and links, check out: NumPy.org/community |

I think we should direct newcomers to Newcomers Hour. I think it would be less intimidating.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree. To me the main community calls is the best way in. That way people can better understand how we follow-up and talk about issues, PRs and community events, with active community members.


---
The NumPy project welcomes your expertise and enthusiasm!
Your choices aren't limited to programming, as you can
see below there are many areas where we need **your** help.
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.