=== plars_ is now known as plars === robbiew is now known as robbiew_ === vorian_ is now known as vorian === randa-lunch is now known as randa_ [09:47] czajkowski: hola chica [09:49] randa_: Aloha :) === ogra_ is now known as ogra === robbiew_ is now known as robbiew === dholbach_ is now known as dholbach [16:01] hi everyone [16:01] welcome to this month's translations meeting [16:02] as usual, let's see who's there... :) [16:02] I'm here [16:02] \o/ [16:02] I'm here [16:03] hi kelemengabor, Andre_Gondim, askhl [16:03] hey adiroiban [16:03] 0/ [16:03] here [16:04] ok, let's get started, then [16:05] (I mean when the Meetings page decides to load on my browser) [16:05] ok, here it is, let's talk about the first topic [16:05] [TOPIC] Pending actions in defining Ubuntu Translations bugs handling [16:06] Basically, we've been using the ubuntu-translations project in LP to handle translation bugs for a while [16:06] we've talked with the bugsquad on how to best use it [16:07] and created a joint team with the bugsquad, the Ubuntu Translations Bugs Supervisors, so that bugsquad team members have also got permissions to set the [16:07] bug status as Triaged in ubuntu-translations [16:07] So far it has worked well [16:08] and I wanted to check that the process to file and handle bugs is by now well understood [16:09] and that we've done all of the actions we talked about in recent times [16:09] because then I'd like to make an announcement on the Planet on Ubuntu Translations bugs [16:09] Well here in pt_BR team I will teatch other how to do/use this way, before this we just use mail list to report it [16:10] The Danish translation team already has a launchpad project for bugs in Ubuntu, https://launchpad.net/fjel . Is this a more centralized equivalent? [16:10] Andre_Gondim, great, thanks. Yeah, that makes things easier for bugs, but do not let this feel discouraged to ask things and siscuss issues on the Mailing List [16:11] askhl, let me have a look... [16:12] askhl, I think it's completely fine to have a separate project for bugs in a particular language, but if you see bugs that can affect all languages, you should file them against ubuntu-translations [16:12] Right. [16:12] going back to ubuntu-translations and bugs, from my side, I can think of two things which are still pending: [16:13] * Merging https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs and https://wiki.ubuntu.com/Translations/KnowledgeBase/ReportingBugs [16:13] * Decide on which tags we want to use [16:14] Before going into more detail into those, can anyone think of any other pending issues? Or has anyone got questions about the ubuntu-translations project and its use for bugs? [16:15] We've basically got https://help.ubuntu.com/community/ReportingBugs#Filing%20translation%20bugs as a higher-level explanation to direct users to file bugs against ubuntu-translations [16:16] And I think it is fine in its current status [16:16] Any comments, suggestions? [16:17] can this be made a bit more visible somehow? [16:17] this is the first time I see this section [16:17] dpm: I will change „ you can always contact the Translations team” [16:18] to point to Launchad Ubuntu Translators Group [16:18] kelemengabor: you get to this page when you click „Report bug” in Ubuntu [16:18] http://bugs.edge.launchpad.net/ubuntu [16:19] I'd love to make it more visible, but right now I cannot think of any other better place [16:20] agree with dpm :) [16:20] adiroiban: oh, I never click the Report bug item :( [16:20] kelemengabor: how do you report bugs? [16:20] :) [16:20] kelemengabor goes straight to fixing them! :) [16:20] :) [16:20] right [16:20] i forgot :) [16:21] no, I usually find the source package from the translation template [16:21] on which I detect something to report :) [16:21] but this is perhaps just me [16:21] Can I systematically get all reports filed on the Danish translations? [16:21] askhl: not realy... [16:22] sometimes they are assigned to ubuntu danish team [16:22] I would suggest using the 'official' ubuntu translators groups to manage bugs in each language [16:22] and you can see all bugs assigned to a team [16:22] askhl, not, unless you give them a tag, but generally, we tend to assign language-related bugs to particular teams [16:22] as Adi is expplaining [16:22] askhl: and we do use the official ubuntu translation teams :) [16:23] askhl, we already do this [16:23] dpm: okay, so I would be alerted, being a member of the Danish team, in spite of not knowing anything about the central bug reporting? [16:23] only that perhaps no one has noticed any Danish bugs yet on ubuntu-translations [16:23] askhl: yes [16:23] as a translator [16:23] askhl, yes, when we assign a bug to the team, the team mailing list gets an e-mail [16:23] you don't need to care about how bugs are reported [16:24] just check the bugs assigned to your team [16:24] and fix them :) [16:24] Great. [16:25] anyway, just a quick note on kelemengabor's question, it might be that if you go to the source package, the redirect to the ReportigBugs page is disabled, so you can file the bug directly. I think that's ok (other than we should advertise the ubuntu-translations project better), since generally only advanced users will do this [16:26] I think I'll prepare a blog post on Ubuntu Translations bugs for next week [16:26] yes. if you go to a series or a sourcepackage, you will not be redirected to the wikipage [16:27] oh, I see... [16:27] but the ubuntu bugsquad should know about „ubuntu-translations” [16:27] so, onto the pending points I was mentioning, I think I should just take care of putting the content from KnowledgeBase/ReportingBugs into HandlingBugs, and removing the "Brainstorming" section. I think most of the things discussed there have already been implemented [16:28] and when they triage your bug [16:28] they will assign it to „ubuntu-translations” [16:28] dpm: +1 [16:28] adiroiban, they know by now. Since the joint meeting with them, we've been getting more and more reports from bugsquad members assigned to ubuntu-translattions [16:29] which is good [16:29] ok, then I'll take care of the page merging [16:30] The other thing was tags, we talked a bit about them, put those we thought would be useful to use in the wiki page and we should perhaps discuss them [16:31] I think we talked about getting rid of the i18n one, as we've got the project itself and it might not be that interesting to know which bugs are i18n-related. What do you think? [16:31] since we have the ubuntu-translation project and we assign bugs to specific teams/persons [16:32] I no longer find them useful [16:33] what about the l10n tag? Do you think we should stop using them as well? (that's specifically the one where we assign the bugs to teams) [16:33] who uses these tags, and for what? [16:33] kelemengabor: :) [16:33] I don't, but I'm usually just reporting bugs [16:34] usually those who triage the bugs, if the reporter hasn't used them [16:34] i18n should also have a bug task on the package [16:34] by doing so, the developers are aware of them [16:34] l10n bugs are assigned to translations teams [16:34] I would still like to keep the needs-pot-on-build one and such, as I think they are useful to group similar bugs [16:35] yes [16:35] we can use then „on demand” [16:37] ok, so we agree on getting rid of i18n and l10n [16:37] if you find them useful [16:37] we can keep them [16:38] like kelemengabor asked: who uses these tags, and for what? [16:38] maybe we should define some „goals” and see if we can reach them using tags [16:38] ok, the needs-*, I use them, for grouping similar bugs :) [16:38] any translations-related tags you think would be worth having as Ubuntu official tags? [16:39] We've got them here, btw: [16:39] https://wiki.ubuntu.com/Translations/KnowledgeBase/HandlingBugs#Tagging [16:39] rather than making sure each translation bug is tagged [16:40] adiroiban: how about setting goals like "no bug tagged x can be open y weeks before release" [16:40] we should take care of assigning them to translation teams [16:41] adiroiban, yeah, I agree, but those assigned to teams are usually the easy ones, and fixed within hours (go translation teams!) [16:41] I like kelemengabor's idea, but that we can also do with priorities [16:41] we can keep needs-* tags [16:41] i.e. no Critical bugs can be open y weeks before release and such [16:42] cjk tag was useful, but now we have a team dedicated to those issues [16:43] ah, I see what you mean with teams, not only the translation ones [16:43] we can get rid of kubuntu/unr/xubunut/distro specific tags [16:43] as we should target packages [16:43] not distribution using them [16:43] dpm: I was thinking about bugs making i18n impossible, like the ones tagged with needs-* [16:45] ok, sounds like a good idea. And it might tie in nicely with the other point in the agenda: organizing another Hug Day on translations [16:46] we could set a goal for the Hug Day as well, not only triage bugs [16:47] having a Hug Day is a good idea [16:47] most importantly, not all translators are into the more technical stuff, but many coordinators are the ones with the in-depth technical knowledge [16:47] and it would be good if they especially would participate [16:48] for the more involved issues [16:48] when talking about bug, taging and triaging bugs, maybe we can ask the bugsquad for opinions. They whould have a good understanding of handling bugs [16:48] triaging can be done by nearly everyone, so all translators could participate as well [16:49] we asked them on the last meeting with them, there was some feedback, let me see if I can find the minutes... [16:49] i'm not saying that only bugsquad should handle bugs [16:49] Hello? [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] [16:50] but maybe we can get some feedback regarding bug handling process [16:50] crap. [16:50] SCREW YOU! [16:50] !ops | StupidStudios [16:50] StupidStudios: Help! Seveas, Hobbsee, LjL, ompaulafk, Keybuk, mdz, sabdfl, janimo, ogra, mdke, dholbach, or jono [16:50] [16:50] [16:50] [16:51] thanks vorian [16:51] anyway, today I must go a bit earlier, I've got a session on Opportunistic Developer Week [16:51] np. Pici did the hard work [16:51] what would you think of a Hug Day in let's say ~1 or 2 weeks? [16:52] on ubuntu-translations, that is [16:52] dpm: after Gnome 2.30 is out, it's fine for me :) [16:52] wait, that's a bit late... [16:53] that'd be in 4 weeks [16:53] 2 weeks then [16:53] ok, let me find a date, and I'll comment it on the ML [16:53] on the 20th? [16:53] and check out with the bugsquad [16:54] that's a Saturday, I'm not sure everyone will be there on the weekend [16:55] anyway, 250 bugs is too much for my nerves to live with :) [16:55] and we might end up doing the Catalan UGJ on the 20th anyway [16:55] :) [16:55] Let me see if I can suggest a date and we continue the discussion on the ML [16:56] ok, I must run today, so as usual, thanks a lot for the participation in today's Translations meeting, and see you around! [16:57] See you [16:58] ;) === andregondim_ is now known as Andre_Gondim === yofel_ is now known as yofell === yofell is now known as yofel === dyfet` is now known as dyfet === HalfWord is now known as Half-Word === Half-Word is now known as HalfWord === RoAk is now known as RoAkSoAx