Planning
|
Size: 7887
Comment:
|
Size: 8015
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 22: | Line 22: |
| || || edubuntu/ubuntu education packages || See: http://benc235.wordpress.com/2010/03/31/edubuntu-bug-day/ || Ben Crisford || |
This is a simple wiki page to have a list of upcoming UbuntuBugDays.
Be sure to check out https://launchpad.net/ubuntu/+upstreamreport along with the old Bug Day Focus history, this will make the choosing of future focuses easier.
If you want to help to organize a Bug day, please look at the Organizing Page
When arranging a Hug Day it is quite helpful to get developer(s) of the package involved. Developer Responsibilities is a good reference for finding out whom to contact.
Proposed Bug Days
Date |
Focus |
Comments |
Organizer |
nautilus |
|
||
20100406 |
indicator-applet |
|
|
20100408 |
rhythmbox |
|
|
|
network-manager |
|
|
|
update-manager |
|
|
|
evince |
|
|
|
xkeyboard-config |
probably all bugs need a status check; feature requests need to be separated from real bugs; watch out for user config errors |
|
|
fontconfig |
probably all bugs need a status check; feature requests need to be separated from real bugs |
|
|
edubuntu/ubuntu education packages |
See: http://benc235.wordpress.com/2010/03/31/edubuntu-bug-day/ |
Ben Crisford |
|
Your Idea Here! |
Comments? |
Your Name Here |
Ideas
< persia> Another idea would be to do a day for patch integration: there's lots of bugs with patches out there. Perhaps have a day where a couple people offer a quick -classroom session on testing/applying/requesting upload for patches every 4-6 hours, and people chase the list of bugs with the patch flag set.
bdmurray has some stuff that will help here
< persia> Something else we used to do for fun was keyword bugdays.
< persia> One of my favorite was "time".
< persia> Basically, pick a word, and do a bugsearch with the word. Find one with about the right number of bugs.
- tagging bugs hug day, create multiple pools of bugs that need to be tagged, example: mark as bitesize the bugs with patches that need to generate a debdiff in order to get bug fixed.
Bugs marked for expiration - List of expirable bugs
- Hug days for each new default application before they are included in a release of Ubuntu.
Kernel bugs with patches attached (How to handle Kernel bugs with patches)
Previous Bug Days
Date |
Focus |
Bugs Hugged |
Ubuntu Translations |
49 |
|
Gwibber |
85 |
|
Ubiquity |
119 |
|
Samba |
107 |
|
Pitivi |
26 |
|
UbuntuOne-Client |
214 |
|
Gnome Power Manager |
174 |
|
Bugs without a package |
113 |
|
Compiz |
134 |
|
18 |
||
Nautilus |
73 |
|
Gwibber |
48 |
|
Server bug day |
155 |
|
Confirmed Bugs without a package |
59 |
|
No Package bugs |
28 |
|
Firefox-3.5 |
15 |
|
Network-Manager |
147 |
|
Totem |
30 |
|
Rhythmbox |
53 |
|
Notify-OSD |
71 |
|
Nautilus |
61 |
|
Evolution |
79 |
|
Synaptic |
132 |
|
Empathy + MSN Support (Butterfly) |
24 |
|
Banshee |
73 |
|
Empathy |
34 |
|
Update-Manager/Notifier |
67 |
|
Thunderbird |
20 |
|
Firefox 3.0 |
|
|
New bugs without a package |
104 |
|
Compiz |
41 |
|
catch new bugs for SRUs and Karmic |
43 |
|
Bugs with Patches |
44 |
|
Xorg |
43 |
|
cups |
57 |
|
samba |
65 |
|
flashplugin-nonfree |
58 |
|
apport-failed-retrace |
71 |
|
network-manager-applet |
81 |
|
Bugs without a package |
125 |
|
update-manager |
48 |
|
Compiz |
~150 |
|
Firefox 3 |
~400 |
|
120 |
Archive
UbuntuBugDay/Planning (last edited 2016-07-11 22:43:55 by tsimonq2)