[00:01] <len-1304> zequence, In qjackctl in the status panel, the time of last start (time running) are 24 hour centric. That is the time of last start is only right if less than 24hours in the past. My logs show an xrun that is long past as still not having been reset, but the reset time is nearer. (jack has been running since last week and only one xrun) Not sure which day though :)
[13:38] <zequence> len-1304: I think we need to do some testing on the menu and seeds before hand. 
[13:38] <zequence> Another thing I want to do is to upgrade the kernel to 3.5
[13:39] <smartboyhw> zequence, do it after 12.04.2 and probably before 12.04.3 :P
[13:39] <zequence> Ah, but the kernel freeze is already in effect
[13:39] <smartboyhw> zequence, that is the problem. Also, -proposed is closing down today for precise:P
[13:40] <zequence> smartboyhw: Do you have a schedule for this somewhere?
[13:42] <zequence> If -proposed is closing down, that propably means it'll be hard for us to get anything in this time
[13:46] <zequence> -default-settings is not going to happen anyway, so we might as well just try to do SRUs manually further down
[13:53] <zequence> No, I think we have no choice but to skip this boat, and take the next one instead
[13:54] <zequence> Anyone able to see wiki.ubuntu.com? Whever I try that page, I just get forwarded to whatever page I was on last at wiki.ubuntu.com
[14:01] <contrapunctus> zequence, not working.
[14:01] <contrapunctus> I get a server not found.
[14:02] <zequence> It's just that page. If you go to another, it'll work. Like, wiki.ubuntu.com/ubuntustudio
[14:02] <zequence> Or, rather, wiki.ubuntu.com/UbuntuStudio
[14:03] <contrapunctus> That ain't workin' either, mane.
[14:04] <smartboyhw> zequence, I heard it from cjwatson in #ubuntu-release
[14:07] <zequence> smartboyhw: I saw it. I also talked with him a bit. 
[14:09] <zequence> I really need to fix my mail filtering. Manual readthrough of 200+ posts a day is not viable. One needs good filters for specific headers and keywords, and have some mail marked "important"
[14:09] <smartboyhw> Grrrr:)
[14:09] <zequence> I use sieve scripting for this on my fastmail account
[14:10] <zequence> I'm thinkin it might be smarter to start using MUTT and do some script integretation
[14:10] <zequence> integration*
[15:01] <smartboyhw> Hey scott-work 
[15:02] <scott-work> mornning smartboyhw , how are you today?
[15:08] <smartboyhw> scott-work, getting a bit troubled since I'm now uploading somewhat 30 attachments to a launchpad bug:(
[15:10] <zequence> scott-work: We won't be able to get anything in for 12.04.2. They've frozen -proposed
[15:10] <zequence> scott-work: I think we could just do the SRU whenever we want for the things we find important
[15:11] <zequence> I missed the opportunity to update the kernel this time, but will make sure to do it for 12.04.3. 
[15:12] <scott-work> zequence: oh, that's kinda disappointing, but yeah, it would be nice to do the SRU for 12.04.03
[15:12] <zequence> scott-work: Working on a sort of development release schedule template https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation#Ubuntu_Studio_Development_Release_Schedule
[15:12] <scott-work> that page is looking good :)
[15:13] <smartboyhw> Guys, scream at Bug 1116321:P
[15:14] <smartboyhw> zequence, good job. Clap Clap Clap at the background
[15:42] <holstein> zequence: cool
[15:42] <holstein> zequence: that has not been my findings
[15:43] <holstein> zequence: i assume you are commenting on my statment that maybe something wasnt supported by the lowlatency kernel?
[15:46] <smartboyhw> holstein, he is
[15:50] <zequence> holstein: Yeah. The lowlatency kernel is the exact same source as generic. There's no diff at all really
[15:51] <zequence> There's just a difference in scheduling, since lowlatency has full PREEMPT and a faster HZ, while generic only has VOLUNTARY PREEMPT and a slower HZ
[15:52] <zequence> So, any driver issue, anything concerning hardware, or whatelse, is exactly the same on both kernel flavors
[15:53] <holstein> zequence: you can step in and help whoever however you want
[15:53] <holstein> zequence: i was just saying that the issue for that user could be mor related to the graphics driver support in *any* os
[15:53] <holstein> he said "ardour3 is slow and glitchy in ubuntu"
[15:54] <holstein> and i was implying that it would be like that for any linux likely
[15:54] <holstein> for any kernel
[15:54] <zequence> holstein: Sorry, I didn't read much of the discussion. I have irssi alert me whenever someone mentions lowlatency :)
[15:54] <holstein> and the hardware support might be bad for his graphics card or whatever
[15:54] <holstein> no worries
[15:55] <zequence> I just wanted to clarify that lowlatency == generic. Many people are not sure what lowlatency is. Some think it's a for of realtime kernel, which of course it is. But, only because much of the older realtime code is now in the vanilla kernel. Other than that, it's just a normal Ubuntu patched kernel
[15:56] <holstein> it hasnt euqaled it for me
[15:56] <holstein> but, i havent dont much testing with it recently
[15:56] <holstein> all i know is, we have it.. its different
[15:56] <zequence> holstein: There seems to be a nvidia bug that is releated to a library that Ardour3 uses
[15:56] <holstein> if something doesnt work, you might want to try the generic
[15:56] <holstein> it might be newer
[15:56] <holstein> zequence: A3 is beta, that was enough for me
[15:57] <zequence> holstein: It's the same. 100%. No diff at all
[15:57] <zequence> holstein: The versions are now in sync, and the source is exactly the same
[15:57] <holstein> if there is not difference, then we shouldnt have it
[15:57] <zequence> I'm doing the maintenance for these kernels, after all, so I should know if anyone
[15:57] <holstein> im not saying its not a user issue either
[15:57] <holstein> sure
[15:57] <holstein> and im not saying you dont know
[15:57] <zequence> holstein: As I said, the only difference is how the scheduler works
[15:58] <holstein> im just saying, if a user says "im having hardware support, im going to suggest a different kernel
[15:58] <holstein> the version is more what im talking about
[15:58] <holstein> zequence: and you can be right there, saying im full of it, and wrong
[15:58] <zequence> Suggesting another flavor is not going to help though
[15:58] <holstein> and i wont care one bit
[15:58] <holstein> zequence: sure... so you dont have to
[15:58] <holstein> and i might still
[15:58] <holstein> since the generic will be newer
[15:58] <zequence> It's not
[15:58] <holstein> but, i understand what you mean
[15:58] <holstein> zequence: ok
[15:58] <zequence> It's the same version. they are in sync
[15:58] <holstein> cool
[15:59] <zequence> On the development release version, currently raring, the kernel will sometimes lag behind. But, not on the released versions. Not anymore
[15:59] <zequence> Not since I overtook maintenance
[16:00] <holstein> sure, but that might be just now... and i'll get there
[16:00] <holstein> and i appreciate your work, and hear what you are saying
[16:01] <zequence> There might be a chance for some form of regression on released kernels, but the chance is probably really slim, as from what I understand, most patches are security fixes of some sort. I estimate the biggest chance for someone to see a difference between kernels is get another version alltogether, like jumping from 3.5 to 3.8
[16:02] <holstein> one thing is for sure.. i dont know much about kernels.. but i might suggest for someone to try a different kernel
[16:02] <zequence> holstein: But, in the case of Ardour, I've heard other complain of slow graphics, and from what I've read, it's somehow related to nvidia graphics.
[16:03] <holstein> i just wouldnt run A3 and expect it to be perfect
[16:04] <holstein> i mentioned running it from the avlinux live CD and the user said he had as well, and that it was slow there too
[16:04] <zequence> I once had my whole system crash from a nvidia bug
[16:04] <zequence> It was a very weird one
[16:04] <holstein> which, supports the fact that its not an ubuntu only issue, which was what he was implying
[16:04] <zequence> Had to do with the mail client Evolution, and gpg signed mail. 
[16:04] <holstein> that the A3 slowness was an ubuntu issue
[16:05] <zequence> Yeah, I doubt it is
[16:05] <holstein> more likely, like what you are saying, something to do with graphics that would be for all kernels and linux's
[16:05] <holstein> i was saying.. A3 is A3
[16:05] <holstein> it was an odd exchange anyways
[16:06] <zequence> The weird thing with my bug was that, it wasn't anything visual, it seemed. Just freaking symbols in a mail
[16:06] <holstein> said he was "bored" with ubuntustudio[C[C
[16:07] <zequence> Some people would prefer we had lots of external repos included by default, but they don't understand what Ubuntu Studio is, that it's actually a flavor of Ubuntu
[16:07] <zequence> I can understand people wanting it to have more
[16:08] <zequence> But, then, it wouldn't be Ubuntu anymore
[16:08] <holstein> sure... lke mint does.. the mp3 stuff.. codecs
[16:08] <zequence> We owe a lot to the Debian Multimedia team for our packages
[16:09] <zequence> Some guys there are maintaining a hell of a lot of them
[16:09] <zequence> Too bad falktx is not that interested in helping out there ;)
[16:10] <holstein> the AVlinux guy said they were doing so much better upstream
[16:10] <holstein> OR, able to do better
[16:11] <zequence> I'm sure there's room for improvement, but that means people need to dive in there and help out
[16:11] <holstein> yup
[16:11] <holstein> i wish i knew enough to help out up there
[16:11] <zequence> I'm going to debconf this year. Hoping to meet some of the guys there. I'm becoming a team member there myself currently
[16:11] <falktx> oh cmon
[16:12] <falktx> zequence: you need to stop that attitude
[16:12] <zequence> falktx: Why?
[16:12] <falktx> I'm already pretty busy as it is
[16:13] <zequence> falktx: I'm just saying that if you find flaws in packages, you might as well do it in Debian source, and not have to do that in your own packages later
[16:13] <falktx> ...
[16:13] <falktx> I did report those issues before
[16:13] <falktx> no one cares or bothers usually
[16:14] <falktx> so I then gave up
[16:14] <falktx> debian is seriously flawed in my opinion
[16:14] <falktx> it's a pain to work with
[16:14] <zequence> falktx: But, you are working with Debian, since you are using it as a source. You're just not making changes upstream to Debian.
[16:15] <zequence> And, I don't find the issue being that nobody cares
[16:15] <falktx> my changes don't really matter to debian
[16:15] <falktx> debian is not a only-jack distro
[16:15] <zequence> Maybe some do, some don't
[16:15] <falktx> but you don't know that, do you?
[16:15] <falktx> you're judging me too quickly
[16:16] <falktx> why do you think TangoStudio and DreamStudio exist?
[16:16] <falktx> why dont they help out with Ubuntu and UbuntuStudio too?
[16:16] <holstein> i havnet looked at them in a while.. i like to load up the live CD's
[16:16] <holstein> see whats going on there
[16:17] <zequence> falktx: tbh, I have no idea. The guy doing DreamStudio has been here, but he was not very interested to do lots of work for us, really. As for TangoStudio, I don't know if anyone even has been around here trying to help
[16:17] <falktx> the changes I make are usually only for working better with jack-only setups
[16:18] <falktx> like removing pulseaudio support
[16:18] <falktx> I have custom+new packages in my ppas, yes, but so does everyone else
[16:18] <falktx> do you know why they prefer to package in a PPA instead of going to Debian directly?
[16:18] <falktx> there's a reason for that...
[16:19] <zequence> The only reason I see is that it makes it easy to do things your own way explicitely
[16:20] <falktx> and because debian is painfully slow and full of politics
[16:20] <zequence> Those things that are the same for all, those should be made for all
[16:20] <zequence> It's just logic
[16:20] <falktx> I feel like you keep bashing me, like you expect me to do a lot more
[16:21] <falktx> I already do quite a lot of things, my whole life the past year has been dedicated to opensource
[16:21] <zequence> falktx: Hey, I'm not being that serious. Please, don't think I disapprove with your work
[16:21] <falktx> I don't have a job for quite a while now, so I can finish my things properly
[16:22] <zequence> falktx: I'm not critizing you, or anything. I'm just looking at possibilities for improving linux audio, that's all
[16:22] <falktx> I know for sure that when I finish my cadence tools that's going to help a lot
[16:22] <zequence> I'm not a member of a football team. I'm not rooting for anyone. Just trying to find a way to do things right
[16:22] <holstein> i just wish it were easier
[16:22] <falktx> and I'm working to get it into debian
[16:22] <holstein> i mean, falktx cant just show up and fix things
[16:23] <zequence> falktx: That will be a good thing
[16:23] <falktx> zequence: it's already in progress, be patient
[16:24] <falktx> holstein: I did sometimes in the past, got some of my efforts totally ignored
[16:25] <falktx> but UbuntuStudio is moving towards something that I don't fully agree with
[16:25] <zequence> I'm going to become a Debian Multimedia Member, and I can say for sure that I will not ignore anyone on purpose. My impression of the team now is that they are too few, and have too much to do. 
[16:25] <holstein> falktx: what is that?
[16:25] <falktx> I'm seriously hoping Cadence will help US, but not sure what I can do more for it
[16:26] <holstein> zequence: lemme know how that goes, or if there is need for someone like me there
[16:26] <zequence> holstein: I think it's mostly working with packages, since Debian is more of a library for other distros, a frame work, and not really a distro per se, like Ubuntu
[16:30] <zequence> scott-work: I more or less copied the Ubuntu schedule. This is still just preliminary, but on the whole, do you agree on the format? The schedule is divided into four periods. 1. planning 2. development 3. Beta testing 4. Final release (which is really not more than for making announcements) https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation#Ubuntu_Studio_Development_Release_Schedule
[16:41] <zequence> I'm still using that whole page as a whiteboard. Will start putting stuff in separate pages later on
[17:11] <zequence> scott-work: Also, I'm working on something now that touches the team structure bit. You started sketching on that last weel. I have suggestions too. 
[17:20] <zequence> scott-work: This is what I've come up with. I was thinking each of these teams will need their own task description, blueprints, and schedule http://paste.ubuntu.com/1613448/
[17:21] <zequence> I don't see a point with having a core team, and what we call the packagin team is really the launchpad -dev team
[17:23] <zequence> I've grouped PR with Support, since users will ask questions on all of our channels. Some may focus mostly on user support, others more on posting news. Some both. I'm thinking both should have access to the same channels either way
[17:24] <zequence> scott-work: I'd like the teams to coincide with the launchpad teams as much as possible. 
[17:25] <zequence> I've created the bugs team, but I'm thinking it's not actually necessary 
[17:27] <zequence> hmm, or maybe yes. I'm thinking of subscribing to bugs for all our multimedia packages. I should subscribe that team to those bugs, now that I think of it
[17:28] <zequence> scott-work: Would be nice if you could change the name of the ubuntustudio-testers team to ubuntustudio-testing
[17:28] <zequence> Just a minor detail :)
[17:30] <zequence> scott-work: My next step is to start working on docs and resources for each team separately. I'll redo our landing wiki at the end of it. Really want to finish my work on dev docs.
[17:31] <zequence> scott-work: So, I really want to get the team structure done, at least as a temporary solutions, so I can go ahead with the docs
[18:40] <ttoine> hello
[18:41] <zequence> ttoine: Hi
[18:53] <zequence> ttoine: What do you think? https://wiki.ubuntu.com/UbuntuStudio/DevelopmentReleaseSchedule
[18:55] <scott-work> zequence: sorry, been in tons of meetings today and fixing problems, i'll will look at this but it will have to be later
[18:56] <scott-work> i'll try to give some time to it in hopefully no more than four hours
[18:56] <zequence> scott-work: np. There's enough to do for the willing, but I'd be happy if we could come to some conclusion today about the team structure
[18:56] <scott-work> that would be nice, and probably easy to do as well
[19:11] <ttoine> zequence, nice work
[20:12] <len-1304> scott-work, zequence, there is a new rewrite of catfish going to be coming out this month. The old version does not work (won't even open) The new one (from the dev's PPA) works really well and is much faster than the one nautilus no longer has.
[20:12] <len-1304> I would like to wait for the new release and then add it.
[20:13] <zequence> len-1304: sounds good to me
[20:13] <len-1304> scott-work, have you played with nautilus in 13.04 yet? I would like to switch back to thunar as default
[20:14] <scott-work> len-1304: let's switch to thunar as default
[20:14] <scott-work> it makes sense now
[20:14] <scott-work> beyond sense
[20:14] <len-1304> Should I remove nautilus from the seeds?
[20:15] <zequence> In that case, I think we might consider going the full way with everything
[20:15] <len-1304> zequence, what other things did you have in mind?
[20:15] <zequence> I mean, using XFCE/Xubuntu defaults for all things desktop related, except for our workflow additions
[20:15] <zequence> len-1304: We're currently shipping the gnome system monitor. Is there anything else?
[20:16] <len-1304> Only things that xfce doesn't have  something with the same function.
[20:16] <len-1304> system monitor was added for that reason too.
[20:17] <zequence> len-1304: Is the XFCE system monitor there still?
[20:17] <len-1304> no.
[20:17] <zequence> My logis is this. The less we change, the more we can reuse Xubuntu documentation
[20:17] <zequence> And focus on the multimedia specific items
[20:17] <len-1304> It didn't show memory used correctly.
[20:18] <zequence> len-1304: Correct is not the right word, I think. 
[20:18] <len-1304> However, I don't care that much.
[20:18] <len-1304> Very few people are going to know what the numbers mean. The rest of the xfce version is fine.
[20:19] <zequence> One could report that upstream to XFCE, and ask for it specifically
[20:19] <len-1304> micahg, you mentioned that ubuntustudio-default-settings needed fixing up before release. If I make changes to it will that get in the way? Can I fix it?
[20:20] <micahg> len-1304: go ahead, I haven't started yet, let me know when you're done
[20:21] <len-1304> Just changing a default application. Will do. micahg 
[22:16] <zequence> scott-work: I think we could differentiate between lead roles and team roles in some situations. 
[22:16] <zequence> project lead is of course not team specific. And some other lead function may not be either
[22:18] <zequence> What I'm after is having as few teams as possible. Each team having their own wiki page, where they can find *everything* related to their area of interest/responsibility, without needing to bother with other teams
[22:18] <zequence> I'm just starting on this page https://wiki.ubuntu.com/UbuntuStudio/KernelTeam
[22:19] <zequence> I'm thinking of keeping separate schedules for each team as well
[22:19] <zequence> As long as it proves to not be too much work, that is, which I'm hoping it won't be
[22:21] <zequence> scott-work: As soon as I'm done working out the docs for a specific team, I feel it's a good time to ask for volunteers for that team on all social channels and mail lists
[22:21] <scott-work> zequence: good idea!
[22:21] <scott-work> i'm hopefully wrapping up a few things and will give 30 minutes to reading/thinking/typing about team stuff with you
[22:22] <zequence> My goal here is actually somewhat hoping to increase the dev team not only with one or two people, but substantially over the next releases
[22:23] <zequence> That does require clear definitions for our areas of development, so that people can just dig in and do work
[22:39] <scott-work> zequence: okay, rereading a few things to get into the right head space and then i'll poke you again
[22:42] <zequence> I already went ahead and did a few changes to this page, but the teams are still the same as before, except I added a list for leads https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[22:44] <zequence> My plan is to make that page a portal to the docs for each team later. To give an ovesight of the whole Ubuntu Studiodevelopment initiative
[22:46] <scott-work> zequence: the only real differences i had was that i combined PR and website team. also didn't have a support team. but i'm good with what you have there
[22:46] <zequence> scott-work: Alright
[22:46] <scott-work> there are other non "dev" teams also in launchpad like "ubuntustudio", "ubuntustudio-user", "irc-ubuntustudio-ops"
[22:47] <scott-work> "nightly"
[22:47] <zequence> Ah, irc ops
[22:47] <scott-work> but we don't really control that team, just memebers
[22:47] <zequence> ubuntustudio-user?
[22:48] <zequence> Can't find that one
[22:49] <zequence> scott-work: ~ubuntustudio is a great resource, I think, though. It has a lot of members. I think it would be good to make announcments on there from time to time, just like the social channels
[22:49] <scott-work> errr, wait...i have that wrong :P
[22:49] <zequence> I'm thinking of that as a -user groub
[22:49] <zequence> group*
[22:49] <scott-work> sorry, was confusing myself with what xubuntu had done
[22:50] <zequence> We should add the irc team
[22:50] <zequence> ..to the list
[22:50] <zequence> scott-work: I'm thinking the website team may be more about administering the theme and the organization of the site, more than the content
[22:51] <zequence> while PR would be responsible only to create content
[22:51] <zequence> I think we can make that happen permission wise too
[22:52] <scott-work> zequence: that's a good idea. i was only trying to minimalize a few things and keep it small. not that this is important, was just a starting place for me. i was worried about not having enough people and didn't want to make a bunch of teams for three people, ya know? :P
[22:52] <zequence> Yeah :)
[22:53] <zequence> There's currently no team for PR on launchpad. I could create one, make it restricted, add it the rights to make content on the website, then hand it over to you
[22:55] <scott-work> zequence: before we make new teams we probably should restructure who is a member of what team
[22:55] <scott-work> when -devel became a meember of -nightly it caused several teams to be restricted, which i don't think we should be
[22:56] <scott-work> i think the majority should be moderated.
[22:59] <zequence> scott-work: I'd need to experiment with that to understand how that works. Using non-real teams, just to see how launchpad does things
[23:00] <zequence> I haven't understood the hierarchy yet
[23:00] <zequence> -dev team doesn't have to be on top of all other teams
[23:01] <zequence> Most teams probably don't need a hierarchy, for any other reason that to just find other teams easily
[23:01] <zequence> than*
[23:02] <zequence> holstein: Do you use FB and such much? We get a few support questions of FB and G+ now and then
[23:03] <scott-work> zequence: i looked heavily at how xubuntu was doing it
[23:03] <holstein> zequence: i do
[23:03] <holstein> i could watch fb
[23:03] <holstein> where do they seem to come in?
[23:04] <scott-work> zequence: holstein: i think it is as follows for xubuntu....
[23:05] <scott-work> xubuntu-team  is there on top
[23:05] <zequence> holstein: http://www.facebook.com/Ubuntustudio. Not sure how to be notified. I guess it shows up on a page tab. I think you should be made moderator of that page though 
[23:05] <holstein> i'll see what i come up with
[23:05] <scott-work> whoops, scratch that
[23:05] <scott-work> xubuntu-users is on top which is an open team
[23:05] <scott-work> xubuntu-team is under that
[23:06] <scott-work> essentially xubuntu-team is their -dev team
[23:07] <scott-work> and there is a strange mixture -team being part of other teams, very non-linear and confusing
[23:07] <scott-work> but since we have ~ubuntustudio i thought we could use that as the top level
[23:08] <zequence> Yeah, I don't find launchpad easy to follow on the team hierarchy
[23:08] <scott-work> then tuck -devel, -website, -testing, et al under there. all co-level with each other
[23:08] <scott-work> zequence: keep in mind, a team's "openness" (open, moderated, restricted) affects the team it is a part of
[23:08] <zequence> I'm finding the ~ubuntustudio-dev team to be more of a packagin/bug fixing team. Not a core team, while being in that team gives you access to almost everytying
[23:09] <scott-work> true
[23:09] <scott-work> i was thinking of adding a -contriburs team for helping with overall development without access to the code
[23:09] <zequence> If we are to have a core team, we should create on specifically, I think. And use the -dev team for what it is being used for now. Break the relations that exist now, etc
[23:10] <zequence> hmm
[23:10] <zequence> What priveleges would the -contributor team have then?
[23:10] <scott-work> i see here http://dullass.blogspot.com/2013/01/lunchtime-thoughts-on-ubuntu-studio.html that i had thought about actually putting -contributors under ~ubuntustudio and then put everything i just mentioned above under that
[23:11] <scott-work> zequence: not much, just sort of a general header to "collect" all the other teams under it
[23:11] <scott-work> but it would be a team that someone who didn't do anythign specific, but didn't do code either, could join and feel they were helping to "develop" ubuntu studio
[23:11] <scott-work> it would be a moderated team this way as well
[23:13] <scott-work> but i'm not really hung up on the -contributors team, but i do think it could be a nice selling point to people
[23:13] <zequence> Yeah, I guess it would make sense to have such a team
[23:13] <zequence> It could be a team one step away from all of the teams that do code, such as -dev, -kernel and -website
[23:14] <zequence> Or, even -PR
[23:14] <scott-work> zequence: i really like what you did with https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation#Ubuntu_Studio_Development_Release_Schedule
[23:15] <zequence> scott-work: I've moved the actual schedule to https://wiki.ubuntu.com/UbuntuStudio/DevelopmentReleaseSchedule
[23:15] <zequence> Did you refresh? Maybe that is what you meant?
[23:15] <zequence> I think the schedules will be very important 
[23:15] <scott-work> sorry, should be this:  https://wiki.ubuntu.com/UbuntuStudio/DeveloperDocumentation
[23:16] <zequence> Ah, yeah
[23:16] <scott-work> i was looking at the whole page actually, not just the schdule
[23:16] <zequence> It's very much work in progress
[23:16] <scott-work> it's funny you made the schedule liek that, because i had been working on one in google docs as well ;)
[23:16] <zequence> :)
[23:17] <scott-work> i was trying to work it based on weeks prior to a milestone in ubuntu
[23:17] <scott-work> i.e. +4 weeks before UDS start blueprints, +1 week have them here or there, etc
[23:18] <zequence> I'm considering the options. I need to look at previous blueprints, and see how easy it would be to make a template. This format might only serve us for another 3 release, including raring, as it seem Ubuntu will be changing the release schedule completely
[23:19] <scott-work> true, but we can cross that bridge when we get there :)
[23:19] <zequence> I didn't consider what needs to be done before UDS. That is a good point
[23:20] <zequence> ..or would be good to have done by then
[23:20] <zequence> That would mean development already begins before last release is out
[23:20] <zequence> or planning
[23:20] <scott-work> do you think we should add a sentence or two (no more than that) on the team structure page to describe each team's purpose and responsibilities
[23:21] <scott-work> (xubuntu did that for a few teams and i thought it was a fab idea)
[23:21] <zequence> scott-work: I think I want to do more than that actually
[23:21] <scott-work> links to stuff as well?
[23:21] <zequence> I want to make it a portal to everything related to those teams. But, as compressed as possible
[23:22] <zequence> At least link to a page for that team
[23:22] <scott-work> yeah, that would be good
[23:22] <zequence> A description, the list of members, link to schedule, link to page
[23:22] <zequence> The page would be a portal to all dev docs for that team
[23:23] <zequence> the specific team page, that is
[23:23] <scott-work> i like it :)
[23:23] <scott-work> i need to go pick up kids and head home. do you want to talk some more tomorrow?
[23:23] <zequence> scott-work: I'll be online most of the time, so I'm available
[23:24] <scott-work> good deal. talk to you tomorrow :)
[23:24] <zequence> Alright :)