17:00:48 #startmeeting Ubuntu Studio collaborator meeting 17:00:48 Meeting started Sun Nov 6 17:00:48 2011 UTC. The chair is astraljava. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. 17:00:48 17:00:48 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 17:00:56 Hello everybody. 17:01:07 Who's with us today? 17:01:08 hello astraljava 17:01:10 i am here 17:01:15 Hi 17:01:27 can't stay too long 17:01:28 holstein and falktx said they would not be present today 17:01:44 Right, okay. Do we have an agenda? 17:01:45 stochastic, how much time, do you have preferred topics to discuss now 17:01:54 agend: https://wiki.ubuntu.com/UbuntuStudio/Meetings/2011September4 17:01:56 agenda 17:02:20 just the sooner I get on the road today the happier I will be, preferably no more than 30min 17:02:21 Same as from the last one? 17:02:33 stochastic, ack 17:02:44 Ok. What are the most important topics, Scott? 17:02:55 astraljava, no, i unfortunately updated the wrong one (i.e. sept) 17:03:04 Ahh... okay, that's fine. 17:03:22 so the agenda in the link is correct in scope, just not on the right wiki, i will resolve that after the meeting 17:03:45 okay, i won't bother reading the old business in the meeting 17:04:07 i will quickly explain the new development process for the ubuntu studio team 17:04:16 we will be actively involved with the release planning team this cycle 17:04:21 #topic New development process 17:04:37 we will collate a group of tasks we want into blueprints within launchpad 17:04:51 kate stewart, the release manager, will approve them as she sees fit 17:05:20 our progress will then be tracked on the status.ubuntu.com site 17:05:34 if anyone has questions how this works, please let me know outside the meeting 17:05:42 17:05:47 Sounds good, thanks. 17:05:51 this is good because it forces us to be organized 17:06:12 but it also holds us accountable as our progress (or lack of) will be extremely public 17:06:31 but this also gives us a forum for resolution if someone is blocking us this cycle 17:06:35 That is true. 17:06:39 done 17:06:52 Ok, any comments/questions regarding this topic? 17:07:24 just want to say that I'd love a step-by-step e-mail to be sent to the dev list regarding the process if that's possible 17:07:37 i.e. how do I get task x approved etc.. 17:08:00 keep everyone in the loop 17:08:16 Sure, we can work something out, right Scott? 17:08:17 stochastic, i can do that, but i should point out that this is something done only at the beginning of the cycle (i.e. getting blueprints approved) 17:08:26 okay 17:08:49 i should probably also note this in a wiki somewhere, i'll work on that too 17:09:01 i'm good 17:09:13 #action Scott document devel process in the wiki 17:09:13 * meetingology Scott document devel process in the wiki 17:09:22 #topic Release planning for Precise 17:09:37 has anyone NOT looked at the release planning wiki? 17:10:03 i don't want to over commit the team 17:10:06 hi shnatsel 17:10:17 hi scott-upstairs 17:10:24 so i wanted to make sure that people agree with what is preliminarily planned 17:10:38 I like the scope of the release plan 17:11:01 thank you starcraftman 17:11:04 stochastic, 17:11:06 Yeah it shouldn't be impossible. 17:11:08 sorry, starcraftman 17:11:45 shnatsel, any opinion on the scope of precise release planning https://wiki.ubuntu.com/UbuntuStudio/ReleasePlanning 17:12:23 i think most of the tasks already have people (mainly me) associated with them, so we will be asking people to commit as well 17:12:44 We can't just do it now, as there's not many in here. 17:12:55 I just wanted to briefly mention that I'd like to revisit the concept of putting a 'documentation' link on the desktop. 17:13:14 So I suppose we will ask people to assign themselves due some time? 17:13:18 This can fit under UI redesign and I'd be happy to help with that task in general 17:13:29 astraljava, i agree, we don't need to assign everything today, just getting the agreement on the scope was enough to move forward with the release team 17:13:41 Ok. 17:14:10 stochastic, there are several items for "new users" i would like to address as well, but unless they are liminted in scope or studid-simple i was planning on deferring them to later 17:14:20 you can see them in the release planning page as well 17:14:29 scott-upstairs: I want more graphics apps. The doc is large, needs thinking. 17:14:44 starcraftman, look under precise+1 -> new user support 17:14:56 quit it with the starcraftman 17:15:06 I see thanks 17:15:11 scott-upstairs: popups tend to not work usually 17:15:14 stochastic, sorry again 17:15:19 scott-upstairs: they're too intrusive 17:15:39 shnatsel, that is just brainstorming, i expect others have better methods to accomplish the goals ;) 17:15:54 Yes, agreed. 17:15:56 scott-upstairs: also, you'll need the support to be somewhat localized... and adding bookmarks to firefox doesn't work, I've tried that. 17:15:58 shnatsel, also, we can certainly explore more graphic applications 17:16:17 hi JonReagan 17:16:40 as long as everyone is okay with the scope of precise development then we can discuss the particulars later 17:16:52 yup 17:16:53 hello Scott :) Sorry I'm a bit late 17:16:55 Ok, anything else regarding this topic? 17:17:00 astraljava: yes 17:17:19 scott-upstairs: when are you going to introduce workflows in the installer instead of broad categories? 12.10? 17:17:19 Go ahead. 17:17:34 shnatsel, that is the next topic actually ;) 17:17:39 but it will be this cycle 17:17:41 Yes, thank you. :) 17:17:44 ah :D 17:17:46 great! 17:17:58 #topic Updating seeds based on workflows 17:18:02 scott-upstairs: why it's not in the planning doc then? 17:18:29 shnatsel, part of https://wiki.ubuntu.com/UbuntuStudio/ReleasePlanning#live_dvd 17:18:40 i'll explain a bit for those not familiar 17:19:18 our goals is to do something similar to what tasksel did during the alternate installation where users could pick certain package sets to install or not install 17:19:37 however, going to the live dvd will will use a GUI method that edubuntu is currently using 17:19:49 and we will base this on work flows, instead of just broad categories 17:20:23 https://blueprints.launchpad.net/ubuntustudio/+spec/livedvd has more resources 17:20:26 17:20:40 Thanks. Comments/questions? 17:20:51 do we need the alternate image at all? 17:20:52 the exact work flows do not have to be decided this meeting but hopefully we can decide _which_ work flows we will support 17:20:59 Ah, workflows meaning packages that would pertain to what people want to do with their system? 17:21:05 if not the exact contents of each work flow 17:21:20 JonReagan: yes, see https://wiki.ubuntu.com/UbuntuStudio/Workflows 17:21:22 shnatsel, i believe we should not make an alternate dvd 17:21:31 err, alternate image 17:21:52 I think so too 17:22:08 JonReagan, rather than make a large cache of audio applications we want to support a smaller, less intrusive package set based on a smaller granularity 17:22:15 we will targe what people actually want to accomplish 17:22:22 rather than a broad generalized term 17:22:26 gotcha, that makes a lot of sense 17:23:14 everyone can see what is listed for the work flows at https://wiki.ubuntu.com/UbuntuStudio/ReleasePlanning#live_dvd 17:23:29 i'll send out an email to the list to solicit peoples opinions so we can make a decision next week 17:23:36 I'll just have a comment on this; let's not get carried away and add too many of those. This is going to be supported for 3 years. 17:23:49 aye! very, very good point 17:23:49 astraljava: 5 years? 17:23:58 this LTS is supported for 5 years 17:23:58 shnatsel: No, that's just server edition. 17:24:02 Really? 17:24:05 All of it? 17:24:09 astraljava, they have changed policy during uds 17:24:17 Holy c**p. 17:24:27 they are trying to embrace corporations more 17:24:38 I stand corrected. 17:24:43 we'll see where it goes and adjust later 17:24:46 Even more so. 17:25:08 astraljava's point still remains, we should ease into this (even if it wasn't an LTS) 17:25:19 and we still have the opportunity to adjust next cycle if we want to add something 17:25:27 and backport back to precise if we feel something is worth it 17:25:38 Yep, thanks. 17:25:46 so i am strongly suggesting we are cautious and prudent 17:26:05 any further comments or questions at this time? 17:26:19 now postponing workflows to 12.10 sounds like a good idea 17:26:29 astraljava, can you make the bot recognize i should email the list about work flows? 17:26:37 can we really develop and polish them in a cycle? 17:26:52 #action Scott to email lists regarding work flows 17:26:52 * meetingology Scott to email lists regarding work flows 17:26:53 shnatsel, do you really want to? i would think getting the process established now would be good 17:27:14 we can continue refining the work flows each cycle as needed then 17:27:31 I agree, this one is going to be present for a long time. Better include it now. 17:27:40 I'm neutral on this. 17:27:47 as long as we can give at least the same functionality as we did with the alternate cd i don't see a downside at this point 17:27:51 essentially the concept between selecting workflows and selecting a bunch of software bundles is the same, we just label and organize them slightly differently? 17:28:08 stochastic, from the user perspective, i would say yes 17:28:31 okay, but we'd be re-arranging packaging from the dev perspective? 17:28:38 stochastic: from dev perspective also 17:28:50 stochastic: just requires much more fine-grained selection 17:28:50 stochastic, i would say yes again 17:29:06 What does that mean exactly? 17:29:53 stochastic, but i would describe it more as we are re-arranging the package sets but not really the packaging 17:30:02 astraljava, which part are you asking about? 17:30:03 well I think it is a do-able concept with very few modifications required. The largest problem will be selecting the ideal workflows to include - that's a big list. 17:30:20 stochastic, agreed! this is one reason to focus small on this set 17:30:21 Re-arranging packaging from dev perspective? 17:30:36 also, not all work flows are a) complete or b) desired 17:30:51 we should consider if we feel a large group of users actually desire a work flow 17:31:02 astraljava, we'd be heavily adjusting the content/labelling of the meta packages 17:31:24 Ok. 17:32:06 any further comments or questions? 17:32:10 yes, this is a task best handled by a committee I think 17:32:20 agreed! oh, i defintely agree! 17:32:22 but done for 12.04 17:32:22 +1 on that 17:33:05 stochastic, please keep in mind we only need to decide _which_ work flows soon, not just _what_ exactly is in each one 17:33:11 this may seem strange, but hear me out 17:33:21 i think we should look at what the users want to do 17:33:22 yes, true 17:33:35 would this mean some sort of survey? 17:33:36 if we think we can support it, then we can consider it for inclusion 17:33:48 then later we can fine tune the contents of the ones we will support 17:34:16 obvsiously we WILL need to examine the contents first if we are not sure we can support it properly before deciding about inclusion 17:34:36 JonReagan, it could, but perhaps we should discuss that in the next meeting 17:35:13 i would be completely open to a meeting of anyone interested to discuss these things outside of this meeting 17:35:35 #action Have a separate meeting for work flows discussion 17:35:35 * meetingology Have a separate meeting for work flows discussion 17:35:45 who would be interested in such a meeting? 17:35:47 i would 17:35:49 o/ 17:35:49 aie 17:36:02 i'm sure holstein would be as well 17:36:04 I'd be interested for sure 17:36:14 good :) basically everyone 17:36:30 probably me too 17:36:37 i can send out an email to coordinate times then 17:36:50 is this a good time for almost everyone? earlier? later? 17:36:52 We just don't have everyone here, so we'll throw some suggestions for times on the -devel channel and mailing list later? 17:37:04 Ahh, one step ahead of me, sorry. 17:37:26 good time, but depends on the week as to if this day is free for me 17:37:32 would someone else but me email the list for this purpose, i have enough tasks already 17:37:36 Good time for me. 17:37:48 I can do that. 17:37:48 sure, I could send out an email 17:37:57 Oh okay, Jon, go ahead. 17:38:33 Moving on? 17:38:35 is it okay if we move on? 17:38:36 hehe 17:38:36 * stochastic needs to be leaving soon 17:38:43 #topic Meeting schedule 17:38:53 Alrighty then. What should be said? Need a meeting to discuss workflows, ask for which time works best on Sunday? 17:38:57 i have a few questions about making our meetings more effective 17:39:08 JonReagan, stochastic needs to leave, can you and i coordinate after this meeting? 17:39:17 absolutely 17:39:18 how often should we have meetings? 17:39:35 should we alternate times between meetings for our european friends? 17:39:39 bi-weekly or weekly would be good for informal, monthly for formal team meeting? 17:39:45 should have stagger meetings with "informal" meetings in between? 17:40:02 I'm good for weekly. 17:40:09 Whatever the formality. 17:40:13 stochastic, would you suggest using a regular time for the "informal" meetings? 17:40:34 not asking you to actually suggest a time right now, just qualify if you think we _should_ use a regular time 17:40:45 yes, a set hour where it's generally anticipated that people would be around 17:40:47 i have opinions but don't want to bias the group 17:40:48 bi-weekly preferred here (I'm ok with not attending half of meetings, though, and you're probably OK with me missing too) 17:41:07 lol shnatsel , you are important man! 17:41:15 but i understand as well 17:41:24 I'd be up for weekly meetings, we have an awful lot to do before the next release 17:41:36 Agreed. 17:41:57 the general consensus i'm seeing is weekly meetings, but perhaps alternating "formal" and "informal"? 17:42:08 weekly will definitely make the dev process more lively. 17:42:10 both using an agreed time? 17:42:27 for predictability, I'd say yes 17:42:34 Preferably, but subject to change if necessary. 17:42:40 agreed 17:43:07 to explain 'formal' and 'informal' I think one would be in here, logged, with an agenda, the other, in -dev with minimal agenda 17:43:11 perhaps we alternate times between week#1 and week#3 for the "formal meeting" and the same for #2 and #4 for "informal"? 17:43:23 Sounds good to me. 17:43:24 stochastic, +1 17:43:55 okay, let's go with that and we can make changes as necessary as astraljava and stochastic are saying 17:44:10 any other comments or questions? 17:44:20 I really feel formal will only be needed monthly, but that's just a minor technicality that can be adjusted later 17:44:27 #action Move to bi-weekly formal and informal meetings alternating 17:44:27 * meetingology Move to bi-weekly formal and informal meetings alternating 17:44:34 astraljava, what was that sign you suggested to let the chair know we are done with a topic? 17:44:37 was it '..' 17:44:39 i.e. 17:44:40 .. 17:44:45 Yes, that would be good. 17:45:05 And asking for voices with o/ while someone is talking? 17:45:11 As in not interrupting the talk. 17:45:12 if we can use .. to help the chair know when to move to the next topic, that would help the meeting progress 17:45:35 okay, i didn't know that one :) 17:45:45 everyone okay moving to next topic? 17:45:48 It helps to keep the talk coherent. 17:45:52 yup 17:46:02 #topic Other business 17:46:09 i have no other business 17:46:19 Me neither. 17:46:36 I'd just like to say one brief thing 17:47:17 In the coming days it'd be nice if the devs could ponder how much social interaction they'd feel comfortable with on the new website. 17:47:45 stochastic, would you be up to emailing the -dev list about this? 17:47:51 yes 17:48:00 will do 17:48:06 this would be a good forum to aggregate opinions i think 17:48:12 err, that would be 17:48:21 .. 17:48:22 for now, ponder away, I'm on vacation for a couple days 17:48:32 enjoy your vacation :) 17:48:48 next topic? 17:48:50 #topic Next meeting 17:48:54 oi :) 17:49:07 okay, sounds like we will meet "formally" in two weeks 17:49:21 same bat channel, same bat time? (american joke) 17:49:35 sure 17:49:40 So according to the decision today, we shall meet formally here on 2011.11.20 1700 UTC 17:49:44 I might not make that meeting 17:50:01 stochastic, should we reschedule the time? 17:50:06 move it ahead a day? 17:50:10 haha, that would work for me. you mentioned earlier perhaps finding a time that would work for both europe and in the US? 17:50:25 And informally on #ubuntustudio-devel on 2011.11.13 1700 UTC, unless otherwise signalled. 17:50:33 JonReagan, yes! good point 17:50:41 should the next "formal" meeting be euro friendly? 17:50:42 scott-upstairs, no need to move it, just uncertain schedule at this point 17:51:04 perhaps move ahead 12 hours? 17:51:15 shnatsel, JonReagan, any suggestions? 17:51:27 * scott-upstairs is presuming that JonReagan is in a european time zone 17:51:30 That's gonna be 5 am. for me. Well, I can work it out. 17:51:40 lol nope, I'm EST 17:51:50 I'm GMT+4 17:52:12 shnatsel, do you have a preference what we should do for the next meeting in two weeks? 17:52:21 either case would be fine for me 9am or 9pm 17:53:09 I like the idea of alternating, but I'm not sure how successful it will be :) 17:53:22 Let's have a voting on this later. 17:53:30 So we can wrap up here. 17:53:33 scott-upstairs: last time I checked there was only one time that fits both european and american useras 17:53:36 users 17:53:53 I've found one, let me look it up... 17:54:01 Asia is out ofc 17:54:23 * stochastic is out for now. Will read the rest in meeting minutes 17:54:35 goodbye 17:54:40 Bye. 17:54:44 bye stochastic ,enjoy the vacation :) 17:55:25 i actually need to go as well, JonReagan can you email me about what we were going to work on together or catch me later this afternoon in IRC? 17:55:35 poof 17:56:18 #action Decide alternating meeting times on channel/mailing list later 17:56:18 * meetingology Decide alternating meeting times on channel/mailing list later 17:56:27 #endmeeting