[16:00] <mvo> hello
[16:01] <barry> hi
[18:11] <Edward_Elric> .
[18:15] <UndiFineD> o/
[18:59] <_oo__anand__oo_> .
[19:57] <HedgeMage> highvoltage: I'll idle and log to read later, but I'm not really here
[19:57] <HedgeMage> I have to get LF from school soon.
[19:57] <highvoltage> HedgeMage: ok :)
[19:57] <highvoltage> anyone else present and ready for action?
[19:57]  * highvoltage stares at mgariepy 
[19:57] <highvoltage> (IRL and on IRC)
[19:57] <mgariepy> I'm here
[19:58] <HedgeMage> highvoltage: if these meetings happened a different time of day, I'd attend most of them...they just happen to hit the pick-up-from-school time.
[19:58] <mhall119> I'm here
[19:59] <highvoltage> I started working on the release announcement, it's available for preview here: http://edubuntu.org/news/10.10-release
[19:59] <highvoltage> still very draft
[19:59] <mhall119> on time for once
[19:59] <highvoltage> HedgeMage: ok, you get to pick the next meeting time, mail/jabber/irc me
[19:59] <highvoltage> hey mhall119
[20:00] <HedgeMage> highvoltage: coolness!  Will do.
[20:00] <HedgeMage> ttyl
[20:00]  * HedgeMage idles
[20:00] <highvoltage> hmm, slow wiki is sloooooooow
[20:00] <mhall119> "installable directly from the installer, allowing a much more intuitive installation" sounds funny to me, too many uses of "install"
[20:00] <highvoltage> I started working on https://wiki.ubuntu.com/Edubuntu/Community/WorkForGrabs
[20:01] <mhall119> but I'm not sure how else to phrase it
[20:01] <highvoltage> it's not as nice as the KDE one yet. at UDS we can expand it and probably assign people to tasks too
[20:01] <highvoltage> mhall119: noted! I'll put some thought into it (suggestions still welcome)
[20:01] <mhall119> also, a description of what Gnome Nanny is would be good
[20:02] <highvoltage> I'm extremely tempted to make it slightly more flashy and add pictures and screenshots, but it will mostly be distributed in text form anyway
[20:02] <mhall119> you can just add a link to screenshots
[20:02] <pleia2> highvoltage: nice!
[20:02] <highvoltage> yep, I guess
[20:03] <highvoltage> besides release announcement / release notes, I'm just going to work on testing the final image that's going to be built today
[20:04] <highvoltage> if all goes well that will be our release that would get released on Sunday
[20:04] <highvoltage> anyone is welcome to do that though :)
[20:04]  * mhall119 needs to zsync the new dvd image
[20:04] <highvoltage> I gave dinda blog access on the site
[20:05] <highvoltage> mhall119, mgariepy: if you'd like access too just poke me in pvt some time and I'll create you an account
[20:05] <highvoltage> will be nice to have people write blog entries on the site that's just not me and stefanlsd :)
[20:05] <highvoltage> oops, that was aimed at stgraber (sorry stefanlsd)
[20:06] <mhall119> highvoltage: I might do that after UDS, so I can blog about integrating Qimo
[20:06] <highvoltage> mhall119: that would be really nice
[20:06] <mhall119> and any other edubuntu work I will (hopefully) be doing this cycle
[20:06]  * stgraber waves
[20:06]  * mhall119 plans to apply for Edubuntu membership this cycle
[20:07] <highvoltage> mhall119: you're already an Ubuntu member aren't you?
[20:07] <mhall119> yeah
[20:07] <mhall119> just not Edubuntu
[20:07] <mhall119> cause I've done nothing much for it yet
[20:07] <mhall119> but that's all gonna (hopefully) change this cycle
[20:08] <highvoltage> ok, previously ubuntu members got edubuntu membership for free, I can't remember if that changed with the new EC charter
[20:08] <highvoltage> (well, if they asked for it)
[20:08] <mhall119> I didn't ask for it
[20:09] <highvoltage> well, you're stable and have been present in the community a long time now, and you've worked on edu-related packages in Ubuntu, so perhaps it's about time you ask for it :)
[20:09] <mhall119> I will, in due time
[20:10] <highvoltage> anything else we should cover in this meeting?
[20:10] <highvoltage> we're almost at that stage where we just have to hold our breath until release :)
[20:10] <mhall119> I sent comments back to dinda on her marketing stuff
[20:11] <mhall119> I'm not sure when she had to have those done
[20:11] <mhall119> still don't know if she'll be at UDS or not
[20:12] <highvoltage> she'll be at half of it, I just can't remember if it was the first half or second half
[20:12] <mhall119> ok, cool
[20:12]  * highvoltage wonders where dinda is today, she's usually quite vocal
[20:14] <highvoltage> well, I'm off to go on with work again, if anyone needs anything, feel free to poke me :)
[20:15] <mhall119> meeting over already?
[20:15] <highvoltage> mhall119: unless you have anything else? :)
[20:15] <mhall119> nope, just looking forward to seeing everyone at UDS
[20:15] <highvoltage> yes, that will be great!
[20:16] <ElWuilMeR> is mandatory to have the wiki in English to ask for membership?
[20:19] <mhall119> ElWuilMeR: it helps if your board doesn't all speak your native language
[20:19] <highvoltage> ElWuilMeR: good question, we won't count it against you if it's not, but if no one is available to translate if for us or if we can't make sense out of it with google translate as a last resort, then it will be harder to evaluate your application
[20:22] <ElWuilMeR> mhall119: highvoltage thanks I will have three months before applying for membership and pass it to English then wiki
[21:59] <barry> hi folks.  udd meeting in 1m
[21:59] <poolie> hi there barry
[22:00] <barry> hi poolie
[22:00] <barry> #startmeeting
[22:00] <MootBot> Meeting started at 16:00. The chair is barry.
[22:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:00]  * ajmitch will try & be around
[22:00] <barry> ajmitch: cool
[22:00] <barry> james_w: hi
[22:01] <barry> y'know i don't know if rockstar plans to be around for these.  thunper was last time
[22:01] <barry> slangasek: hi
[22:01]  * slangasek waves
[22:01] <poolie> thumper is on holiday this week
[22:01] <poolie> agenda?
[22:01] <barry> [TOPIC] agenda
[22:01] <MootBot> New Topic:  agenda
[22:01] <barry> https://wiki.ubuntu.com/DistributedDevelopment/20100106
[22:01] <barry> [LINK] https://wiki.ubuntu.com/DistributedDevelopment/20100106
[22:01] <MootBot> LINK received:  https://wiki.ubuntu.com/DistributedDevelopment/20100106
[22:02] <barry> i figured we'd review action items first
[22:02] <james_w> howdy
[22:02] <barry> [TOPIC] action items
[22:02] <MootBot> New Topic:  action items
[22:02] <james_w> always a good idea
[22:02] <barry>    * '''poolie to confirm charline to do user studies at UDS-N'''
[22:02] <barry>  
[22:02] <flacoste> hi folks
[22:02] <poolie> hi flacoste
[22:02] <barry> flacoste: hi!
[22:03] <poolie> charline hasn't replied to my pings; i asked matthew to contact her but i still haven't heard back
[22:03] <poolie> i'll escalate to someone else
[22:03] <poolie> maybe she's been away
[22:03] <flacoste> no she was there last week
[22:03] <flacoste> have you sent her an email?
[22:03] <poolie> yes, a couple
[22:03] <poolie> mail pings, i meant, not irc
[22:03] <flacoste> she's kind on the opposite end of the world to you
[22:03] <flacoste> ok
[22:04] <flacoste> i'll try to grab her tomorrow
[22:04] <barry> flacoste, poolie thanks
[22:04] <poolie> thanks, please just ask her to answer them or to call me
[22:04] <barry>    * '''poolie to organize a foyer poster'''
[22:04] <poolie> related note, the survey is now ready to launch
[22:04] <poolie> i'll ask mrevell to turn it into production
[22:04] <barry> poolie: very cool.  it will be nice to get some data before uds
[22:05] <poolie> not done yet; still a good idea; will do it before we go
[22:05] <poolie> flacoste: can you help me get a small bit of attention from design people?
[22:05] <barry> np.  we can keep both on the list for next time
[22:06] <barry> * '''barry to register udd sessions at uds''' (after finding the right theme/track)
[22:06] <barry>    * '''barry to register general bzr/lp session in "app devs" theme'''
[22:06] <flacoste> poolie: for charline or something else?
[22:06] <flacoste> hmm, the foyer poster
[22:06] <flacoste> forget it
[22:07] <flacoste> you are on your own there :-)
[22:07] <poolie> ok :)
[22:07] <flacoste> no way they can do something about this before UDS
[22:07] <barry> :D
[22:07] <poolie> probably would be too long, yeah
[22:07] <poolie> it'll be nerdy but it'll be there
[22:07] <barry> poster board + fat sharpie :)
[22:07] <barry> i coordinated both with robbiew who actually scheduled the blueprints for all three session we talked about last time
[22:07] <barry> so i think we're good to go for uds sessions
[22:08] <james_w> thanks
[22:08] <barry>    * '''barry to make ajmitch be udd stakeholder representing REVU'''
[22:08] <barry>  
[22:08] <barry> done
[22:08] <ajmitch> not much to do with that one :)
[22:08] <barry>    * '''poolie to get a better graph of package import failures'''
[22:08] <barry> ajmitch: no, but thanks for coming by today!
[22:09] <poolie> i see james did some of that for me
[22:09] <barry> saw that too, thanks james_w
[22:09] <james_w> jml fixed the internal graph
[22:09] <james_w> and I produced some external ones
[22:09] <james_w> already showing some interesting results :-)
[22:09] <poolie> hottest100 is not yet graphed; i tried that but it got too many errors connecting to lp
[22:09] <james_w> http://package-import.ubuntu.com/status/index.html
[22:09] <MootBot> LINK received:  http://package-import.ubuntu.com/status/index.html
[22:10] <james_w> see at the bottom for the graphs
[22:10] <barry> james_w: what's the spike?
[22:10] <poolie> lp outage, i think :)
[22:10] <james_w> LP refusing to talk to us for a while
[22:10] <poolie> to judge from the errors i saw yesterday
[22:11] <barry> ;)
[22:11] <james_w> I'd love it if someone could code a higher level of backoff too
[22:11] <poolie> i think adding more graphs is not a priority atm
[22:11] <poolie> i'd rather force that existing graph down to 0 and then worry about whether there are things its not measuring
[22:11] <poolie> any objections?
[22:12] <barry> agreed.  i think we can mark this one "done" for now
[22:12] <james_w> poolie, which graph in particular, or all of the ones we have now?
[22:13] <poolie> specifically "number of packages that failed to import"
[22:14] <poolie> it would be a bit nice to graph "hottest100" and i may yet do it, but i don't know if i'll do it before UDD
[22:14] <poolie> s//UDS-N
[22:14] <james_w> ok
[22:14] <barry>    * '''barry to start some sphinx docs to be well-integrated w/ wiki.u.c'''
[22:14] <barry> not done. will carry over
[22:15] <barry>    * '''barry to talk to dholbach about making sure udd is well advertised in pkg guide'''
[22:15] <barry> not done.  i'll probably wait and chat with daniel f2f @ uds
[22:15] <barry>    * '''barry/poolie to write up job announcements; barry posts to python job board, james_w/slangasek posts to debian-jobs, ubuntu-devel'''
[22:15] <james_w> not done
[22:15] <poolie> perhaps we should have a small udd docs session at uds? maybe just informally
[22:15] <barry> i have a template almost ready for review for the python jobs board.  i'll send around a pastebin when i think it's ready
[22:16] <poolie> ok
[22:16] <slangasek> I haven't been given anything to post, so haven't posted :)
[22:16] <poolie> i'm planning to do some interviews before UDS
[22:16] <barry> poolie: good idea
[22:16] <poolie> http://webapps.ubuntu.com/employment/canonical_BSE
[22:16] <MootBot> LINK received:  http://webapps.ubuntu.com/employment/canonical_BSE
[22:16] <barry> the python jobs board has a very specific template, which is what i'm fitting the above into
[22:16] <poolie> thanks
[22:17] <poolie> so doing it this week or at least next week would be really good
[22:17] <poolie> please also personally invite anyone you know with relevant skills that you'd like to work with
[22:17] <barry> poolie: i'll have something to review by tonight or tomorrow.  debian-jobs and ubuntu-devel might need a different format
[22:18] <poolie> related question, would anyone like to interview shortlisted candidates?
[22:18] <poolie> thanks very much barry, i really appreciate circulating it to there
[22:18] <slangasek> I don't think debian-jobs has any particular formatting requirements, fwiw
[22:18] <barry> poolie: i'm happy to, though i probably can't grill them too much on bzr internals
[22:18] <james_w> poolie, I would
[22:19] <james_w> though maybe would should avoid too many interviews :-)
[22:19] <poolie> i think about 2-3 would be ok
[22:19] <barry> james_w: maybe just make them fix a bug using udd as the first gauntlet
[22:19] <poolie> so me plus one of you plus statik
[22:20] <poolie> and write a short report on it :)
[22:20] <james_w> heh
[22:20] <barry> :)
[22:20] <barry> poolie: sounds good
[22:20] <barry> btw, i did post it on my fb wall for all the good it did ;)
[22:21] <barry> anyway...
[22:21] <barry>    * '''james_w to merge bzr-debuntu to bzr-builddeb'''
[22:21] <barry> well, not done, but sort of morphed
[22:21] <barry> bug 609186 is tracking this
[22:21] <barry> we're going to get the uncontroversial ones into bzr 2.3 and then worry about the rest
[22:22] <barry> https://code.edge.launchpad.net/~barry/bzr/609186-shortcuts/+merge/37787
[22:23] <barry> that's it for the action items.  does anyone have comments to add on any of the above before we move on?
[22:23] <james_w> on the poster idea from last time
[22:23] <james_w> I have been thinking for a while that one of the issues people have with using bzr-builddeb is getting the mental model of what is going on right
[22:24] <james_w> and I think I have some pictures that will help with this
[22:24] <james_w> I started putting together an ebook that I showed barry, and he suggested perhaps getting it printed to hand out at UDS
[22:24] <james_w> I thought that this was a great idea, but there are a couple of problems with it
[22:24] <james_w> 1) that ebook is now on my barely-alive harddrive, so it may be lost
[22:25] <james_w> 2) printing in that form would be very expensive
[22:25] <barry> :(
[22:25] <james_w> so, would something simpler be good to have
[22:25] <james_w> say a 2-fold booklet or similar?
[22:25] <poolie> perhaps
[22:25] <james_w> we can still distribute a full thing electronically of course
[22:26] <barry> james_w: definitely.  think we can get something useful on a single 8.5x11 (front & back)?  we could print that at any kinkos to pass out
[22:26] <poolie> may also be more likely to be read in the short-attention-span environment of uds
[22:26] <poolie> perhaps we could also put that content on the poster, along with a description of what we're doing and who to talk to
[22:27] <james_w> barry, I haven't figured out how to present the information in that format yet, but I don't think it would be impossible to get something
[22:27] <barry> be sure to include the url to the top udd wiki page
[22:27] <james_w> I'm not sure a poster is the right format for what I was working on, as I'm not sure many people would digest it from a poster
[22:27] <james_w> but if we can get something that works as a poster that would be great
[22:28] <james_w> I wish I had the start of the content to show you all now, I'll try and rescue it and send it around
[22:28] <barry> james_w: i was thinking about something we could (at least) hand out at the educating-users session
[22:28] <poolie> james_w: next time, duplicity backups to s3 :)
[22:28] <poolie> from cron :)
[22:28] <james_w> :-)
[22:28] <barry> james_w: i forget - did you email it to me?
[22:29] <james_w> barry, no, I don't think so
[22:29] <james_w> and I don't think I sent you the source either?
[22:29] <barry> ah.  oh well
[22:29] <barry> no, pretty sure you didn't
[22:29] <james_w> ah, as it was IRC it is probably on the web somewhere
[22:30] <barry> riigght
[22:30] <james_w> yes http://people.canonical.com/~jamesw/guide.pdf
[22:31] <barry> so for action item wrap up: poolie will continue with poster and james will send around his ebook, and (?) get it into a format for passing out at uds
[22:32] <poolie> good
[22:32] <barry> cool, moving on...
[22:32] <poolie> and the rest of you will circulate/recommend the job ad
[22:32] <barry> poolie: +1
[22:32] <barry> [TOPIC] MVO feedback
[22:32] <MootBot> New Topic:  MVO feedback
[22:33] <barry> so, i had a brief mumble chat w/mvo today and we talked about udd a bit.  he had some interesting feedback that i'd like to share.  i'll paste the points here and then we can discuss...
[22:33] <barry>    * Fast and easy for simple case (version bump only)
[22:33] <barry>    * upstream tarball is all you need (no source branch; debian/ only)
[22:33] <barry>    * `dch -i` + build and that's it
[22:33] <barry>    * people who are only packagers don't need full source
[22:33] <barry> (done)
[22:34] <barry> so mvo was most concerned with packages who aren't developing the code, or the many people who just need to do a version bump.
[22:34] <james_w> version bump with no changes?
[22:34] <barry> his concern was that it needs to be at least as fast to do that with udd as it is now
[22:34] <barry> james_w: yep
[22:34] <poolie> that's a good test
[22:34] <james_w> build-from-branch!
[22:34] <barry> or, just grab debian version and bump
[22:34] <james_w> if we have build-from-branch then we can make it super-cheap
[22:35] <slangasek> yes, it does need to be fast - I think that ties in with my concerns about having easy-to-configure mirrors of bzr branches
[22:35] <james_w> then you don't even need to get the branch even, just commit remotely and request a build
[22:35] <poolie> it'd be good to make sure they're documented, then see how simple the documentation looks and how long it takes to execute
[22:35] <barry> james_w: can you elaborate?  mvo's main concern was downloading the source branch when a lot of folks (currently) only use debian/
[22:35] <james_w> or we make it a non-issue by implementing rebuild support in soyuz :-)
[22:36]  * barry looks to flacoste 
[22:36] <james_w> barry, you don't /need/ the data locally to do that, Launchpad is the source and target, and so if the pieces are there we can just ask Launchpad to do the operation
[22:37] <james_w> that will be faster than the current approach of apt-get source + dput
[22:37] <barry> james_w: so no need to branch locally to dch -i?
[22:37] <flacoste> i don't understand how rebuild helps here?
[22:38] <slangasek> barry: I do disagree strongly with mvo's conclusion that packagers only need debian/; that guarantees that if that package ever needs patching to the upstream sources, you end up with a two-step merge (VCS merge, followed by a quilt merge).  debian/-only VCS branches drive me crazy!
[22:38] <james_w> barry, we can remove that need, as bazaar's vcs means that you can commit remotely if you want
[22:38] <james_w> barry, so we can simulate dch -i + commit remotely, and then request a build
[22:39] <james_w> or, as I said, rebuild support makes it all a non-issue really, as you just ask soyuz to rebuild without a source change, so you don't need apt-get source, dput or bzr
[22:40] <slangasek> james_w: "without a source change"?
[22:40] <james_w> binNMU
[22:40] <barry> i think i see.  this is definitely a workflow not covered in the current wiki docs
[22:40] <flacoste> isn't a version upgrade a source code change?
[22:40] <slangasek> my understanding is that "version bump only" refers to "upstream version bump only"... where you don't care about the old upstream source because you're forklift replacing it for the upload you're preparing
 version bump with no changes?
 james_w: yep
[22:41] <poolie> so the top level issue is, they want to just pull in a new upstream version, and that should be as fast and simple as possible? or no?
[22:41] <james_w> I read that as "no-change rebuild", not "new upstream version"
[22:41] <flacoste> right, that's the confusion
[22:41] <flacoste> barry which one is it?
[22:42] <barry> well, now i'm not 100% sure what mvo was getting at.  he kind of mentioned both scenarios
[22:42] <flacoste> lol
[22:42] <james_w> because "dch -i + build" isn't all you need for a new upstream version
[22:42] <slangasek> james_w: it is for /many/ packages
[22:42] <james_w> no, because dch -i gives you the same upstream version number as you had before :-)
[22:43] <slangasek> oh, I interpreted that as pseudocode, sorry :)
[22:43] <poolie> why would they want a no-change rebuild? to rebuild on new dependencies?
[22:43] <james_w> poolie, yes
[22:43] <flacoste> for the rebuild use-case, i agree that the easiest thing is to implement it in LP directly
[22:43] <james_w> there are many reasons why it can happen, but there are several hundred occurences per-cycle
[22:44] <barry> i'm sure mvo mentioned the "new upstream version" scenario
[22:44] <james_w> "new upstream version" is harder, I agree, and we should ensure that it is optimised too
[22:44] <flacoste> especially, if he was referring to the debian/ branch packaging
[22:44] <poolie> that seems fairly obviously like the first thing someone might want to do in udd
[22:45] <barry> yes, he specifically mentioned debian/-only branches
[22:45] <james_w> where there are no patches, I would argue that we are /almost/ as efficient as the old way, discounting the overhead of bzr branch/push
[22:45] <james_w> we just need someone to implement watch-file support in merge-upstream
[22:45] <barry> james_w: that's something i'd like to attempt
[22:46] <james_w> barry, great, I'm happy to help
[22:46] <barry> thanks!
[22:46] <poolie> so this should live in https://wiki.ubuntu.com/DistributedDevelopment/Documentation/NewUpstreamVersion
[22:46] <james_w> where there are patches, then I think both methods are terrible, but I would think that the old method is currently better there
[22:46] <poolie> and then you would do https://wiki.ubuntu.com/DistributedDevelopment/Documentation/UploadingAPackage ?
[22:47] <james_w> because it's less likely to get you really stuck
[22:47] <james_w> poolie, yes
[22:47] <barry> poolie: i'm not sure i have a good enough sense of what to add there for this scenario
[22:49] <poolie> ok, so what are we going to do on this topic, beyond this meeting?
[22:49] <poolie> just reaffirm that that story is important?
[22:50] <poolie> perhaps james and/or myself should go over those pages with mvo and see where the problems are?
[22:50] <barry> we should make sure mvo comes to the user feedback session at uds so we can mine this topic more
[22:50] <james_w> barry, +1
[22:50] <barry> poolie: yes, that would be great, but i think f2f @ uds will be the most productive
[22:51] <james_w> to me this reaffirms the importance of having a good patch handling story, and speed of bzr+LP
[22:51] <barry> james_w: big +1 to both of those
[22:51] <poolie> right
[22:51] <barry> so i'll contact mvo and invite him to the session.  i'm sure he'll be happy to join us
[22:52] <barry> anything else on this topic?
[22:52] <poolie> perhaps we can have footnote-like links to bugs from the udd doc pages, pointing to ways they could be better
[22:52] <poolie> i think that's it for me
[22:53] <barry> good idea.  i have a place for those i think
[22:54] <barry> [TOPIC] AOB
[22:54] <MootBot> New Topic:  AOB
[22:54] <barry> anybody have anything not on the agenda?
[22:54] <barry> going once...
[22:54] <james_w> I think we are missing the one thing that we want to fix first
[22:55] <poolie> that'd be a good recurring item to add
[22:55] <poolie> any nominations for most-wanted bug?
[22:55] <barry> agreed.  i'll add that to the ongoing agenda
[22:56] <barry> watch file support?
[22:56] <james_w> +1, it's fairly small, easy and well-contained, and will have a big usability win
[22:56] <barry> (though i don't see a bug open on that yet)
[22:56] <barry> cool.  i'll open a bug and see if i can put together a branch
[22:56] <james_w> then we can move on to something larger next meeting :-)
[22:57] <barry> [ACTION] barry to open bug for watch file support
[22:57] <MootBot> ACTION received:  barry to open bug for watch file support
[22:57] <james_w> bug 295274
[22:57] <barry> ah, it's on bzr-builddeb not udd
[22:58] <james_w> feel free to add a udd task
[22:58] <barry> +1
[22:58] <barry> so, if there's nothing else.  meet again in 2 weeks?  (that'll be right before uds so we can do last minute planning)
[22:59] <poolie> wfm
[22:59] <slangasek> sure
[23:00] <barry> #endmeeting
[23:00] <MootBot> Meeting finished at 17:00.
[23:00] <barry> thanks everyone.  see you in 2 weeks
[23:00] <slangasek> thanks :)
[23:00] <poolie> oh, btw, i'll be away the week after uds, which would be the 2nd meeting from now
[23:01] <poolie> i'll ask someone else from bzr to come to this in my place
[23:01] <barry> poolie: k.  flacoste i do think we need to sort out who will be the launchpad stakeholder.  if not rockstar, then thumper?  if not him, then you?
[23:02]  * barry -> dinner
[23:02] <flacoste> barry: i'll talk to thumper
[23:02] <barry> flacoste: thanks
[23:02] <barry> just let me know
[23:02] <james_w> thanks everyone
[23:03] <flacoste> see you around