[12:00] hi abogani [12:02] * ScottL is off towork [13:06] scott-work, I've been having some internet problems. I should be able to connect now. I'm available for discussing the documentation this week. Did you start anything yet? [13:07] * abogani waves all [13:08] hi abogani ! [13:09] which kernel should i be looking at for testing? the latest in /broken? [13:09] hi ailo, we missed you yesterday at the meeting, but nevertheless i am glad you seem to have resolve your issues [13:09] scott-work: Yeah [13:10] scott-work, Yeah. Sorry about that. Haven't read through it yet. I'll have a look at it [13:10] ailo: i am looking forward to working on the documentation. did you want to use the outline i had created before? [13:10] https://wiki.ubuntu.com/UbuntuStudio/IntroTutVideos [13:12] ailo: it's not a big deal about the meeting, not much came out that (i think) we didn't already know [13:12] except that jorge will not be working on the website any longer on account of life [13:12] * scott-work learned a lesson from this situation [13:12] scott-work, jorge's dropping out completely? What about implementing his work? [13:13] ailo: i'm not sure how involved he would have been during implementation, but yes practically immediately he will be needed to move on [13:14] he took a job in japan and thought he had several months to prepare, turned out he had less than a month to move apparently [13:15] scott-work, I need to load the IntroTutVideos into my RAM :P. Later today I can let you know what I think. Seemed like everyone were really into jorge's work, so it would be a shame if we don't use it. [13:17] I read from the logs that it is to be used [13:17] yes, he felt it was quite functional and could still be used [13:18] and it remains a considerable improvement from our current site [13:18] i will email him today or tomorrow about getting the work from him so we can implement it [13:18] by the way, i pulled a few strings and got some help getting my access to our website on canonical's server [13:19] however, this still leaves a huge bottleneck for access [13:19] i will be researching hosting and thinking about our hosting needs [13:19] * scott-work was concerned about hosting user content, but if they go the vimeo or youtube route we can link those from our website [13:22] i feel that with the limited access [1] to the canonical servers that if we can find a comparatively inexpensive hosting resource then we should go with hosting the site our own [13:23] my concern is financing the hosting, i personally do not want to be liable for this cost solely out of my own pocket [13:23] it seems that jorge intimated that this wouldn't be a concern so i would like to get his thoughts on this [13:24] cory also apparently had some ideas in this area as well, so i would like to discuss it with him as well [13:25] [1] while i have access, this is not enough, and given how difficult and/or time prohibitive it is to get access, i am finding this option rather difficult [13:30] As long as one can update the main site whenever needed, I still think having it hosted under Canonical is the best alternative. [13:39] ailo: let me know when you are ready to talk about the documentation, both identifying the content and the order you wish to work it [13:39] ailo: also, we could decide on splitting the work between us [13:39] sadly, i don't expect anyone else to assist, but i was going to send out an email to the -users and -devel lmailing list anyways [15:22] hey guys [15:39] hi falktx [15:39] holstein: thanks for chairing the meeting by the way! [15:41] scott-work: o/ [15:41] no problem [15:41] scott-work: did my us-menu thing got commited? [15:51] falktx: i don't know, but i want to explain a few things to you so you have clear expectations [15:51] falktx: pushing to bzr doesn't get teh package built or in the repos [15:52] falktx: someone (i.e. persia or TheMuso or possibly someone else) has rights to do that currently [15:52] falktx: but also before we do purse doing this i want to make sure we are making the right changes [15:52] scott-work: I know, we have to open a bug report first, then make a debdiff, blah ... [15:53] scott-work: I can make a patch... ? [15:53] falktx: we don't HAVE to make a bug report, etc [15:53] falktx: The.Muso has regularly made necessary changes, pushed to bzr, then uploaded to the repos without bug reports [15:54] falktx: my immediate concern is that the changes your are proposing are the correct ones [15:55] falktx: is there something i can use to see what is changing? [15:55] scott-work: as I said, I can make a patch [15:55] give me 5 mins [15:55] falktx: then sure :) i would like the patch then [15:58] holstein: but i still ask that we use the action command when we/someone needs to do something, this way it helps coordination and remind people of tasks that need to be accomplished [15:58] holstein: it will especially be helpful when creating the minutes from the meeting [16:01] scott-work: will do [16:01] i actually used the action command for the same reason though [16:02] scott-work: here: [16:02] http://kxstudio.sourceforge.net/tmp/us-menu_xfce.patch [16:02] use wget, firefox has utf-8 issues [16:02] holstein: oh, sorry then ;) i thought you used it in a few places to just announce some items, like new applications [16:02] the way that bot works [16:02] http://www.novarata.net/mootbot/ubuntu-meeting.20110605_1202.html [16:03] in this log (which we dont really have a policy in place yet anyways) [16:03] but, if you dont say 'action' it doesnt show up [16:03] i also was doing that to kinda breeze through the topics a bit, and get them counted* [16:03] Daviey: ping [16:05] holstein: OOOHHHH, that's nice :) [16:05] holstein: in this case, i wholeheartedly apologize for my ignorance ;) [16:06] scott-work: nah, i agree with you [16:06] i just went with it for that reason though [16:06] oh falktx, we might also wait for the menu update until we see what cory has, i'm not sure it will affect this but it might [16:06] action *should* be just for action items [16:07] scott-work: i'll ask daivey about how to get the mootbotuk fucntionality [16:07] yeah, i looked for a [NOTE] command and only saw [IDEA] holstein [16:07] im sure its something im not familiar with* [16:07] mootbot-uk would spit out .html, and a moin log too [16:08] that was VERY helpful, and looked nice, and was paste-able on the wiki's [16:08] holstein: o./ [16:08] Daviey: COOL [16:08] Daviey: do you have a minute? [16:08] I am indeed. [16:08] lol [16:08] hehe [16:08] anythying we can do to make it easier would be great, including getting minutes into the wiki [16:08] holstein: For you, i have 2 mins. [16:08] i have a question about the bot from -meeting [16:08] http://www.novarata.net/mootbot/ubuntu-meeting.20110605_1202.html [16:08] ^ thats the log i get [16:09] falktx: but i will look at the patch shortly, but i'm at work right now on a windows machine :/ [16:09] and i remember from mootbot-uk i was getting some moin? right? [16:09] thats really nice and easy [16:09] am i just not looking in the right place? [16:09] holstein: yes.. only mootbot-uk has moin output [16:09] Daviey: DOOD, thats *so* nice [16:09] i cant believe its not in the -meeting bot :/ [16:10] I didn't author the moin output facility, but i'll happily take the praise by proxy. [16:10] Daviey: :) [16:10] well, that answers my short-term question then [16:10] Handy, because you are out of time :) [16:11] Daviey: thanks o/ [16:16] holstein: i'm hoping to go ahead and implement a header like xubuntu does: https://wiki.ubuntu.com/Xubuntu/Meetings [16:16] i had played with this before i really would like to do this, maybe make a template that we start new pages with [16:17] also, you notice that if you look at the code for the wiki, it's a reference, the code itself isn't listed on each page [16:17] <><> [16:17] that's two of the headers: the larger menu and the smaller banner [16:17] i realize that can happen* [16:17] in practice though... [16:18] im still learning [16:18] lol, why do you keep ending sentences with an asterisk? [16:18] i keep waiting for the explanation at the bottom of the page :) [16:18] *reading this message may cause headaches ;) [16:18] LOL [16:18] not sure... [16:18] its a bad habit* [16:19] hehehe [16:19] its part of my using enter for punctuation problem [16:20] i haven't done it yet because i kept thinking about trying to find all the things we might need there without showing too much and not actually doing _anything_ in the process [16:20] oh, that was to be *anything* because i don't think my underscores showed up :/ [16:20] oh, there they are, my bad [16:20] but i realize now that if we get something up there then we can always add or take away from it :P [16:21] as it is, nothing has been done up till this point [16:21] scott-work: header-wise? [16:21] ailo: you up to testing abogani new kernel? I should be by this weekend [16:21] holstein: yes [16:21] although i guess that could be an apt description of many things....trying to get it set up perfectly and not actually accomplishing anything for months and months [16:23] eh, that could be another thing i could take on though [16:23] not too technical [16:48] astraljava: https://wiki.ubuntu.com/Xubuntu/Testing [16:49] this is the Xubuntu testing page that i said i would link to you [16:51] linux outlaws published the episode with the xfce interview in it :) [16:51] they used a crappy old picture of me for the show notes :( [16:51] http://linuxoutlaws.com/podcast/211 [17:45] holstein: don't feel like you have to be the one to do the header thing, i'll help as well [18:05] scott-work: oh, US related podcast ? [18:07] falktx: the linux outlaw thing? yeah, i emailed them about ubuntu studio moving over and they wanted to interview about it [18:09] cool [18:10] scott-work: I see you... [18:12] yeah, lol [18:12] i told fab he choose the scrariest picture i have [18:12] i'm totally cuddly and huggable...really ;) [18:30] scott-work: Thanks, I'm on it! [18:31] astraljava: as some point i'd like for us to put in the wiki the differences and uses of the daily images vs. the published alpha/beta/rc images [18:32] as well [18:32] and maybe even develop some levels of testing [18:32] i.e. level0 might be test the iso, that is, does the iso image install and work [18:32] level1 - system settings, that is, does jackd work because we have the user in the audio group [18:33] level2 - application testing, does that latest version fix a bug [18:33] scott-work: I agree, it should help bring in volunteers, or at the very least help understand what parts have been tested and where we stand in the devel cycle. [18:33] these are just some things floating in my head [18:33] astraljava: oh agree, the better we document how to test then we are more likely to get people who can and will test :) [18:33] scott-work: That's good, all help is more than welcome, as I said, not a real tester. :D [18:34] astraljava: i don't think anyone really is, ailo probably has dug into testing the kernel more than anyone else at this point however [18:36] Right. Well, I shall do some initial preparation, and then we could have some meeting of sort, to go over the stuff and hear about people's ideas for what is missing etc. [18:56] cya [21:56] i interviewed with the Linux Outlaws about ubuntu studio in general, and the xfce transition in specific: http://linuxoutlaws.com/podcast/211 [21:56] i *think* it went pretty well [22:27] ScottL: Coolness! Will listen to the podcast tomorrow. [22:33] ScottL, Sorry. Been a busy day. Got my internet working well today at least. I saw abogani's build of the new kernel, so I will install and try it. Soon time to start testing it. On the documentation, I'll need another day for it. After a quick look, it looks ok to me. I think I'll be mostly interested in the audio bit concerning system setup, hardware issues and even workflow. I would like to limit the documentation so it d [22:33] oesn't get too specific with some things. [22:37] Specific things can be covered in the wiki. It would be nice to have a page with links in alphabetical order to anything related to Ubuntu Studio [22:37] ailo_: I would very much appreciate your advice and views on how to document some of those from testing point of view. [22:37] ailo_: Also a good point, will keep that in mind. [22:39] astraljava, Documentation on testing? [22:40] ailo_: We were talking about this with Scott, that we want to have quite detailed steps of what things need to be tested in order to provide a solid and functional distribution. [22:41] ailo_: I will be in charge of creating such documentation. Since you have quite a lot of experience in working with these kind of multimedia distributions, your opinions would be greatly valued. [22:45] astraljava, I suppose I do have some experience from different things that have been a problem in the past concerning multimedia distros, but I haven't worked on a testing procedure myself. I'm sure I can contribute with a few ideas on audio orientated stuff. [22:46] I know holstein has experience from recording. Ralf on the mail list seems to have some experience on some specific areas like midi [22:48] I myself am mostly experienced in setting up a system for realtime audio, but I don't use a big variety of software normally. I do have experience with all sorts of software on other systems, like sequencers, daws and wave editors [22:50] So, I know my way around audio software, just not as much on Linux as on Windows for instance [22:51] ailo_: Sure, well, one part of the testing will be how the system settings can be set, for instance Scott mentioned jackd settings. [22:52] jackd I do know my way around, so no problem ther3e [22:53] Cool. Well, I will at some point create a base page for the testing stuff, I'll quite possibly borrow heavily from Xubuntu. When I have something in place, I'd like to have a meeting of sort to discuss about that. [22:54] Create test cases, see what needs to be done in order to be confident we have a solid release coming by the end of the devel cycle. [22:55] From my experience with Natty so far, I think doing more testing with standard stuff like jack / pulseaudio may be a good idea [22:57] If there is a nice, clean testing procedure that is not too hard to complete, it would be easier to try get more people to do tests [22:58] So, I'm all for getting some work done on that [23:06] ailo_: Good to hear! Thanks. :) [23:37] ScottL: Going to strat listene to your interview right now :D [23:38] 6 AM??????? [23:38] WTF???? lol [23:39] Fame doesn't look at the clock, you know. :D [23:40] lol [23:42] rlameiro, 6 am was when the interview started... [23:43] i actually got up a bit earlier than that [23:43] ailo, i'll read this in a bit after i take the dogs outside for their business ;) [23:43] ScottL: man, if i were a woman I would ask you to marry me :D [23:43] ScottL: Cool! What kind of dogs? [23:44] rlameiro: He's taken. [23:44] rlameiro: If he weren't, I would. [23:44] You're next in line. [23:44] yeah, I know, but one can try, cant we? [23:53] astraljava, we have two shih tzu's [23:55] I usually get to walk a Samojed that likes to lick female pee off the grass. He also likes used raindeer food. Dogs are wonderful animals [23:55] our dogs like to eat either deer or rabbit poop...strange little buggers [23:56] ScottL, Are you available tomorrow? I'd like to drop by then. [23:57] ailo, i agree that an index would be nice, i think there is a way to do this if we "tag" each wiki page with a "group" or "subgroup" or we could do it the old fashion and manual way [23:57] ailo, yes i will be at work tomorrow and should be available at almost any time during the day [23:57] ScottL, Tagging should be easy enough. Seems like there's a similar system to what is used in wikipedia [23:57] ailo, please work on any part of the documentation that moves you and I will happily work on the rest [23:58] Wikipedia uses categories and subcategories