On Thu, May 10, 2012 at 12:36 PM, yahoo-pier_andreit <[email protected]> wrote: > cut.... > >> >> I wrote a blog about that as well: >> >> http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/ it >> has quite a few links at the bottom that are useful. >> >> Regards, Myriam > > > dear myriam, I red your blog, as I haven't been able to write in it I tell > you here, about this: > >> 3. The subject and comment must be in English… > > > That excludes most international users as possible bug reporters. I know the > developers cannot do much a respect, but its a pity. > > myriam says: > 20/10/2011 at 1:13 pm > > Well, we simply can’t change that. Also, a user must be able to give > feedback in English. As I said, English is the language most used in > computing and all developers can read and understand it. > > an alternative could be to insert a language flag, like the status or > product(, where can be inserted the language, this can be done by the > submitter or the triager, if can argue which language is used otherwise the > unknown can be used, this can be useful for somebody who want help, he can > filter for example the Italian language and add a translation of it and > change the language to english, or filter the unknown to find the proper > language, what do you think about? > Given the general usefulness of most bug comments, and that we're not 100% complete on translations in KDE software I can't see this ever being practical. We already have a triaging problem and having bugs that most developers/triagers can't read isn't going to help. Especially as developers need to communicate back and forth with a user even if just to say "can you confirm this patch fixed it".
> one more, is possible to add some numbers about the time? something like : > 240 average hours to solve a bug > 350 average hours to be contacted by a developer after have subitted a bug > 25 average hours to triage a bug > Are these real stats? These change so much product to product, and bug to bug. We've had some bugs open for years, and I've closed some bugs in under a minute from being reported. Unless they look really favourable I imagine these stats will just put people off reporting. It may be interesting to try and keep these stats for everything generated from our KDE4.9 official testing though. Dave > manythanks, ciao , Pier > > > ================================================== > MESSAGGIO ISTITUZIONALE > ================================================== > > Destina il 5 per mille all'ENEA > Abbiamo bisogno del tuo contributo per dare nuove opportunità ai giovani e > al Paese. > Utilizzeremo il contributo per guidare una serie di giovani verso nuove > professioni necessarie per garantire la sostenibilità dello sviluppo > attraverso la conoscenza approfondita delle tecnologie e degli strumenti per > l'efficienza energetica e la gestione del territorio. > Li formeremo sui temi dell'efficienza energetica, su come si effettua una > diagnosi energetica in una industria o su un edificio pubblico e su come si > interviene per renderli più efficienti. > Insegneremo loro a studiare il territorio, ad affrontare problemi di natura > ambientale e a trovare il modo per risolverli. > Li formeremo e li affiancheremo per offrire soluzioni. > Questi giovani potranno avere in futuro un ruolo fondamentale per la > crescita del Paese nel rispetto della natura e della salute di tutti i > cittadini. > Il nostro codice fiscale è 01320740580 > Per maggiori informazioni: www.enea.it > > > _______________________________________________ > Kde-testing mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-testing > _______________________________________________ Kde-testing mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-testing
