Post History
I volunteer as an editor for the Mozilla Developer Network (MDN), an organization that creates free open source software such as the Firefox browser. MDN has a large number of technical topics awai...
#3: Attribution notice added
by
System
·
2019-12-08T04:53:48Z (almost 5 years ago)
Source: https://writers.stackexchange.com/q/20256 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
rolfedh
·
2019-12-08T04:53:48Z (almost 5 years ago)
I volunteer as an editor for the Mozilla Developer Network (MDN), an organization that creates free open source software such as the Firefox browser. MDN has [a large number of technical topics awaiting review](https://developer.mozilla.org/en-US/docs/needs-review/editorial), around 625 at this moment. Most topics are very short and well-written, so they require few if any edits. Other topics are long and written by smart people who aren't great at technical writing. Very few topics are poorly written. The scope, pace, and choice of topics to edit are up to the editor. The style guidelines are not stringent. So far, I haven't come across any interactive examples that need testing. I enjoy editing, and I find contributing to open source software gratifying. It also improves my writing/editing skills, and I gain technical knowledge. However, there aren't a lot of extrinsic rewards, such as earning reputation points. People who volunteer do this have to be mostly content to work quietly in the background. Do you have any suggestions on how to attract and retain like-minded technical editors?
#1: Imported from external source
by
System
·
2016-01-02T04:27:07Z (almost 9 years ago)
Original score: 4