From Fedora Project Wiki
(Created page with "<!-- waiting for content -->") |
No edit summary |
||
| Line 1: | Line 1: | ||
* [[User:Kparal|Kparal]] ([[User talk:Kparal|talk]]) - We should revive our approach of contacting individual developers before a blocker bug meeting and invite them there. Of course this consumes more of our time. But I think it really helps (and speeds up) the blocker bug meeting, on the other hand. There were some proposals from Anaconda devs for e.g. sorting the bugs discussed by package maintainer (person or team), not by package name in alphabetical order. That way we can invite a person and discuss all of his/her packages together. We could also compute some statistics about the average time a bug gets discussed, and provide a rough idea of time when the bug is going to get discussed. We should point out that these people don't need to ''attend'' the meeting, just lurk in the channel and be available when we ping them, roughly about that time. If they are not available to come, they should provide some information in the bug itself. We can create templates describing all of this, and paste them into bugzilla + send them to the person's email and irc. | |||
Latest revision as of 10:29, 8 December 2014
- Kparal (talk) - We should revive our approach of contacting individual developers before a blocker bug meeting and invite them there. Of course this consumes more of our time. But I think it really helps (and speeds up) the blocker bug meeting, on the other hand. There were some proposals from Anaconda devs for e.g. sorting the bugs discussed by package maintainer (person or team), not by package name in alphabetical order. That way we can invite a person and discuss all of his/her packages together. We could also compute some statistics about the average time a bug gets discussed, and provide a rough idea of time when the bug is going to get discussed. We should point out that these people don't need to attend the meeting, just lurk in the channel and be available when we ping them, roughly about that time. If they are not available to come, they should provide some information in the bug itself. We can create templates describing all of this, and paste them into bugzilla + send them to the person's email and irc.