Skip to content

Commit

Permalink
Merge branch 'main' of https://github.com/processing/p5.js into main
Browse files Browse the repository at this point in the history
  • Loading branch information
Ayush23Dash committed Sep 16, 2023
2 parents 58d345d + 88ea17e commit c526260
Show file tree
Hide file tree
Showing 26 changed files with 2,343 additions and 1,147 deletions.
24 changes: 24 additions & 0 deletions .all-contributorsrc
Original file line number Diff line number Diff line change
Expand Up @@ -5230,6 +5230,30 @@
"code",
"bug"
]
},
{
"login": "Ankush263",
"name": "Ankush Banik",
"avatar_url": "https://avatars.githubusercontent.com/u/86042508?v=4",
"profile": "https://my-portfolio-ankush263.vercel.app/",
"contributions": [
"bug",
"code",
"talk",
"question"
]
},
{
"login": "tetunori",
"name": "tetunori",
"avatar_url": "https://avatars.githubusercontent.com/u/14086390?v=4",
"profile": "https://qiita.com/tetunori_lego",
"contributions": [
"blog",
"code",
"example",
"tool"
]
}
],
"repoType": "github",
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/labeler.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ jobs:
triage:
runs-on: ubuntu-latest
steps:
- uses: github/issue-labeler@v2.0
- uses: github/issue-labeler@v3.2
with:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
configuration-path: .github/labeler.yml
Expand Down
8 changes: 6 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
[![npm version](https://badge.fury.io/js/p5.svg)](https://www.npmjs.com/package/p5)
[![All Contributors](https://img.shields.io/github/all-contributors/processing/p5.js?color=ee8449&style=flat-square)](#contributors-)
[![All Contributors](https://img.shields.io/github/all-contributors/processing/p5.js?color=ee8449&style=flat-square)](#contributors)


# [p5.js](https://p5js.org)
Expand Down Expand Up @@ -93,7 +93,7 @@ Lead/Mentor Alumni

## Contributors

We recognize all types of contributions. This project follows the [all-contributors](https://github.com/kentcdodds/all-contributors) specification and the [Emoji Key](https://allcontributors.org/docs/en/emoji-key) ✨ for contribution types. Instructions to add yourself or add contribution emojis to your name are [here](https://github.com/processing/p5.js/issues/2309). You can also post an issue or comment on a pull request with the text: `@all-contributors please add @YOUR-USERNAME for THING(S)` and our nice bot will add you.
We recognize all types of contributions. This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification and the [Emoji Key](https://allcontributors.org/docs/en/emoji-key) ✨ for contribution types. Instructions to add yourself or add contribution emojis to your name are [here](https://github.com/processing/p5.js/issues/2309). You can also post an issue or comment on a pull request with the text: `@all-contributors please add @YOUR-USERNAME for THING(S)` and our nice bot will add you.

<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore-start -->
Expand Down Expand Up @@ -898,6 +898,10 @@ We recognize all types of contributions. This project follows the [all-contribut
<td align="center" valign="top" width="16.66%"><a href="https://github.com/yulicai"><img src="https://avatars.githubusercontent.com/u/14118438?v=4?s=120" width="120px;" alt="Yolonanido"/><br /><sub><b>Yolonanido</b></sub></a><br /><a href="#eventOrganizing-yulicai" title="Event Organizing">📋</a></td>
<td align="center" valign="top" width="16.66%"><a href="https://github.com/SableRaf"><img src="https://avatars.githubusercontent.com/u/290261?v=4?s=120" width="120px;" alt="Raphaël de Courville"/><br /><sub><b>Raphaël de Courville</b></sub></a><br /><a href="#eventOrganizing-SableRaf" title="Event Organizing">📋</a> <a href="#video-SableRaf" title="Videos">📹</a> <a href="#ideas-SableRaf" title="Ideas, Planning, & Feedback">🤔</a> <a href="#promotion-SableRaf" title="Promotion">📣</a></td>
<td align="center" valign="top" width="16.66%"><a href="https://github.com/mykongee"><img src="https://avatars.githubusercontent.com/u/10676303?v=4?s=120" width="120px;" alt="Mike "/><br /><sub><b>Mike </b></sub></a><br /><a href="https://github.com/processing/p5.js/commits?author=mykongee" title="Code">💻</a> <a href="https://github.com/processing/p5.js/issues?q=author%3Amykongee" title="Bug reports">🐛</a></td>
<td align="center" valign="top" width="16.66%"><a href="https://my-portfolio-ankush263.vercel.app/"><img src="https://avatars.githubusercontent.com/u/86042508?v=4?s=120" width="120px;" alt="Ankush Banik"/><br /><sub><b>Ankush Banik</b></sub></a><br /><a href="https://github.com/processing/p5.js/issues?q=author%3AAnkush263" title="Bug reports">🐛</a> <a href="https://github.com/processing/p5.js/commits?author=Ankush263" title="Code">💻</a> <a href="#talk-Ankush263" title="Talks">📢</a> <a href="#question-Ankush263" title="Answering Questions">💬</a></td>
</tr>
<tr>
<td align="center" valign="top" width="16.66%"><a href="https://qiita.com/tetunori_lego"><img src="https://avatars.githubusercontent.com/u/14086390?v=4?s=120" width="120px;" alt="tetunori"/><br /><sub><b>tetunori</b></sub></a><br /><a href="#blog-tetunori" title="Blogposts">📝</a> <a href="https://github.com/processing/p5.js/commits?author=tetunori" title="Code">💻</a> <a href="#example-tetunori" title="Examples">💡</a> <a href="#tool-tetunori" title="Tools">🔧</a></td>
</tr>
</tbody>
</table>
Expand Down
4 changes: 2 additions & 2 deletions contributor_docs/contributor_guidelines.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Similarly, if you have come across an issue or joined in discussions of an issue
You should not "jump the queue" by filing a PR for an issue that either someone else has indicated willingness to submit a contribution or has already been assigned to someone else. We will always prioritise "first assigned first serve" order for accepting code contribution for an issue, if you file a PR for an issue while someone else is still working on the same issue, your PR will be closed. If you see that it has been a few months since last activity on an issue with an assigned individual, you can check in with them by leaving a polite comment on the issue asking for progress and if they need help with the implementation. We generally allow for fairly long time frame for people to work on their contributions as we understand that most people will often be working on a volunteer basis or it simply takes more time for them to work on the feature; similarly, you should work at your own pace and be confident that there is no hard time limit on how long you can spend working on something. That being said, if you are having trouble with any aspect of your code contribution, do not hesitate to ask for help in the issue, the stewards and maintainers, as well as members of our community, will do their best to guide you!

## Quick Get Started For Developers
If you want to work/contribute to P5's🌸 codebase as a developer, either directly for improving P5 or for improving it's sub projects like [Friendly Error Systems](https://github.com/processing/p5.js/blob/main/contributor_docs/friendly_error_system.md), you can follow the following steps directly :
If you want to work/contribute to p5.js'🌸 codebase as a developer, either directly for improving p5.js or for improving it's sub projects like [Friendly Error Systems](https://github.com/processing/p5.js/blob/main/contributor_docs/friendly_error_system.md), you can follow the following steps directly :

1. Create a fork of p5.js.
2. Clone your locally created fork.
Expand Down Expand Up @@ -246,4 +246,4 @@ Once a steward has reviewed your PR, one of two things may happen: 1. Your PR is

If changes are requested of your PR and you are able to make those changes, follow the [same process as before](#git-workflow) but just continue from your local copy of the repo and relevant branch, make those changes, commit them into git, and push them to your forked remote repo. Once you have pushed additional commits to your forked remote repo, you will see that the new commits automatically show up in the PR. Leave a comment in the PR to let the reviewer know you have made the changes requested and if no additional changes are needed, your PR will be merged!

---
---
3 changes: 3 additions & 0 deletions contributor_docs/project_wrapups/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@ This folder contains wrap-up reports from p5.js related [Google Summer of Code](

## Google Summer of Code

### Google Summer of Code 2023
* [Mobile/Responsive Design Implementation of p5.js Web Editor](https://github.com/processing/p5.js/blob/main/contributor_docs/project_wrapups/dewansDT_gsoc_2023.md) by Dewansh Thakur, 2023

### Google Summer of Code 2022
* [p5 /teach reorganize & update](https://github.com/processing/p5.js/blob/main/contributor_docs/project_wrapups/graciazhang_gsoc_2022.md) by Gracia Zhang, 2022
* [p5xr Immersive Session Process and Controller API update](https://github.com/processing/p5.js/blob/main/contributor_docs/project_wrapups/smrghsh_gsoc_2022.md) by Samir Ghosh, 2022
Expand Down
Loading

0 comments on commit c526260

Please sign in to comment.