[00:04] duanedesign: you ready? [00:04] duanedesign, [00:04] yes [00:05] #startmeeting [00:05] Meeting started Fri Aug 12 00:05:04 2011 UTC. The chair is duanedesign. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [00:05] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [00:05] o/ [00:06] hello [00:06] raise hand ih here o/ [00:06] okay [00:06] o/ [00:07] o/ [00:07] at least in spirit [00:07] o/ [00:07] Aloha [00:07] Sorry I'm late [00:07] ok i will start charles proposal [00:08] i hope some you had time to read it [00:08] read what (I just joined) [00:08] https://wiki.ubuntu.com/cprofitt/sandbox [00:09] #link will add it to the log pretty like I think [00:09] I had my personal live intervene [00:09] thanks led [00:09] duanedesign: who is here from the bt council ? [00:09] late, but here [00:09] [LINK] https://wiki.ubuntu.com/cprofitt/sandbox [00:10] I think that link is mute ^^ [00:10] it just doesn't repeat them here anymore [00:10] Sorry I'm late [00:10] DarkwingDuck, we are just starting =] [00:11] Outstanding [00:11] I think the BT is all but dead, if people want to support new users, let them support new users on the forums or irc or LP or what have you [00:11] i dont know about that [00:11] If the BT wants to morph itself into an ambassador role, new to Ubuntu, and helping people integrate into the community, we need buy in from other teams [00:11] i think te team has a lot to offer. [00:12] Which we clearly do not have [00:12] so I suggest we discuss the BT with the CC [00:12] We have a lot to offer, but why do we need the BT to make the offering ? [00:12] bodhi_zazen: whilst me and UBT had issues, that news is devarsting to me [00:12] bodhi_zazen: I have contagted the MOTE Mentoring Program and the bugs Mentoring Program and they were interested in woring with us === PabloRubianes_ is now known as PabloRubianes [00:13] Well, that is what needs to be discussed, not the link from cprofit [00:13] IMO [00:13] What UBT needs is a core of people with TONs of time to drive it. [00:13] i think thr issue is we, the BT, put to many obstacles in the way for someone who just wants to learn Documentation [00:13] I don't have the time at the moment to be a driving force. [00:13] I think the link was one of the subjects of the meeting [00:13] DarkwingDuck, I thought that's part of what council was? People that were committed and had the time. [00:13] We need to map out how we are going to integrate the BT into the community [00:14] charlie-tca, +1 [00:14] charlie-tca: it is , but it is sort of irrelevant, IMO [00:14] I think we are missing the point [00:14] DarkwingDuck: we gave the coucil those ruights? [00:14] Unfortunately, there seems to be at least one person here who refuses such a meeting to even take place [00:14] * bkerensa can help with UBT [00:14] if we want to be a team or just pointers to upstream [00:14] Yes, but the Council can't even get on the same page. [00:14] as I see it [00:15] and I'm saying that as a Jr member on the council. [00:15] Hi [00:15] Hi JasonO [00:15] Hi [00:15] Hi jledbetter [00:16] Hi bkerensa [00:16] That's the issue... we have no "roadmap" [00:16] the mentoring programs that exist in different areas of the community are struggking, as i understand, The beginners Team has much knowkedge in this area we can bring ti the table [00:16] This is Ubuntu Beginners Team Meeting correct? [00:16] bkerensa, Yes :) [00:16] * bkerensa is in the right place then [00:17] duanedesign, yes but I see that the original BT way was the best [00:17] I see the BT as feeding the other projects. a place people can go and ask (and get help with) "I want to help. Where/How can I?" [00:17] where you have a guide (human) to interact [00:17] Its not just the core team to spend time. We ned contribution from each memeber, atleast for an hour each day [00:17] We need to work with Doc Team, Bug Squad, MOTE wcwtera to best determin how to get people interested in their team. At the sametime encourage their mentoring program to join ours,So we can share best practices and resources [00:17] The future of the BT is what needs to be discussed, there is no consensus on the council or within the team , there is no mission [00:18] bodhi_zazen, true [00:18] jledbetter: i agree, er nned to push people to these other teams [00:18] Oh no... she's going to be one of *those* people.... [00:18] duanedesign: indeed, as of my "leaving" UBT, is also seems that things like MOTU, have failed... miserably [00:18] "The Ubuntu Beginners Team exists to enhance the initial experience of new Ubuntu users and to guide existing Ubuntu users to become part of the global Ubuntu community. " https://wiki.ubuntu.com/BeginnersTeam/ [00:18] but if we are just pointer to other places, none stays and knowledge get lost [00:18] I'm still here. [00:19] jledbetter: that definition is depreciated [00:19] and I went from BT to Doc team and Kubuntu Council [00:19] PabloRubianes, I would think folks would be happy to be helped and emaybe stick around to help others. [00:19] And can be better served in other ways [00:19] bodhi_zazen, Oh? Documentation? [00:19] PabloRubianes: good point. I would work to integrate the other teams mentoring processes into the beginnersteam [00:19] You do not need a BT to help on LP, forums, irc .... [00:19] PabloRubianes; I think you have it wrong, at least in my eyes [00:19] bodhi_zazen, Nope. Anyone can. :) [00:19] jledbetter: Documentation of what ? [00:20] bodhi_zazen, Why it's deprecated. [00:20] MrChrisDruif, what do you think? [00:20] It would be *awesome* is "we" would become the mentoring area [00:20] jledbetter: did you not read https://wiki.ubuntu.com/cprofitt/sandbox [00:20] bodhi_zazen, That's what we're discussing. It's not in place :) [00:20] * phillw to be suspended for a sense of humour.... What rules where there for that? [00:20] It has not been fully adopted [00:20] That way we wouldn't loose any knowledge [00:20] bodhi_zazen: i agree we need no team buti can not imagine I would have ever been so active had I not belong to a team than containeed so many knowledgable people in different areas of the community [00:20] MrChrisDruif, I mean in the new model proposed [00:21] I think BT should have a person who handles each aspect of contribution: bugs, doc, locos, dev, marketing etc and should act as a beginner mentor in each area [00:21] What we need to do is have a discussion with the CC and other community leaders [00:21] and build a role for the BT [00:21] i agree bodhi_zazen [00:21] support will be a part of what we do [00:21] bodhi_zazen: +1 [00:21] I think becoming a mentorship area is the ideal, but first we have to have a strong team behind with sense of pretence [00:21] bodhi_zazen: preliminary talks have happened with Joeb454 [00:21] and half the team can not grasp that concept [00:21] PabloRubianes, +1 [00:21] err, jono [00:22] like jledbetter , and others [00:22] Wow. [00:22] which results in chaos [00:22] sense of you belong there [00:22] bodhi_zazen, and I think there should be a -team where we had all fun and more than that [00:23] IAmNotThatGuy: I agree, but that is not the future of theBT [00:23] bodhi_zazen, What can't I grasp, exactly? [00:23] IAmNotThatGuy, +1 [00:23] What does the UBT think they are? [00:23] the council has been debating this for ever now... [00:23] What does the rest of the UBT see the UBT being? [00:23] bodhi_zazen: i think i agree that input from thecommunity is essentkial. What do they want, what will help most. From who i talked to a Mentor program woould help most. AS lot of teams have troublemaintaining them. hving a team that is all they do increases chances for succes IMHO [00:23] I do not know jledbetter , you are citing the old mission statement and wondering what happened [00:23] duanedesign: well, that is haelpful [00:24] apparently, if the team consists of bodhi_zazen, it is what ever he decides [00:24] bodhi_zazen, Because that's what is on our wiki page and what brings people to us and why we get emails of people wanting to join. Right? [00:24] can you lay that out on a wiki page ? [00:24] duanedesign, Yes, mentoring is what I keep hearing too. [00:24] DarkwingDuck; I would see it as it is; which would be support for beginning ubunteros and help in the transition from ubuntero to active ubuntero [00:24] I think we need to try not to be a mess in here [00:24] * phillw can I state how totally wrong the lp emails are? [00:25] The current mission is: The Ubuntu Beginners Team exists to enhance the initial experience of new Ubuntu users and to guide existing Ubuntu users to become part of the global Ubuntu community. [00:25] DarkwingDuck: ^ [00:25] PabloRubianes: the Bt is in shambles, from top to bottom, from bottom to top [00:25] if yoiu wish to be professionall, then gewt them sorted [00:25] bodhi_zazen, I love UBT for the helpp and the team channel rather than FGs. And thats why I am not ready to leave the -team channel. It gives me some sort of energy to proceed forward. Kinda a force to run [00:25] bodhi_zazen, yes [00:25] Yes, I know the mission statement.. I'm looking at what the members within the team view the team as. [00:25] Even within this meeting there is no agreement as to what the BT is any longer [00:25] With that in mind; that would mean that we should be mentoring people to becoming members in their prospected area [00:25] Same for the mailing list [00:25] That's my point bodhi_zazen [00:26] same for the council [00:26] Those areas would have people coming back to us to let the knowledge remain [00:26] MrChrisDruif, I think there is where you get it wrong, [00:26] new members should be first members of the team and then go upstream [00:26] i would like to thing if you go through the Beginners team and lear Documentation, you will come back and repay that favor mentoring someone else [00:27] The greater community is asking the BT to morph from what is is/was into something else and most of the council see the team going in that direction [00:27] duanedesign, What I was thinking too [00:27] if we only help to evolve people to other teams in a few time none will remain in the bt [00:27] If not all of the council [00:27] The BT membership seems split 50/50 [00:28] one idea was to have an open team of eople looking for help [00:28] PabloRubianes: that may be the future of the BT [00:28] and another team of mentors [00:28] if there is no mission / purpose [00:28] bodhi_zazen, but I don't think that is right... [00:28] What is not right ? The UDS request ? the team forking ? === rsalveti` is now known as rsalveti [00:29] bodhi_zazen, you know that this is our home. People who are loving it hard are still there. And how can we break it? We can do help in all FG, but lets also have #UB and -team [00:29] bodhi_zazen, let out team future on other decision [00:30] bodhi_zazen: My Lord and Master, I really feel to see a sense of humour. It has really troubled me as I so, so strongly belive in UBT.... where did they & I go wrong? [00:30] The team needs to decide what it wants to be [00:30] lord and master? [00:30] * DarkwingDuck sighs [00:30] * MrChrisDruif joins DarkwingDuck in sighs [00:30] Are we going to answer the request from the community ? [00:31] Or be a support team ? [00:31] bodhi_zazen, why cant we do both? [00:31] bodhi_zazen, You would prefer support? As in "how to do I make X work in Ubuntu"? [00:31] Anyhow, I think duanedesign and I pretty much are on the same page, but just rephrasing it differently [00:31] Lets not break what we are till now and lets work on the request from the community [00:31] IAmNotThatGuy: because half the team does not want to do both, half the team wants to be support only [00:32] Then they can be support. Those that don't can mentor ;) [00:32] jledbetter; +1 [00:32] DarkwingDuck: and MrChrisDruif you do not see our nick names, fior some this is a 'problem' but for those who know, this a statememnt of authourity [00:34] phillw: What are you smoking and where can I get some? :P [00:34] lol [00:34] =D [00:34] So put that for a vote, both, then change the various wiki pages, and mov eforward [00:34] bodhi_zazen, Or lets m,ake it like to be an UBT member, they should provide help in any one FG(If thats the case) but not breaking the -team :[ [00:35] We should seriously do away with "membership" [00:35] We should either : [00:35] bodhi_zazen: +1 [00:35] 1. Be an open team - probably best, anyone can join [00:35] I'm going to be brutally honest for a moment... [00:35] 2. Write out specific expectations for membership [00:35] DarkwingDuck: Sure [00:35] and if you all want to fire me as a council member after, that's fine. [00:35] UBT is too full of egos and "look at what I can do" people [00:36] +1 DarkwingDuck [00:36] DarkwingDuck: I have a guy who states "Hello Master" - I have been hi master, he inseests upon it because of it being barred [00:36] We seriously need to bleed off the disruptive members [00:36] It's turned into a group where people point at themselves and yell at what they do/have done. [00:36] +1 [00:36] Ubuntu is not for people like that... [00:36] +1 [00:36] bodhi_zazen: and replenish with valuable ones? [00:36] If you want to brag about how great you are... go to Fedora or Arch [00:37] lol [00:37] replenish what [00:37] council seem to be closed qligue [00:37] I thought folks were in UBT to help others. [00:37] bodhi_zazen: members [00:37] jledbetter: in theory. In reality it's the inflated ego club of the month [00:37] I say we do not need "membership" [00:37] I was astounded to realise tat council only vote on new mwmbwrs [00:37] should be an open team [00:38] DarkwingDuck, great I think you are showing your ego [00:38] bodhi_zazen, I agree with you: open [00:38] How is that? [00:38] PabloRubianes: ^^ [00:38] At one time we sort of needed a membership process, but that was long ago and we have outgrown that need [00:39] the first thing we should do is not to say... if you want that go to arch or fedora... [00:39] The idea of membership is dragging the team down and interfering with integration into the community [00:39] bodhi_zazen: started UBT.... those who fail to listen to his advice, are fools. [00:39] bodhi_zazen, the community don't even know we exist until they need a team to get people in [00:39] bodhi_zazen, Agreed. Can we vote on that? [00:39] phillw: Can you please kindly stop trolling? [00:40] * jledbetter would love to see a positive outcome from our first meeting in a while :) [00:40] What the BT needs is [00:40] 1. to define a mission statement [00:40] 2. We could use a few leaders please. Leaders have tended to go MIA [00:41] i agree with ann open Beginners Team, But a closed Council Team [00:41] 3. We need some people who are willing to put some serious time into productive projects [00:41] Council conversations and decitions need to be open. [00:41] s/council/bt channel ops [00:41] i agree, i think the monthly Council meetings will quickly bleed off the inactives [00:42] That is all we really need, channel ops to rid the channel of the occasional troll [00:42] I do not want to see this team implode. We worked to hard to get hear an a lot of the community is starting to take notice of us [00:42] We still need leaders [00:42] We do have an opening, I think. [00:42] so let us ne civilized in handling this dierty laundry [00:42] bodhi_zazen, Running? [00:42] Who is going to work with other community teams ? [00:43] Who is going to provide support ? Where ? IRC ? Forums " LP ? [00:43] Not me for a while, personal life issues [00:44] I'm hunting for a job, trying to stay in my apt and at this point in the release cycle my Ubuntu time is tied up in Kubuntu... [00:45] Don't all step forward at once =) [00:45] bodhi_zazen: the support will be prvided not by BT [00:45] You see, all this team does any more is debate, no workers [00:46] bodhi_zazen, I am always in. But Promise me that a -tem channel exists [00:46] -team* [00:46] bodhi_zazen: the spport will be provided by the teams we mentor users for [00:46] duanedesign: I thought we agreed to split the team into two roles - support AND working with other teams [00:46] * MrChrisDruif is off, bicker among yourselves. I think the document Charles put up is the direction we should try to go for. [00:46] we should first start by defining the BT mission [00:47] duanedesign: I agree with your definition "the spport will be provided by the teams we mentor users for" [00:47] bodhi_zazen: at its most simp[le. Help users get involved in the community [00:47] I agree, drop support form BT, support goes to IRC, forms, LP, etc [00:47] I would agree with that definition, and I think the entire council would as well [00:48] I agree with that mission, duanedesign, for what it's worth. [00:48] The rest of the team, however, is not willing to do that [00:48] +1 the statement [00:48] Which would mean forking the team [00:48] bodhi_zazen, Am I in the "rest of the team" statement still? [00:48] Why not? [00:48] One team for community involvement and one for support [00:49] bodhi_zazen: does that mean dropping MOTU training? As they understood it was going to be UBT? [00:49] phillw: depends on who you ask [00:49] I thought MOTU had a mentoring project? [00:50] bodhi_zazen: indeed, so a meeting like this is good :) [00:50] jledbetter: not really, they were heading to UBT [00:50] Personally I would drop the support role from the BT and change to getting people involved in the community [00:50] I think the entire council wants that [00:51] a lot of active users like to give supprt. So i think we politely nudge then to #ubuntu [00:51] move support to the appropriate, already existing community infrastructure - forums, LP, IRC, wiki [00:52] The BT is for"Help users get involved in the community" [00:52] bodhi_zazen: you know through ~lubuntu, I do want at least one of our devs to become MOTU, He is capabble, but the the teams do not sema to be able to decide who says 'yes' [00:52] so this may mean directing them to forums, IRC, LP wiki [00:52] This is what I am looking for. 1) I don't like duplicated efforts. 2) I believe in helping new contributers make the transition into a team that works on a 6 month cycle with hardcore deadlines. 3) I believe in helping new people to Ubuntu. [00:52] or MOTU or what have you [00:53] 4) I dislike people who try to use teams to inflate egos. [00:53] The actual "work" gets done by the wiki team, or on #ubuntu, or on the fourms [00:53] One moment! [00:53] DarkwingDuck: +1 [00:54] I think we vote for a council... so this is just input [00:54] So again, back to square one, mission statement please =) [00:54] Probably need to stage the transition to be honest [00:55] Change mission statement to support and Help users get involved in the community [00:55] nudge members to #ubuntu or LP or MOTU [00:55] In 6-12 months re-define the mission statement to only "Help users get involved in the community" [00:55] what's wrong to give support? waste of time? or something? [00:55] you are not oblide to do it [00:56] Nothing is wrong with it [00:56] In the past support was the core of the mission statement, and we are changing [00:56] PabloRubianes: some we win, some we lose - that should not stop us trying [00:57] so support will be provided not by the BT, but by existing teams / venues == less duplication of effort, etc [00:57] Okay sorry gang.. Kids are yelling and I need to support the wife. [00:57] DarkwingDuck, See you later. Thank you for coming:) [00:59] bodhi_zazen: I'd give a +1 for that :) [01:00] My proposal would be - Change the mission statement to include BOTH support AND Help users get involved in the community [01:01] Expect those who want to do #2 , Help users get involved in the community, build the bridges over the next 6 months [01:01] then re-evaluate [01:01] bodhi_zazen: how many coucil members are here? [01:01] Depending on what progress is made we can morph to Help users get involved in the community or support ONLY, or continue on the dual path [01:02] seem like that would make the most people happy [01:02] poke Calling all FC council members [01:02] * bodhi_zazen is here [01:03] The team also has to find a more effective method of communication, not everyone can make IRC meetings [01:04] as do rioters, if you would propose your motion. [01:05] phillw: you willing to post that on the BT mailing list ? [01:05] Ask people to vote on the mailing list ? [01:05] Or set up some other voting method ? [01:05] We could take a straw poll here now [01:06] Please vote , Dual mission (+1) ? [01:07] bodhi_zazen: with the greatest of pleasure, but there is a PM for you :) [01:07] duanedesign, You can do #vote and I think it'll tally up votes for you [01:08] we are voting now? [01:08] bodhi_zazen put a vote to the floor [01:09] jledbetter: I do not think I can do that [01:09] Why not, bodhi_zazen? [01:09] My point is, I do not think there are enough people here now to vote, we should up it up on the mailing list [01:09] Alright. Sounds good. I second that motion. [01:11] duanedesign, Still with us? [01:11] I'm back [01:12] welcome back DarkwingDuck [01:18] Are we done here? [01:18] Mmm [01:18] Done are we? [01:18] Dunno, I came back and nothing. [01:19] bodhi_zazen, I think, was making a motion to vote on the mission on the mailing list. [01:19] +1 [01:19] We seem to have lost duanedesign to the RL monster so can't #vote or #endmeeting :) [01:19] DarkwingDuck, Since you're our other leader here. Feel free to stick a fork in it :) [01:20] Anything else anyone else wants to bring up? [01:22] What about the people who want to be mentored? Just received an email from a new person. [01:22] Or was that previously mentioned? [01:23] :/ [01:24] JasonO, Mentoring will happen (According to the FGs) [01:24] Okey. FGs? [01:24] but I am still not sure whether #ubuntu-beginners-team will exist or not [01:24] Focus Group [01:25] Oh. [01:25] Why wouldn't it exist? [01:33] Well, I need to get back to work :) See y'all later! [01:33] #endmeeting [01:33] duanedesign: ping === seeker_ is now known as seeker === doko__ is now known as doko === medberry is now known as med_out [10:47] + === Mkaysi_ is now known as Mkaysi === micahg_ is now known as micahg [14:57] hey [14:59] o/ [14:59] * wendar = pseudoskaet waves [14:59] * joshuahoover waves [14:59] * charlie-tca waves [15:00] hi all, let's get started [15:00] #startmeeting [15:00] #topic Oneiric Release Meeting overview - wendar [15:00] . [15:00] Agenda is at: [15:00] wendar: Error: Can't start another meeting, one is in progress. [15:00] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-08-12 [15:00] . [15:01] duanedesign: could you end your meeting? :) [15:01] pseudoskaet... sounds clinical [15:02] hi [15:03] slangasek: I don't see duanedesign, can we force an old meeting to end? [15:03] did this meeting move to an hour earlier? usually I can't make it but this is nice :) [15:03] AlanBell: is there any way to end an old meeting now? [15:03] wendar: only if we have someone ( AlanBell ?) who can kick it on the server [15:04] last time this occured, someone just /nick'd to the person who should have closed their meeting and #endmeeting'd [15:05] ah, but duanedesign is still on the channel :/ [15:05] poop [15:05] I think we've no choice but to move ahead without the bot to back us? [15:05] #endmeeting [15:05] thanks, AlanBell [15:06] it didn't do it [15:06] I will try and do it another way [15:07] #startmeeting [15:07] nope . . . [15:08] let's carry on, then [15:08] Is there some file which can be edited for meeting to stop? [15:08] thanks for trying [15:08] @help config reload [15:08] Mkaysi: (config reload takes no arguments) -- Reloads the various configuration files (user database, channel database, registry, etc.). [15:08] Could do it after editing config [15:08] * AlanBell restarts the bot [15:08] I was going to code something up to automatically end a meeting after an hour of inactivity or something [15:09] try now [15:09] #startmeeting [15:10] and again [15:10] #startmeeting [15:10] Meeting started Fri Aug 12 15:10:33 2011 UTC. The chair is wendar. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [15:10] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [15:10] yay [15:10] yay! [15:10] onward... [15:10] #topic Oneiric Release Meeting overview - wendar [15:10] . [15:10] Agenda is at: [15:10] [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2011-08-12 === meetingology changed the topic of #ubuntu-meeting to: Oneiric Release Meeting overview - wendar [15:10] TOPIC: Oneiric Release Meeting overview - wendar [15:10] . [15:11] interestingly enough, unloading a plugin isn't case sensitive, but loading it again is! [15:11] 11.10 FeatureFreeze : August 11, 2011 at 2100 UTC [15:11] If new features still need to be uploaded, please follow: [15:11] https://wiki.ubuntu.com/FreezeExceptionProcess [15:11] and the plugin is "MeetBot" [15:11] . [15:11] Upcoming events: [15:11] - 11.10 BetaFreeze: Aug 25, 2011 at 2100 UTC. [15:11] - 11.10 UserInterfaceFreeze: August 25, 2011 at 2100 UTC. [15:11] - 11.10 Beta 1: Sept 1, 2011. [15:11] . [15:11] AlanBell: yay posix semantics :) [15:11] Bugs targetted for this release can be found: [15:11] #link https://bugs.launchpad.net/ubuntu/oneiric/+bugs [15:11] Bugs milestoned for oneiric beta-1 are at: [15:11] #link https://bugs.launchpad.net/ubuntu/oneiric/+bugs?field.milestone% [15:11] 3Alist=39143 [15:11] . [15:11] Other news: [15:11] Please take a moment to complete the bug life cycle survey, [15:11] #link https://docs.google.com/spreadsheet/viewform?formkey=dGZqcm9YS083V19XT1RSMmV1RFJ2U3c6MQ [15:11] your input on helping us improve our workflow would be much appreciated. The survey closes next Friday. [15:12] . [15:12] Reminder: please use ".." on separate line when you've finished [15:12] typing. If someone wants to comment during the updates, please "o/", [15:12] so we know to wait. [15:12] questions? [15:12] .. [15:13] #topic QA team update - jibel or pgraner === meetingology changed the topic of #ubuntu-meeting to: QA team update - jibel or pgraner [15:13] TOPIC: QA team update - jibel or pgraner [15:13] Hey all [15:14] * Automated Testing progress [15:14] * public jenkins is available: https://jenkins.qa.ubuntu.com/ [15:14] Test from the private instance will be added to the public instance in the coming weeks [15:14] * Created isolated VM environment for DX to run tests [15:15] * New tests added to daily run for alternate and desktop OEM install [15:15] * Follow up on A3 ISO Testing [15:15] * bugs from Alpha 3 ISO Testing have been affected to the engineering team or defect analysts for review. [15:16] * Bug activity [15:16] * Top 5 packages with most opened bugs reported during last week (over a total of 471 unique reports (no dups)) [15:16] unity: 50 reports (10.62%) [15:16] compiz: 26 reports (5.52%) [15:16] linux: 20 reports (4.25%) [15:16] software-center: 19 reports (4.03%) [15:16] nautilus: 17 reports (3.61%) [15:16] * 33 reports are regression (7% of the bugs reported over last week) [15:16] unity/compiz, ati and intel video driver and various gnome applications [15:16] .. [15:16] any questions ? [15:16] or comment [15:17] o/ [15:17] charlie-tca, please ask [15:18] Does jenkins being public mean we can now get Xubuntu images tested automatically? [15:18] or is that not an appropriate question here and I will discuss later? [15:19] it is not ready yet, we'll first publish what we are currently running on the private instance. [15:19] Okay, thanks [15:19] .. [15:19] we can talk about it during next qa meeting, please add an item to the agenda [15:19] Any more questions for jibel? [15:20] #topic Hardware Certification team update - mlegris === meetingology changed the topic of #ubuntu-meeting to: Hardware Certification team update - mlegris [15:20] TOPIC: Hardware Certification team update - mlegris [15:20] Hi all o/ [15:20] [Week 32 Testing Report] [15:20] A3 Testing this week, ~200 systems being manually tested [15:20] [link] http://people.canonical.com/~hwcert/oneiric-testing/oneiric_alpha3.html [15:20] ~100 tested so far, about halfway through the laptop/desktop pile :) [15:20] . [15:20] Bugs: [15:20] ~20 HW specific bugs reported against Oneiric [15:21] .. [15:22] any questions? [15:22] #topic Security team update - micahg or mdeslaur === meetingology changed the topic of #ubuntu-meeting to: Security team update - micahg or mdeslaur [15:22] TOPIC: Security team update - micahg or mdeslaur [15:23] [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Oneiric [15:23] [LINK] http://status.ubuntu.com/ubuntu-oneiric/canonical-security.html [15:23] We are on the trend line for our assigned work items in our blueprints. We are trying to balance reactive security with work items at this time, and are getting to our remaining work items as time allows. [15:23] A new apparmor snapshot landed before Feature Freeze, there might be a need for an FFe for the dbus mediation, but we'll know more next week. [15:23] Looking at the list of oneiric bugs, I don't see anything else worth highlighting. [15:23] .. [15:24] Any other FFe's likely from security? [15:24] Depending on if I have time, I might need some for apparmor browser profiles [15:25] but it's already getting late for that [15:25] possibly a couple of FFe's to continue migrating away from gksu to pkexec [15:25] ok, thanks [15:25] other questions for micahg? [15:26] #topic Kernel team update - ogasawara === meetingology changed the topic of #ubuntu-meeting to: Kernel team update - ogasawara [15:26] TOPIC: Kernel team update - ogasawara [15:26] Overall status is reported at the first link below. Burn down for Oneiric Beta-1 is at the second link below. Burndown for the cycle is at the third link: [15:26] [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Oneiric [15:26] [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team-ubuntu-11.10-beta-1.html [15:26] [LINK] http://people.canonical.com/~platform/workitems/oneiric/canonical-kernel-team.svg [15:27] Last week we uploaded the Ubuntu 3.0.0-8.10 kernel. This was rebased onto upstream stable v3.0.1. We've queued some security and bug fixes recently and plan to upload soon. We are currently trending above our burn down chats and will begin raising any outstanding work items that need finishing with the team. They are not release critical. [15:27] Of the bugs called out on the agenda against the kernel, status is as follows: [15:27] #542660: looks to be related to EFI boot not loading the video bios into ram. [15:27] #557261: awaiting updated dmesg output. [15:27] #708286: assigned to kernel dev and actively being investigated. [15:27] #754711: on a 3.0 oneiric kernel, system now suspends but doesn't resume. systemtap debug scripts to help investigate are being worked on for Oneiric, see 815944 (systemtap fix recently posted upstream). [15:27] #758486: updated debug information attached, investigation ongoing. [15:27] #760131: partly fixed in Oneiric and soon natty, more analysis ongoing upstream. [15:27] #784937: investigation by kernel dev still ongoing as well as discussion with upstream. [15:27] #790712: the order 5 allocation seems to be bogus and non-fatal; further investigation ongoing. [15:27] #791850: kernel dev able to reproduce on a CentOS test system. appears to have isolated the bad commit. investigation remains ongoing. [15:27] #793486: the requested debug info has been attached, investigation ongoing. [15:28] Questions? [15:28] .. [15:29] #topic Foundations team update - cjwatson === meetingology changed the topic of #ubuntu-meeting to: Foundations team update - cjwatson [15:29] TOPIC: Foundations team update - cjwatson [15:29] Feature progress this week: [15:29] * foundations-o-ipv6-healthcheck: d-i now supports IPv6. [15:29] * desktop-o-gtk3-gnome3: Completed Ubiquity port to PyGI. (This is blocked on resolving webcam-related dependencies before upload, but that should be finished ASAP; Evan is going to write an FFe request.) [15:29] * foundations-o-great-cd-debate: Allison's USB seeds landed (and decrufted). After discussion with Kate et al, we'll finish converting the DVD images to these next week. [15:29] * desktop-o-cd-localization: syslinux-theme-ubuntu uploaded, and fixed some associated live-build issues. The generated images are still somewhat broken, but should be easily fixable at this point. [15:30] * foundations-o-ubiquity: Wireless networking page merged. [15:30] * Upstart: Sprint held last week: see https://lists.ubuntu.com/archives/upstart-devel/2011-August/001707.html for a summary. [15:30] * foundations-o-dhpython-transition: python-support and python-central removed from all Ubuntu CDs by FF. [15:30] * foundations-o-multiarch-next-steps: skype installable from the archive via multiarch (modulo a Qt fix). [15:30] I don't have a bug update right now, just working our way through them ... [15:30] Also part of the multiarch spec is still pending an LP rollout [15:30] .. [15:31] Questions for cjwatson? [15:31] Any FFe's anticipated from Foundations? [15:32] ubiquity as mentioned above [15:33] it's possible we'll need something for the tail-end of localised image building [15:33] I think the apt mirror method is probably shelved for this cycle due to being blocked on IS, but if IS come through on that it's possible we might consider that since the code is mostly done on our side [15:34] aside from that I'm not aware of anything but I will keep the release team informed if anything else does come to my attention [15:34] great [15:34] (this may reflect my lack of knowledge as much as anything else though ;-) ) [15:35] (skaet asked me to pester everyone about FFe's, so she can look over the logs later) [15:35] yeah [15:35] Daviey and most of the server team are traveling after the sprint, so we'll skip them. [15:36] But, I hear great progress was made this week. [15:36] #topic ARM team update - ogra === meetingology changed the topic of #ubuntu-meeting to: ARM team update - ogra [15:36] TOPIC: ARM team update - ogra [15:36] oops [15:36] = Full Status is at: = [15:36] https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Oneiric [15:36] -- [15:36] = Summary = [15:36] - Parts of the ARM team attended the LXC/server meeting this week. [15:36] - TI/linaro reworked u-boot to not need a separate x-loader package anymore, this will require some changes [15:36] to build system and bootloader tools which will likely need freeze exceptions (the change sadly was only announced yesterday) [15:36] - Cleanup of jasper is ongoing [15:36] - AC100 image is in progess, ac100-tarball installer sits in NEW awaiting review, debian-cd changes are pending [15:36] - mx5 images are in progress, kernel sits in NEW, awaiting review [15:36] - server QA testing is ongoing [15:37] -- [15:37] = Image Status = [15:37] - Desktop images don't build due to archive skew [15:37] - Server images build and install fine [15:37] - Netboot images work fine [15:37] -- [15:37] = Specs = [15:37] - Entire http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel.html [15:37] - B1 http://people.canonical.com/~platform/workitems/oneiric/ubuntu-armel-ubuntu-11.10-beta-1.html [15:37] (the tracker has only been adjusted today for the new launchpad team name, WI tracker should pick up tomorrow) [15:38] .. [15:38] Questions for ogra? [15:38] o/ [15:39] shoot [15:39] GL-ES patches for compiz / nux [15:39] do you have the "bandwidth" to take that at this stage? [15:39] (there should be a discussion on monday about that in the team as well) [15:39] afaik the patches exiswt and are on their way upstrream [15:40] right, but i want to get a feel of who's onboard to have that change go [15:40] we can take that offline or on monday [15:40] ok [15:40] it is expected that we ship GLES support in unity in oneiric [15:41] so we better find out who adds them ;) [15:42] the branch arrived a few days ago, right, we need to find out [15:42] afaik it shouldnt be much effort though given they were all written in an upstreamable way for natty [15:43] anything else ? [15:43] nope [15:43] :) [15:43] .. [15:43] #topic Linaro update - fabo or rsalveti === meetingology changed the topic of #ubuntu-meeting to: Linaro update - fabo or rsalveti [15:43] TOPIC: Linaro update - fabo or rsalveti [15:43] o/ [15:43] Linaro update - courtesy of rsalveti [15:44] * Cross toolchain based on 4.6 for armel/armhf updated against latest gcc update [15:44] * linux-linaro-lt-mx5 (freescale landing team tree, based on .38 with Natty's sauce on top) pushed to the archive, janimo will be creating ubuntu images with it for imx53 [15:44] * Good discussions at Connect about continuous integration and validation for the Linaro components. Upstream and Linaro kernel validation should be the first steps. [15:44] * May need a FFe if the x-loader replacement with U-Boot SPL goes fine with Linaro 11.08 release (require image changes for at least omap 4) [15:44] * Good progress at bug 810402 by Dave Martin, seems we have at least a valid workaround, what should help with tons of ARM FTBFS [15:44] Launchpad bug 810402 in ocaml (Ubuntu Oneiric) "all native ocaml programs segfault on armel" [High,Confirmed] https://launchpad.net/bugs/810402 [15:44] * Seems no progress with bug 775849, we had a conversation with Michael Hope and doko, but it seems this bug is still not at the TWG radar [15:44] Launchpad bug 775849 in eglibc (Ubuntu) "[armel] eglibc test regressions on armel in oneiric" [High,Confirmed] https://launchpad.net/bugs/775849 [15:44] .. [15:44] Any questions for fabo? [15:45] fabo: the TWG doesn't seem to be responsible for it [15:46] doko: the bug is assigned to the TWG. If they aren't responsible, we should find the right assignee [15:47] doko: any suggestions on who should take it on? [15:47] ubuntu-arm? [15:50] sounds like there may be a little bug handoff needed, we can find out if they're willing to adopt it this week [15:50] well, please re-assign to ubuntu-arm. we'll follow with the TWG in case they find time to look at it. [15:50] will add it to the action items so kate remembers to check up on it next week [15:51] ogra: ^ [15:51] other questions for fabo? [15:52] #topic Desktop Team update - kenvandine or seb128 or pitti === meetingology changed the topic of #ubuntu-meeting to: Desktop Team update - kenvandine or seb128 or pitti [15:52] TOPIC: Desktop Team update - kenvandine or seb128 or pitti [15:52] hey wendar [15:52] hi [15:52] pitti is travelling back so it's me [15:52] [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [15:52] [LINK] http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team-ubuntu-11.10-beta-1.html [15:52] [LINK] http://status.ubuntu.com/ubuntu-oneiric/canonical-desktop-team.html [15:53] * Reduced activity during a part of the week due the desktop summit participation and holidays [15:53] * We got most of the feature landed before the feature freeze though [15:53] * New unity and indicator stack got uploaded on time for the freeze (with quite some bugs though) [15:53] * Compiz still pending from dx, will likely need a ffe [15:53] * GNOME 3.1.5 coming next week [15:53] [15:53] * pitti pinged me just an hour before the meeting so I didn't manage to review the bug list, we will do that next week now that the ff is over [15:53] * the retracers are down, not sure when they will be sorted [15:53] * we will like have a ffe requests (lightdm, gwibber, telepathy-indicator, thunderbird u1 contacts syncing, ...) [15:53] .. [15:53] Questions for seb128? [15:55] #topic Desktop Experience Team Update - dbarth or njpatel === meetingology changed the topic of #ubuntu-meeting to: Desktop Experience Team Update - dbarth or njpatel [15:55] TOPIC: Desktop Experience Team Update - dbarth or njpatel [15:55] hi [15:55] full report at https://wiki.ubuntu.com/DesktopExperienceTeam/OneiricReleaseStatus [15:55] to add to what seb128 just said [15:55] unity 4.8 released on time, along with unity-2d [15:56] we have bugs but we're there [15:56] the compiz release was scattered later this week: we have test package ready, we're assessing the quality of the latest changes to request an FFE or fallback to an earlier version [15:57] indicators got a nice update with the rest of the peripherals support we had planned for O [15:57] the touch team has hit 100% on the work items board, with eog / evince support now in 11.10 [15:58] and we're on top of the upper half of the CJK issue, knowing that the bottom half is now fixed [15:58] i take this occasion to remind people about the CJK call for testing sent o u-devel this week [15:59] status for the bugs on the radar: [15:59] [805063]: on the work list, will start fixing those regressions next week [15:59] [806358]: probably a driver issue, passed to Jay for further investigation with the xorg team [15:59] [809378]: didrocks on top of it, was fixed but there is a further regression elsewhere [15:59] [814065]: invalid, design guidance sought [15:59] [810145]: incomplete, investigating to get a reproducible test case [15:59] .. [16:00] Any other FFE's anticipated beyond what you and seb already mentioned? [16:01] an update to the music lens maybe [16:01] but that's still discussed closely with desktop and the release team [16:01] a delightfully short list, thanks [16:01] other questions for dbarth? [16:01] hpopefully yes ;) [16:03] #topic Kubuntu Team update - ScottK === meetingology changed the topic of #ubuntu-meeting to: Kubuntu Team update - ScottK [16:03] TOPIC: Kubuntu Team update - ScottK [16:03] seb128: when will gnome updates start next week? [16:04] doko, today, I'm going to upload a few, continued on monday and tuesday next week [16:04] gah ... [16:06] doko: want to elaborate before we go on to Edubuntu? or, just a passing comment? [16:06] no, just did hope for some stability for a test rebuild [16:08] wendar: I'm here now. [16:08] seb128/doko: sounds like it would be helpful to coordinate a time of relative stability [16:08] For Kubuntu we are in good shape for base KDE/distro packages. We didn't get all the feature work done we wanted due to less manpower this cycle. [16:09] I anticipate a standing FFe for additional (tech preview) work on plasma-mobile/active work. [16:10] slangasek multiarch'ed qt4-x11 yesterday, so waiting to see how that works out. [16:10] ... [16:10] Questions for ScottK? [16:11] #topic Xubuntu Team update - charlie-tca === meetingology changed the topic of #ubuntu-meeting to: Xubuntu Team update - charlie-tca [16:11] TOPIC: Xubuntu Team update - charlie-tca [16:11] There were no desktop images all week. We have gotten fresh desktop images today. Don't know if they work yet because the syncs are taking a long time due to the massive changes. [16:12] * #789333: "users-admin crashes on start because of mixed GTK2 and 3 symbols" - derivatives are working on this, hopefully will have a fix for beta1. [16:12] * #799238: "Xubuntu i386 and amd64 20110618 xserver abort" - resolved with current xorg [16:12] * #820731: "Oneiric Ocelot Xubuntu Desktop images fail to install" - Don't know which casper upload fixed it, there were two. One of them did fix the issues. [16:12] * #820460: "User not created with encrypted home partition: user-setup exit code 32" - fixed [16:12] Don't really know what the status of lightdm is now for derivatives. Not having valid images made testing difficult. [16:13] Xubuntu will ask for FFe's as they come up. We are waiting for things to settle down now after FeatureFreeze to see how good everything is. :) [16:13] Any questions? [16:13] .. [16:14] #topic Edubuntu Team update - highvoltage === meetingology changed the topic of #ubuntu-meeting to: Edubuntu Team update - highvoltage [16:14] TOPIC: Edubuntu Team update - highvoltage [16:14] highvoltage: around? or should I do the Edubuntu update? [16:15] hmm, guess I'll go ahead (quite likely highvoltage is out for lunch at this time) [16:15] so not much on Edubuntu's side. alpha-3 went quite well and we didn't have anything big to push by feature freeze [16:16] the biggest news is that our installer is now fully translated (took a long time to get it working) [16:16] I fixed LTSP to actually install and work but we'll still need to rewrite the current LTSP live plugin as it doesn't work with NM 0.9 [16:17] we'll file a FFe for the LTSP live work (as it's going to be a full rewrite to use the NM API instead of ignoring it) [16:17] I saw that lightdm is now apparently fixed to work for derivatives so that's still on our todo list (as we offer two choices of desktop environment) [16:17] other than that, I think that's it for Edubuntu [16:17] any questions? [16:17] .. [16:19] gilir is on holiday, so we'll skip Lubuntu [16:19] #topic Toolchain update - slangasek or doko === meetingology changed the topic of #ubuntu-meeting to: Toolchain update - slangasek or doko [16:19] TOPIC: Toolchain update - slangasek or doko [16:22] they were both around earlier, perhaps they'll pop back on in a minute [16:22] #topic MOTU team update - tumbleweed === meetingology changed the topic of #ubuntu-meeting to: MOTU team update - tumbleweed [16:22] TOPIC: MOTU team update - tumbleweed [16:22] The usual, lots of FTBFS packages: [16:22] http://corelli.tumbleweed.org.za/ubuntu-qa/qa-ftbfs/oneiric-historical.html [16:22] a handful of RC Bugs to look at merging/picking: [16:22] http://qa.ubuntuwire.com/bugs/rcbugs/oneiric/ [16:22] a good number of unfinished transitions: [16:22] http://people.canonical.com/~ubuntu-archive/transitions/ [16:22] http://people.canonical.com/~ubuntu-archive/nbs.html [16:22] I saw a few new releases and dh_python2 transitions without FFes, this morning. I assume we're giving them some slack for a day or so? [16:23] (sorry, I'm here, was just checking with doko which of us should give the update) [16:23] anyway, that's me [16:23] .. [16:24] they should have FFE's, feel free to remind folks who missed [16:24] questions for tumbleweed? [16:25] oh, micahg reminds me that he intends to FFe eclipse (if it's possible without breaking the universe) [16:26] fortunately, eclipse is more of a "leaf" package than a "root node" package [16:26] but, I imagine skaet will want to do some dependency checking [16:27] back to... [16:27] #topic Toolchain update - slangasek or doko === meetingology changed the topic of #ubuntu-meeting to: Toolchain update - slangasek or doko [16:27] TOPIC: Toolchain update - slangasek or doko [16:27] wendar: it is, but its deps aren't necessarily :) [16:27] the last toolchain updates anticipated for the cycle have been done [16:28] micahg: indeed [16:28] the latest eglibc from unstable has also been merged up - regressing multiarch support temporarily, but that's worked on [16:28] now just waiting for the archive to be in a buildable state generally in order to start test rebuilds [16:28] .. [16:29] questions for slangasek? [16:30] That brings us to the end of reports. Any other questions? [16:30] doko, wendar: I don't expect disturbances due to the GNOME updates [16:30] they are mostly standalone components if they fail to build they should not break other things [16:30] sure, xubuntu will need ffe's for dh_python2 and libssl1.0.0 transitions needed for xubuntu still [16:32] surely libssl1.0.0 transitions are RC bugs, and won't require FFe? (they will be packages that can't currently be rebuilt) [16:32] tumbleweed: yeah, that was a C/P error :) [16:33] err...C&P [16:33] .. [16:34] sounds like that's a wrap [16:34] Thanks jibel, mlegris, michahg, ogaswara, cjwatson, ogra, fabo, seb128, dbarth, ScottK, charlie-tca, stgraber, tumbleweed, slangasek and all! [16:34] thanks, wendar! [16:34] Thank you, wendar, for chairing! [16:34] thanks wendar [16:34] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology is the new Mootbot https://wiki.ubuntu.com/AlanBell/mootbot [16:34] Meeting ended Fri Aug 12 16:34:31 2011 UTC. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot . (v 0.1.4) [16:34] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-12-15.10.moin.txt [16:34] thanks wendar! see you at LinuxCon [16:34] thanks for chairing wendar [16:34] see you there! [16:35] thanks wendar [16:42] (thanks stgraber) [16:47] highvoltage: np. I really should add the release meeting to my calendar so I make sure I'm around [16:48] (I just happened to look at -meeting at the right time) === jsalisbury is now known as jsalisbury_otp === Ursinha is now known as Ursinha-bbl === lag` is now known as lag === lag is now known as Guest26716 === jsalisbury_otp is now known as jsalisbury === ghostcube_ is now known as ghostcube === yofel_ is now known as yofel === emma is now known as em