Bugday is a single day each month devoted to improving Gentoo in all aspects.
Next Bugday: April 4th, 2020
Who: Gentoo community (developers and users) - organized by the Gentoo Bugday team.
When: Usually on the first Saturday of every month, when possible.
Time: 24h event.
Where: The #gentoo-bugs IRC channel on Freenode.
- A Gentoo installation.
- An IRC client.
- A Gentoo Bugzilla account.
- A Gentoo Wiki account (optional).
- Good mood and a friendly attitude.
- Fix bugs.
- Bug triaging.
- Version bumps.
- Close old fixed bugs.
- Add or improve documentation here on the wiki.
- Bugs with the Bugday flag
- maintainer-wanted (current packages)
- maintainer-wanted (new packages)
- maintainer-needed - Existing ebuilds that need a developer.
- bugs last touched by year
- Requested articles - Articles about things our community would like to know more about, but haven't been written yet.
- Contribute to articles in the Todo category:
- Dirty - Clean up 'dirty' articles by improving grammar, punctuation, or clarity.
- Outdated articles - Bring outdated articles up to speed on current practices.
- Stub - Fill stub articles with appropriate content.
- Misused templates - Fix misused templates.
- Wikify articles - Add proper formatting to articles that need wikification.
- Todo articles - Cross off itemized tasks that need action.
- Open discussions - Complete open discussions and mark them as done.
- Suggestions - Suggest wiki maintainers to make a wiki-wide change.
- Contributing to Gentoo — explains how users can contribute to the development of Gentoo
- Submitting ebuilds — explains how to submit ebuilds through the Bugzilla bug tracking web application.
- Bugzilla/Guide — covers the recommended method of reporting bugs for Gentoo.
- Bugzilla/Bug report guide — explains how to report bugs on the Gentoo Bugzilla
- Project:Quality_Assurance/Backtraces — provides users with a simple explanation of why a default Gentoo installation does not provide meaningful backtraces and how to set it up to get them.