diff --git a/building/tracks/articles.md b/building/tracks/articles.md index 3706acdf..7d28bda8 100644 --- a/building/tracks/articles.md +++ b/building/tracks/articles.md @@ -22,7 +22,7 @@ Any exercise, as long as there is something interesting to explore. Each article must add the following two files: -- `.articles//content.md`: description of the articleh (see [the docs](/docs/building/tracks/practice-exercises#file-articles-article-slug-content-md)) +- `.articles//content.md`: description of the article (see [the docs](/docs/building/tracks/practice-exercises#file-articles-article-slug-content-md)) - `.articles//snippet.md`: snippet showcasing the article (see [the docs](/docs/building/tracks/practice-exercises#file-articles-article-slug-snippet-txt)) You'll then need to add or update: diff --git a/using/product/reputation.md b/using/product/reputation.md index 1e939389..c2f4de80 100644 --- a/using/product/reputation.md +++ b/using/product/reputation.md @@ -69,7 +69,7 @@ Depending on the content of the pull request, a maintainer can award more (or le | --------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `x:rep/tiny` | 3 |
  • Fixing a single typo or link
  • Removing a blank line or adding a line break
  • Changing/adding a single code comment
| | `x:rep/small` | 5 |
  • Fixing a single test case, task or example
  • Fixing multiple typos or links in a single file
  • Clarifying content by adding a few lines to a file
| -| `x:rep/medium` | 12 |
  • Syncing an exercise with problem-specifications (incl. edits)
  • Adding one or more test cases from scratch
  • Improving multiple files in an exercise
  • Adding mentor notes for an exercise from scratch
  • Fixing a small bug in a test runner/analyzer/representer
  • Adding analyzer comments for a single exericse
| +| `x:rep/medium` | 12 |
  • Syncing an exercise with problem-specifications (incl. edits)
  • Adding one or more test cases from scratch
  • Improving multiple files in an exercise
  • Adding mentor notes for an exercise from scratch
  • Fixing a small bug in a test runner/analyzer/representer
  • Adding analyzer comments for a single exercise
| | `x:rep/large` | 30 |
  • Adding a new concept or practice exercise
  • Adding new concept documentation
  • Substantial re-writing of an existing concept or exercise
  • Adding new CI scripts or other automation
| | `x:rep/massive` | 100 |
  • Creating a test-runner, analyzer, representer or generator from scratch
  • Major refactors to those tools
  • Creating major documentation from scratch (e.g. contribution or testing guides)
| @@ -82,7 +82,7 @@ The examples above can serve as rough orientation when to apply which label but _For backwards compatibility purposes, we also support using the `x:size` labels to determine the awarded reputation._ -### Reviewing a pull requests +### Reviewing a pull request For each merged or closed pull request reviewed by the user, `5` reputation is awarded.