[15:09] cjohnston, sorry for the late notice, but would you mind delaying the meeting in ~1h by 30 mins? [15:27] dpm: to what time please? [15:28] cjohnston, 16:30 UTC (just 30 mins delayed) [15:29] I thought we already had delayed it to 1630 for newz2000 [15:29] cjohnston, ah, that's fine then, you already talked :) [15:29] yup [15:29] :-) [15:29] ok, yeah, that was it, then :) [15:30] okie.. see ya in an hour [15:30] yep [16:21] I'm here, whenever you two are ready.. :-) [16:21] No rush [16:25] hi, will be ready in 5 min or less [16:30] ok, I'm all set [16:31] cjohnston, newz2000: so, on the last meeting we were saying that cjohnston would be the driver for this project, and that we'd need a spec for understanding what's involved, discussion and coordinating the work [16:31] cjohnston, I see you've created a blueprint and added some actions at https://blueprints.launchpad.net/ubuntu-website/+spec/website-localization/, thanks a lot for that. [16:31] ok, I'm ready [16:32] :-) [16:32] first time making a spec, so i hope its decient [16:33] sure, I hope you had fun with blueprints in LP :) [16:33] I've done another one now too.. And that project is going quite well..:-) [16:33] However, there is still one pending item we talked about: having a spec in the wiki linked to the blueprint, following (more or less) the template at https://wiki.ubuntu.com/SpecTemplate [16:34] The same thing we do at UDSs when we flesh out the roadmaps for each team. [16:34] Here's an example: [16:34] Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/lucid-qa-community-testing-translations [16:34] Spec: https://wiki.ubuntu.com/Specs/TestingForTranslations [16:35] We could reuse the existing page at https://wiki.ubuntu.com/Website/WebsiteLocalization/Roadmap, but it might need to be expanded a bit [16:35] https://wiki.ubuntu.com/Website/WebsiteLocalization/Spec [16:36] cjohnston, ah, I mixed up the pages... great, there is a spec in the wiki as well :) [16:36] * newz2000 had not seen that yet [16:36] I added the spec to the blueprint [16:36] that looks like a fair summary [16:37] cjohnston, ah, you've just linked it now. I read the blueprint this morning and I coldn't see it. Great, that looks good [16:37] ty [16:37] Didn't know about linking it.. hehe [16:37] The spec I do believe was in the email though. :-) [16:38] yeah, I went straight to the blueprint, though [16:38] lol [16:38] All good [16:38] ok, that's what we need to get the ball rolling [16:39] dpm: you mentioned a concern about burdening some of the people who will be working on this [16:39] (during a normally busy period of time) [16:39] yeah, we're aproaching Lucid [16:39] and people is getting more and more busy [16:40] I have a question.. Do we want to put this on the M cycle then? [16:40] Use UDS as a launching point? I don't know if newz2000 is ok with this [16:40] I'm OK w/ it but: [16:41] a: I don't know that all people who will particpate will be at UDS, so we may use it as a milestone, not a locastion [16:41] b: I think we have untapped technical potential that is not tied up w/ Lucid launch [16:41] (so we may be able to start earlier on that side if we want) [16:42] (that's it) [16:42] I am up for whatever... [16:42] I think we can start with an announcement, and see how it goes, but simply not commit with Lucid from the start [16:42] yeah, I'm totally in favour of that [16:42] cjohnston: didn't you suggest targeting May? [16:43] newz2000, where do you think we can coordinate this? would the ubuntu-website mailing list be a good place? [16:43] I think that would be excellent [16:43] That was my thought, that way people can still focus on Lucid.. I don't know how much work this is going to be, and the possibility of taking away from Lucid [16:44] Does it make sense to deliver the technical implemetnation first and then do the tranlsations as step 2? [16:44] IMO, without the translations, there is no need for technical implementation [16:44] ok [16:45] but thats just my opinion [16:45] you're leading this. :-) [16:46] cjohnston, there is some work to do in setting up a project in LP and exposing the translations, but I think it should not be much of a problem [16:46] you two both have more experience though... So if you recommend something, its more than anything I have to go off of. [16:46] Let me ask you a question... [16:47] if we have only one or two languages but otherwise it's working, do you think it will be good enough to launch? [16:47] Yes. [16:47] (and add translations as they come on) [16:47] The implication is that it needs to work first and foremost, and have at least one or two translations [16:47] newz2000, yes, but I'm pretty certain that when the technical implementation is working, we'll get lots more of just two :) [16:48] lots more of just than 2 translations, I meant [16:48] Right.. I think we need some sort of translations as a start... Then implement it.. and get the word out.. [16:48] right, my point is that the technical part may be more critical [16:48] and then get more tanslations [16:48] I see what your saying [16:48] I agree with newz2000, the implementation is what's most important here [16:49] Okie then... [16:49] I can provide a couple of translations for testing, that wouldn't be a problem [16:49] Ok.. [16:50] ok, that's cool [16:50] and I'm sure other Ubuntu translators will as well [16:50] Even partial translations can be used for testing [16:50] Technically: This page is the X language can be used for testing [16:50] true [16:51] So before translations can start there needs to be a source to translate from [16:51] Plus that would allowe me to see it works right.. lol [16:51] Correct. [16:51] what was decided regarding ES where there are many loco teams and a variety of resources? [16:52] I don't remember there being any specific decisions.. [16:52] Do we create one ES page that lists all the resources? [16:52] I remember what you and I had talked about was trying to get as many as possible.... and then if there is none specific to what the user has default fall back on the default es [16:52] newz2000, we can put it in https://wiki.ubuntu.com/Website/WebsiteLocalization/Spec#Unresolved Issues, we'd need more input from LoCos for that [16:52] ok. [16:52] cjohnston: would you do that? [16:53] My question about it is: [16:53] yup [16:53] if we choose to have es-mx and mx has few resources, would it be better to show them all of es? [16:54] hmm [16:54] Some big teams have got a central [16:54] coordination forum or mailing list [16:54] so perhaps they could be directed to that [16:54] But then the other issue, es-mx and es-something else, the same word has two different meanings [16:55] right. How bad is this? Can it be avoided using careful wording? [16:55] I don't know.. [16:55] * newz2000 doesn't expect you to know, just a question [16:55] I know I run into the issue with my line of work [16:55] and thats why I bring it up [16:55] newz2000, it can be avoided using the standard variant of the language [16:56] ok, that's good [16:56] So we need to identify what languages this could be problematic for [16:56] The Spanish translation team uses the same variant for all countries/regions. [16:56] I know Spanish and English both need to address it [16:56] -> another action for the spec [16:56] (and yes, i'm suggesting there be an EN translation too :-) ) [16:56] then that would probably be bestoh no [16:56] lol [16:57] yeah, en_GB [16:57] umm [16:57] dunno what I was saying [16:57] btw, my reasoning for there being an EN translation is so that this script can be used by the loco teams that don't speak English [16:57] ok [16:58] so what are the next action items? [16:58] I must go in a few minutes, shall we wrap up with a summary of what we've discussed? Otherwise, you two can continue after me, I'll read the logs [16:59] I'm adding the Unresolved Issue of how to handle languages with multiple LoCo teams... [16:59] also what languages need to deal w/ multiple locale dialects (or whatever the proper name for taht is) [16:59] Need to create an LP project. [16:59] we need to create a source document [17:00] Use the website ML for communication [17:01] I will submit a visual mock-up for what I see the end result looking like [17:01] Create a LP project [17:01] I think that's about it? [17:01] newz2000, I think that would be a great help [17:01] the visual mock-up [17:02] also decide on the final URL structure for translated docs [17:02] (that needs to be done) [17:02] Yup. [17:03] another item for unresolved issues (or pending discussion) [17:03] we can start with regular meetings as well, what do you think? [17:04] I'm fine with that. [17:04] when will the next meeting be? Same time (as originally scheduled)? [17:05] biweekly meetings would be fine for you guys? [17:05] In two weeks I will be on a beach with a beer in my hand [17:05] ;-) [17:05] And my wife would kill me if I got online for a meeting [17:06] no worries [17:06] Ooo.. I could talk to some poeple about es_MX tho [17:06] lol [17:06] :-) Lets meet next week to discuss the technical bits. dpm need not attend I think. [17:07] Actually, cjohnston: lets aim for Thursday [17:07] newz2000: I'm open.. Your call [17:07] cjohnston: ok. before lunch or after? [17:07] Doesn't matter [17:07] newz2000, sounds good to me. I can be there if I've got time, but I'm also fine with skipping if you don't need me on that one [17:08] dpm: we always need you.. ;-) [17:08] :) [17:08] lol [17:08] cjohnston: either 11:30 your time or 3:00 your time? [17:08] ok, I really need to go now. Is everyone clear with the plan before the next meeting, then? [17:08] Yup.. Thanks dpm ! [17:08] dpm: yep, thanks a bunch [17:08] 1130 newz2000 [17:09] ok, got it on my calendar [17:09] no worries [17:09] have a great weekend! [17:09] You too dpm !! [17:10] great. It sounds like we're a little close to action. [17:10] I'm working on a screenshot now [17:10] Cool.. [17:10] newz2000: so should I take and create a seperate LP project from the ubuntu-website project then? [17:11] * newz2000 ponders [17:11] I'm not sure [17:11] Yeah, maybe [17:11] to avoid intermingling bugs [17:11] ok [17:12] website-localization too long? [17:15] cjohnston: no, I don't think so [17:16] ok [17:17] https://edge.launchpad.net/website-localization [17:18] cool. I'll upload my graphic to the wiki, but first I must catch the IS team before they leave for the day [17:19] yup [17:19] I'm about to take off.. We can catch up later if your still around [17:20] ok, sounds good [22:02] howdy