Le mardi 31 janvier 2006, Molle Bestefich a écrit : > There's also a Wine Developer's Guide, but I couldn't find it linked > from anywhere on either the winehq.org main pages or the > wiki.winehq.org main pages. It's out there.... somewhere... [...] http://www.winehq.org/site/docs/winedev-guide/index To get it you just go on the website (http://www.winehq.org), then Documentation, then Wine Developers Guide. > It's a somewhat complex interface (IMHO) and you'll need to enter some > magic keywords to make sure that the right developers see your > particular bug. > > That's out of my league, someone else will have to tell you what > keywords apply here, I don't know. But opening a bug would be a good > start, anyway :-). There are many people (me included) that are doing bug triage and who will direct the bug to the correct developer/choose the correct keyworkd in most cases. Not knowing what keyword to give to a bug doesn't make bugzilla hard to use or give an excuse to don't report bugs. Just choose wine-misc or wine-whatever. Best regards.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
_______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
