diff --git a/.github/ISSUE_TEMPLATE/1-p5.js-2.0-RFC-proposal.yml b/.github/ISSUE_TEMPLATE/1-p5.js-2.0-RFC-proposal.yml deleted file mode 100644 index f36459c09e..0000000000 --- a/.github/ISSUE_TEMPLATE/1-p5.js-2.0-RFC-proposal.yml +++ /dev/null @@ -1,98 +0,0 @@ -name: 📃 p5.js 2.0 RFC Proposal -description: This template is for submitting a proposal to the p5.js 2.0 RFC. -title: "[p5.js 2.0 RFC Proposal]: " -labels: [p5.js 2.0] -body: - - type: textarea - attributes: - label: Increasing access - description: How would this proposal help [increase access](https://github.com/processing/p5.js/blob/main/contributor_docs/access.md) to p5.js? (If you're not sure, you can type "Unsure" here and let others from the community offer their thoughts.) - validations: - required: true - - type: markdown - attributes: - value: | - ### Acceptance criteria - The [p5.js 2.0 RFC](https://github.com/processing/p5.js/blob/dev-2.0/rfc_p5js_2.md) is a compilation of proposals for the next major version of p5.js. - - **✖️ New features**: In order to focus the community's efforts, proposals for new features will typically not be accepted into the RFC. A [New Feature Request](https://github.com/processing/p5.js/issues/new?assignees=&labels=Feature+Request&projects=&template=feature-request.yml) may still be submitted, but it will only be considered after the release of p5.js 2.0. - - **✔️Existing features**: This proposal will be accepted if the community determines it would improve an existing feature through a breaking change, a systemic change, or an overdue change. - - type: checkboxes - id: type-of-change - attributes: - label: Which types of changes would be made? - description: Please select at least one. - options: - - label: Breaking change (Add-on libraries or sketches will work differently even if their code stays the same.) - - label: Systemic change (Many features or contributor workflows will be affected.) - - label: Overdue change (Modifications will be made that have been desirable for a long time.) - - label: Unsure (The community can help to determine the type of change.) - - type: checkboxes - id: sub-area - attributes: - label: Most appropriate sub-area of p5.js? - description: Please select at least one. - options: - - label: Accessibility - - label: Color - - label: Core/Environment/Rendering - - label: Data - - label: DOM - - label: Events - - label: Image - - label: IO - - label: Math - - label: Typography - - label: Utilities - - label: WebGL - - label: Build process - - label: Unit testing - - label: Internationalization - - label: Friendly errors - - label: Other (specify if possible) - - type: textarea - attributes: - label: What's the problem? - description: Describe the problem this proposal aims to solve. (Use as much space as you need.) - validations: - required: true - - type: textarea - attributes: - label: What's the solution? - description: Describe how you would solve the problem. (For large proposals, a summary is fine; this proposal can link to sub-issues for details.) - validations: - required: true - - type: textarea - attributes: - label: Pros (updated based on community comments) - description: Indicate the advantages of implementing this proposal. If the community identifies more advantages in the comments, please add them. - value: | - Example list: - * **Consistency:** This proposal increases API consistency by... - * **Readability:** This proposal makes the source code more readable by... - * Other advantages... - validations: - required: true - - type: textarea - attributes: - label: Cons (updated based on community comments) - description: Indicate the disadvantages of implementing this proposal, if you know of any. If the community identifies disadvantages in the comments, please add them. - placeholder: None so far... - validations: - required: true - - type: dropdown - attributes: - label: Proposal status - options: - - Under review - - Accepted - - Not accepted - default: 0 - validations: - required: true - - type: markdown - attributes: - value: | - ### Implementation process - If this proposal is accepted, it will be included in the p5.js 2.0 RFC. A contributor who has participated in the discussion will then be assigned to lead the implementation, which will happen on the [dev-2.0](https://github.com/processing/p5.js/tree/dev-2.0) branch. diff --git a/.github/ISSUE_TEMPLATE/1-p5.js-2.0-bug-report.yml b/.github/ISSUE_TEMPLATE/1-p5.js-2.0-bug-report.yml new file mode 100644 index 0000000000..bb04352fa9 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/1-p5.js-2.0-bug-report.yml @@ -0,0 +1,81 @@ +name: 📃 p5.js 2.0 Beta Bug Report +description: This template is for submitting a bug report for bugs found in the p5.js 2.0 beta releases. +title: "[p5.js 2.0 Beta Bug Report]: " +labels: [p5.js 2.0] +body: + - type: markdown + attributes: + value: | + ### What falls under this category? + There has been many changes to p5.js in 2.0 that is currently released as beta versions. If you suspect there may be a bug, please follow the below steps before opening a bug report using this template: + + 1. There are some differences in behavior between p5.js 1.x and 2.0 beta, please check the changelog and/or [proposal list](https://github.com/orgs/processing/projects/21) to see if the difference in behavior is intended. If in doubt, feel free to open the issue anyway and ask. + 2. Breaking changes may still happen between beta versions, please make sure to include the full beta version number and use the latest beta release where possible. + 3. We are not considering any new proposal for p5.js 2.0 at this stage and if you would like to request new features, please use the "New feature request" issue template. + 4. The documentation and examples may be outdated at this stage while we work on updating them. + - type: checkboxes + id: sub-area + attributes: + label: Most appropriate sub-area of p5.js? + description: You may select more than one. + options: + - label: Accessibility + - label: Color + - label: Core/Environment/Rendering + - label: Data + - label: DOM + - label: Events + - label: Image + - label: IO + - label: Math + - label: Typography + - label: Utilities + - label: WebGL + - label: Build process + - label: Unit testing + - label: Internationalization + - label: Friendly errors + - label: Other (specify if possible) + - type: input + attributes: + label: p5.js version + description: You can find this in the first line of the p5.js file. + validations: + required: false + - type: input + attributes: + label: Web browser and version + description: In the address bar, on Chrome enter "chrome://version", on Firefox enter "about:support". On Safari, use "About Safari". + validations: + required: false + - type: input + attributes: + label: Operating system + description: "Ex: Windows/MacOSX/Linux/Android/iOS along with version" + validations: + required: false + - type: textarea + attributes: + label: Steps to reproduce this + description: 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! + value: "### Steps: + + 1. + + 2. + + 3. + + + ### Snippet: + + + ```js + + + // Paste your code here :) + + + ```" + validations: + required: true \ No newline at end of file