1. GTK+ Patch triaging
Once or twice a month, a "Patch biohazard report" is sent to the GTK+ mailing list. It's meant to draw attention to quickly fixable bugs that include simple patches. Most GTK+ hackers never go through the bugzilla patch list because it's big and really cluttered.
The goal is to create short summaries promoting a small collection of these patches so GTK+ developers can quickly accept or reject those patches.
Currently this is coordinated by JavierJardon (jjardon) and ChristianDywan (kalikiana). You can find them in the IRC in the #gtk+ channel on irc.gimp.org.
Go check current unreviewed patches and do the following:
- Read the report, see if it still makes sense
- Try the patch and see if it applies cleanly
- Fill below a new entry in a category that makes sense
Using terminology similar to previous issues is suggested but using something new is also welcome.
1.1. Sending a new Issue
Basically these are the steps to follow:
- Read the last email, see if any of those bugs were fixed
- Check this page for the bugs marked as commit now or docs or easy fixes
- Wrap up a list of 9 or so bugs in 3 sections: easy fixes, docs, proposals/ complex stuff
- Put your bugs with links and a one line comment in a new issue or the current one being worked on
Send it to the GTK+ devel list, but please let someone know about this before, patchsquad list is a good place for that.
1.1.1. In progress issue
Current (in progress) Issue: GtkLove/PatchTriaging/Issue8
1.1.2. Past issues
1.2. The bugs
This is the list of bugs that have been mentioned or promoted in any of the biohazard report issues.
FIXME: GtkLove/PatchTriaging/Issue7 not yet included FIXME: GtkLove/PatchTriaging/Issue6 not yet included
1.2.1. Can be committed
1.2.2. Documentation
https://bugzilla.gnome.org/buglist.cgi?bug_id=452949,339205,323904
1.2.3. Final review
https://bugzilla.gnome.org/buglist.cgi?bug_id=502266,521366,382646,423201
1.3. Needs-work
https://bugzilla.gnome.org/buglist.cgi?bug_id=351247,313273