[07:58] morning everyone [07:58] morning ochosi [07:59] you know anything about lightdm and setting sessions, if you do someone could use your help :) [08:04] hmm [08:05] well generally i think you need to create a session file and then set a session in lightdm.conf [08:05] but i could be wrong, has been a while since i set up my own sessions [08:05] madnick knows more about lightdm [08:05] * ochosi thinks it's not lightdm specific [08:06] I have fluxbox - did sudo /usr/lib/lightdm/lightdm-set-defaults -s fluxbox - that sets lightdm.conf ok, it also made no difference - fiddled with .dmrc to change that - that failed as well [08:06] * hobgoblin gave up :) [08:06] hobgoblin: i think you need something like: /usr/share/xsessions/xubuntu.desktop [08:06] for fluxbox [08:09] I got a fluxbox.desktop [08:09] but no matter - wasn't for me :) [12:42] quick reminder: there's a xubuntu team meeting today (15:00 UTC) [13:47] Oh cr*p, gotta run to the grocery store now instead of after the QA meeting. [14:09] astraljava, heh. :) [14:10] Xubuntu community meeting in about 50 mins at #xubuntu-devel. Everybody is welcome! Agenda at https://wiki.ubuntu.com/Xubuntu/Meetings [14:12] knome: Is the next meeting's agenda always on that page? [14:12] astraljava, yup. [14:12] 'k, thanks. [14:13] astraljava, after the meeting, the chair updates the minutes and the "prev meeting", and empties the agenda [14:13] (or leaves the items that are carried on, but you get the idea) [14:13] Sounds like a good process. [14:13] well, it works. [14:13] you don't have to edit *too many pages* [14:20] knome: Just a quick check, am I correct in not seeing any real updates recently? [14:21] yup, that's correct [14:21] Well, my seeing is not the part that needs a reality check. :D [14:21] heh :) [14:21] Ok, thanks. [14:21] * astraljava tries to pay more attention from now on. [14:21] i'm expecting things to start rolling soonish, hopefully our meeting at sunday clears some things up [14:21] It's been a helluva spring/early summer [14:21] well, things should be reported at the meetings [14:21] Sunday? [14:21] so that should be relatively easy [14:22] xubuntu QA? [14:22] Oh yeah, that. [14:22] what time was that again, btw? :P [14:22] I was thinking the Team meeting. [14:22] not that i ever forget any times. [14:22] Well I don't know, for some reason it's not visible in my google cal at the moment. Let me get back to you on that one. [14:23] awwh :D [14:23] pleia2! === yofel_ is now known as yofel [14:31] hey GridCube [14:31] hi knome :) [14:31] sup? [14:31] meeting in 30 [14:32] nothing much else up ;) [14:32] :D i know [14:32] :D good to know [14:39] Ха!!! Назгул с нами... :-) [14:39] !en [14:39] The #ubuntu, #kubuntu and #xubuntu channels are English only. For a complete list of channels in other languages, please visit https://wiki.ubuntu.com/IRC/ChannelList [14:39] humph, goes for -devel too [14:39] Sorry!!! [14:39] no problem === newbie is now known as Guest20627 [14:53] Err... ok, for some reason, I'm not seeing the QA meeting for X anymore. [14:54] I wonder what happened. [14:54] pleia2: HALP! [14:56] so, who's here for the meeting? [14:56] o/ [14:56] have to run now :( [14:56] see you ochosi [14:56] madnick_ also told he's not able to make it today [14:56] I'm around [14:56] hey bluesabre_ :) [14:56] but: on the subject of compositor by default: i'm for keeping it on. haven't had (m)any complaints about it [14:57] the only bug i know is from ubiquity installer [14:57] ochosi, we'll probably postpone any decisions to next meeting anyway [14:57] ochosi, regarding that, i mean [14:57] mhm, just wanted to tell you what i think quickly :) [14:57] seey'all! [14:57] yop [14:58] seeya ochosi [14:59] astraljava, micahg, mr_pouit, pleia2, Unit193: you around? [14:59] o/ [14:59] and others too, of course (just pinging team members) [14:59] :) [15:00] seems like we don't have quite as good attendance as hoped for, but anyway [15:00] #startmeeting Xubuntu community meeting [15:00] Meeting started Wed Jun 13 15:00:21 2012 UTC. The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:00] 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 [15:00] #topic Items carried on [15:01] #subtopic Open action items from previous meeting [15:01] #action pleia2 and knome to work on marketing products [15:01] ACTION: pleia2 and knome to work on marketing products [15:01] #action pleai2 to raise publicity on triaging, testing and docs [15:01] ACTION: pleai2 to raise publicity on triaging, testing and docs [15:01] -typo :) [15:02] that was it for the action items, there's nothing special going on there, still need to get working! [15:02] #topic Team updates [15:02] #subtopic Development [15:02] #info Some work done to get Xfce 4.10 in Quantal [15:03] #subtopic Quality Assurance [15:03] astraljava, your stage [15:03] (please use #info) [15:04] #info Some work was done recently to enhance the testing docs, I will dig up the link to those in a minute. The testcases were sanitized, and should now be easier to follow was non-regulars as well. [15:05] #info Since Xubuntu did not do an Alpha-1, we haven't used the new tracker much, yet. We should pick up on that now, though. [15:05] :) i zsynked the images yesterday [15:06] #info https://launchpad.net/~xubuntu-testers is now an *open* team, no need to add your information on the wiki anymore. [15:06] #info There's an upcoming QA meeting this Sunday, I will post info about it on the mailing lists after this meeting. [15:06] #action astraljava to send information on the Xubuntu QA meeting [15:06] ACTION: astraljava to send information on the Xubuntu QA meeting [15:06] bah... you beat me to it. [15:06] hi [15:06] .. [15:06] :)= [15:06] xacobe, hello [15:06] i suppose that's it [15:07] #info The testers should try to make the QA meeting on Sunday to organize [15:07] #subtopic Marketing, Promotion and Artwork [15:07] #info Some improvements done for Greybird, more information later [15:08] #action ochosi to send more information on Greybird and a request for feedback to ML [15:08] ACTION: ochosi to send more information on Greybird and a request for feedback to ML [15:08] can i paste what ochosi said? [15:08] GridCube, the thing about compositor is on the agenda, not WIP [15:08] GridCube, (it's a new item) [15:09] GridCube, but if it's something that's WIP, go ahead :) [15:09] (i mean, if it's something else) [15:09] :) no, it was that [15:09] okay, let's go forward [15:09] #subtopic General updates [15:10] #info knome has been working on the Strategy Document review, more info soon [15:10] #action knome to send information about the revised Strategy Document to ML soon [15:10] ACTION: knome to send information about the revised Strategy Document to ML soon [15:10] is there anything else? [15:10] #info All blueprints are now in place, start your engines! [15:11] i have a comment but goes more to the meetings part [15:11] ok, let's discuss that there then :) [15:11] #topic Announcements [15:11] #subtopic Changes in chairing the meetings [15:11] #link https://lists.ubuntu.com/archives/xubuntu-devel/2012-June/008239.html [15:12] #info The change described in the mail will take place now [15:12] that was what i wanted to comment :) i like that [15:13] we should enforce it to happen, meetings are extremely important to me [15:13] #info Basically, any team lead can chair a meeting; if the project lead or any team lead is not available, an informal meeting should take place, and the main points sent to the ML [15:13] #subtopic Changes to the Testing lead position [15:13] #link https://lists.ubuntu.com/archives/xubuntu-devel/2012-June/008242.html [15:14] #info Since there has been no objections against the mail, the change takes place now [15:14] #info Janne Jokitali (astraljava) is the new Xubuntu QA lead [15:14] ...aaaand for the records, it's Jokitalo (will fix that in the minutes) [15:14] astraljava, congrats! [15:14] *smirk* [15:14] Danke. [15:15] is there any announcements any team leads (including new ones) would like to shout out? [15:15] #subtopic Other announcements [15:15] From QA: a small addition. [15:16] (again, use #info :)) [15:16] #info The updated (short) testcase sits now at https://wiki.ubuntu.com/Xubuntu/Testing/Short [15:16] No idea what happened to the longer one. [15:16] .. [15:16] that wasn't updated; the old one is still at https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Long [15:17] Oh okay, that's the reason. (we can have a word on why it wasn't updated later...) [15:17] *smirk* [15:17] hehe. :) [15:17] #topic New and emerging items [15:17] #subtopic Feedback on Precise development cycle [15:17] okay, so [15:18] if there is any feedback on the dev cycle, how to do things better, proposals, what worked better than before or anything, the floor is yours [15:18] i think we need more communication [15:18] please note that we are not evaluating the *product* but the *process* [15:18] oh [15:18] well [15:18] no, you are right :) [15:19] that's exactly about the process [15:19] ah [15:19] and i agree [15:19] we started well with the meetings, but somehow let that slip [15:19] +1 [15:19] yes, that what i mean, i was extremely surprised by the logo change [15:19] this is one of the reasons why i made the change to chairing [15:19] i think that was handled pretty bad [15:19] i like the new logo now, but it was an unpleasant surprise [15:20] GridCube, while i agree that we could've communicated better on it, but it was announced [15:20] yes i know, but meeting where so far apart and sporadic that missing them was extremely easy [15:20] i think the biggest reason why the communication was bad was that it happened so late in the cycle; we actually had a real rush to even get it to the release [15:20] GridCube, exactly; again, that's why the new chairing stuff :) [15:20] :) [15:20] GridCube, (and note about the informal meetings) [15:20] yes i see that [15:21] generally, any communication between contributors and community is encouraged [15:21] and i see we have a twitter feed and g+ [15:21] so i hope we use it [15:21] yes, though that's for a bit different communication, but still [15:21] yes, the twitter and G+ accounts will be used to announce meetings and new articles on the blog [15:21] no, it the same, sending the minutes to twitter and g+ [15:22] its part of the communication [15:22] (and we now have an official linkedin xubuntu users group) [15:22] Whee! [15:22] :) yes, i hope the password didnt got stolen in the bunch :P [15:23] GridCube, yes, it's part of it, but it's not developer-developer communication; IRC, wiki and the mailing lists are designed for those :) [15:23] I hope all of those twitter etc are extra to existing methods of communication - or some od us will miss things [15:23] :) i know [15:23] hobgoblin, yes, that's how it is [15:23] ok thanks :) [15:23] hobgoblin, as long as you follow the -devel ML, this IRC channel (and maybe the website), you're fine [15:24] and wiki too, if you're interested in a specific area [15:24] I do [15:24] :) [15:25] #agreed We need better communication this cycle; actions already taken are changes in the meetings and social media accounts [15:25] anything else on the subject? [15:25] not from me [15:25] somebody else? [15:25] bluesabre_? [15:26] I'm good. :) [15:26] bluesabre_, is there something we can do better to make new contributors feel more included? [15:26] I felt pretty included the whole time [15:26] that's good feedback - thanks :) [15:26] Thanks! [15:26] let's get rolling again then! [15:27] #subtopic Blueprints; feedback, questions and answers [15:27] o/ [15:27] #link https://wiki.ubuntu.com/Xubuntu/Roadmap/ [15:27] GridCube, go ahead [15:27] #info I've been working on the comparison of music players against gmb, can not continue until i have some input about which are the ones that could be considered to compare, because if media libary integration is not obligatory we already have parole [15:27] :) [15:28] .. [15:28] i'd suggest scheduling some time in the near future (maybe next week) with me, you and maybe ochosi (and of course, others interested) to go through what you have done already, and what would be the next steps [15:29] does that sound like a good plan? [15:29] (I'm a fan of keeping something with a library and sound menu support) :) [15:30] mmh, one of the things we need to discuss is what the "requirements" for features are for the default media player [15:30] that needs to be done before we can rule out players from the comparison [15:30] yes [15:30] i agree that we have way too many players up right now; it would be way too much work to compare all those [15:31] i agree, it sounds like an idea knome [15:31] my stance on it is that we should at least drop anything with Qt or anything that's CLI off [15:31] and, everything that is not on the repositories too [15:31] (and everything that takes >200MB) :D [15:31] mmhm yes, i added them just because they qhere recomended to me to test [15:32] yup, that's good [15:32] in this channels [15:32] #action knome to follow up about the default media player -blueprint on the ML, scheduling some time to go through the spec next week [15:32] ACTION: knome to follow up about the default media player -blueprint on the ML, scheduling some time to go through the spec next week [15:33] GridCube, something around these times is good for you? ~15UTC ? [15:34] anything else on the blueprints? [15:35] #info Generally, all blueprints have no or slow progress, but things are expected to change relatively soon as infrastructure on a few things has been set up [15:36] knome, yes, that a good time [15:37] GridCube, ok, good [15:37] bluesabre_, you have anything about the blueprints? [15:37] astraljava, you? [15:37] Not really. Slow going on the keyboard shortcuts overlay and catfish (which is nearly done) [15:38] o/ [15:38] bluesabre_, great to hear :) you know it already, but please remember to update the work item statuses while you progress :) [15:38] GridCube, yep? [15:38] about the arandr thing [15:38] sure thing :) [15:38] Not really, pretty much the same as others; slow progress, unfortunately. Trying to pick up soon. [15:38] GridCube, what's up with that? [15:38] theres just arandr, grandr is not been made anymore [15:39] i mean theres only one current interface for xrandr [15:39] !info grandr [15:39] Package grandr does not exist in precise [15:39] GridCube, mm-hmm; in that ase, the question is if we want to include that or not [15:39] +c [15:39] yep [15:39] i'm not sure what the status on xfce monitor management dialog is [15:40] if that looks good, then it's an option too [15:40] in 4.10 its the same that in 4.8 [15:40] if not, then there shouldn't be much stopping us from shipping arandr [15:40] so its not good [15:40] well, we can cherry-pick changes if the dialog gets much love in the next weeks [15:40] mmhm [15:40] i agree [15:40] * micahg sees there's a meeting of some sort going on [15:41] micahg, yes, the community meeting announced on the ML;) [15:41] micahg, a community meeting not the less [15:41] :D [15:41] #info grandr is no more, keep an eye on the xfce monitor management dialog [15:42] anything else on the blueprints? [15:42] not from my pocket :P [15:43] ok, let's continue then (let's try to fit this in 1h) [15:43] #subtopic Enable or disable compositor by default? [15:43] #info ochosi told he's +1 for enabling by default [15:43] I'm all for keeping it by default [15:43] i don't really care [15:44] Keeping? [15:44] the reason why i brought this up is that it takes some resources and even causes some problems when enabled [15:44] *enabling [15:44] astraljava, it's enabled by default now. [15:44] Ok. [15:44] What problems exist with it enabled (besides ubiquity)? [15:44] i think that it might be disabled by default in the livecd and enabled in the final install [15:45] bluesabre_, for some people it has brought some rendering issues [15:45] (really rare, but happens) [15:45] ah [15:45] i think the main argument for keeping it enabled is our semi-transparent launcher panel [15:45] we'd have to change that if we disabled compositor [15:46] GridCube, yes, that's something we should look at, because it brings some problems to ubiquity [15:46] GridCube, or, just fix how ubiquity runs xfce, because that's what is actually causing the problems [15:47] maybe we can make some performance tests on how it affects low-end machines at installation time [15:47] knome, the pseudo dock can be rezised and centered and locked so it wont be on all over the bottom of the monitor [15:48] GridCube, yes, but that's not the issue; the issue is that if we disable the compositor, we can't have panel transparency [15:48] and that doesnt need transparencies [15:48] possibly [15:49] #info drop compositor on ubiquity? performance issues with low-end machines at installation time if compositor enabled? [15:49] i think we should investigate this more when we start testing [15:49] right now, there is not much to do [15:49] I'll mark it as a TODO for me. [15:49] astraljava, ok, thanks:) [15:50] #action astraljava to look at enabling/disabling compositor [15:50] ACTION: astraljava to look at enabling/disabling compositor [15:50] #subtopic Meeting schedule; how often should we have meetings? [15:50] weekly, be-weekly? [15:50] we should just run a quick poll to get some idea [15:51] I think bi-weekly is enough. [15:51] #vote Meetings; +1 for bi-weekly, -1 for weekly [15:51] Please vote on: Meetings; +1 for bi-weekly, -1 for weekly [15:51] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [15:51] +1 [15:51] +1 received from knome [15:51] +1 [15:51] +1 received from astraljava [15:51] +1 [15:51] +1 received from bluesabre_ [15:51] GridCube, micahg? [15:51] -1 [15:51] -1 received from GridCube [15:51] sorry i have a huge lag [15:51] no problem :) [15:52] i'll try to wait for some time before proceeding [15:52] i'm sure not all can be as focused as i am... [15:52] i mean, need to chair == need to be focused [15:52] hobgoblin, ? [15:52] hello [15:52] oic [15:53] +1 [15:53] +1 received from hobgoblin [15:53] vote hobgoblin :D [15:53] +0, biweekly except around a release milestone IMHO [15:53] +0, biweekly except around a release milestone IMHO received from micahg [15:53] micahg, mm-hmm, might be ideal that way :) [15:53] #endvote [15:53] Voting ended on: Meetings; +1 for bi-weekly, -1 for weekly [15:53] Votes for:4 Votes against:1 Abstentions:1 [15:53] Motion carried [15:54] let's set the next meeting to two weeks from now [15:54] if there is need, people can have an informal meeting next week :) [15:54] :D [15:54] I'd actually suggest a meeting next week if you want an alpah2 [15:54] micahg, ah. [15:54] *alpha2 even [15:54] in that case... [15:54] let's make it next week ;) [15:55] Decisions are made to be broken anyway. [15:55] #info Next Xubuntu community meeting at 21st of June, at 15UTC [15:55] especially with the meetings on wed, the pre freeze meeting can be planning and the pre release meeting can be make sure everything is good [15:55] * GridCube wonders if that wouldnt actually be alpha1... you know... because we hadnt that one... [15:55] GridCube: because the release schedule says so :) https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule [15:55] GridCube, no, that's still a2 in the ubuntu calendar :) [15:55] :P [15:55] #endmeeting [15:55] Meeting ended Wed Jun 13 15:55:50 2012 UTC. [15:55] Minutes (wiki): http://ubottu.com/meetingology/logs/xubuntu-devel/2012/xubuntu-devel.2012-06-13-15.00.moin.txt [15:55] Minutes (html): http://ubottu.com/meetingology/logs/xubuntu-devel/2012/xubuntu-devel.2012-06-13-15.00.html [15:55] okay, thanks! [15:56] i'll set up the minutes soonish, or at least today [15:56] :D [15:56] Thanks knome, all! [15:56] see you all next week [15:56] :) [15:56] thank astraljava and congrats again on the new position [15:56] add a link to the google calendar [15:56] :D [15:56] Merci beacoup. [15:56] astraljava, i promised ochosi he can chair the next meeting, but you can do the next after that if you want ;) [15:56] sorry [15:56] pleia2, heh, no problem... :) [15:56] knome: Sure thing, I already mentioned to balloons I need practice. :) [15:57] hehe [15:57] also the google calendar link should be linked on the topic fo this channel [15:57] GridCube, we'll get to that later, the whole calendar things is still WIP :) [15:57] (need to see what are the best practices) [15:57] :D yes i know, im just saying [15:57] i need to go to the gents', brb [15:58] astraljava: meeting is on sunday, see it? [15:59] pleia2: Yeah, for some reason it just didn't appear on my other machine. I see it now, thanks! [15:59] ok good :) [15:59] knome: It's 1600 UTC, as well as the QA roundtable. [16:00] pleia2: Are you an expert on google accounts, btw.? [16:00] ...or anyone else in here? [16:00] that's quite a big topic [16:00] * knome is always when he is paid on that [16:00] I have a problem; I want to use another address for all ubuntu-related work, but I can't use google calendar links directly, because that address isn't a google account thingie. [16:00] ^ exactly that :D [16:01] i can learn but.. [16:01] astraljava, i think you need a google account [16:01] astraljava: the other address has to request access [16:01] pleia2: Oh? Tell me more? [16:01] and create a google account with it, as knome says [16:01] google account != gmail [16:02] Hmm... ok. I'll look it up, for now I have no idea how to do that. Thanks! [16:02] just create a google account with the other address [16:04] hmm, any reason the meetings page has the ubuntuteams category? [16:05] isn't it enough for the main page to have it [16:06] ermh, the meeting is of course on the 20th. [16:23] updated https://wiki.ubuntu.com/Xubuntu/Leaders [16:23] astraljava, you don't seem to have a wikipage [16:24] astraljava, or, tbe, anything 'custom' on your wikipage [16:24] No I don't. Yeah, I need to do that. [16:25] yup. once you've done that, link to it from the leaders page [16:26] Will do, thanks. [16:28] np [16:40] *ARGH* [16:40] Now that I created an account for my other email address, there's a rule that you cannot connect two google accounts. [16:41]