Andriy Palamarchuk wrote:
--- Tony Lambregts tony_lambregts@telusplanet.net wrote:
Andriy Palamarchuk wrote:
[snip]
[snip]
Of course, the responsibility is voluntary (as the whole project BTW :-).
Suggested list (so far):
- Guy L. Albertelli - GUI
- Alexandre Julliard - wineserver, kernel
- Marcus Meissner - printing
- Andreas Mohr - documentation
- Andriy Palamarchuk - winelib applications under
"programs" directory (agreed).
- Dimitrie O. Paun - GUI
- Laurent Pinchart - copy protection
- Eric Pouech - sound
- Hidenori TAKESHIMA - quartz, DirectShow (is the
scope too narrow?)
- Dmitry Timoshkov - internationalization, Unicode,
keyboard i/o
- Martin Wick - sockets
Do we need following directions, who are good owners:
- DOS support
- common controls
- command-line handling
- wine tools
* Dustin Navea - wine tools (scripts?) * Duane Clark - toolbar
This list is *very* subjective. I went through the last month archives of wine-patches. Please, let me know if you agree or not, know other better owner for the subsystem, want to suggest new subsystem, any other comments are welcome.
Could we can get some help to make this list somewhat complete, Please?
[snip]
issues do not present challenge to them. BTW, I do not see a field "Priority" in the bugs entries.
The Severity field is for this and yes we should use it.
Not exactly. "Severity" is an importance for the end user - e.g. crash is the highest level of severity. "Priority" is an importance of the issue for us. E.g. crash of an application due to Wine not supporting vxd is severity "Critical" for the user, but priority is "Minor" for the Wine developers because we are not going to support vxd anyways.
To most users that encounter a bug the severity is "critical". It is up to the bug owners and triage to decide what is important. Mozzilla has a resolution "WON'T FIX" for some bugs. I think vxd is "WONT FIX". As a long term tester of Mozilla I can say with confidence that severity is a flag for triage and development not for bug reporters. [blocker] is the highest priority: for example something prevents wine from compiling.
Anyway the way that mozilla uses bugzilla is not the only way to use it. We have the source code if we really want to change it. I just don't see that it is nesessary.
[... skipped ...]
If there are no objections can we change the official documentation to say that bugzilla is the place to report bugs. I noticed that when the wineinstall script had a bug in it that it told the users to report it to wine-devel when it should point them to bugzilla. One other comment about this is that bugzilla's address is http://wine.codeweavers.com/bugs/ and I think it scares people away from using it. I have nothing against CodeWeavers but I think If bugzilla's address was http://www.winehq.com/bugzilla users would be certain it is the place for wine bugs
Agree. Now enter bugs to bugzilla for these changes ;-)
I entered bugs for the first two, and the third seems to be resolved already. <grin>
Tony Lambregts