GoogleCodeIn2016
Differences between revisions 4 and 5
|
Size: 1792
Comment:
|
Size: 986
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 15: | Line 15: |
| == QA Tasks == Ubuntu QA Team wiki page: https://wiki.ubuntu.com/QATeam (refer to this page for further help, if needed). === ISO testing === Using the ISO tracker: http://iso.qa.ubuntu.com/qatracker, that is a tool utilized to record manual test results for ISO tests, choose one or more tests, perform the test as explained in the tracker and report the result. To carry out this task you need to have a Ubuntu SSO account, if not you can get one [[https://login.ubuntu.com/|here]]. === Package testing === Using the Package tracker: http://packages.qa.ubuntu.com/qatracker that is a tool utilized to record manual test results for package testing, choose one or more tests, perform the test as explained in the tracker and report the result. To carry out this task you need to have a Ubuntu SSO account, if not you can get one [[https://login.ubuntu.com/|here]] |
[[https://wiki.ubuntu.com/GoogleCodeIn2016/ProposedTasks|Proposed Tasks]] |
Ubuntu is planning to apply as a mentoring organization for Google Code In for 2016! For more information, see the Google Code In Page, or the community site. Still have questions? Check out the FAQ.
The contest runs from December 2016 into January 2017. We are looking for mentors to help create tasks and mentor the students. Interested? Read on!
Keeping in touch
We'll be communicating via IRC and the mailing list. If you are interested in helping or volunteer to be a mentor, please subscribe to the list and idle in the channel.
and
Proposed Tasks
GoogleCodeIn2016 (last edited 2016-11-01 15:01:45 by carla-sella)