You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CODE_OF_CONDUCT.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,13 +11,14 @@
11
11
12
12
Use your best judgement. If it will possibly make others uncomfortable, do not post it.
13
13
14
-
***Be respectful.** Disagreement is not an opportunity to attack someone else's thoughts or opinions. Although views may differ, remember to approach every situation with patience and care.
15
-
***Be considerate.** Think about how your contribution will affect others in the community.
14
+
***Be respectful.** Disagreement is not an opportunity to attack someone else's thoughts or opinions. Although views may differ, remember to approach every situation with patience and care.
15
+
***Be considerate.** Think about how your contribution will affect others in the community.
16
16
***Be open minded.** Embrace new people and new ideas. Our community is continually evolving and we welcome positive change.
17
17
18
18
If you believe someone is violating the code of conduct, we ask that you report it by emailing [hello@p5js.org](mailto:hello@p5js.org). Please include your name and a description of the incident, and we will get back to you ASAP.
19
19
20
-
Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the p5.js Team may take any action they deem appropriate, up to and including expulsion from all p5.js spaces and identification of the participant as a harasser to other p5.js members or the general public.
20
+
Participants asked to stop any harassing behavior are expected to comply immediately. If a participant engages in harassing behavior, the p5.js Team may take any action they deem appropriate, up to and including expulsion from all p5.js spaces and identification of the participant as a harasser to other p5.js members or the general public.
21
21
22
22
## Also
23
+
23
24
* You can read our [community statement](http://p5js.org/community/) on our website.
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+30-21Lines changed: 30 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,22 @@
1
1
# Contributing to the p5.js Web Editor
2
2
3
-
Hello! We welcome community contributions to the p5.js Web Editor. Contributing takes many forms and doesn't have to be **writing code**, it can be **report bugs**, **proposing new features**, **creating UI/UX designs**, and **updating documentation**.
3
+
Hello! We welcome community contributions to the p5.js Web Editor. Contributing takes many forms and doesn't have to be **writing code**, it can be **report bugs**, **proposing new features**, **creating UI/UX designs**, and **updating documentation**.
4
4
5
5
Here are links to all the sections in this document:
6
6
7
7
<!-- If you change any of the headings in this document, remember to update the table of contents. -->
8
8
9
-
-[Code of Conduct](#code-of-conduct)
10
-
-[How Can I Contribute ?](#how-can-i-contribute?)
11
-
-[First Timers](#first-timers)
12
-
-[Want something more challenging](#want-something-more-challenging)
13
-
-[Feature Enhancement](#feature-enhancement)
14
-
-[Creating a Pull request](#creating-a-pull-request)
15
-
--[Tips](#tips)
9
+
-[Contributing to the p5.js Web Editor](#contributing-to-the-p5js-web-editor)
10
+
-[Code of Conduct](#code-of-conduct)
11
+
-[How Can I Contribute?](#how-can-i-contribute)
12
+
-[First Timers](#first-timers)
13
+
-[Milestones](#milestones)
14
+
-[Project Ideas](#project-ideas)
15
+
-[Issue Search and Tagging](#issue-search-and-tagging)
@@ -23,21 +27,29 @@ Please follow the guidelines mentioned at [CODE OF CONDUCT.md](https://github.co
23
27
### First Timers
24
28
For first-time contributors or those who want to start with a small task: [check out our list of good first bugs](https://github.com/processing/p5.js-web-editor/labels/good%20first%20issue). First read the github discussion on that issue and find out if there's currently a person working on that or not. If no one is working on it or if there has was one claimed to but has not been active for a while, ask if it is up for grabs. It's okay to not know how to fix an issue and feel free to ask questions about to approach the problem! We are all just here to learn and make something awesome. Someone from the community would help you out and these are great issues for learning about the web editor, its file structure and its development process.
25
29
26
-
### Want something more challenging
27
-
If you're already familiar with the project or would like take on something a little more challenging, please take a look at the [priority: high](https://github.com/processing/p5.js-web-editor/labels/priority%3Ahigh) issues.
30
+
### Milestones
31
+
A good place to check for tickets to work on is [milestones](https://github.com/processing/p5.js-web-editor/milestones), as miletones have a due date, and will give you a sense of tickets the tickets that maintainers would like to be completed sooner rather than later.
28
32
29
-
### Feature Enhancement
30
-
If you want to work on building new things, please take a look at [type: feature](https://github.com/processing/p5.js-web-editor/labels/type%3Afeature).
33
+
### Project Ideas
34
+
If you're looking for inspiration for Google Summer of Code or a bigger project, there's a [project list](https://github.com/processing/processing/wiki/Project-List#p5js-web-editor) maintained on the Processing wiki.
31
35
32
-
If you'd like to work on a bug, please comment on it to let the maintainers know.
33
-
If someone else has already commented and taken up that bug, please refrain from working on it and submitting a PR without asking the maintainers as it leads to unnecessary duplication of effort.
36
+
### Issue Search and Tagging
37
+
If you're looking for issues to work on, a good place to start is with tickets labeled [high priority](https://github.com/processing/p5.js-web-editor/labels/priority%3Ahigh). You can also look for tickets that are [feature enhancements](https://github.com/processing/p5.js-web-editor/labels/type%3Afeature), [bug fixes](https://github.com/processing/p5.js-web-editor/labels/type%3Abug), and a few other tags.
34
38
35
-
### Contribution guides
39
+
If you feel like an issue is tagged incorrectly (e.g. it's low priority and you think it should be high), please update the issue!
40
+
41
+
### Beginning Work
42
+
43
+
If you'd like to work on an issue, please comment on it to let the maintainers know. If someone else has already commented and taken up that issue, please refrain from working on it and submitting a PR without asking the maintainers as it leads to unnecessary duplication of effort.
44
+
45
+
Then, follow the [installation guide](https://github.com/processing/p5.js-web-editor/blob/master/developer_docs/installation.md) to get the project building and working on your computer.
Good commit messages serve at least three important purposes:
43
55
@@ -69,9 +81,6 @@ Structure your commit message like this:
69
81
* Always leave the second line blank.
70
82
* Be as descriptive as possible in the description. It helps reasoning about the intention of commits and gives more context about why changes happened.
71
83
72
-
Tips
73
-
----
74
-
75
-
* If it seems difficult to summarize what your commit does, it may be because it includes several logical changes or bug fixes, and are better split up into several commits using `git add -p`.
76
-
84
+
## Tips
77
85
86
+
* If it seems difficult to summarize what your commit does, it may be because it includes several logical changes or bug fixes, and are better split up into several commits using `git add -p`.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,22 @@
1
1
<!--
2
2
Hi there! If you are here to report a bug, or to discuss a feature (new or existing), you can use the below template to get started quickly. Fill out all those parts which you're comfortable with, and delete the remaining ones.
3
-
4
-
To check any option, replace the "[ ]" with a "[x]". Be sure to check out how it looks in the Preview tab!
5
-
6
-
Feel free to remove any portion of the template that is not relevant for your issue.
7
3
-->
8
4
9
5
#### Nature of issue?
10
6
11
-
-[ ] Found a bug
12
-
-[ ] Existing feature enhancement
13
-
-[ ] New feature request
7
+
<!-- Select any one issue and delete the other two -->
8
+
9
+
- Found a bug
10
+
- Existing feature enhancement
11
+
- New feature request
14
12
15
13
<!-- If you found a bug, the following information might prove to be helpful for us. Simply remove whatever you can't determine/don't know. -->
16
14
#### Details about the bug:
17
15
18
16
- Web browser and version: <!-- On Chrome/FireFox/Opera you can enter "about:" in the address bar to find out the version -->
19
17
- Operating System: <!-- Ex: Windows/MacOSX/Linux along with version -->
20
-
- Steps to reproduce this:
18
+
- Steps to reproduce this bug:
19
+
21
20
<!-- Include a simple code snippet that demonstrates the problem, along with any console errors produced. If this isn't possible, then simply describe the issue as best you can! Feel free to link to the web editor or include pictures or a video. -->
22
21
23
22
<!-- If you want to enhance an existing feature, please describe here, otherwise remove this section -->
Before your pull request is reviewed and merged, please ensure that:
1
+
I have verified that this pull request:
2
2
3
-
*[ ] there are no linting errors -- `npm run lint`
4
-
*[ ] your code is in a uniquely-named feature branch and has been rebased on top of the latest master. If you're asked to make more changes, make sure you rebase onto master then too!
5
-
*[ ] your pull request is descriptively named and links to an issue number, i.e. `Fixes #123`
6
-
7
-
Thank you!
3
+
*[ ] has no linting errors (`npm run lint`)
4
+
*[ ] is from a uniquely-named feature branch and has been rebased on top of the latest master. (If I was asked to make more changes, I have made sure to rebase onto master then too)
5
+
*[ ] is descriptively named and links to an issue number, i.e. `Fixes #123`
# Configuration for welcome - https://github.com/behaviorbot/welcome
2
+
3
+
# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
4
+
5
+
# Comment to be posted to on first time issues
6
+
newIssueWelcomeComment: >
7
+
Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, be sure to follow the issue template if you haven't already.
8
+
9
+
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
10
+
11
+
# Comment to be posted to on PRs from first time contributors in your repository
12
+
newPRWelcomeComment: >
13
+
🎉 Thanks for opening this pull request! Please check out our [contributing guidelines](https://github.com/processing/p5.js-web-editor/blob/master/CONTRIBUTING.md) if you haven't already.
14
+
15
+
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
16
+
17
+
# Comment to be posted to on pull requests merged by a first time user
0 commit comments