Difference between revisions of "Documentation/BugDay"
(→Documentation Bug Day) |
(→Documentation Bug Day) |
||
Line 5: | Line 5: | ||
'''Communications''': #openstack-doc on the [[IRC|Freenode IRC Network]] | '''Communications''': #openstack-doc on the [[IRC|Freenode IRC Network]] | ||
+ | |||
+ | '''Aim''': Close at least 100 documentation bugs. | ||
+ | |||
+ | ===How to Participate=== | ||
+ | # Before the day, try to become familiar with [[Documentation/HowTo|How To Contribute to the Documentation]] | ||
+ | # On the day join #openstack-doc on the [[IRC|Freenode IRC Network]] so you can communicate with everyone | ||
+ | # Pick up one or more of the tasks below: | ||
+ | |||
+ | ==== Close old fixed bugs ==== | ||
+ | |||
+ | Old bugs are nasty. Even when they are long dead, they clog bug views and render the lists unusable. Just look at old bugs and check if they still apply ! If they don't, close them as ''FixReleased'' (if you can pinpoint when they were fixed) or ''Invalid'' (if you can't). | ||
+ | |||
+ | ==== Fix bugs ==== | ||
+ | |||
+ | The best thing you can do on a bug squashing day is to kill a live one. Just look at the list of ''Confirmed'' or ''Triaged'' and pick your target. Submit a change that fixes it. Ask for review help on the channel. | ||
+ | |||
+ | |||
===Finding Bugs=== | ===Finding Bugs=== | ||
− | + | The lists of bugs are here: | |
* [https://bugs.launchpad.net/openstack-manuals Bugs in OpenStack Manuals] | * [https://bugs.launchpad.net/openstack-manuals Bugs in OpenStack Manuals] | ||
* [https://bugs.launchpad.net/openstack-api-site Bugs in the API Site and API References] | * [https://bugs.launchpad.net/openstack-api-site Bugs in the API Site and API References] | ||
+ | |||
+ | # If you only feel comfortable making small changes, look for bugs with the tag [https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=low-hanging-fruit low-hanging-fruit] | ||
+ | ## If you can't find low-hanging-fruit to fix, you should try to complete tasks described at [[BugTriage]] instead ! | ||
+ | # Next, bugs marked [https://bugs.launchpad.net/openstack-manuals/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search|"Triaged"] have some helpful hints in them to assist | ||
+ | # However, most bugs are marked [https://bugs.launchpad.net/openstack-manuals/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=CONFIRMED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search|Confirmed] | ||
+ | |||
Revision as of 03:13, 22 November 2013
Contents
Documentation Bug Day
Date: Friday 20th December 2013
Time: Whenever you're awake!
Communications: #openstack-doc on the Freenode IRC Network
Aim: Close at least 100 documentation bugs.
How to Participate
- Before the day, try to become familiar with How To Contribute to the Documentation
- On the day join #openstack-doc on the Freenode IRC Network so you can communicate with everyone
- Pick up one or more of the tasks below:
Close old fixed bugs
Old bugs are nasty. Even when they are long dead, they clog bug views and render the lists unusable. Just look at old bugs and check if they still apply ! If they don't, close them as FixReleased (if you can pinpoint when they were fixed) or Invalid (if you can't).
Fix bugs
The best thing you can do on a bug squashing day is to kill a live one. Just look at the list of Confirmed or Triaged and pick your target. Submit a change that fixes it. Ask for review help on the channel.
Finding Bugs
The lists of bugs are here:
- If you only feel comfortable making small changes, look for bugs with the tag low-hanging-fruit
- If you can't find low-hanging-fruit to fix, you should try to complete tasks described at BugTriage instead !
- Next, bugs marked "Triaged" have some helpful hints in them to assist
- However, most bugs are marked [1]
Getting Help
If you need assistance with knowing where something goes, fixing build failures, or approving reviews, please contact the following people on IRC during the allotted time.
UTC | Mentors | Timezone handover |
---|---|---|
2300 | slong, loquacity | Australia |
0000 | slong, loquacity | |
0100 | slong, loquacity, fifieldt | Asia |
0200 | slong, loquacity, fifieldt | |
0300 | slong, loquacity, fifieldt | |
0400 | slong, loquacity, fifieldt, chandankumar | India |
0500 | slong, loquacity, fifieldt, chandankumar | |
0600 | slong, loquacity, fifieldt, chandankumar | |
0700 | fifieldt, chandankumar | |
0800 | fifieldt, chandankumar, AJaeger | Europe |
0900 | chandankumar, AJaeger | |
1000 | chandankumar, AJaeger | |
1100 | chandankumar, AJaeger | |
1200 | AJaeger | |
1300 | AJaeger | |
1400 | AJaeger, NickChase, nermina | US-East |
1500 | AJaeger, NickChase, nermina | US-Central |
1600 | NickChase, nermina, annegentle, dfleming | |
1700 | NickChase, nermina, annegentle, dfleming, sarob | US-West |
1800 | NickChase, nermina, annegentle, dfleming, sarob | |
1900 | NickChase, nermina, annegentle, dfleming, sarob | |
2000 | NickChase, nermina, annegentle, dfleming, sarob | |
2100 | NickChase, nermina, annegentle, dfleming, sarob | |
2200 | annegentle, dfleming, sarob | |
2300 | sarob | |
0000 | sarob | |
0100 |