-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Ciger wrote: > >>Apply for edit_bug status (IIRC it was on the login screen a while >>back). But then be very careful not to confirm duplicates, confirm bugs >>that are already fixed. > > > Similar thing was asked already - how ? It is not written anywhere and an > "outsider" has no way to know it. I support the idea of the HOWTO mentioned > in other threads, that could help a lot. >
It was somewhere in bugzilla but I could not find it now with a quick look. >>Well, this is better than having millions of duplicate and bad bug >>reports, as it was before, and the developers are so swamped they stop >>using bugzilla. > > > Buchan, but if we do not trust the bug reporters, then what's the point of > having public Bugzilla ? The reports would go ignored one or the other way. The issue is not trusting unknown testers totally with the quality of bugzilla. Ask why Mandrake was not using Bugzilla for 9.0 and 8.2 ... > > I know that people file bad reports and misreport bugs. That's normal. But > usually the approach taken is similar to something like below, instead of > ignoring the reports : > > 1) somebody files a bug > 2) QA tests and tries to verify it > 3) if the bug is there, mark as 'NEW' and/or 'ASSIGNED' (depends on the > workflow in the company) > 4) if the bug is invalid, gets marked as 'INVALID' or 'WORKSFORME' > 5) developers fix assigned bugs, put them in 'FIXED' state > 6) QA tests the fix and either 'CLOSE's the bug or reassigns it back > > In our case, since Mandrakesoft's QA obviously is not able to do all this > because of the sheer amount of bugs and various combos of the hardware and > software installed, let's establish a network of trusted volunteers > "prescreening" the bugs for each component. These would be people who are in "edit_bug". The only issue is that this is not well known enough. Any cooker regulars should have this status, if they are willing to do the job well. > These people should be very > responsive to the reports and Mandrakesoft would colaborate with them > closely. Something similar works for Linux kernel, where there was the > discussion, that "Linus does not scale" some time ago. They solved it by > establishing several "patch penguins", who take bug reports and patches, test > them and only then feed them upstream to Linus for inclusion. I think, that > something similar could work here too. Note that there are already people like this, just more people need to request that status. You will notice I do confirm some bugs that are not mine ... I just do not have time to read all bugzilla mail (I resorted to splitting cooker and bugzilla mail by procmail about 4 weeks ago). > And if Mandrakesoft rewards them > somehow (club points or a free powerpack or I do-not-know-what), it could > work for both sides. VIP membership in the club would be the standard way, since there are people here who do a lot more than many others, and they have received VIP membership. It would not do to reward some beta-testers better than some really good contributors (like Oden, Guillaume Rousse, Gotz, Olivier, Austin, Danny etc). But, maybe a prize for the contibutor closing the most (real) bugs? But that could be rigged (Oden could file a bug for each apache2 module, fix them all, and beat everyone hands down;-)) Buchan - -- |--------------Another happy Mandrake Club member--------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+Z6F1rJK6UGDSBKcRAmupAJ92li1fNqG4GJuP66xxh9FnehG/xgCeNPUN zS+0alm2wtbmZO5KQDcciso= =jDCT -----END PGP SIGNATURE-----
