Closed
Bug 1183782
Opened 10 years ago
Closed 9 years ago
Create/Repair wiki for the new contributors on Firefox OS
Categories
(Mozilla QA :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: njpark, Assigned: njpark)
Details
This bug is a placeholder for the discussions regarding the creation of friendlier wiki for new contributors/ new hires.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → npark
Comment 1•10 years ago
|
||
https://wiki.mozilla.org/QA/B2G/How_To_Test_Firefox_OS and subsequent pages were built to help support new contributors. There are other sources as well.
Assignee | ||
Comment 2•10 years ago
|
||
Below spreadsheet contains the tentative criteria for the available tasks to the newcomers:
https://docs.google.com/spreadsheets/d/1smGTsmeTyBa0ZYcCtTW6xCjk9h6F8g-plwAI6e6rl_U/edit?usp=sharing
My current idea is to match people's interests (top table) to the necessary information ('Learning Activities' table), which can be used to complete QA tasks ('QA Tasks' table). Before we start writing the wiki content, I want to clarify the list of tasks that can be done by contributors. It would be great if you can find the time to make comments directly in the spreadsheet, so I can make sure that I'm on the right track.
Assignee | ||
Comment 3•10 years ago
|
||
The second step will be to collect the list of existing wikis (like in Comment 1) and see whether they are up to date, and how to reference/reuse them.
Comment 4•10 years ago
|
||
Suggestions: We should also review https://quality.mozilla.org/teams/firefox-os-qa/ to make sure it is up to date, and link the final document there.
Of late we have been porting all our documents to MDN - https://developer.mozilla.org/en-US/docs/Mozilla/QA. If it makes sense for some reference docs to reside there, we should do that as well.
Comment 5•10 years ago
|
||
Hey all, I like the idea of njpark, so Me and Marcia we created an etherpad before the last work week contains few links *help/guide* contributor for debugging or test so I Would propose to you to use it https://etherpad.mozilla.org/Debugging-FXOS such the pad is not complete :)
Ps: @njpark Could you add me in the doc (https://docs.google.com/spreadsheets/d/1smGTsmeTyBa0ZYcCtTW6xCjk9h6F8g-plwAI6e6rl_U/edit?usp=sharing) it seems closed,need access, thanks
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Manel Rhaiem [:manel] from comment #5)
> Hey all, I like the idea of njpark, so Me and Marcia we created an etherpad
> before the last work week contains few links *help/guide* contributor for
> debugging or test so I Would propose to you to use it
> https://etherpad.mozilla.org/Debugging-FXOS such the pad is not complete :)
> Ps: @njpark Could you add me in the doc
> (https://docs.google.com/spreadsheets/d/1smGTsmeTyBa0ZYcCtTW6xCjk9h6F8g-
> plwAI6e6rl_U/edit?usp=sharing) it seems closed,need access, thanks
Thanks! you should have access now. the above etherpad looks like it should be merged with https://wiki.mozilla.org/QA/B2G/How_To_Test_Firefox_OS, I should go over both of them soon.
Comment 7•10 years ago
|
||
Just to be clear, this is all related to help contributing in testing Firefox OS, not actual development, right?
Assignee | ||
Comment 8•10 years ago
|
||
(In reply to Martijn Wargers [:mwargers] (QA) from comment #7)
> Just to be clear, this is all related to help contributing in testing
> Firefox OS, not actual development, right?
Correct, the page is only for the Firefox os qa side of it.
Assignee | ||
Comment 9•9 years ago
|
||
The daily bulletin page is added here:
https://wiki.mozilla.org/B2G/QA/Daily_Bulletin
The new qa page for contributors are added here:
https://quality.mozilla.org/firefox-os-qa/
next step is to talk to contribution team and expose the contributor website
Assignee | ||
Comment 10•9 years ago
|
||
Email sent to the participation team, pending update
Assignee | ||
Comment 11•9 years ago
|
||
Lucy Harris confirmed that the welcome e-mail text is now updated with the reference to the new qa page.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•