devel:bughunting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| devel:bughunting [2014-02-27 00:28] – Klap-in | devel:bughunting [2023-09-24 19:44] (current) – andi | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The rationale behind it is that it is more fun to work on bug fixing together and having immediate feedback and discussions makes it easier to decide how a bug is best fixed or if a feature should be implemented or not. | The rationale behind it is that it is more fun to work on bug fixing together and having immediate feedback and discussions makes it easier to decide how a bug is best fixed or if a feature should be implemented or not. | ||
| - | BHW's are held irregularly and are announced and coordinated through the [[: | + | BHW's are held irregularly and are announced and coordinated through the [[: |
| - | Here's an example of the results of a [[http:// | + | Here's an example of the results of a [[https:// |
| ===== How to Contribute ===== | ===== How to Contribute ===== | ||
| Line 13: | Line 13: | ||
| * Join the [[:IRC]] channel | * Join the [[:IRC]] channel | ||
| * say hi :-) | * say hi :-) | ||
| - | * Go through open tasks at the [[https:// | + | * Go through open tasks at the [[issue>|bug tracker]] and open PRs at [[https:// |
| * If you think a task can be closed but aren't sure, ask in IRC | * If you think a task can be closed but aren't sure, ask in IRC | ||
| - | * If you don't have enough permissions to close tasks, ask in IRC for a status upgrade | + | * If you don't have enough permissions to close tasks, ask in IRC for help |
| * If reasonable, write [[unittesting|tests]] for open bugs | * If reasonable, write [[unittesting|tests]] for open bugs | ||
| * Assign bugs to yourself that you want to work on | * Assign bugs to yourself that you want to work on | ||
| * Fix bugs you can fix within reasonable time | * Fix bugs you can fix within reasonable time | ||
| * Add comments to outline how a bug could be fixed when fixing itself would take a lot of time | * Add comments to outline how a bug could be fixed when fixing itself would take a lot of time | ||
| - | * Send patches as [[devel: | + | * Send patches as [[devel: |
| * From time to time announce what you're currently working on - it helps others to get a feel who's busy right now | * From time to time announce what you're currently working on - it helps others to get a feel who's busy right now | ||
| * Goal: answer or close as many tasks as possible | * Goal: answer or close as many tasks as possible | ||
| Line 26: | Line 26: | ||
| * go through the bugs and see if you can reproduce them and add that info to the bug report | * go through the bugs and see if you can reproduce them and add that info to the bug report | ||
| * linger in the channel and see if developers need a certain environment to test things | * linger in the channel and see if developers need a certain environment to test things | ||
| + | |||
| ===== Upcoming Bug Hunting ===== | ===== Upcoming Bug Hunting ===== | ||
| - | Next bug hunting is on Saturday the 15th of February 2014. | + | Bug Hunting Weekends need organizing. If you'd like to have one again, you're welcome to initiate it. |
| + | |||
| + | * check interest from other developers | ||
| + | * check potential dates and timezones | ||
| + | |||
| - | You can keep up to date with all important DokuWiki events, including bug hunting days, by subscribing to our [[: | ||
devel/bughunting.1393457294.txt.gz · Last modified: 2014-02-27 00:28 by Klap-in