[opensuse-translation] Bugzilla as a project management tool
Hello, During the last several months, the process of localization of OpenSUSE has been improved greatly thanks to efforts of Novell and the SUSE team. We owe you a big 'Thank you' for L10n wiki, mailing lists and - last but not least - SVN access. What I would like to present in this e-mail is yet another enhancement that could improve the process and make our lives easier. I'm talking namely about Novell's Bugzilla, which as of yet, is not at all used to report bugs and mistakes in the translations. For SUSE Linux 10.0, 10.1 and OpenSUSE 10.2 there have been 143 bugs reports submitted in total, for all the languages <http://tinyurl.com/j2747>. Not too many, as it seems to me. I would like that we considered and discussed here on the list the ways to improve this situation. The e-mail is mainly address to Karl and Klára, but it would be obviously beneficial if everybody took part in the discussion. Please :-) I think we could try to use Bugzilla more extensively, not only for reporting bugs about typos and untranslated files, but also as a general project management tool. Pretty much like the Mozilla guys use it now. So that 'bugs' become more like 'tickets', general issues and not only errors. Examples of cases in which bugzilla could be employed: - Tracking L10n of a new version of openSUSE (fixed when l10n is ready) - New localizer requesting a SVN access - A new file / group of files available for translation (assigning translation, tracking it). Real-life example: Packages descriptions in OpenSUSE 10.2 translation of which could be managed via the bugzilla. - Last minute fixes required after the string freeze - Local license policy issues (if any) - Unable to land translations into the system (the reason should determine assignee) - Spelling/style/grammar mistake in application Foo / window Bar To implement these various functions for Bugzilla, I would like to suggest some modifications to the current structure of bugzilla.novell.com. Three proposals follow, together with more detailed info. Proposal 1 no changes to bugzilla, least efficient - Classification: SUSE Linux - Product: OpenSUSE 10.2 - Component: Translations / L10n / I18n - Version: Alfa 4 - Subject: Polish / pl / pl-PL / pl_PL bug (requires precise user's input or moderation so that the bugs are easily findable) Proposal 2 small changes to bugzilla, provides Language component (this way it would be possible to run searches easily and to assign different owner for different components, i.e. languages) - Classification: SUSE Linux - Product: I18n - Component: Polish - Subject: OpenSUSE 10.2 Alfa4 bug (requires precise user's input or moderation so that the bugs are easily findable) Proposal 3 more changes to bugzilla (not time-consuming nonetheless) but also presumably the most efficient - Classification: I18n - Product: Polish - Component: OpenSUSE 10.2 - Version: Alfa 4 The rationale behind Proposal 3 is that internationalization, as a process, concerns many fields of Novell's activity. It includes OpenSUSE, true, but what I would like to propose is a holistic approach to managing the i18n process by means of the bugzilla. I see other "products" such as wiki, mailing list, administration, communication and so on. I know that this might sound like introducing a lot of red tape all around, but in fact it turns out (once again I refer to Mozilla) that it works and that it works well. So, what do you think? Are there any chances that this could become reality in the near future? How do you feel about it, about working through Bugzilla and the proposals I came up with. In particular, what do you think of proposal 3? Looking forward to your comments and ideas. Best regards, Stanisław Małolepszy -- AviaryPL L10n team --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Stanisław Małolepszy a écrit :
I'm talking namely about Novell's Bugzilla, which as of yet, is not at all used to report bugs and mistakes in the translations.
first, we should make difference between various kinds of translations: * wiki translation * Yast and other suse related translation * openSUSE manuals translation * others products translation that probably don't rely on openSUSE
I think we could try to use Bugzilla more extensively,
bugzilla is quite imtimidating at first, but it's a great tool The first kind of translation (given above) can be fixed easily when it is about accessible wiki. but the present system (the XX-english named pages) clutters the "recent documents" page of the english wiki, what is uneven, but I think somepeople are working on this, so we can probably let this alone. The manual translation, at least the French one (the only I can talk of) is really nice, very few typos. But for the manual and the Yast stuff, the main problem for non Novell people is the way any bug report can be handled. Fort example, the actual policy about yast (If I understand well) is to _don't_ fix any string after the release. As the string freeze is very early in the process (for good reasons), it seems unusefull to make any report. There are two ways to find typos: proofread the very text, for example po files. This can be largely enhanced if these files are made available easier than now, for example online (readonly) with page numbers and line numbers or any sort of easy to get reference. This is nice, but out of context, translation can prove to be very difficult and error prone. The second way is to use the product. This way any out of context string is easy to find, but: * if the string do not get corrected (patches), why report? * if the module is to be changed for the next version, why report? So, at least, we should know what modules are to stay still from the present one to the next (string wise). The main problem is that the new distribution don't become really usable before the Beta issue. I can't afford personnally to test really (more than a simple install) an alpha version. to summarise, I don't see any reason not to patche the buggy strings. It's very unpleasant to see again and again a typo (and once seen, you never miss it :-) jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (2)
-
jdd -
Stanisław Małolepszy