Hi everyone,
Let's work on a process for onboarding new contributors in 2015. I've started a discussion here but let's continue on this thread per Alice's suggestion.
I've posted a rough draft here, but let's use this doc as our working copy so it's easier to comment and edit together. You can also add your feedback to this thread.
Continuing our discussion from the thread I referenced above:
- I didn't mean to suggest that only paid staff can create articles without permission. My initial thought was that newcomers would need feedback from existing contributors before creating an article. The intention was to make sure that newcomers don't create either duplicate content or content that doesn't fit into our scope (i.e. articles about third-party software), but I can see that this isn't a good way to accomplish this. Perhaps we should just keep content creation the way it is, but make our best practices for new content more visible.
- The "KB to-do list" mentioned in the proposal was created for newcomers who want to write, but prefer to be "assigned" specific articles. The list only has a few entries right now, but only because I didn't want to invest a lot of time in filling it out before we decide on the process. I've encouraged new contributors to come up with article ideas, and walked a few through bugzilla, as well as our new features spreadsheet, but none of them felt compelled to write articles after that - they still want specifics.
Please add any other feedback and offer suggestions.
Thanks, Joni
Hi everyone,
Let's work on a process for onboarding new contributors in 2015. I've started a discussion [https://support.mozilla.org/en-US/kb/quick-guide-contributing-knowledge-base/discuss/5636 here] but let's continue on this thread per Alice's suggestion.
I've posted a rough draft [[A quick guide to contributing to the Knowledge Base | here]], but let's use [https://docs.google.com/document/d/1H6Tc29hMew0YBj7S_pdIBtWXx8JJrDUnnn0UkDVEPKc/edit?usp=sharing this doc] as our working copy so it's easier to comment and edit together. You can also add your feedback to this thread.
Continuing our discussion from the thread I referenced above:
* I didn't mean to suggest that only paid staff can create articles without permission. My initial thought was that newcomers would need feedback from existing contributors before creating an article. The intention was to make sure that newcomers don't create either duplicate content or content that doesn't fit into our scope (i.e. articles about third-party software), but I can see that this isn't a good way to accomplish this. Perhaps we should just keep content creation the way it is, but make our best practices for new content more visible.
* The "KB to-do list" mentioned in the proposal was created for newcomers who want to write, but prefer to be "assigned" specific articles. The list only has a few entries right now, but only because I didn't want to invest a lot of time in filling it out before we decide on the process. I've encouraged new contributors to come up with article ideas, and walked a few through bugzilla, as well as our [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0Amy0OSD97CR6dGF4ZkhVaFFnaEI1cWhpR0dyM1hlaUE&usp=drive_web#gid=6 new features spreadsheet], but none of them felt compelled to write articles after that - they still want specifics.
Please add any other feedback and offer suggestions.
Thanks,
Joni
