=== mpt_ is now known as mpt [16:12] newz2000: pre-meeting meeting question.. you can answer during the meeting though.. are teams going to be required to stick to the template provided? [16:23] I may be one or two min late, will be close though [16:23] ok.. my dad is over.. so ping me when your ready [16:31] cjohnston: I'm here but I can delay for a bit if needed [16:41] newz2000: is 1200 est ok? sorry [16:41] if not, i can start now [16:41] yep, that's fine [16:41] so in about 20m? [16:41] ok.. yes [16:41] thanks [16:45] newz2000: he just left.. so im ready whenever [16:45] ok, lets go [16:46] To answer your question, I think that yes, they need to use it unless we give them permission to change that [16:46] ok [16:46] and I can discuss this with the community council to make it a policy [16:46] ok [16:46] * newz2000 adds that to his todo list [16:47] * newz2000 will check to see if the community council even needs to be involved [16:47] ok.. [16:49] So you were wanting to talk about the tecnical side of this? [16:49] yes [16:50] You'll have to forgive me, I'm a bit sick and my head is not working at normal speed [16:50] no problem.. [16:50] cjohnston: Do you know what I mean when I refer to the "critical path" in project management? [16:50] nope [16:51] it is the parts of the project, and their order, that must be completed for the project to be a success [16:51] (and cannot be cut out) [16:51] sounds logical enough [16:51] So we need to define the critical parts and decide the order and dates that they will be done [16:52] ok... [16:52] You start. :-) [16:53] so things like url structure, template, gather resources.. stuff like that? [16:53] and then obvoiusly code [16:53] yeah [16:54] uggh.. wiki [16:54] yeah, we're still getting slashdotted [16:54] Well.. URL structure needs to be near the top... [16:54] but that should be pretty easy [16:55] I think that the URL structure can make the life of the js devs easier or harder depending on if it's well planned or not [16:55] there are two main parts of the project, that can be done at the same time or seperate are the coding and the gathering of resources/actual localizing.. [16:56] since we determined last week that we dont really need the translations to code [16:56] I understand what your saying, but I don't know how... ;-) [16:57] It may be appropriate to set up a meeting for people interested in the technical side. [16:57] Agreed... [16:58] Some of the outcomes of that meeting should be: [16:58] a. Agree on a URL structure [16:58] b. Find out who will actually do the code [16:58] c. ??? [16:58] d. Profit [16:59] scratch that last one. ;-) [16:59] lol [17:00] by url structure, are you meaning something like w.u.c/Local/en_US? [17:01] yeah [17:01] ok [17:01] I think coming to that point implies some actual technical discussions about how the code will actually work [17:02] So it might be good to start it on the mailing list [17:02] ok.. [17:03] the next part of the critical path will be... [17:03] So basically if the browser choice is es_MX then it would look for Local/es_MX, and if es_MX doesnt exist it would look for /Local/es? [17:03] That seems to make sense to me [17:03] ok.. [17:04] Is the next step to create the Template to be localized? [17:04] Prior to that there needs to be a template.. [17:04] But the template shouldnt be required prior to code.. nor code prior to template [17:04] right [17:06] Since I cant work on the wiki.. http://etherpad.com/SoCfQHOdCn [17:06] my notes [17:07] Is it possible to have two critical path's.. one translation side and one code side? [17:08] possible is probably the wrong word.. valid I guess may be a better one [17:08] we can do it however we want [17:08] ok.. [17:10] On the technical side, I will definatly need help.. I'm sure that more needs to be added than just write code, test, implement [17:10] well, what is needed from you is leadership [17:10] so set dates, write emails, do follow up [17:10] right... [17:12] I am at your disposal, so think of me as a resource [17:13] Should I leave the technical path until the meeting with the people interested and let them help determine what it should be? [17:14] I would start like this... [17:14] let's focus on the technical path first, getting it started [17:14] then once it's rolling start the template and then the localization [17:14] Ok.. [17:14] we'll need cooperation between teams for that [17:15] A good way to start would be to have a kick-off email to start discussions [17:15] give an overview of the project, ask for specific help, and then start the planning for a meeting [17:18] is there a preferred language for this? js... anything else? [17:18] js, definitely [17:19] completely in js? [17:20] probably [17:20] ok.. [17:20] I'll start writing the email now.. but not going to send out until I get back from vacation. [17:20] ok [17:21] were you going to still send an email announcing the project and me as the leader? i think you had mentioned that at one point [17:23] oh yeah, I can do that [17:24] I will do that [17:24] when do you come back from vacation? [17:24] Next Saturday.. the 13th is when I actually come back [17:25] * newz2000 checks his cal [17:26] I will probably announce a week from tomorrow then [17:26] okie [17:26] and I'll shoot for the day after I get abck for my email [17:26] ok [17:27] Should we adjourn our meeting? [17:27] sure. :-) [17:27] ok [17:31] * newz2000 goes to take a nap [17:32] ooo [17:32] that sounds fun [17:32] enjoy [18:29] the wiki is driving me nut [18:29] nuts [19:13] hi there! [19:14] hey jamalta [19:14] newz2000: i forwarded you an email from jamalta... :-) [19:15] just to confirm, ubuntu.com is on drupal, right? === jamalta is now known as jamalta-afk