GettingInvolved
|
Size: 2499
Comment:
|
Size: 3289
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| <<Include(ReviewersTeam/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
|
| Line 3: | Line 5: |
| We have a script which automatically finds bugs with patches. Of course, it can't decide whether the patch is good or not, we need a human for this. The script does two things: Adds a patch tag and subscribes ubuntu-reviewers. The tag is used to track state as the patch goes through our process. The subscription is there to prompt us to start the process with a given bug. | We have a script which automatically finds bugs with patches. Of course, it can't decide whether the patch is good or not, we need a human for this. The script does two things: Adds a '''patch''' tag and subscribes '''ubuntu-reviewers'''. The tag is used to track state as the patch goes through our process. The subscription is there to prompt us to start the process with a given bug. |
| Line 5: | Line 7: |
| As you complete each step of the process, you will mark your process by adding an appropriate 'patch-*' tag and removing the old one. Make sure to ALWAYS include a comment when you change the tag just like you would if you changed the bug status, so it's clear to later reviewers what happened. | As you complete each step of the process, you will mark your process by adding an appropriate '''patch-*''' tag and removing the old one. Make sure to ALWAYS include a comment when you change the tag just like you would if you changed the bug status, so it's clear to later reviewers what happened. |
| Line 7: | Line 9: |
| Btw, if you spot an abandoned patch that still looks relevant, that isn't tagged 'patch', feel free to add it manually and subscribe ubuntu-reviewers. | Btw, if you spot an abandoned patch that still looks relevant, that isn't tagged 'patch', feel free to add it manually and subscribe '''ubuntu-reviewers'''. |
| Line 11: | Line 13: |
| == Places to sign up == === Maiing List === https://lists.ubuntu.com/mailman/listinfo/Ubuntu-patch-reviews <<BR>> Our mailing list keeps track of activity by subscribers in the bugs where ~ubuntu-reviewers team is subscribed. Join to have a first catch of the new bugs with patches attached (optional). === Launchpad Team === Once you have triaged a few patches and have a general feel for the review process, you can apply to join the team. A +1 from another member helps speed up the application. == What can I do? == === Review Patches === Patch Review is the important task for the Reviewers Team at the moment. * 1800 open bugs with patches * Send the working patches upstream |
|
| Line 12: | Line 25: |
| Places to sign up | So what are you waiting for? Go to the [[ReviewersTeam/ReviewGuide|Review Guide]] and start reviewing! === Packaging === The bugs with tag '''patch-accepted-upstream''' and '''patch-accepted-debian''' are patches that are ready to be integrated into Ubuntu. You can package these patches to help the reviewers team |
| Line 14: | Line 29: |
| Maiing List https://lists.ubuntu.com/mailman/listinfo/Ubuntu-patch-reviews Our mailing list keeps track of activity by subscribers in the bugs where ~ubuntu-reviewers team is subscribed. Join to have a first catch of the new bugs with patches attached (optional). |
* Patche accepted upstream or Debian: [[https://bugs.launchpad.net/ubuntu/+bugs?field.tag=patch-accepted-debian+patch-accepted-upstream&field.tags_combinator=ANY|Bug Query]]<<BR>> * Packaging and working with patch systems: [[PackagingGuide/Complete|Packaging Guide]] * If the source package can be imported straight from Debian (Ubuntu package unchanged): SyncRequestProcess * If the change needs to be merged from Debian: [[UbuntuDevelopment/Merging]] * Getting a patch uploaded by a sponsor: SponsorshipProcess |
| Line 18: | Line 35: |
| Launchpad Team Once you have triaged a few patches and have a general feel for the review process, you can apply to join the team. A +1 from another member helps speed up the application. What can I do? Review Patches Patch Review is the important task for the Reviewers Team at the moment. * 1800 open bugs with patches * Send the working patches upstream So what are you waiting for? Go to the Review Guide (link to Review Guide) and start reviewing! Documentation Good documentation helps new contributors to know where to start and also not-so-new team members how to do specific things; you can help with updating wiki pages for the Reviewers Team (adding information, linking up to other documention, doing things in 'TODO' list) Packaging The patch-accepted-upstream are patches that are ready to be integrated into Ubuntu. You can package these patches to help the reviewers team Patches Accepted Upstream Complete Packaging Guide |
=== Documentation === Good documentation helps new contributors to know where to start and also not-so-new team members how to do specific things; you can help with updating wiki pages for the Reviewers Team (adding information, linking up to other documention, doing things in [[ReviewersTeam/TODO|TODO list]]) |
Welcome to the Reviewer's Team! Patches submitted by the community are extremely important to us. The process described here is aimed at helping ensure good patches make it into Ubuntu in a timely fashion and also get integrated upstream. Your help in reviewing patches make the process go fast.
We have a script which automatically finds bugs with patches. Of course, it can't decide whether the patch is good or not, we need a human for this. The script does two things: Adds a patch tag and subscribes ubuntu-reviewers. The tag is used to track state as the patch goes through our process. The subscription is there to prompt us to start the process with a given bug.
As you complete each step of the process, you will mark your process by adding an appropriate patch-* tag and removing the old one. Make sure to ALWAYS include a comment when you change the tag just like you would if you changed the bug status, so it's clear to later reviewers what happened.
Btw, if you spot an abandoned patch that still looks relevant, that isn't tagged 'patch', feel free to add it manually and subscribe ubuntu-reviewers.
So this all sounds cool to you? You want to get involved in the Reviewers Team? Brilliant!
Places to sign up
Maiing List
https://lists.ubuntu.com/mailman/listinfo/Ubuntu-patch-reviews
Our mailing list keeps track of activity by subscribers in the bugs where ~ubuntu-reviewers team is subscribed. Join to have a first catch of the new bugs with patches attached (optional).
Launchpad Team
Once you have triaged a few patches and have a general feel for the review process, you can apply to join the team. A +1 from another member helps speed up the application.
What can I do?
Review Patches
Patch Review is the important task for the Reviewers Team at the moment.
- 1800 open bugs with patches
- Send the working patches upstream
So what are you waiting for? Go to the Review Guide and start reviewing!
Packaging
The bugs with tag patch-accepted-upstream and patch-accepted-debian are patches that are ready to be integrated into Ubuntu. You can package these patches to help the reviewers team
Patche accepted upstream or Debian: Bug Query
Packaging and working with patch systems: Packaging Guide
If the source package can be imported straight from Debian (Ubuntu package unchanged): SyncRequestProcess
If the change needs to be merged from Debian: UbuntuDevelopment/Merging
Getting a patch uploaded by a sponsor: SponsorshipProcess
Documentation
Good documentation helps new contributors to know where to start and also not-so-new team members how to do specific things; you can help with updating wiki pages for the Reviewers Team (adding information, linking up to other documention, doing things in TODO list)
ReviewersTeam/GettingInvolved (last edited 2010-08-21 07:53:27 by ABTS-KK-dynamic-249)