mirror of
https://github.com/scratchfoundation/scratch-storage.git
synced 2025-08-28 22:39:11 -04:00
Add GitHub templates
This commit is contained in:
parent
9dac5297eb
commit
1d15895980
3 changed files with 57 additions and 0 deletions
27
.github/CONTRIBUTING.md
vendored
Normal file
27
.github/CONTRIBUTING.md
vendored
Normal file
|
@ -0,0 +1,27 @@
|
|||
## Contributing
|
||||
The development of Scratch is an ongoing process, and we love to have people in the Scratch and open source communities
|
||||
help us along the way.
|
||||
|
||||
If you're interested in contributing, please take a look at the [issues](https://github.com/LLK/scratch-storage/issues)
|
||||
on this repository. Two great ways of helping are by identifying bugs and documenting them as issues, or fixing issues
|
||||
and creating pull requests. When looking for bugs to fix, please look for the
|
||||
["Help Wanted" label](https://github.com/LLK/scratch-storage/issues?q=label%3A%22help+wanted%22). Bugs with this label
|
||||
have been specifically set aside for Open Source contributors. Issues without the label can also be worked on but we
|
||||
ask that you comment on the issue prior to starting work. When submitting pull requests please be patient -- it can
|
||||
take a while to find time to review them. The organization and class structures can't be radically changed without
|
||||
significant coordination and collaboration from the Scratch Team, so these types of changes should be avoided.
|
||||
|
||||
It's been said that the Scratch Team spends about one hour of design discussion for every pixel in Scratch, but some
|
||||
think that estimate is a little low. While we welcome suggestions for new features in our
|
||||
[suggestions forum](https://scratch.mit.edu/discuss/1/) (especially ones that come with mockups), we are unlikely to
|
||||
accept PRs with new features that haven't been thought through and discussed as a group. Why? Because we have a strong
|
||||
belief in the value of keeping things simple for new users. To learn more about our design philosophy, see
|
||||
[the Scratch Developers page](https://scratch.mit.edu/developers), or
|
||||
[this paper](http://web.media.mit.edu/~mres/papers/Scratch-CACM-final.pdf).
|
||||
|
||||
Beyond this repo, there are also some other resources that you might want to take a look at:
|
||||
* [Community Guidelines](https://github.com/LLK/scratch-www/wiki/Community-Guidelines) (we find it important to
|
||||
maintain a constructive and welcoming community, just like on Scratch)
|
||||
* [Open Source forum](https://scratch.mit.edu/discuss/49/) on Scratch
|
||||
* [Suggestions forum](https://scratch.mit.edu/discuss/1/) on Scratch
|
||||
* [Bugs & Glitches forum](https://scratch.mit.edu/discuss/3/) on Scratch
|
15
.github/ISSUE_TEMPLATE.md
vendored
Normal file
15
.github/ISSUE_TEMPLATE.md
vendored
Normal file
|
@ -0,0 +1,15 @@
|
|||
### Expected Behavior
|
||||
|
||||
_Please describe what should happen_
|
||||
|
||||
### Actual Behavior
|
||||
|
||||
_Describe what actually happens_
|
||||
|
||||
### Steps to Reproduce
|
||||
|
||||
_Explain what someone needs to do in order to see what's described in *Actual behavior* above_
|
||||
|
||||
### Operating System and Browser
|
||||
|
||||
_e.g. Mac OS 10.11.6 Safari 10.0_
|
15
.github/PULL_REQUEST_TEMPLATE.md
vendored
Normal file
15
.github/PULL_REQUEST_TEMPLATE.md
vendored
Normal file
|
@ -0,0 +1,15 @@
|
|||
### Resolves
|
||||
|
||||
_What Github issue does this resolve (please include link)?_
|
||||
|
||||
### Proposed Changes
|
||||
|
||||
_Describe what this Pull Request does_
|
||||
|
||||
### Reason for Changes
|
||||
|
||||
_Explain why these changes should be made_
|
||||
|
||||
### Test Coverage
|
||||
|
||||
_Please show how you have added tests to cover your changes_
|
Loading…
Add table
Add a link
Reference in a new issue