Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.
3 Matching Annotations
- Dec 2020
-
hacks.mozilla.org hacks.mozilla.org
Tags
- helping others to learn
- opportunity to improve/fix something
- community (for a project or product)
- community relations
- encouraging feedback
- helping others
- receiving feedback
- relationship (people)
- open source community
- opportunity
- wiki model
- online community
- reverting a previous decision/change/commit
- community building
- pull request workflow
- reverting: creates negative experience
Annotators
URL
-
- Nov 2020
-
github.com github.com
-
There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.
Tags
- reversible decisions
- intentionally doing it differently / _not_ emulating/copying the way someone else did it
- reference implementation
- get back on course
- learn from your mistakes
- reverting a previous decision/change/commit
- don't let previous decisions/work constrain you
- intentional
- intentional/well-considered decisions
Annotators
URL
-
- Sep 2020
-
www.changelogs.md www.changelogs.md
-
Move svelte into dependencies, as it was accidentally stuck in peerDependencies
"accidentally stuck in": well, not really accidentally; it's in the change log so I assume it was intentional
-