[21:05] <raven> hi. how to install a normal kernel instead of a low latency one?
[21:11] <holstein> raven: sudo apt-get install linux-generic should do it
[21:11] <holstein> raven: or just search "linux" in the package manager of your choice.. then refer to...
[21:11] <holstein> !grub
[21:12] <holstein> might need/want linux-generic-pae
[21:12] <holstein> !pae
[21:12] <raven> ok tnx


[14:00]  * stgraber waves
[14:00] <arges> o/
[14:01] <stgraber> #startmeeting 12.04.1 team meeting
[14:01] <meetingology> Meeting started Thu Jul 26 14:01:14 2012 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:01] <meetingology> 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
[14:01] <stgraber> stokachu, smoser, jamespage, jibel_, skaet: ping
[14:01] <smoser> o/
[14:01] <jibel_> o~
[14:02] <NCommander> o_/
[14:02] <stgraber> #topic Action items review
[14:02] <stgraber> xnox to liase with ballons, gema and jibel w.r.t. fs/storage testing
[14:03] <stgraber> no xnox around, so not sure what's the status on this, will keep it on the list of now
[14:03] <stgraber> #topic Review of upcoming deadlines
[14:03] <jibel_> no news from xnox this week
[14:03]  * skaet o/
[14:04] <stgraber> jibel_: ok, I know he's quite busy (days off and quite a bit of work when he's around), so I wouldn't expect much to change at this point
[14:04] <stgraber>   - 2012/08/02: Beginning of PointReleaseProcess and DesktopInfrastructureFreeze
[14:04] <stgraber>   - 2012/08/09: KernelFreeze, LanguageTranslationDeadline, SRU Fix Validation Testing
[14:04] <stgraber>   - 2012/08/16: FinalFreeze, ReleaseNoteFreeze
[14:04] <stgraber>   - 2012/08/23: Ubuntu 12.04.1
[14:04] <stgraber> in case it's not already clear ;) you have ONE week to get your fixes in!
[14:05] <stgraber> #topic Quick look through the current bug lists, checking for progress.
[14:05] <seb128> hey
[14:05] <stgraber> hey seb128
[14:05] <seb128> sort of around but at GUADEC so I might drop offline or not be responsive
[14:05] <stgraber> seb128: just did the action reviews and pasted the deadlines, starting with the bugs now.
[14:05] <stgraber> The number of targeted bugs went from 120 last week to 106.
[14:05] <seb128> if you have questions for me please ask them while I'm around ;-)
[14:05] <stgraber> Of these 106, 45 are in fix commited state (likely waiting in -proposed)
[14:05] <stgraber> and 14 are marked "in progress" (waiting to be approved).
[14:06] <stgraber> So that's 47 bugs that still need fixing of which 19 aren't assigned to somebody.
[14:06] <stgraber> With just one week to go, now would be a good time to cleanup these lists and remember your teammates that they have bugs to fix :)
[14:06] <seb128> we should start moving agressively stuff to .2 I guess
[14:06] <seb128> right, will do that
[14:06] <stgraber> The full list of bugs can be found at: https://bugs.launchpad.net/ubuntu/precise/+bugs?field.milestone%3Alist=49926
[14:06] <stgraber> The list of remaining bugs to fix can be found at: http://goo.gl/RUiZe
[14:06] <stgraber> Some of these aren't assigned to someone yet: http://goo.gl/22zV2
[14:06] <seb128> did we have an improved report?
[14:07] <stgraber> we have http://people.canonical.com/~arges/point-release/milestone-12.04.1.html thanks to arges
[14:07] <arges> seb128, still getting the cron job set up on cranberry
[14:07] <seb128> thanks
[14:07] <stgraber> xnox offered to help arges and stokachu with the required rdepends rebuild for their multiarch packages by using his rebuild scripts on the HP cloud.
[14:09] <stgraber> stokachu, arges: did you make any progress on that side (multiarch bugs)? I expect these to take quite a while to verify, so we really need them in ASAP
[14:09] <arges> stokachu is out right now, but I'll sync with him when he gets out of his meeitngs
[14:10] <stgraber> ok
[14:10] <stgraber> If someone has fixes will be uploaded after the deadline and this was agreed with the release team, please let me know, otherwise I'll move all remaining bugs to 12.04.2.
[14:10] <stgraber> #action stgraber to move all remaining bugs from 12.04.1 to 12.04.2 on the 2nd of August at 21:00 UTC
[14:10] <meetingology> ACTION: stgraber to move all remaining bugs from 12.04.1 to 12.04.2 on the 2nd of August at 21:00 UTC
[14:10] <stgraber> *that will be
[14:11] <stgraber> I'd obviously prefer that people re-milestone their own bugs before that ;)
[14:11] <stgraber> that's it on my side for the bugs, anyone has anything to highlight?
[14:12]  * arges looks
[14:13] <arges> stgraber, http://launchpad.net/bugs/979003  <-- this one
[14:13] <skaet> stgraber,   some of the remaining bugs we may want to go to -updates instead of 12.04.2 - so a scrub rather than bulk move is probably appropriate.
[14:15] <stgraber> arges: I'm told that one will be fixed on time by infinity
[14:15] <stgraber> arges: along with a couple others eglibc bugs
[14:15] <seb128> ok, I'm moving room, might get disconnected
[14:15] <stgraber> skaet: yeah, that's why I'd prefer the assignee to re-milestone their own bugs before I mass re-milestone the rest. I'm just going to move from 12.04.1 to 12.04.2, but anything that should instead go to updates should ideally be done by the assignee
[14:15] <arges> stgraber, ok cool that's my understanding too
[14:16] <stgraber> #topic Media oversizedness (skaet)
[14:16] <skaet> no updates on this from me.    We do need to understand why we're oversized.
[14:17] <stgraber> so, currently the only images that are oversized are amd64, amd64+mac and i386 daily-live
[14:17] <stgraber> one of the main reasons is the inclusion of duplicate kernel headers
[14:17] <stgraber> infinity said he'd hack live-build to fix that, but that didn't happen yet apparently
[14:18] <stgraber> I'll poke infinity post-meeting regarding eglibc + live-build, to confirm that these will land before the 2nd
[14:18] <skaet> thanks.
[14:19] <stgraber> I haven't looked at flavour oversizedness yet, mostly because we're not building them yet (AFAIK), but it's possible that we'll have some problems with kubuntu, xubuntu, .. too
[14:19] <stgraber> edubuntu should be fine as it's a DVD and has around 2GB of free space :)
[14:20] <stgraber> #topic Round table
[14:20] <stgraber> stgraber@castiana:~$ echo $(shuf -e NCommander seb128 stgraber stokachu arges jibel skaet smoser jamespage)
[14:20] <stgraber> stokachu stgraber arges NCommander smoser jamespage jibel seb128 skaet
[14:20] <stgraber> no stokachu, so skipping to me
[14:21] <stgraber> I've been uploading a bunch of SRUs that had patches attached or were easy cherry-pick. I have a couple more like that to do.
[14:21] <stgraber> I'm also going to do another round of SRU verification as the list is getting a bit long to my taste.
[14:21] <stgraber> Besides that, I've been nagging my teammates and cleaning up the bug list :)
[14:21] <stgraber> arges:
[14:22] <arges> Trying to get the point-release dashboard working on cranberry
[14:22] <arges> it works on my machine, but not there, so trying to debug it
[14:23] <arges> I know its very late in the cycle here, but I'm hoping its more useful in .2
[14:23] <arges> ..
[14:23] <stgraber> NCommander:
[14:23] <stgraber> around?
[14:24] <stgraber> apparently not
[14:24] <stgraber> smoser:
[14:25] <smoser> - server tracked bugs list is quite resonable.
[14:25] <smoser>   It really feels to me like 12.04.1 and maas updates are not likely.
[14:25] <smoser>   I believe the team is still considering what to do for maas updates to LTS. I'll poke today.
[14:25] <smoser> we've had some srus. maas is the big stuff still left on the bug list.
[14:25] <smoser> 'im pinging others on their bugs right now.

[14:26] <NCommander> stgraber: sorry, was OTP'ed
[14:26]  * NCommander will wait for you to comearound
[14:26] <stgraber> NCommander:
[14:27] <NCommander> highbank SRUs are in propsed, known to work (aside fromyou have to enable proposed on the kernel command line for the moment)
[14:27] <NCommander> Expecting no issues to passing into updates, and mreed already validated, and mahmoh is re-validating as a second check
[14:28]  * smoser was also covering for jamespage per his request
[14:28] <NCommander> Unless castrophy strikes, Highbank will release with 12.04.1 as planned

[14:29] <stgraber> jibel_:
[14:29] <jibel_> SRU verification of ubiquity, update-manager and other upgrades defects and found no regression.
[14:30] <jibel_> Blocked on bug 1017580 , the test case must be clarified
[14:30] <jibel_> and bug 987050 , alternate is not installable
[14:30] <jibel_> precise alternate and server fail to install with a typical 'no kernel module found' which should be fixed with debian-installer 20101020ubuntu136.2 uploaded yesterday.
[14:30] <jibel_> But from the version file on the media the image is built with 20101020ubuntu136 (version from the release pocket)
[14:31] <stgraber> jibel_: I can take care of bug 1017580 if you want
[14:31] <jibel_> my understanding was that images are built from proposed, is it the case for d-i based images too ?
[14:31] <jibel_> I'll continue SRU verification by the top of the list.
[14:31] <jibel_> Did a bunch of installation with Ubiquity 2.10.18 and no new bug found so far.
[14:31] <jibel_> ..
[14:32] <stgraber> jibel_: yeah, all images are supposed to be built with -proposed enabled... not sure what happened to the alternates...
[14:32] <jibel_> and server
[14:33] <stgraber> seb128:
[14:33] <seb128> not a lot from desktop
[14:33] <seb128> we got a new unity SRU in proposed
[14:34] <seb128> we should get another set of compiz uploads
[14:34] <seb128> then some GNOME updates and small fixes
[14:34] <seb128> then done for .1
[14:34] <seb128> ..
[14:34] <stgraber> skaet:
[14:34] <skaet> discussed with vanhoof the cedartrail* landing late,   looking into a bug with the slideshow on a fresh install,  settled with martin and david that david will be doing the translation updates.   Doing calculations to add rest of LTS dailies to cron job,  will add after A3 publishes.
[14:35] <skaet> ..
[14:36] <stgraber> #topic AOB
[14:36] <stgraber> one reminder on bug statuses as I've had to fix quite a few lately
[14:37] <stgraber> for the SRU tasks (series = precise, milestone = 12.04.X), the reports and scripts usually expect the following
[14:37] <stgraber> triaged + assigned => bug is being worked on or at least on someone's todo list
[14:37] <stgraber> in-progress => fix has been uploaded and is waiting in the queue for an SRU team member to review
[14:37] <stgraber> fix-commited => the fix has landed in -proposed and is pending verification
[14:38] <stgraber> fix-released => the fix has landed in -updates and is available to everyone
[14:38] <stgraber> the most common mistakes I've seen so far has been marking fix-released when they're only in -proposed and marking fix-commited when the fix hasn't even been uploaded yet (or is still in the queue)
[14:39] <stgraber> I'm doing weekly passes on the 12.04.1 bugs to try and fix any mistake so the reports are accurate, but would be even better if the statuses would be correct to start with :)
[14:39] <stgraber> ..
[14:39] <stgraber> anything else?
[14:41]  * skaet thinks silence indicates EOM... ;)
[14:42] <stgraber> #endmeeting
[14:42] <meetingology> Meeting ended Thu Jul 26 14:42:23 2012 UTC.
[14:42] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-14.01.moin.txt
[14:42] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-14.01.html
[14:42] <jibel_> thanks stgraber
[14:42] <stgraber> skaet: yeah, I had a 40s lag for some reason, so it took a while for that #endmeeting to go through ;)
[14:42] <stgraber> thanks everyone!
[14:43] <skaet> thanks stgraber
[16:01] <micahg> o/
[16:01] <bdrung> o/
[16:01] <tumbleweed> o/
[16:01] <coolbhavi> o/
[16:01] <asomething> hi all
[16:01] <coolbhavi> hi asomething
[16:03] <tumbleweed> coolbhavi: I guess you are the chair, from the last minutes
[16:04] <coolbhavi> tumbleweed, just was having dinner ll be back in just a moment
[16:04] <tumbleweed> coolbhavi: does that mean we should start without you?
[16:05] <coolbhavi> #startmeeting MOTU meeting
[16:05] <meetingology> Meeting started Thu Jul 26 16:05:09 2012 UTC.  The chair is coolbhavi. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:05] <meetingology> 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
[16:05] <coolbhavi> hi all
[16:05]  * coolbhavi checks the latest agenda
[16:06] <asomething> doesn't seem to have anything up for discussion...
[16:06] <coolbhavi> yes asomething
[16:06] <maco> mono: go!
[16:06]  * cody-somerville is here but in another meeting concurrently.
[16:07] <coolbhavi> I had a couple of work items myself
[16:07]  * micahg hasn't gotten to his WI yet
[16:07] <micahg> umm, how about scheduling an event where MOTU help Debian close RC bugs?
[16:07] <micahg> most of them are RC in Ubuntu as well
[16:07] <micahg> err...well, at least a good portion
[16:08] <coolbhavi> micahg, certainly yes :)
[16:08] <tumbleweed> micahg: I like that
[16:08] <asomething> +1
[16:09] <bdrung> sounds good (besides that it needs manpower which is a rare resource)
[16:09] <micahg> by MOTU I mean the MOTU community, not just MOTUs as I'm sure most of those present understand
[16:11]  * bdrung nods.
[16:11] <coolbhavi> micahg, sounds good.. are you willing to take a session on the same in MOTU school?
[16:12] <micahg> coolbhavi: my biggest problem ATM is time, I can try to be around to help when the event happens, but can't commit to a session right now
[16:12] <tumbleweed> I don't know if one can teach "fixing RC bugs"
[16:12] <micahg> well, show how to find them, what to do once you have a patch...
[16:12] <tumbleweed> but it would be easy enough to do a quick overview of how to find Debian RC bugs, what makes them RC, and how to contribute
[16:12] <ScottK> tumbleweed: You can teach finding which ones are RC bugs and sorting through them to find the one you can ifx.
[16:12] <coolbhavi> tumbleweed, just a process workflow insight would help I guess
[16:13] <ScottK> That's hard enough if you don't know the tools.
[16:13] <tumbleweed> yes
[16:14]  * tumbleweed can volunteer for that session
[16:14] <coolbhavi> ScottK, agreed but as micahg said one can always show a bug or two as an example and interested people can pickup I guess
[16:17] <coolbhavi> any further inputs on the same anyone?
[16:18] <bdrung> no
[16:19] <tumbleweed> picking a date would be good
[16:19] <coolbhavi> tumbleweed, how about next tuesday or anyday of next week?
[16:20] <tumbleweed> next tuesday works for me. from midday UTC?
[16:21] <coolbhavi> fine with me too
[16:21] <bdrung> why not the whole day?
[16:21] <tumbleweed> if one wants a training thing, it starts with that
[16:21] <bdrung> agreed
[16:21] <tumbleweed> but I suppose, it doesn't have to
[16:24] <coolbhavi> bdrung, we initially thought of a series of intro sessions (maybe around 4 or 5) with introduction to some development topics this cycle as a part of relaunch of MOTU school. take a look at the response and then plan it forward the next cycle
[16:26] <coolbhavi> tumbleweed, any time proposal for the session in your mind?
[16:28] <tumbleweed> my proposal was midday UTC, it suits me well, just after lunch. But I can make any time after 8am UTC
[16:28] <coolbhavi> tumbleweed, how about 2PM UTC then?
[16:28] <coolbhavi> next tuesday>
[16:31] <tumbleweed> coolbhavi: sure, that's afternoon for europe and morning for the US
[16:32] <coolbhavi> I'll make an action item then
[16:33] <coolbhavi> #action tumbleweed to take a session on RC bug fixing workflow on tuesday 31st at 1400 UTC
[16:33] <meetingology> ACTION: tumbleweed to take a session on RC bug fixing workflow on tuesday 31st at 1400 UTC
[16:35] <coolbhavi> other point of discussion was spreading the word around MOTU School
[16:35] <coolbhavi> IIRC
[16:35] <coolbhavi> any thoughts anyone?
[16:35] <tumbleweed> what are you needing for that. People to sign up?
[16:35] <tumbleweed> is there a schedule and has a call for speakers been posted? I don't recall it
[16:37] <coolbhavi> tumbleweed, something like a blogpost would do I had called for speakers during 1st session https://lists.ubuntu.com/archives/ubuntu-motu/2012-July/007273.html
[16:37] <coolbhavi> #link https://lists.ubuntu.com/archives/ubuntu-motu/2012-July/007273.html
[16:39] <tumbleweed> coolbhavi: can I propose having a schedule wiki page like we do for UDW
[16:39] <tumbleweed> then it's obvious when there are gaps that should be filled
[16:39] <tumbleweed> or do sessions only happen when we have speakers offering?
[16:39] <coolbhavi> tumbleweed, sure +1 here
[16:41] <coolbhavi> tumbleweed, A schedule list on the wiki and a call for speakers before each session on the list would be fine I guess
[16:42] <tumbleweed> coolbhavi: it'd be great
[16:42] <tumbleweed> I'll happily sign up for a session or two, if I saw the huge gaps that needed filling :)
[16:42] <coolbhavi> tumbleweed, thanks a lot :)
[16:43] <coolbhavi> #action tumbleweed to set up a MOTU school schedule page on the wiki
[16:43] <meetingology> ACTION: tumbleweed to set up a MOTU school schedule page on the wiki
[16:44]  * tumbleweed shuts up so he stops getting action items
[16:44] <tumbleweed> :)
[16:45] <coolbhavi> other thing we discussed was merging of packaging training and MOTU school pages on the wiki which I hope to finish by next monday
[16:45] <coolbhavi> tumbleweed, sorry for those :)
[16:46] <tumbleweed> no, that's how it works...
[16:46] <coolbhavi> :)
[16:47] <coolbhavi> so those were the discussion points from the last meeting afaik. Is there anything anyone wants to discuss?
[16:48] <tumbleweed> there are also standing agenda items on the wiki page
[16:50] <bdrung> i like to discuss merges
[16:50] <bdrung> how many package are modified in Ubuntu? does this number increase or decrease? can we get the changes back into Debian?
[16:51] <tumbleweed> have you seen the graphs at the bottom of https://merges.ubuntu.com/universe.html
[16:51]  * micahg thinks MoM is broke again
[16:51] <tumbleweed> don't forget debian is frozen
[16:52] <tumbleweed> which makes it suprising that so many things need merging
[16:52] <micahg> nope, it's broke :), last graphs generated 7 days ago
[16:52] <tumbleweed> we should post some reminders about that...
[16:52]  * tumbleweed hides
[16:54] <micahg> well, we can push patches up while Debian is frozen, but they probably won't be integrated until after DIF for R when Debian unfreezes
[16:54] <bdrung> tumbleweed: the graphs is too small
[16:55] <tumbleweed> what I mean is, we should be easily able to catch up on the merges
[16:55] <ScottK> bdrung: You have access to the source, so you can fix that.
[16:55] <tumbleweed> there should be few incoming changes from Debian that aren't very important to us
[16:56] <ScottK> BTW, I've found in my RC bug fixing in Debian a few cases where when I went to sync the fix to Ubuntu, it was already in Ubuntu (and recently so).
[16:56] <ScottK> No patch was ever sent.
[16:56] <ScottK> So that could be better still.
[16:57] <coolbhavi> ScottK, +1 here
[16:57] <ScottK> blockdiag beint the one I hit last night.
[16:57] <ScottK> ... being ...
[17:00] <coolbhavi> ScottK, how about notifying the developer (from the changes list) when he does patch a ubuntu package and the patch would be applicable in debian too (like ftbfs patches) to forward it to debian as a remainder after checking the BTS if the developer hasnt done so?
[17:00]  * coolbhavi thinks its a weird idea
[17:01] <tumbleweed> calling out poor behavior ++
[17:01] <ScottK> I can take care of the specific case, but there's obviously more work to be done.
[17:02] <coolbhavi> tumbleweed, ScottK agreed
[17:05] <coolbhavi> any inputs from anyone regarding the same? and any other topic to discuss?
[17:06] <tumbleweed> I still see a few standing items on https://wiki.ubuntu.com/MOTU/Meetings thath we haven't covered
[17:06] <tumbleweed> but I need to run off
[17:07] <coolbhavi> tumbleweed, I thought those are fixed items
[17:10]  * coolbhavi sees that the meeting is well past time :)
[17:12] <coolbhavi> btw anyone volunteering to chair next meeting?
[17:13] <coolbhavi> tumbleweed, bdrung ScottK ^^^^^
[17:13]  * ScottK is not.
[17:13] <coolbhavi> micahg,
[17:14]  * bdrung hides.
[17:14] <ScottK> That leaves tumbleweed.
[17:14] <micahg> I guess I can chair if I'm around next time
[17:15] <coolbhavi> micahg, great :)
[17:16]  * coolbhavi searches around for tumbleweed
[17:17] <coolbhavi> tumbleweed, is afk hmm
[17:18] <coolbhavi> #action micahg to chair the next MOTU meeting on 10th July
[17:18] <meetingology> ACTION: micahg to chair the next MOTU meeting on 10th July
[17:18] <coolbhavi> alright, thats it from me then
[17:18] <coolbhavi> thanks all
[17:19] <coolbhavi> #endmeeting
[17:19] <meetingology> Meeting ended Thu Jul 26 17:19:25 2012 UTC.
[17:19] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-16.05.moin.txt
[17:19] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-16.05.html
[17:32] <tumbleweed> coolbhavi: I understand that "fixed" as "standing"
[17:33] <tumbleweed> certainly we were supposed to be having a bug fixinging inititiative item as a standing item
[17:33] <coolbhavi> tumbleweed, sorry I took it in the other sense
[18:00] <jono> alrighty
[18:00] <jono> #startmeeting
[18:00] <meetingology> Meeting started Thu Jul 26 18:00:14 2012 UTC.  The chair is jono. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:00] <meetingology> 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
[18:00] <jono> hey folks!
[18:00] <jono> who is hear for the Ubuntu Accomplishments team meeting?
[18:00]  * janos_ here
[18:01] <janos_> hey jono!
[18:01] <notgary> Me o/
[18:01] <jono> hey janos_!
[18:01] <Andy80> <---- me :)
[18:01] <margo> hi
[18:01] <jono> cool, thanks, folks for joining us :-)
[18:01] <jvrbanac> here
[18:01] <jono> awesome :-)
[18:02] <jono> so which of you folks is new and interested in helping with the project?
[18:02] <jaywink> \o/ new here, would like to help :)
[18:02] <margo> me too
[18:02] <jvrbanac> I'm new here as well
[18:03] <jono> fantastic, so maybe if you folks could just let us know the kind of things you like doing (e.g. programming, writing docs) or anything else, and we can get you started :-)
[18:03] <jaywink> programming here: do Python mostly and I like the idea so figured this would be a nice way to try Ubuntu stuff for the first time
[18:03] <jono> jaywink, oh awesome!
[18:04] <jono> jaywink, you should take a look at https://wiki.ubuntu.com/Accomplishments/GetInvolved/Hacking first
[18:04] <Andy80> I like to code, maybe you remember I contributed with a small accomplishment. But right now (at least until the end of august) I cannot be sure to have enough time to help, since I work all day and when I go back home I'm very tired :(
[18:04] <Andy80> so I'm here just to listen and to remain updated with the project status
[18:04] <jono> Andy80, no worries, anything you can do to help would be great - maybe helping with some bugfixes?
[18:04] <jvrbanac> Programming here. I took a look at at the hacking portion of the Wiki last night
[18:04] <margo> i can code too, but i am not too experienced, and i can write doc or translate to german too if that is needed
[18:04] <jono> jvrbanac, ahhh cool, did it make sense?
[18:04] <jaywink> jono, yeah did read through today, will need to dig in deeper
[18:04] <TheTattooedGeek> Hey Jono, Just here to see where the project is headed.. the only language I currently work in is PHP
[18:05] <jvrbanac> yes it did.
[18:05] <notgary> I'm relatively new here. Been to one meeting before and chimed in on the mailing list once. I'm a software developer in my day job, working with C++ and Qt. I'm making my way into iOS development in my spare time and have python and Django/Quickly on my todo list to learn.
[18:05] <epikvision> I want to learn to code.
[18:05] <jono> cool, so it seems like a lot of coding interest here
[18:05] <gigix> hello
[18:05] <jono> you folks should definitely check out https://wiki.ubuntu.com/Accomplishments/GetInvolved/Hacking to get started
[18:05] <jono> it explains how to install the branches and provides some details of how the project works
[18:06] <jono> this is an evolving document so if things are not clear, do let me know, and I will clarify and then update the doc so everyone benefits
[18:06] <jono> you folks should all join #ubuntu-accomplishments for sure
[18:07] <jono> and I know a few of you mentioned being new, well the other primary hacker on the project, cielek, who unfortunately could not make the meeting today, well he was new to Python when he joined
[18:07] <jono> and he is doing awesome work on the project
[18:07] <jono> we just want to make sure that getting involved is as simple as possible
[18:07] <TheTattooedGeek> nice
[18:07] <jono> we are also growing our API docs for the project - they are linked on the Hacking page too
[18:08] <jono> so if you want to start on something, we recommend picking a bug and hacking on it
[18:08] <margo> sounds good ;)
[18:08] <jono> the Viewer bugs are probably the easiest to get started with, and the bugs list is at https://bugs.launchpad.net/ubuntu-accomplishments-viewer
[18:08] <jono> just pick a bug, work on it in your branch and then submit it
[18:08] <jono> details of how to hack on it and submit it are at https://wiki.ubuntu.com/Accomplishments/GetInvolved/Hacking#Step_4:_Create_and_Submit_Your_Fix
[18:09] <jono> you might also want to join the mailing list at https://launchpad.net/~ubuntu-accomplishments-contributors
[18:09] <jaywink> are bugs usually claimed or just worked on by however gets it done first? :) I guess that's not normally a problem ;)
[18:09] <janos_> and if you have any questions along the way, usually somebody on #ubuntu-accomplishments can help if you explain where you got stuck
[18:09] <jono> jaywink, right now we recommend people just pick a bug and post a comment to say they are working on it
[18:10] <jono> but if you find you don't have time, please post a follow up comment so the bug is not blocked by others thinking you are working on it
[18:10] <jono> yeah as janos_ says, we are always open to questions in #ubuntu-accomplishments
[18:10] <jono> do any of you have any questions about the project, how to get started, or the code?
[18:10] <TheTattooedGeek> negative
[18:11] <gigix> so far so good for me
[18:11] <jono> cool
[18:11] <jono> well feel free to chip in with questions if you have them
[18:11] <janos_> the wiki has step-by-step instructions, if something is missing or was not clear to you, let us know because others might be blocked by the same thing too
[18:11] <jaywink> have been scared to participate in any UBuntu project so far - but this has been laid our so well that had to :) props, no questions so far, the hacking page is a good intro
[18:12] <jono> jaywink, awesome! well, happy to take more questions so I can also expand the docs
[18:12] <jono> jaywink, I recommend just picking a bug, starting hacking on it, and then just asking questions where you are unsure
[18:12] <jono> and when you contribute your fix, we will also do a code review and offer further comments and guidance
[18:12] <jaywink> ok cool
[18:12] <jono> our goal is to make our community as welcoming and open as possible :-)
[18:13] <jono> ok, so next topic
[18:13] <jono> which will be of interest to janos_ and gepatino_mobile in particular
[18:13] <jono> I have been chatting with Canonical IS about how we can have them host the project
[18:14] <jono> I am not the best sysadmin :-)
[18:14] <jono> this is the broad plan:
[18:14] <jono>  * Canonical IS will set up a VM with a staging and production environment
[18:14] <jono>  * trophies.ubuntu.com will be production and staging.trophies.ubuntu.com will be staging
[18:14] <janos_> that is so awesome
[18:14] <jono>  * they will deploy our current validation server, the web gallery, and our admin interface
[18:15] <jono> :-)
[18:15] <gepatino_mobile> jono, will the soft be updated automatically or by request?
[18:15] <jono> we will all work on the staging server and when we cut a release in bzr, we will notify IS who will simply do a pull on production to deploy the code (as well as any additional deployment steps)
[18:16] <jono> gepatino_mobile, my thinking is that for staging we will try to have hourly updates but for production it will be pulled on new releases
[18:16] <jono> make sense?>
[18:16] <janos_> jono how do we tell them the additional deployment steps?
[18:16] <jono> janos_, we can always put it in a document somewhere
[18:16]  * gepatino_mobile is typing in a blackberry on the bus...
[18:16] <jono> gepatino_mobile, I admire your commitment to the meeting :-)
[18:16] <gepatino_mobile> sounds good
[18:17] <jono> ok cool
[18:17] <jono> so I chatted to mbarnett today about this
[18:17] <jono> and we can also safely presume the two django apps will be on the same machine as the validation server
[18:17] <jono> which means we can presume the web gallery can see the shares
[18:17] <jono> so there should be no changes requires to deploy in Canonical IS
[18:18] <gepatino_mobile> makes sense, I was actually thinking more in staging than prod
[18:18] <jono> right
[18:18] <jono> it would be cool to have the current list of shares in staging as well as prod
[18:18] <jono> so this should make your work easier
[18:19] <jono> is there anything that you guys need janos_, gepatino_mobile?
[18:20] <gepatino_mobile> for staging, probably we don't need live shares, a copy could be enough
[18:20] <gepatino_mobile> updated daily, maybe
[18:20] <jono> right
[18:21] <jono> I am thinking we could just copy over the lives shares once a day to staging
[18:21] <jono> hey n8k99
[18:21] <n8k99> hi jono
[18:21] <n8k99> got here as quickly as i could
[18:21] <jono> no worries :-)
[18:21] <jono> thanks for joining us!
[18:21] <jono> n8k99, are you interested in contributing to the project?
[18:22] <n8k99> i am, i like the accomplishments application
[18:22] <n8k99> the concept is pretty cool way to drive more interest in the ubuntu community and project
[18:22] <jono> n8k99, awesome - what kind of contribution? programming, docs, translations?
[18:22] <janos_> jono: not sure the automatic updates are a good idea even on staging
[18:22] <jono> janos_, no?
[18:23] <n8k99> i had an idea this morning, started trying to write it, to make an accomplishment for making your first accomplishment for ubuntu-accomplishments
[18:23] <jono> janos_, how do you think we should update staging? just a pull?
[18:23] <jono> n8k99, cool!
[18:23] <janos_> jono: if it takes the IS folks days or weeks to perform the manual deployment steps, then the site can be broken for days or weeks
[18:23] <n8k99> far too meta perhaps, but i got the .accomlishment written
[18:23] <jono> janos_, right, this is why I think automatic staging might work best
[18:23] <jono> janos_, updating production should be quick
[18:23] <jono> asking them to perform a pull doesn't take much
[18:24] <jono> n8k99, oh cool!
[18:24] <jono> n8k99, we are definitely in need of new accomplishments so I am glad you are helping :-)
[18:24] <n8k99> coding isn't really my strong suit, but i'm gonna give that a whack
[18:24] <janos_> jono: the current demo site was often broken for many days because of the automatic pull and that no sysadmin had time to do the manual steps
[18:24] <jono> n8k99, well you can help in other ways too, such as writing the docs :-)
[18:25] <jono> janos_, ahhh I see
[18:25] <n8k99> that was where i was seeing my bigger contributions coming in
[18:25] <jono> janos_, so I presume you would prefer if you could do a pull directly
[18:25] <janos_> jono: I think it's better the IS update the staging site when they can actually perform the manual steps too
[18:25] <gepatino_mobile> jono, janos_: could we have some kind of access to do the deploys? maybe using sdome deployment tool?
[18:25] <jono> janos_, we could do that
[18:26] <jono> janos_, how often do you think you will need staging updated?
[18:26] <jono> n8k99, awesome :-)
[18:26] <jono> n8k99, well your help is much appreciated :-)
[18:26] <gepatino_mobile> juju someone? :)
[18:26] <n8k99> glad to be involved again after far too long away!!
[18:26] <jono> gepatino_mobile, a juju charm might be a good solution
[18:26] <oneouthere> jono: do you have to be on ubuntu to add to the coding?
[18:26] <janos_> jono: i think it's better if the IS guys do the update, so they build up expertise which will be useful for troubleshooting PROD in the future
[18:27] <jono> oneouthere, pretty much, you need at least Ubuntu 12.04 to run the current codebase
[18:27] <jono> oneouthere, we haven't tried it on other distros
[18:27] <jono> janos_, how often do you think you will need staging updated?
[18:27] <oneouthere> jono, okay thank you
[18:28] <janos_> jono: once a week or so?
[18:28] <jono> janos_, and is it the same manual steps each time that are run?
[18:28] <jono> I am wondering whether this could be rolled into a juju deployment charm for the site
[18:28] <janos_> jono: most of the time there are no manual steps
[18:28] <jono> jan
[18:28] <jono> janos_, I see
[18:29] <jono> lets have a conversation with jcastro about this post-meeting - I will kick off a thread and lets see if Juju can support this
[18:29] <jono> if not we can see if there is another option
[18:29] <jono> I think it would be good if you guys could trigger a staging update when needed
[18:29] <jono> and IS look after the production instance
[18:29] <jono> then you are not blocked
[18:30] <janos_> ok let's discuss later or in emails
[18:30] <gepatino_mobile> that would be great, theres another python framework for deploying, but i cant remember the name
[18:30] <jono> ok cool
[18:30] <jono> thanks folks
[18:31] <jono> the good news is that we should be in a position to get this up and running over the next few weeks
[18:31] <n8k99> thank you!
[18:31] <jono> janos_, gepatino_mobile can you summarize what the web gallery does now and what functionality is missing?
[18:31] <janos_> sure, hang on
[18:32] <jono> thanks
[18:32] <janos_> 1. most of the functionality is there, as per the spec document
[18:32] <janos_> 2. most of the pages are "not the prettiest" and need some touching up in the graphics
[18:33] <jono> maybe imbrandon can help with the CSS there
[18:33] <jono> he is a bit of a CSS guru :-
[18:33] <jono> :-)
[18:33] <janos_> we definitely need that
[18:34] <jono> seeing if he is online and can join the meeting
[18:34] <jono> I am sure he would be happy to help
[18:34] <janos_> 3. the opportunities page should not show already achieved accomplishments
[18:35] <janos_> 4. locked opportunities should use a lock image overlay like the viewer does
[18:36] <jono> awesome
[18:36] <janos_> 5. "Responsive design" would be nice, so the site looks nice on screens of all sizes
[18:36] <janos_> I think these are the big todo items
[18:36] <jono> sounds great
[18:36] <janos_> gepatino_mobile: feel free to add!
[18:36] <jono> I presume the mobile stylesheet is not started yet
[18:36] <janos_> btw guys you can see it in action here: http://<IP_ADDRESS>:8000/
[18:37] <janos_> jono: nope, and some css guru awesomeness would be great there
[18:37] <jono> :-)
[18:37] <jono> I am almost 100% sure Brandon would love to help with this
[18:37] <jono> I will drop him an email
[18:37]  * gepatino is back to a real keyboard
[18:37] <jono> gepatino, welcome! :-)
[18:37] <jono> thanks again for you hard work janos_ gepatino
[18:37] <jono> so quick q
[18:38] <gepatino> i've read up to janos_ point 2, did I miss something?
[18:38] <jono> in the future it would be nice to show things such as "Other people who have accomplished this trophy"
[18:38] <jono> I presume this is possible with the current data structure?
[18:38] <jono> gepatino, he made more points:
 maybe imbrandon can help with the CSS there
[18:38] <jono>  he is a bit of a CSS guru :-
[18:38] <jono>  :-)
 we definitely need that
 seeing if he is online and can join the meeting
[18:38] <jono>  I am sure he would be happy to help
[18:38] <jono>  JanC janos_
 3. the opportunities page should not show already achieved accomplishments
[18:38] <jono>  4. locked opportunities should use a lock image overlay like the viewer does
 awesome
[18:39] <jono> <-- virgil153 has quit (Remote host closed the connection)
 5. "Responsive design" would be nice, so the site looks nice on screens of all sizes
[18:39] <jono>  I think these are the big todo items
 sounds great
 gepatino_mobile: feel free to add!
 I presume the mobile stylesheet is not started yet
 btw guys you can see it in action here: http://<IP_ADDRESS>:8000/
[18:39] <jono> <-- gepatino_mobile has quit (Remote host closed the connection)
 jono: nope, and some css guru awesomeness would be great there
[18:39] <janos_> jono yes we can do this: "Other people who have accomplished this trophy"
[18:39] <gepatino> I could ad a 6th point: I'm not sure if we got rid of some duplicated urls
[18:40] <gepatino> maybe we should review the current url catalog before going live
[18:40] <jono> gepatino, makes sense
[18:40] <jono> janos_, cool
[18:40] <jono> I am concious that we don't provide leaderboards (as people game them) but other social features would be cool
[18:40] <jono> so it sounds like the core infrastructure will support those social features
[18:40] <jono> awesome
[18:41] <jono> ok, anything else on the deployment topic?
[18:41] <gepatino> is there any estimate on how many users/shared we'll have when launching this?
[18:42] <janos_> gazillions
[18:42] <n8k99> that's an awfully small number
[18:42] <jono> gepatino, not sure yet, I need to give IS an estimation of traffic
[18:42] <jono> currently we have some stats:
[18:42] <gepatino> are we sure that crawling all the shares to get the current trophies will work with so many users?
[18:43] <jono> today we have about 700 users
[18:43]  * gepatino only made tests with millions, not gazillions :/
[18:43] <jono> hehe
[18:43] <jono> I don't anticipate us hitting scaling issues for a while
[18:44] <gepatino> ok, so it's something to be reviewed in future releases
[18:44] <jono> I think we will be under 5000 shares for a while
[18:44] <gepatino> ok, that's not that much
[18:44] <jono> but who knows
[18:44] <jono> I hope we explode with popularity :-)
[18:44] <jono> the good news is that fixing scaling issues on the validation server would be simple
[18:44] <gepatino> in that case we'll have to run, as usual in IT :)
[18:45] <jono> indeed :-)
[18:45] <jono> ok then, any other questions or topics?
[18:45] <jvrbanac> Speaking about scalability, What is the policy on contributing towards code improvements, optimization, and unit testing?
[18:45] <jvrbanac> ^speaking of
[18:45] <notgary> Just like to point out that I pushed a basic iOS app to Launchpad yesterday. https://code.launchpad.net/~notgary/+junk/ubuntu-accomplishments-ios-app
[18:46] <jono> jvrbanac, we welcome all contributions towards that
[18:46] <notgary> It's very basic - I wrote a grand total of 4 lines
[18:46] <jono> jvrbanac, mfisch has been working on unit tests for the daemon - most of the tests are in place
[18:46] <notgary> But it point to a hard-coded url, in this case the project wiki until trophies.ubuntu.com goes live
[18:46] <jvrbanac> jono, awesome thanks!
[18:46] <jono> jvrbanac, we have performed some optimizations over the last few releases, but plenty more scope for improvements
[18:47] <jono> jvrbanac, if you see areas of improvement that are quite big changes, we recommend you mail the list first to discuss, but feel free to hack on a branch and propose it
[18:47] <jono> notgary, oh wow!
[18:47]  * n8k99 is wondering about some of the launchpad account interactions
[18:47] <jono> notgary, did you see the MobileSpec?
[18:47] <n8k99> probably more of a QA interest at this point
[18:47] <jono> notgary, https://wiki.ubuntu.com/Accomplishments/Specs/Mobile
[18:48] <jono> n8k99, what kind of interactions?
[18:48] <n8k99> there's been a few bugs filed where the launchpad accomplishments are not being picked up
[18:49] <jono> n8k99, yeah we have had a few bugs where trophies are not validated
[18:49] <jono> in most cases this has typically been due to Ubuntu One downtime or someone entering their credentials with a typo
[18:49] <notgary> jono, I've seem it. It looks like the bulk of the functionality will be implemented server-side with the device-specific CSS. My plan was to wait until that got started before adding more code into the app, so I could see what actually needed the work.
[18:49] <jono> notgary, perfect :-)
[18:50] <jono> notgary, yeah, our thinking is a custom stylesheet for each device, and then the app has native menus that point to different parts of the site
[18:50] <notgary> Has anyone started an Android app yet, because I'd be willing to work on that too, given that there's little involved in a wrapper for a web site.
[18:51] <n8k99> i probably need to look at the way its being done before i'm able to form my thinking into an actual question
[18:51] <jono> notgary, nope, no one contributed anything yet
[18:51] <jono> n8k99, no worries!
[18:51] <jono> n8k99, feel free to post the mailing list or ask on IRC when you are ready
[18:51] <n8k99> i will. :-)
[18:51] <jono> man, the mobile is going to be sweet :-)
[18:52] <jono> any other topics or questions?
[18:52] <notgary> That iOS project contains an iPad app as well
[18:52] <jono> cool
[18:52] <notgary> so we should get tablet CSS too
[18:52] <n8k99> speaking of mobile, are there plans to be able to push trophies out to social media channels?
[18:52] <jono> I am going to ask imbrandon if he can contribute stylesheets for the different devices
[18:53] <jono> n8k99, yep, we have built in support in the desktop client
[18:53] <jono> this could arguably be added on trophies.ubuntu.com too
[18:53] <janos_> notgary: is there a way test an ios app without an ios dev env?
[18:53] <jaywink> optional automatic social media pushing on trophies would be cool :)  <--- lazy
[18:54] <notgary> Not that I'm aware of. I'll look into it and let you know on the mailing list.
[18:54] <jono> jaywink, :-)
[18:54] <janos_> notgary: probably not. on the other hand android is a lot easier, so i'm very much looking forward for that!
[18:54] <notgary> If you have an iOS device then you could install a (read, my) development provisioning profile on the device which means you could run pre-release code signed by me
[18:54] <jono> janos_, maybe one approach is to pass a device=ios string to the site and then it loads the relavant stylesheet
[18:55]  * n8k99 thinks a new accomplishment is installing ubuntu-accomplishments for android
[18:56] <jono> ok, I think we are about out of time
[18:56] <jono> thanks everyone for joining!
[18:56] <n8k99> is it too much scope to think about being able to use this to register meeting other people from the community?
[18:56] <jono> be sure to add #ubuntu-accomplishments to your IRC auto-join :-)
[18:56] <jono> and join the mailing list
[18:56] <jvrbanac> Thanks Jono! will do!
[18:56] <jono> n8k99, that is out of scope :-)
[18:56] <jono> thanks, folks!
[18:57] <jono> #endmeeting
[18:57] <meetingology> Meeting ended Thu Jul 26 18:57:00 2012 UTC.
[18:57] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-18.00.moin.txt
[18:57] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-26-18.00.html
[18:57] <n8k99> thought so!
[18:57] <janos_> notgary: oh i see, good to know!
[18:58] <notgary> janos_: I have no idea how to distribute my profile, so bare with me :)
[18:58] <janos_> jono: i think we can detect screen size with css selectors, so we can be mobile platform agnostic
[18:59] <janos_> notgary: in any case i'm interested in trying the android anyway! ;)
[19:00] <notgary> I'll get onto that while I'm waiting for the CSS.
[19:00] <janos_> great!
[19:02] <jono> janos_, cool!
[19:06] <janos_> ok guys I'll be on #ubuntu-accomplishments channel


[12:44] <T-Bone> http://buildd.slashdirt.org/logs/wnn6-sdk_1.0.0-12_20050407-1249 <- that one might be looking for libwnn6.so.1.0.0 (at the end of the build)
[12:45] <T-Bone> oops
[12:57] <lamont_r> T-Bone: it's ok... he reads the logs
[12:57] <T-Bone> lol
[12:57] <T-Bone> i hate you :)
[01:08] <zul> hey
[02:10] <zul> hey again
[02:32] <zul> me thinks im the only one here..
[04:54] <fabbione> morning guys
[04:55] <zul> hey fabbione crap its late :)
[04:55] <fabbione> no.. it's earlier than usual
[04:55] <zul> late for me
[04:55] <fabbione> the other for me
[04:55] <zul> yeah..
[04:55] <zul> whats up?
[04:55] <fabbione> have to catch an airplane for london :)
[04:55] <zul> ah...
[04:56] <fabbione> i am going to join the others for today's party
[04:56] <zul> cool...im just going through the 00list
[04:56] <fabbione> did you do any work on the patches?
[04:57] <zul> yeah im going through them now, dropped a couple so far
[04:57] <zul> besides the drivers
[04:57] <fabbione> ok
[04:57] <fabbione> did you commit stuff in your branch already?
[04:57] <zul> not yet...i thought i would get through most of it tonight
[04:58] <fabbione> ok
[04:58] <zul> since you guys are going to be partying anyways while im at work...*grumble*bastards*grumble*
[04:59] <fabbione> zul: ok.. just give me the name of the patches and i will kill them here..
[04:59] <fabbione> ah well no
[04:59] <fabbione> you killed the drivers too
[04:59] <zul> yes since we are going to be updating them as well
[04:59] <zul> i can send you my 00list without the drivers
[05:00] <fabbione> nah.. just commit before you go to sleep
[05:00] <fabbione> i will merge when i am in london
[05:00] <zul> sure
[05:00] <fabbione> btw. you can also kill the patches if you want
[05:00] <zul> how long is the flight?
[05:00] <fabbione> not just from 00list
[05:00] <zul> ill get to that :)
[05:00] <fabbione> i will be there in approx 4 hours
[05:01] <fabbione> it takes 2 hours of flight + 2 hours of house <-> airport
[05:01] <zul> cool..copehagen to heathtrow or something?
[05:01] <fabbione> gatwick
[05:01] <zul> ah
[05:01] <fabbione> or whatever is called
[05:01] <zul> heathrow is nice last time i was there
[05:01] <fabbione> heathtrow was twice as expensive
[05:01] <zul> heh
[05:02] <fabbione> yeah because it is more central than the other one
[05:02] <zul> yeah we always landed there when i was living in africa heathrow
[05:03] <fabbione> yeah
[05:05] <zul> fuck...i cant believe i just did that
[05:07] <zul> i need to go to bed..
[05:07] <zul> later
[01:58] <sataere> !ping
[02:08] <fabbione> sataere ?
[02:08] <sataere> Yes?
 !ping
[02:08] <sataere> :)
[04:03] <zul> wtf? arch_commit: unable to acquire revision lock (internal error in archive-pfs.c(pfs_lock_revision))
[04:08] <fabbione> zul: did you interrupt a commit?
[04:08] <fabbione> btw... since you forgot to commit i went forward
[04:08] <fabbione> i need to revert the last commit
[04:09] <fabbione> it's bong
[04:09] <zul> i probably interrupted the commit
[04:09] <zul> what did you change?
[04:09] <fabbione> i started cleaning the patches
[04:10] <zul> k
[04:11] <zul> are you in london yet?
[04:11] <fabbione> yup
[04:11] <fabbione> i am already
[04:11] <zul> cool
[04:12] <zul> i take it you are drinking tonight ;)
[04:12] <fabbione> ok you can sync from now
[04:12] <zul> ok
[04:13] <zul> im just trying to put my changes into baz now
[04:13] <zul> ill sync after
[04:15] <fabbione> zul: it's not easy to fix that problem
[04:16] <fabbione> you need to change some stuff in the archive manually
[04:16] <zul> ok..bleah..frigging baz.
[04:32] <zul> fuck...now i know why its bailing on me
[04:33] <zul> /dev/hda11            4.6G  4.5G     0 100% /var
[04:39] <fabbione> doh
[05:08] <zul> hmmm...PANIC: conflict applying patch in arch_build_revision
[05:44] <spanglesontoast> ?
[05:46] <lamont> spanglesontoast: is conversation in another channel
[05:47] <zul> bbl lunch
[05:47] <spanglesontoast> what you on?
[05:57] <fabbione> guys we are going to face a real problem with 2.6.12
[05:58] <fabbione> apparently they changed something in the evdev driver that changes numbering of some input devices
[05:58] <Mithrandir> uhm
[05:58] <fabbione> like mouse0 -> mouse1
[05:58] <Mithrandir> that's _very_ bad, isn't it?
[05:58] <fabbione> yes, it s for us
[05:58] <fabbione> i need to see if i can find the code change
[05:59] <fabbione> and revert it
[05:59] <fabbione> i am not sure 100% tho...
[05:59] <Mithrandir> sounds easy enough per se
[05:59] <fabbione> it's only one report
[05:59] <Mithrandir> but why have they changed it?
[05:59] <fabbione> i dunno.. we will need to check
[05:59] <fabbione> given that what i was told is true
[07:17] <jbailey> lamont: Around?
[07:17] <lamont> yeah
[07:19] <jbailey> How much of a pain in the arse is it to do a throwaway build of the archive?   I know you suggested that we done one after the toolchian updates, but if it's only a days work on a machine, it might be tempting to do it a few times so that we know if something is seriously broken before we get to the finish line.
[07:19] <jbailey> I just have no concept of what the resource requirements are.
[07:22] <lamont> jbailey: for main, it's the matter of a day or 2, if all 3 buildds are on it.
[07:22] <lamont> it's those really slow gcc-* packages that hurt the most
[07:22] <lamont> :-)
[07:23] <lamont> as for actual work, it's a matter of deciding  what wants to be in the chroot, etc, etc. and then having elmo populate the tree, and periodically flush it
[07:23] <zul> hmmm..conflict...
[07:23] <zul> lamont: how do you resolve a conflict with baz?
[07:23] <lamont> zul: you edit the file, look at the conflicts, and fix them
[07:24] <lamont> just like every other revison control system. :-)
[07:24] <jbailey> lamont: Cool thanks.
[07:24] <lamont> then baz --resolved filename
[07:24] <lamont> or baz --resolved --all


[01:14] <IdleOne> IRCC there is no rush but you may want to ask for +F in #ubuntu-qc to be given to UbuntuIrcCouncil
[01:14] <IdleOne> just in case there is a need at some point
[01:15] <IdleOne> swe3tdave: link to LP profile
[01:16] <swe3tdave> https://launchpad.net/~swe3tdave
[01:16] <IdleOne> swe3tdave: looks good. IRCC I believe swe3tdave would like an ubuntu/member cloak
[01:17] <IdleOne> swe3tdave: sit tight and they will get to it ASAP
[01:17] <swe3tdave> thx
[01:17] <IdleOne> pas de probleme :)
[12:59] <Pici> Pricey: Could we please get an ubuntu/member/swe3tdave cloak for swe3tdave here?
[13:00] <Pricey> Pici: sure, one sec
[13:03] <Pici> thanks
[13:51] <Pricey> Pici: Waiting for their acceptance.
[13:58] <Pricey> Pici: Done.
[13:58] <Pici> Pricey: thanks
[14:01] <IdleOne> Welcome back swe3tdave
[14:02] <swe3tdave> thx
[14:02] <IdleOne> Pici: Pricey #ubuntu-qc needs the UbuntuIrcCoucil added with +F and I need +f in there or whatever it is to be able to add people to the ACL.
[14:04] <Pici> Pricey: can you grant +F to UbuntuIrcCoucil in #ubuntu-qc as well please?
[14:09] <Pricey> Pici: ubuntuirccouncil ?
[14:09] <Pici> Pricey: yes?
[14:09] <Pici> er, yes
[14:09] <Pici> sorry
[14:10] <Pricey> Pici: That's done.
[14:10] <Pici> thanks
[14:10] <Pricey> IdleOne: You'll have to get an Ubuntu GC to make those requests.
[14:11] <IdleOne> Pricey: will do and done, thanks :)


[01:01] <ubotu> New bug: #113992 in xorg (main) "Driver refuses to match my display's resolution or accepta modline to suit" [Undecided,Unconfirmed]  https://launchpad.net/bugs/113992
[04:03] <ubotu> New bug: #113885 in linux-restricted-modules-2.6.20 (restricted) "Wrong resolution detected in DVI (and not in VGA)" [Undecided,Needs info]  https://launchpad.net/bugs/113885
[07:56] <ubotu> New bug: #29880 in xorg "X server failed to start - Fatal server error: Active ring not flushed (does not release console)" [High,Fix released]  https://launchpad.net/bugs/29880


[15:46] <highvoltage> stgraber: hey, do you still happen to have one of those Edubuntu presentation templates? (or if you could forward me some old slides that would be great)
[16:43] <stgraber> highvoltage: I'll forward you some stuff


[18:44] <rpadovani> balloons, I think I understood why tests fail in calculator app. Seems sometimes when it creates the arm package it doesn't include all files, I was able to reproduce it locally.
[18:44] <rpadovani> like http://<IP_ADDRESS>:8080/job/generic-mediumtests-vivid/644/testReport/junit/ubuntu_calculator_app.tests.test_main/MainTestCase/test_operation_after_clear/
[18:44] <rpadovani> there is qml: Error: math.jsTypeError: Cannot call method 'eval' of undefined engine formula:8*8
[18:44] <rpadovani> balloons, could be a CMake problem?


[03:48] <KlfJoat> Does anyone care to look at bug 1102797 for me and make sure I did it right?  It's my first time, so be gentle.  <grins>
[03:48] <ubot2> Launchpad bug 1102797 in sane-backends (Ubuntu) "Fujitsu ScanSnap S1500 does not work after fresh install of 12.10 x64" [Undecided,New] https://launchpad.net/bugs/1102797
[15:26] <om26er> where to report bugs for cdimage.ubuntu.com ?
[15:27] <ogra_> against ubuntu-cdimage
[18:38] <psusi> wasn't there a tag to make the bot stop messing with bugs in the linux package?
[18:42] <ogra_> bot-stop-nagging ?
[18:42] <ogra_> or some such
[18:44] <psusi> that's it
[19:17] <bluefoxxx> this is probably a better channel than #-devel
[19:17] <bluefoxxx> is it appropriate to file bugs in the distribution found?
[19:17] <bluefoxxx> Or should I be working my way upstream, checking for behavior in Debian, and filing from top down?
[19:17] <bluefoxxx> Particularly in this case apache2 comes with a configuration file that includes a global Listen directive
[19:18] <bluefoxxx> this is 1) useless; 2) stupid; 3) problematic if you don't run a VirtualHost on port 80 but DO run other services on port 80
[19:18] <bluefoxxx> Those of us pushing vhosts out with configuration management software can generally avoid messing with httpd.conf except for that
[19:19] <bluefoxxx> anyway
[19:19] <bluefoxxx> trying to decide if I need to file with Launchpad or with Debian's bug tracker
[19:46] <hggdh> bluefoxxx: if it affects Ubuntu, then you can open the bug here. If it is also present in Debian, you should _also_ open one in Debian, and cross-ref both
[19:47] <TheLordOfTime> what hggdh said :)
[19:47]  * TheLordOfTime was ninja'd.
[19:47] <hggdh> (it is better to have upstream fix an issue, always, and it minimises future merges)
[19:47] <hggdh> TheLordOfTime: :-)
[19:48] <TheLordOfTime> hggdh, you pulled the words out of my mouth about upstream... i do that with nginx all the time :P
[19:48] <TheLordOfTime> SEND: bug upstream to nginx trac.  WAIT: for patch.  APPLY: patch for SRUing.
[19:48] <TheLordOfTime> ::p
[19:48] <TheLordOfTime> speaking of which, one of my nginx servers died...  o.O
[19:48] <hggdh> sometimes I *do* pay attention to this channel ;-)
[19:48] <TheLordOfTime> hggdh, :P
[19:59] <bluefoxxx> hggdh, I was more in the mind that I'm not a strictly Debian proper user, it's an extra step for me to go back
[20:00] <bluefoxxx> and interested in if it's fairly likely that opening an Ubuntu bug will get the changes propagated back to Debian if it affects Debian, due to collaboration
[20:00] <bluefoxxx> or if I should spin up a VM and test everything and see if the same bugs come from upstream
[20:01] <TheLordOfTime> typically, what i'd do is look at the debian package...
[20:01] <TheLordOfTime> and see if it exists there.
[20:01] <TheLordOfTime> already *
[20:02] <TheLordOfTime> usually i find already-filed upstream ones, but i also usually file bugs in debian if its not already filed - usually including which version of the package is affected, or the nearest equivalent one.
[20:02] <TheLordOfTime> and of course, testing the upstream package :p
[20:02] <TheLordOfTime> (of course, for PHP5 and nginx, i don't have to do that, its already done by others... xD)   (my specialization is server packages :P)
[20:02] <hggdh> but you are not *required* to open it on Debian. It would help, but it is not necessary. Eventually, someone will.
[20:03] <hggdh> meanwhile, you wait ;-)
[20:03] <TheLordOfTime> yep
[20:03] <TheLordOfTime> ... okay, either apt-mirror hates me or my system is broken..........
[20:03] <TheLordOfTime> :/
[20:06] <antiface> Hi, I'm new to this. Am I supposed to be Triaged first before coming here?
[20:06] <TheLordOfTime> no, we can help you regardless of if the bug is triaged or not :)
[20:06] <TheLordOfTime> although hggdh'll probably be more help than I right now
[20:06]  * TheLordOfTime is debugging apt-mirror
[20:07] <antiface> Ok. Thanks. I just switched to Ubuntu less than a month ago, so it's all very new to me. :)
[20:09] <antiface> I'm still gathering together a proper documentation of the problem anyway.. and it's something that's been discussed a good deal on forums..
[20:09] <yofel> TheLordOfTime: what's wrong with your apt-mirror?
[20:09]  * TheLordOfTime reads the logs
[20:09]  * TheLordOfTime facedesks
[20:10] <TheLordOfTime> lolololololololololololol... its erroring out because one of the mirrors that it mirrors is down xD
[20:10] <yofel> heh
[20:10]  * TheLordOfTime repoints the offline-mirror entry to the US regional archive
[20:11] <TheLordOfTime> s/regional/country code/
[20:11] <antiface> There must be a resource out there, a site or IRC channel for people having a hard time with audio setups?
[20:13] <bluefoxxx> ok
[20:13] <bluefoxxx> That should be a very low importance but I can't triage my own bugs.
[20:13] <TheLordOfTime> triage requires bugcontrol usually, which bug?
[20:13] <bluefoxxx> 1105411
[20:13] <TheLordOfTime> LP Bug 1105411
[20:13] <ubot2> Launchpad bug 1105411 in apache2 (Ubuntu) "apache2 default conf file contains Listen directive" [Undecided,New] https://launchpad.net/bugs/1105411
[20:14] <TheLordOfTime> bugs usually need to be confirmed before we triage, but i agree on the low importance
[20:14]  * TheLordOfTime sets the bug as Low Importance
[20:14] <bluefoxxx> It's low priority because it's effectively meaningless housekeeping minimizing the configuration
[20:14] <TheLordOfTime> agreed, which is why i set it :)
[20:17] <TheLordOfTime> bluefoxxx, which releases are affected?
[20:17] <TheLordOfTime> all of em?
[20:17] <bluefoxxx> 12.10 last I looked
[20:17] <bluefoxxx> I stumbled over it trying to deploy puppetmaster-passenger from a puppet module
[20:18] <bluefoxxx> couldn't figure out how to get port 80 closed
[20:18] <bluefoxxx> manager stumbled over the same issue in RHEL6 a few hours ago because Apache was binding to 80 and breaking another server software ;p
[20:18] <TheLordOfTime> sounds like upstream issues?
[20:18] <bluefoxxx> (I guess it affects RHEL/Fedora too)
[20:19] <TheLordOfTime> if its in Ubuntu its likely in Debian, *checks debian BTS to see whether this is filed there*
[20:19] <bluefoxxx> well, the location is in httpd.conf in RHEL and ports.conf in Ubuntu, but it's probably in Ubuntu because it's in Debian
[20:19] <bluefoxxx> hence why I asked if I should test this in Debian and file there earlier, which I don't have time to do at the precise moment and which requires me to figure out where to get a Debian install ISO :)
[20:21] <TheLordOfTime> i'd file in both Ubuntu and Debian then.  i usually file in ubuntu first and triage it up to Debian where necessary, and sometimes all the way to upstream :P
[20:22] <yofel> ports.conf from SID: http://paste.kde.org/656618
[20:22] <yofel> so feel free to bug them
[20:22]  * TheLordOfTime triages to Debian
[20:23] <bluefoxxx> yofel, is it inconceivable to keep Debian packages in git?
[20:23] <bluefoxxx> like, the build tree, sans the source code
[20:23] <yofel> uh, I think the debian folks do that
[20:23] <bluefoxxx> I don't remember, but i thought that the source of a deb file was without any source code, and that it knew where the code came from, got the tar.gz, extracted it, built, packaged, etc.
[20:23] <bluefoxxx> is that still correct?
[20:23] <TheLordOfTime> yofel, 2.2.22-12, right?
[20:23] <TheLordOfTime> (what you found it on)
[20:24] <bluefoxxx> yofel,  cool, I should find their git server so I can just read through stuff there :)
[20:24] <yofel> bluefoxxx: not really, a normal debian source package is source+packaging as it doesn't need a VCS at all
[20:24] <bluefoxxx> yofel, it's notable that the Listen 443 thing is broken in newest httpd anyway
[20:25] <yofel> but there is a git plugin I believe that does exactly what you're saying
[20:25] <bluefoxxx> I think.  SOmething is.
[20:25] <bluefoxxx> Like, SSL won't inherit SSL configuration directives from the global space in virtualhost anymore, which is funny.  It broke our Web server here when I tried to migrate it.  8)
[20:25] <bluefoxxx> but I know awk
[20:25] <yofel> TheLordOfTime: 2.2.22-12 yeah
[20:25] <bluefoxxx> which is Unix kungfu
[20:26]  * yofel solved *that* with c&p as he only had one host there
[20:26] <yofel> but yeah, I did notice that -.-
[20:28] <yofel> bluefoxxx: I think you're looking for http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=summary btw
[20:28] <yofel> seems to be the full source too though
[20:29] <bluefoxxx> excellent
[20:32] <TheLordOfTime> i shall return, i have to disappear because of reboot :/
[20:47] <TheLordOfTime> yofel, bluefoxxx, bug sent to debian.  Debian Bug 698967 has been linked to the Ubuntu bug.
[20:47] <ubot2> Debian bug 698967 in apache2 "apache2 default conf file contains Listen directive" [Minor,Open] http://bugs.debian.org/698967
[20:48] <TheLordOfTime> (The LP bug is LP Bug 1105411)
[20:48] <ubot2> Launchpad bug 1105411 in apache2 (Ubuntu) "apache2 default conf file contains Listen directive" [Low,New] https://launchpad.net/bugs/1105411
[20:51]  * TheLordOfTime goes off to beat his head into the wall because of Windows being stupid.
[21:12] <TheLordOfTime> bluefoxxx, still here?
[21:34] <bluefoxxx> TheLordOfTime, barely
[21:35] <bluefoxxx> TheLordOfTime, messing with a media server on CentOS6
[21:35] <TheLordOfTime> bluefoxxx, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698967
[21:35] <ubot2> Debian bug 698967 in apache2 "apache2 default conf file contains Listen directive" [Minor,Open]
[21:35] <bluefoxxx> Cannot wait for CentOS7
[21:35] <TheLordOfTime> bluefoxxx, well if you can divert your attention
[21:35] <TheLordOfTime> someonie responded on the debian bug
[21:35] <bluefoxxx> because for a few days, RHEL will not be so much of a pile of crap.
[21:36] <bluefoxxx> TheLordOfTime, from what I can tell the Listen directive is completely unneeded at all
[21:36] <TheLordOfTime> if you have email you can respond :P
[21:36] <bluefoxxx> ok
[21:37] <TheLordOfTime> email<EMAIL_ADDRESS>to respond.  you may want to point out if you're the poster of the ubuntu bug too
[21:37] <TheLordOfTime> since all i did was "triage" it to debian
[21:39] <bluefoxxx> TheLordOfTime, I must have missed something somewhere.  Trying to figure out what I did.
[21:39] <TheLordOfTime> :)
[21:40] <bluefoxxx> TheLordOfTime, I think I'm completely wrong :(
[21:41] <bluefoxxx> Apache listens on whatever it's told to listen on, whether or not there is actually a virtual host listening there.  It doesn't cry that you have a VirtualHost listening on another port that it's not listening on, doesn't open the port, and will cry if you're not listening on any ports.  Blah.
[21:43] <TheLordOfTime> bluefoxxx, so... notabug and i should have it invalid'd in debian and invalid it in  ubuntu?  :P
[21:43]  * TheLordOfTime yawns
[21:43] <TheLordOfTime> apache, while being a server package, isn't on my list of favorite packages :P
[21:45] <bluefoxxx> probably.
[21:54] <bluefoxxx> responded
[22:14] <bluefoxxx> made a fool of myself now
[22:15] <TheLordOfTime> :P
[22:17] <TheLordOfTime> bluefoxxx, don't forget to mark that on the debian bug as well<EMAIL_ADDRESS>:P
[22:17] <bluefoxxx> i replied to the debian bug
[22:17] <bluefoxxx> i should probably put something on the launchpad bug
[22:17] <bluefoxxx> or not do this crap while I'm doing 40 other things at work
[22:17] <TheLordOfTime> someone already did on the lp bug
[22:17] <TheLordOfTime> :P
[22:17] <bluefoxxx> I have too much negative karma to make mistakes :|
[22:17] <TheLordOfTime> https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/comments/2  <-- you?
[22:17] <ubot2> Ubuntu bug 1105411 in apache2 (Debian) "apache2 default conf file contains Listen directive" [Unknown,New]
[22:20] <TheLordOfTime> bluefoxxx, i'm going to assume that comment was yours.
[22:20] <bluefoxxx> DA
[22:20] <TheLordOfTime> i'm forwarding to debian, with the suggestion to mark it as invalid or similar.
[22:25] <bluefoxxx> i think it got there by way of e-mail to the list
[22:25] <bluefoxxx> ...
[22:25] <bluefoxxx> I have no idea what I did, all I know is I saw an e-mail and I hit reply.
[22:26] <bluefoxxx> TheLordOfTime, just send them 'nevermind, end user is incompetent'
[22:26] <bluefoxxx> that should get the point across
[22:29] <TheLordOfTime> :P
[22:29] <TheLordOfTime> doesn't matter.
[22:29] <TheLordOfTime> i've already sent the message along :)
[22:29] <TheLordOfTime> we tend to be nicer than just "INCOMPETENT! </banrifle?>"
[22:29] <TheLordOfTime> :P
[22:34] <TheLordOfTime> bluefoxxx, i suggested that they close the bug as won'tfix or notabug.
[22:34] <TheLordOfTime> they did so :)
[22:34] <TheLordOfTime> and i politely suggested that :)


 I just caught that message today
 X_X
 I did not end up going
 So Comcast never got back to me after they said they would send me audio of the unauthorized call
 No shock there
 I think I need help dealing with this
 They are quick to do that when it does not support their story. I had to bring my own recordings
 Am I allowed to record the call?
 In the case of Comcast, the answer is likely yes as long as they say that the call may be recorded for quality ...
 They allowed someone into the property to change the lines and hose service for other tenants
 I don't even know which laws that falls under
 Likely nothing illegal if they did not release any personal details about the account. Stupid but not illegal
 What about the access and changes to the building?
 Surely you can't legally mess with people's lines without permission
 Or are the lines owned by them on the property?
 The problem is the tenant technically granted entry to the property. I would say the tenant shares the responsibility. It is messy to say the least
 I see
 Palm Beach?
 Found you @RazPi !!! Look behind you
 :( I looked and didn't see you
 I could not resist
 XD
 https://www.npr.org/2018/12/07/674548447/facing-critical-labor-shortage-japan-opens-door-wider-to-foreign-workers
 Looks like Japan may be a nice spot for programmers?
 Do you speak Japanese?
 いいえ、私は本当にGoogle翻訳が得意です。
 Not even a few sentences
 cant we just import japanese
 Due to the planned shutdown of Google Plus in the next few months (Although I hope Google Re-Considers). I have spent the past 15 hours archiving and importing all of my content into my blog @ https://kmyers.me/google-plus-archive/
 Visiting family for Christmas? Replace Windows 10 on their computer with Peppermint OS 9 Respin Linux distro | BetaNews … https://betanews.com/2018/12/22/visiting-family-for-christmas-replace-windows-10-on-their-computer-with-peppermint-os-9-respin-linux-distro/
 While they're not looking
 https://store.steampowered.com/app/331690/Crossing_Souls/
 Some may be interested in that game for the nostalgia factor
 Brought it back to life.
 It was still on 5.x
 @govatent, Red Nexus?
 Nope. I still have my red nexus, but this is the old nexus 7 tablet
 I'm studying for the vmware vcap exam and this will help me read the docs I need to review.
 I hate reading on a laptop
 Oh nice


[08:22] <kjerome> Hi, can anyone take a look at my bugfix? https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2028172
[08:22] -ubottu:#ubuntu-devel- Launchpad bug 2028172 in cups-browsed (Ubuntu) "Cups-browsed cannot bind to port 631 as non-root user on Ubuntu 23.04" [Undecided, New]
[12:22] <ogayot> kjerome: I would suggest subscribing ubuntu-sponsors to your bug so that it eventually appears in the sponsoring queue (http://reqorts.qa.ubuntu.com/reports/sponsoring/). Someone (e.g., a patch pilot) should pick it up from there.
[14:25] <lvoytek> LocutusOfBorg: Hi, sorry I was on break. I don't have upload permissions to lua5.4 in Debian, but I'll go ahead and send in the changes then attempt to get them sponsored, then I'll merge into Ubuntu
[14:26] <LocutusOfBorg> lvoytek, as said, I can sponsor for Debian, once you have a bug with a patch :)
[14:26] <LocutusOfBorg> oh... https://salsa.debian.org/lua-team/lua5.4/-/merge_requests/3/diffs
[14:26] -ubottu:#ubuntu-devel- Merge 3 in lua-team/lua5.4 "Update to lua 5.4.6" [Opened]
[14:26] <LocutusOfBorg> so maybe you can just update the merge request and open a bug pointing to it!
[14:27] <LocutusOfBorg> we don't get notifications about new merge requests...
[14:27] <lvoytek> Alright will do!
[14:27] <LocutusOfBorg> :)
[14:28] <LocutusOfBorg> the maintainer looks active, so this is probably a case of "no email received"
[14:58] <tsimonq2> @pilot in
[14:58] <tsimonq2> ✈✈✈✈✈✈
[14:59] <tsimonq2> Oh nice, 22. Mostly white rows, one yellow, nine red (four of which are still security).
[15:01] <tsimonq2> ogayot: Something's up between our installed quilt versions... figuring out what exactly that is.
[15:01] <tsimonq2> ogayot: So, for example... https://paste.ubuntu.com/p/qkrdp9QjYz/
[15:04] <tsimonq2> ogayot: All of this is entirely personal preference, I'd say. I'll bikeshed further in the Patch Pilot Discourse thread, but I follow a guide with some great recommended defaults for quilt. It doesn't have that Index line, and keeps it pretty minimal. I'd recommend doing a little work on your ~/.quiltrc ;)
[15:05] <tsimonq2> https://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
[15:09] <tsimonq2> Protip for sponsors, that I'll also put in my Patch Pilot response: if you find yourself manually specifying `-k`, just set DEBSIGN_KEYID=<YOUR_KEYID_HERE> in ~/.devscripts - this will pick up your key every time.
[15:09] <tsimonq2> (TODO low-hanging fruit if someone is working on a packaging guide ^^^)
[15:10] <tsimonq2> ogayot: khmer> Uploaded.
[15:10] <tsimonq2> I'll keep an eye on it, in case something fails again. I really appreciate your followup work on this (document it in your application for upload rights! ;))
[15:24] <ogayot> tsimonq2: Thanks for uploading! Hopefully this is the right fix now :)
[15:24] <ogayot> tsimonq2: oh that could be the -pab (or absence of) that I use inconsistently when playing around with quilt, I assume
[15:29] <ogayot> tsimonq2: I'll check the how-to!
[15:30] <tsimonq2> ogayot: No worries, thanks again!
[15:30] <tsimonq2> TIL git-ubuntu doesn't grab the source tarball from the archive for use with debuild, which Sometimes doesn't match the tarball uscan gives you.
[15:32] <tsimonq2> ogayot: python-ulmo> Uploaded as well.
[15:32] <tsimonq2> Not gonna lie, I did type python-elmo to start, as a mistake. :P
[15:33] <tsimonq2> (First kitty, now elmo, ogayot really does find the interesting packages... ;) )
[15:35] <tsimonq2> ogayot: Just for your reference, I fully support filing a bug for tracking, but if ~ubuntu-sponsors is requested as a reviewer, no need to create two queue items by also subscribing -sponsors to the bug. ;)
[15:35] <tsimonq2> (I guess it does work as a fallback.)
[15:37] <ogayot> tsimonq2: ah, I remember adding ~sponsors to the bug. But I believe the automation added it to the MP. Nice asciiart though!
[15:38] <tsimonq2> ogayot: Got it, thanks :D
[15:38] <tsimonq2> @pilot out
[15:38] <tsimonq2> For the next Pilot, I'd recommend bug 2035561 as a starting point. Might need a beefier SRU template.
[15:38] -ubottu:#ubuntu-devel- Bug 2035561 in OEM Priority Project "[SRU]crash when installing tp-smapi" [Critical, Triaged] https://launchpad.net/bugs/2035561
[15:39]  * tsimonq2 goes to bikeshed on the thread, I'll post a link here after
[15:42] <tsimonq2> adrien: Hey, you should add your @canonical.com email address to your LP profile, so your uploads can be linked to you. ;)
[15:42]  * tsimonq2 looks at https://launchpad.net/ubuntu/+source/dpkg/1.22.1ubuntu3 and the ghost profile
[15:44] <adrien> I think it's there but it's not the "main" one; I "only" need to move away from gmail-cannot-sort-emails-but-it's-a-feature-not-a-bug
[15:49] <tsimonq2> I mean, you might be able to merge the ghost one into your actual profile, too.
[16:12] <tsimonq2> https://discourse.ubuntu.com/t/patch-pilot-hand-off-24-04/39509/23
[16:12] <tsimonq2> TODO: ubottu should support Discourse previews, too. :P
[16:17] <tsimonq2> mkukri: It's awfully quiet for a Monday morning (knock on wood...), so I'll hop in and take care of your two latest items.
[16:21] <Eickmeyer> tsimonq2: ubottu requests are a ping to Unit193 *cough*
[16:21] <tsimonq2> adrien: phpmyadmin> I generally disagree with "well, because symphony doesn't have a delta, this means it should be synced," per what the last uploader just commented. That being said, I'll give you an opportunity to follow up before I take that.
[16:21] <tsimonq2> Eickmeyer: Thanks. ;P
[16:24] <mkukri> tsimonq2 thanks
[16:25] <tsimonq2> mkukri: Of course. While you still need a few more uploads, I'll extend the same offer to you regarding endorsing your future application. https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=Mate+Kukri&sponsoree_search=name for your ref :)
[16:26] <tsimonq2> mkukri: nix uploaded for you as well.
[16:26] <tsimonq2> I left a comment on the MP regarding the approach, perhaps for a future merge.
[16:26] <tsimonq2> (Debian allows autopkgtests to access the network?!?)
[16:26] <adrien> tsimonq2: I didn't touch phpmyadmin nor symphony, nor anything PHP :P
[16:26]  * adrien will have to leave in a few minutes
[16:27] <tsimonq2> adrien: I mistakenly pinged you instead of mkukri, sorry. :)
[16:27] <adrien> I'm pretty sure we have a bunch of autopkgtests that access the network and debian has the same afaik
[16:27] <tsimonq2> adrien: Thanks for your quick response :P
[16:27] <mkukri> appreciate it, and yeah im well aware im not there yet, but definitely working towards eventually applying
[16:27] <tsimonq2> adrien: Hmmm. Interesting. Curious on that nix delta then.
[16:28] <tsimonq2> mkukri: Of course. :) If there's anything I can do to help, I'm happy to!
[16:28]  * adrien starts laughing frantically
[16:29] <tsimonq2> I mean, *builds* can't have internet access, maybe the autopkgtest is ran during the build. :P
[16:29] <tsimonq2> (I've made the general assumption thus far that autopkgtests Generally don't access the network.)
[16:29] <mkukri> hmm phpmyadmin is getting comments that it should probably not have any delta anymore
[16:30] <tsimonq2> mkukri: Right. What's your take on it?
[16:31] <adrien> I've seen a number of autopkgtests access the network and sometimes fail due to network issues :P
[16:31] <tsimonq2> hahahahaha :D
[16:31] <mkukri> assuming the commenter is right, ig just disregard the merge and im gonna request a sync
[16:32] <tsimonq2> My original hesitation is around compatibility with PHP 7, but I see we haven't shipped that since Lunar, so I think it should be fine to sync. :P
[16:33] <athos> oh, not really. IIRC the php 7 support was an upstream request
[16:33] <tsimonq2> (Or earlier... don't have a clear view... ubuntu-server may be able to fill in the blanks on my knowledge. I only write in 8 anyway, when I have to do PHP ;) )
[16:33] <mkukri> filed LP: #2044817
[16:33] -ubottu:#ubuntu-devel- Launchpad bug 2044817 in phpmyadmin (Ubuntu) "Sync phpmyadmin 4:5.2.1+dfsg-2 (universe) from Debian unstable (main)" [Wishlist, New] https://launchpad.net/bugs/2044817
[16:34] <athos> we will sync it once the symfony transition is complete though
[16:34] <tsimonq2> athos: Thanks for the insight, could you please comment on the bug when you can? ^^^^
[16:34] <tsimonq2> I'm happy to sync it now, just don't want anything unnecessarily tangled, so I'll hold off.
[16:35] <athos> although we do not ship it in noble, the php community likes to use ondrej's repositories and there are lots of ppl running php 7 from it AFAICT
[16:36] <adrien> I have bad memories of upgrading nextcloud on a debian container: exactly one upgrade path...
[16:37] <tsimonq2> athos: Are you suggesting it would be wise to merge it as originally proposed?
[16:37] <tsimonq2> I mean, in an ideal world, ondrej would just ship this patch in their PPA, we'd sync, everyone is happy.
[16:37] <athos> if we sync it now williamdes_ (upstream) will probably get lots of bugs filed in their bug tracker - that's what we are trying to avoid with the delta
[16:38] <athos> tsimonq2: I suppose a merge would be better for now
[16:38] <tsimonq2> mkukri: Are you cool with that? ^
[16:39] <mkukri> yeah of course, have no stake in this, not my area of the system, im just trying to keep universe up to date :)
[16:40] <tsimonq2> Sounds good! It's my key signing this upload, so if upstream disagrees strongly enough and suggests a different approach, or if ondrej starts deciding to ship this patch, I'm happy to promptly follow up.
[16:40] <tsimonq2> athos: Thanks again for your advice!
[16:50] <tsimonq2> mkukri: Uploaded, FYI. :)
[16:50] <mkukri> ta
[16:55] <lvoytek> LocutusOfBorg: Alright, I've sent in a bug for lua5.4 with an attached merge request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056991
[16:55] -ubottu:#ubuntu-devel- Debian bug 1056991 in lua5.4 "lua5.4: Add packaging improvements from Ubuntu to Debian" [Minor, Open]
[17:06] <mkukri> ive been stupid enough to look at xserver-xorg-input-synaptics and i cannot unsee the horror, fake native package with patches in the tree but applied in git ubuntu in actual reality. turned it into a quilt package and rebased all the ubuntu patches, but it's just all awful because debian is also doing the same horrible thing
[17:07] <mkukri> is there even any point merging that horrible thing as is, and/or fixing it? or just let it die and make everyone use libinput?
[17:09] <tsimonq2> Looks like ubuntukylin still seeds it, but I don't see handsome_feng here... your call. May need some further discussion if the conclusion you come to is "just let it die."
[17:09] <tsimonq2> In general, I
[17:09] <tsimonq2> *I'd support an upload making things better.
[17:09] <tsimonq2> (Plus, it's an example of packaging resilience, hint hint upload rights ;) )
[17:11] <mkukri> the problem with fixing it is that the debian version is similarly bad, so it wouldnt really be a merge but rebuilding the quilt package for ubuntu
[17:12] <tsimonq2> It is in Salsa, and I'd sponsor a (delayed!) NMU if the xorg team is unresponsive (which I highly doubt): https://salsa.debian.org/xorg-team/driver/xserver-xorg-input-synaptics
[17:12] <tsimonq2> Again, up to you if you feel like spending the energy on it. If you've gotten this far, why not :)
[17:13] <mkukri> ill take a look
[17:13] <tsimonq2> Cool!
[17:13] <mkukri> basically the only path to making this nice in ubuntu is fixing debian first
[17:14] <tsimonq2> The only recommended path, yes ;P
[17:56] <mkukri> tsimonq2, i've left an MP on salsa to see what the maintainers think: https://salsa.debian.org/xorg-team/driver/xserver-xorg-input-synaptics/-/merge_requests/8
[17:56] -ubottu:#ubuntu-devel- Merge 8 in xorg-team/driver/xserver-xorg-input-synaptics "Turn this back into a quilt package" [Opened]
[18:13] <tsimonq2> mkukri: Thank you!
[18:14] <tsimonq2> tjaalton: If I'm remembering correctly (I could totally not be), you would know who to ping ^^^
[18:31] <tjaalton> tsimonq2: looks like it got reviewed already
[18:32] <tsimonq2> tjaalton: Rather ping and not need it than not ping and need it :) thank you for your quick response!
[19:01] <seb128> !dmb-ping
[19:04] <mkukri> hmm looks like i was misunderstanding how the upstream package is maintained and was wrong about where the ubuntu package's problems were coming from. closed that MR for now, and will check if i actually need to do something about it upstream tomorrow or just fix the ubuntu package
[19:58] <LocutusOfBorg> lvoytek, can you please also add my patch for debian bug: #1034800?
[19:58] -ubottu:#ubuntu-devel- Debian bug 1034800 in liblua5.4-0 "lualib5.4 is missing expected symbols" [Normal, Open] https://bugs.debian.org/1034800
[19:59] <lvoytek> sure thing
[19:59] <LocutusOfBorg> you need  also to remove the duplicated symbols file because the debian package now in sid dropped the patch 0003-* making the symbols file half useless (c++ symbols are the same as c symbols)
[19:59] <LocutusOfBorg> and my patch of #1034800 is adding obviously 4 new symbols to symbol file
[20:01] <Eickmeyer> lvoytek is a full fledged core dev now. (/me sends stuff for sponsoring 😈 😁)
[20:04] <arraybolt3> Looking forward to getting to do a patch pilot session once I'm a MOTU :P
[20:05] <arraybolt3> though I'm going to have to get faster at packaging - tsimonq2 can burn through stuff in moments that oftentimes takes me 25% longer or so. Hopefully speed will come with experience though.
[20:09] <tsimonq2> mkukri: Thanks again for your efforts on this!
[20:09] <tsimonq2> arraybolt3: Wanna know the secret? Ctrl + R in Bash. Lets you search for previously-typed commands.
[20:10] <tsimonq2> My Bash history also saves as soon as I execute the command, not after I close the terminal.
[20:10] <arraybolt3> Already use that almost daily :)
[20:10] <arraybolt3> Oh, the latter trick I didn't know.
[20:10] <tsimonq2> Okay, nice, so maybe there's another secret I'm not even aware of. :P
[20:10] <arraybolt3> that would be insanely handy, I'm constantly "losing" history between terminals :P
[20:11] <tsimonq2> arraybolt3: Let's continue bikeshedding on this in #lubuntu-devel where it belongs. ;P
[20:12] <tsimonq2> (For context, we keep #lubuntu-devel fairly loose in terms of technical content; it's a good channel to lurk in, but I'm biased. :P)
[20:13] <mwhudson> lvoytek: congrats!
[21:10] <athos> lvoytek <- core-dev; congrats! \o/
[21:44] <lvoytek> Thanks all :)
[22:04] <lvoytek> LocutusOfBorg: I updated the merge request with your patch and the updated symbols file


[04:34] <joji> how to install lamp
[17:19] <Guest19783> Hello , help needed to implement a telepathy client observer properties on dbus without .client file
[18:59] <Rob4> Hi there! Anyone knows how to use HTML5 content hub to retrieve contacts?
[20:14] <Rob4> appdevs, would you know how to read contacts through HTML5 API?


[10:29] <LocutusOfBorg> hello, looks like bos01(s390x) is stuck in some sort of cleaning loop
[10:30] <LocutusOfBorg> (maybe also others)
[10:35] <cjwatson> That's why we have two regions :)
[10:38] <cjwatson> bos01-s390x has been fairly sad for some time - I haven't been putting too much effort into it since IIRC there's a plan to shift hardware over to PS6
[10:38] <LocutusOfBorg> well, bos02 was "disabled" :)
[10:38] <cjwatson> Yeah, I just poked that.
[10:38] <LocutusOfBorg> now looks like situation will shortly improve, thanks
[10:39] <LocutusOfBorg> and yay for hw upgrade!
[10:39] <cjwatson> (This is partly because the usual auto-reset job is currently disabled while IS does some debugging on bos03.()
[10:40] <LocutusOfBorg> thanks
[10:41] <cjwatson> I'm not sure whether it's going to be a hardware upgrade or just redeployment
[11:24] <LocutusOfBorg> sadly looks bos02 is broken again
[11:30] <cjwatson> I'll poke it occasionally, but I'm not going to play manual cron, sorry.  Once IS has finished with their debugging I'll turn the automatic job on again.
[12:01] <cjwatson> IS did some repair work on bos02-s390x, so should be a bit healthier.


[00:33]  * skellat sees that the meeting starts in less than 30 minutes
[00:49] <skellat> Momentary brown-out just happened.  Not good to hear the UPS clicking
[01:00] <skellat> GOOD EVENING UBUNTU OHIO!
[01:01] <belkinsa> (Ouch my hears) ;)
[01:01] <skellat> Who is ready for tonight's meeting?
[01:01]  * belkinsa is ready to go
[01:02]  * drkokandy is hear
[01:02] <drkokandy> whoops
[01:02]  * drkokandy is here
[01:03] <skellat> Who else is ready for tonight's meeting?  jrgifford?  TheMaster?
[01:04] <skellat> Going once
[01:05] <skellat> Going twice
[01:06] <skellat> And with that being said, we'll start the discussion with those who are present and then probably throw this over to our area on discourse.ubuntu.com to keep things moving
[01:06] <skellat> Our agenda can be found at https://wiki.ubuntu.com/OhioTeam/MeetingAgenda2013-11
[01:06] <jenni> [ OhioTeam/MeetingAgenda2013-11 - Ubuntu Wiki ] - https://j.mp/1h2pzsJ
[01:06] <skellat> Tonight's we are "Looking Ahead to the Future"
[01:07] <skellat> Since we were verified by the LoCo Council handily, we need to make some plans for where we are going
[01:07] <skellat> OLF is great but there is life beyond that
[01:07] <skellat> The first item below this is "Mission Statement Discussion"
[01:07] <skellat> drkokandy: I believe you had ideas on this you wanted to propound at the last meeting
[01:09] <drkokandy> I think I just thought that as a group, we ought to have some purpose for being a group. There has been a stagnant mission statement (or something descriptive) on the old Ubuntu Ohio wiki, and so we should at least stop to consider whether that accurately reflects our purpose as an organization.
[01:10] <drkokandy> This is what I added to the beginning of the Verification Application:
[01:10] <drkokandy> Ubuntu Ohio is a LoCo community which is focused on growing the use of Ubuntu in the state of Ohio. Membership is open to anyone with an interest in Ubuntu who commits to abide by the Ubuntu Code of Conduct.
[01:10] <drkokandy> ... which was based on the description on Ubuntu Ohio's Launchpad page
[01:11] <drkokandy> Which was just this:
[01:11] <drkokandy> We are focused on growing the use of Ubuntu in the great State of Ohio!
[01:11] <belkinsa> I agree, that new one should be added on the LP page also.
[01:11] <drkokandy> This was the statement from the main OhioTeam page on the Ubuntu Wiki:
[01:11] <drkokandy> The OhioTeam focuses on distributing, advertising, and demonstrating Ubuntu in the state of Ohio. Through expansion of our projects, we focus on the areas of schools, businesses, and home users.
[01:12] <drkokandy> So, since I am not sure about how this should work, do we want to put what I wrote up as a discourse and have people suggest changes/additions/etc since we are low on attendance today?
[01:13] <drkokandy> Or do you have suggestions that you want to discuss now, belkinsa, skellat?
[01:13] <skellat> We'll post the whole log and then carry on the discussion from there
[01:13] <skellat> We'll build a discussion record now then post the log to discourse and let things continue there
[01:13] <belkinsa> We could have a small one right now if we have something to say.  skellat and I, that is.
[01:14] <skellat> I will put the question at this point to you both.  What would you like the mission statement to be?
[01:14] <belkinsa> skellat and me*
[01:15] <belkinsa> Hybrid of the two.   Well, more like combine what we had one our app with the one on our main wiki page and place that also on the LP page.
[01:16] <drkokandy> hmm... I think what I wrote talks about what LoCos in general do, and is not necessarily about pushing us forward to do more. I think if we wanted to create a mission statement (really a mission statement), we should probably start with identifying some goals (a mission) that we would like to accomplish
[01:16] <skellat> Okay
[01:16] <skellat> What do you want to have accomplished by the community in 2-3 years?  What do you want to strive for?
[01:18] <drkokandy> The old one on the wiki has specifc Whats: distributing, advertising, and demonstrating. And also specific target audiences: schools, businesses, home users. Those could still be possible activities/audiences
[01:19] <drkokandy> What we've done so far recently has been to put on an educational/social event (UbuCon)... if we would like to continue doing that with the goal of making those more frequent, that could be a thing
[01:20] <drkokandy> we could also write into the mission statement the goals that you've been working on to guide Ubuntu Ohio members to full Ubuntu Membership, skellat
[01:20] <skellat> Okay
[01:21] <skellat> Belkinsa, how say you?
[01:21] <belkinsa> I agree with what drkonandy, but I don't have anything else to add.
[01:21] <belkinsa> -what
[01:21] <skellat> Okay
[01:22] <skellat> I think we've got that started enough for others to chime in on
[01:22] <skellat> The second bit is "Plans for the Trusty Tahr Cycle"
[01:23] <skellat> All I can note is that through discussion at vUDS-1311 we're looking at Global Jam being somewhere around 2014-03-21 to 2014-03-23 **tentatively**
[01:24] <jrgifford> Fantastic, glad we've got a sorta date for the jam
[01:24] <belkinsa> Is this virtually speaking or actual in person event?
[01:24] <jrgifford> belkinsa: so, this is a mix
[01:24] <skellat> :-)
[01:24] <jrgifford> it's generally something that is done in person
[01:24] <belkinsa> Okay.
[01:24] <jrgifford> but there are also virtual events that are organized, at least over the past 3-4 cycles, there have been
[01:24] <skellat> UbuCon 2013 was our event for the last Global Jam
[01:25] <jrgifford> ah, cool
[01:25] <skellat> If we want to hold an event during the Trusty Tahr cycle, I need to wait on a blocking dependency
[01:26] <skellat> Namely that I've been made a tentative job offer by an $AGENCY that does not have its appropriations settled past 2014-01-15 so the job offered could disappear on me
[01:27] <skellat> Does anybody have a burning desire to have an event held somewhere in the state before Global Jam?
[01:27] <jrgifford> hm.
[01:27] <jrgifford> could be fun to try something
[01:27] <jrgifford> but the problem is we're scattered
[01:28] <belkinsa> Yeah.
[01:28] <skellat> That's why we could possibly shoot for Global Jam to do something at perhaps a State Park that has a lodge or other campground
[01:28] <belkinsa> Unless done with Hangouts and IRC, like vUDS/
[01:28] <jrgifford> difficulty: Internet
[01:29] <skellat> These have Internet: http://parks.ohiodnr.gov/lodges
[01:29] <jenni> [ Lodges & Conference Centers in Ohio State Parks ] - https://j.mp/18gl9O3
[01:30] <jrgifford> ok, anyone have a clue on pricing then?
[01:30] <jrgifford> that's the only remaining "big" question... i think
[01:31] <skellat> We'd have to contact for quotes
[01:31] <skellat> That could be saved for next month after there is a chance to assess interest
[01:31] <skellat> The only lodge that is off the table is Geneva...because that is **HERE** in Ashtabula County
[01:32] <drkokandy> I can only pull up prices for rooms at the lodge using the online system, not reserving a meeting room at the conference center
[01:33] <skellat> drkokandy: Yeah, that'll require me making contact directly working the phones
[01:33] <jrgifford> ok
[01:34] <skellat> Deer Creek is in Mt. Sterling which is outside metro Columbus so that would be closest to the state's center that we could get
[01:34] <skellat> http://parks.ohiodnr.gov/deercreek
[01:34] <jenni> [ Deer Creek State Park ] - https://j.mp/18glCja
[01:34] <jrgifford> ok, sounds like a possibility.
[01:35] <belkinsa> +1
[01:35] <skellat> We'll leave that for further discussion in keeping with the rest of tonight's meeting
[01:36] <skellat> Item #3 under the main heading is "Planning Beyond Trusty Tahr"
[01:36] <skellat> Does anybody have any thoughts to contribute at this time?
[01:36] <jrgifford> is this somewhat of an open-ended, "Anything goes" question?
[01:36] <skellat> To an extent.
[01:37] <belkinsa> I'm planning to release where we are poll on SurveyMonkey soon so we can think about ReLoCo's.
[01:37] <skellat> What would you like the Ubuntu Ohio community to be doing after April 2014?
[01:38] <skellat> belkinsa: Understood
[01:38] <skellat> But again, what would folks attending tonight like to see Ubuntu Ohio doing after Easter 2014 which would be the week after the latest LTS will be released to the world?
[01:38] <belkinsa> We also have the topic on Disclosure: http://discourse.ubuntu.com/t/where-in-ohio-do-you-hail-from/1257
[01:38] <jenni> [ Where in Ohio do you hail from? - Ubuntu Discourse ] - https://j.mp/Im680n
[01:39] <belkinsa> Could we try using Hangouts and IRC for a release party?
[01:39] <jrgifford> We could.
[01:40] <jrgifford> So something I've noticed, is that it is easier to work on open source stuff if other people are too
[01:41] <jrgifford> Do we want to consider having some sort of an open "here's what we have been/are working on with Ubuntu" thing every month or two?
[01:42] <TheMaster> This presumes you're not bat crap crazy.
[01:42] <belkinsa> As a virtual (Re)LoCo?
[01:42] <jrgifford> Something of the sort belkinsa
[01:43] <belkinsa> I would be okay with that.
[01:43] <jrgifford> TheMaster: oh, you should know I am. :-P
[01:43] <belkinsa> Might be better off for us anyways since we are scattered.
[01:43] <TheMaster> For the most part, the point of a LoCo is because everyone is closer so they should be more able to do in-person events, otherwise it's a mesh up of -devel and -offtopic.
[01:43] <TheMaster> jrgifford: Suuure. :P
[01:44] <jrgifford> TheMaster: true - but we have shrunk in active people. So, this might be a place to start.
[01:45] <belkinsa> We need a YouTube account for this, right?
[01:45] <jrgifford> Just someone with a Google account, if we were to do hangouts.
[01:45] <belkinsa> And maybe a blog where we post the other things from these sessions.
[01:45] <belkinsa> Right, right.
[01:45] <TheMaster> This is sounding like something I could do with people in #xubuntu-offtopic, not something that needs to be in -oh. :P
[01:46] <jrgifford> TheMaster: one word: timezomes
[01:46] <jrgifford> *timezones
[01:46] <belkinsa> At least timezones will not effect us.
[01:47] <TheMaster> Technically no, but patterns still, which may as well be the same thing.
[01:47] <skellat> TheMaster: Explain that further, please, instead of just throwing a one-liner out there
[01:47] <belkinsa> +1
[01:47] <jrgifford> Anyway, didn't mean to hijack the discussion, just tossed out something I've been considering.
[01:48] <belkinsa> You didn't hijack it.  It was along the lines of planing past 14.04.
[01:48]  * TheMaster thinks he should get jrgifford to work on his stuff. :D
[01:49] <skellat> Well, somebody is in a mood tonight
[01:49] <belkinsa> skellat, is (or has) any other LoCo done this idea that jrgifford is suggesting?
[01:50] <skellat> It came up at the macro- level as a proposal from Canonical Community Team during vUDS-1311 but nothing at local level
[01:50] <belkinsa> Okay, just was wondering about this.
[01:51] <skellat> Okay
[01:51] <skellat> Looking past Easter 2014 may be a little rough to do at the moment
[01:51] <skellat> That wraps up the "Looking Ahead" discussion
[01:52] <skellat> Is there "Any Other Business" that needs to be brought forward at this time for resolution?
[01:52] <belkinsa> None for me.
[01:52] <jrgifford> None here
[01:52] <drkokandy> nope
[01:53] <skellat> TheMaster: Anything on your end?
[01:55] <TheMaster> No.
[01:55] <skellat> This meeting stands adjourned.  The next meeting is subject to call.
[01:55] <TheMaster> jrgifford: So been doing anything of interest lately?
[01:55] <jenni> oh baby
[01:56] <TheMaster> jenni: yeah, honey.
[01:56]  * belkinsa rolls my eyes at jenni
[01:57] <TheMaster> jrgifford: You don't happen to have a bitbucket, right?
[01:57] <jrgifford> TheMaster: i  do have a bitbucket
[01:58] <jrgifford> Same username, almost nothing there
[01:58] <jrgifford> Haven't been doing much lately.
[01:58] <TheMaster> Well sweet, that's the only public VCS I have, used or not.
[01:58] <TheMaster> (LP not counting, of course.)
[01:59] <belkinsa> Just a quick question: would a Google form work better as a survey for where our members are located?
[02:06] <belkinsa> Never mind, created one.  I just didn't want to make another useless account on some site that I will only use once
[18:28] <Unit193> paultag: Howdy.
[18:30] <paultag> yo