14:00:33 <flaper87> #startmeeting Glance
14:00:35 <flaper87> #topic Agenda
14:00:37 <flaper87> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
14:00:38 <openstack> Meeting started Thu Dec 10 14:00:33 2015 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:39 <kragniz> o/
14:00:39 <flaper87> Not a very long agenda, yet. HOW'S EVERYONE DOING? :D :D :D
14:00:39 <avarner_> o/
14:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:41 <nikhil_k> o/
14:00:41 <abhishekk> 0/
14:00:42 <openstack> The meeting name has been set to 'glance'
14:00:48 <jokke_> o/
14:01:15 <sigmavirus24> flaper87: still sick, but y'know :P
14:01:19 <ativelkov> o/
14:01:23 <flaper87> let's give some more minutes for folks to join
14:01:30 <flaper87> sigmavirus24: :( get well soon!
14:01:35 <flaper87> btw, happy to have you back :D
14:01:43 <sigmavirus24> I'm happy to be back
14:02:14 <kragniz> sigmavirus24: welcome back!
14:02:26 <flaper87> ok, let's  get started. I still have a crappy internet connection so, expect some lag from me :D
14:02:32 <flaper87> tihs time is not my brain's fault
14:02:47 <sigmavirus24> flaper87: sure ;)
14:02:55 <flaper87> :P
14:02:59 <flaper87> #topic Teams Updates
14:03:12 <flaper87> artifacts nikhil ativelkov
14:03:19 <rosmaita> o/
14:03:24 <nikhil> Hi
14:03:35 <ativelkov> so, we have two specs on review now
14:03:50 <ativelkov> one is for glance v3 -> glare v0.1
14:04:10 <flaper87> ativelkov: I put the v3 -> 0.1 in the specs prio list
14:04:14 <ativelkov> another one is a public API description, i.e. the one which addresses the defcore and API-wg concerns
14:04:32 <ativelkov> flaper87: I saw that, thanks!
14:04:56 <flaper87> awesome, I think I commented on the other one but was just a quick comment. We'll need API-WG feedback on that one but yeah, lets get it reviewed
14:04:57 <ativelkov> Actually, that one was written by mfedosin, but he is on PTO, so I may answer any questions on that
14:04:59 <jokke_> ativelkov: do you have idea about timeline? When would you need the review powar on majority parts of this work?
14:05:43 <ativelkov> jokke_: the migration patch is already submitted. it's still WiP, but I expect it to complete today or tomorrow
14:05:57 <flaper87> #chair nikhil
14:05:57 <openstack> Current chairs: flaper87 nikhil
14:05:59 <jokke_> oh it's on that good shape ... cool
14:05:59 <rosmaita> ativelkov: i left come comments on your spec last night
14:06:08 <flaper87> nikhil: in case disappear :D
14:06:10 <ativelkov> #link https://review.openstack.org/#/c/255274/
14:06:19 <nikhil> flaper87: ah ok, sure
14:06:32 <ativelkov> rosmaita: thanks! Didn't check it yet, will have some cycles for that later today
14:06:53 <flaper87> from a review pov, right now the focus should be on the migration spec and patches implementing that spec
14:06:56 <kairat> o/
14:07:01 <flaper87> not saying we shouldn't review the other one
14:07:05 <ativelkov> I just want to quickly sync some major decision points on that migration
14:07:09 <rosmaita> ativelkov: nothing major, just some clarifications
14:07:22 <flaper87> shooot
14:07:33 <ativelkov> what should be the default glare port? I suggest 8383, but open for other proposals
14:07:42 <flaper87> 9393
14:07:48 <flaper87> I guess that's what you meant
14:07:55 <ativelkov> oh, yeah, 9393, sure
14:08:17 <nikhil> +1
14:08:19 <ativelkov> And what should be the keystone service name and type? I propose type='artifact' and name='glare', but feel free to suggest something else
14:08:22 <jokke_> 9393 would be my preference as well
14:08:22 <flaper87> I think jokke_ checked it and it was free
14:08:26 <flaper87> or was it mfedosin
14:08:26 <sabari> o/
14:08:34 <jokke_> it was at least during summit still
14:08:40 <sigmavirus24> why not 9293 or 9392 just to be funny?
14:08:53 <nikhil> sorry to bring this up late but do everyone feel ok with name "glare"?
14:09:02 <jokke_> sigmavirus24: because this is serious business and we're not funny here ;)
14:09:02 <sigmavirus24> ooo why not randomly bind to one of those two?
14:09:13 * sigmavirus24 shouldnt' be allowed in meetings
14:09:15 <flaper87> I do feel ok with glare
14:09:19 <sigmavirus24> nikhil: I'm meh
14:09:19 <rosmaita> nikhil: i am +1 on Glare
14:09:22 <nikhil> I think as a part of initial phase it seems ok but when you bring up keystone name it sounds a bit weird
14:09:22 <jokke_> I liked it
14:09:27 <sigmavirus24> I don't want glance glaring at everyone but whatever
14:09:38 <nikhil> I would prefer the name "Art"
14:09:46 <sigmavirus24> nikhil: Arti
14:09:49 <flaper87> ativelkov: re service catalog, I think that's fine but please sync with sdague or some keystone folks on that
14:09:55 <nikhil> prolly should send that to ML
14:10:03 <nikhil> sigmavirus24: yeah, that's safer
14:10:06 <nikhil> :_
14:10:08 <nikhil> :)
14:10:19 <sigmavirus24> nikhil: makes Artifacts sound like your neighbor who is super friend "Hey Arti!"
14:10:29 <flaper87> lol
14:10:30 <ativelkov> yeah, nikhil, thanks, ML is a good idea
14:10:31 * sigmavirus24 still wonders why flaper87 invited him back to the core team :P
14:10:32 <flaper87> ok, let's move on
14:10:34 <jokke_> sigmavirus24: but they are!
14:10:43 <sigmavirus24> jokke_: I know!
14:10:46 <flaper87> sigmavirus24: I'm already regrettningit
14:10:48 <flaper87> :P
14:10:49 <nikhil> sigmavirus24: haha, arti in hindi means workship
14:10:58 <jokke_> flaper87: we still have time to block that?
14:11:01 <sigmavirus24> nikhil: all the better :)
14:11:08 <nikhil> :)
14:11:09 <sigmavirus24> jokke_: you already +1'd it :P
14:11:16 <flaper87> ok ok, let's move on
14:11:29 <jokke_> sigmavirus24: I know, but I have friends (believe or not) :P
14:11:30 <flaper87> what else on artifacts?
14:11:45 <flaper87> jokke_: sigmavirus24 friendly notice: shut up!
14:11:47 <flaper87> :P
14:11:49 <ativelkov> well, nothing new for now
14:12:02 <nikhil> flaper87: there are tiny things to be aware of
14:12:09 <nikhil> logged here:
14:12:10 <flaper87> nikhil: shoot
14:12:11 <nikhil> #link http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2015/glance_artifacts_sub_team.2015-12-07-14.04.html
14:12:13 <nikhil> done
14:12:21 <flaper87> okidoki, I'll read through
14:12:24 <flaper87> thanks for the heads up
14:12:36 <nikhil> np
14:12:38 <flaper87> Drivers updates:
14:12:58 <flaper87> Let me start with saying that I've added the reviews priorities for specs to the drivers meetting's agenda. To all drivers and people interested in providing feedback, please, take a look here:
14:13:00 <flaper87> #link https://etherpad.openstack.org/p/glance-drivers-meeting-agenda
14:13:02 <flaper87> Also, if you think your spec should be a priority, let me (or any of the drivers) know and we'll evaluate the urgency based on the current load.
14:13:04 <flaper87> Image Import process broken down into sub-tasks (flaper87)
14:13:06 <flaper87> #link https://review.openstack.org/#/c/232371/
14:13:08 <flaper87> There have been more comments and updates on the spec. If you haven't followed-up on it, this would be a good time to re-read it as I believe we're getting closer to an almost-ready status.
14:13:10 <flaper87> In addition to this, we've broken the spec down into several work items and we'll keep expanding the list as new items/parts are agreed on. This is fairly new and it happened yday, I believe. If you're looking forward to contribute to this work, I'd highly recommend you to go through this list, provide some feedback on the work items and take them :)
14:13:12 <flaper87> Note that there are some dependencies in this work items so please, respect that.
14:13:14 <flaper87> To all reviewers, whenever you're reviewing patches for this work, make sure you have the spec openned right next to the patch you're reviewing :D
14:13:54 <flaper87> questions? concerns? feedback?
14:14:21 <jokke_> can we agree that bikeshed is called bikeshed?
14:14:38 <rosmaita> jokke_: it's now called "stage"
14:14:43 <flaper87> jokke_: no, that actually changed in PS8
14:14:45 <flaper87> :D
14:14:54 <rosmaita> but we can change it back
14:15:00 <jokke_> ++
14:15:01 <flaper87> rosmaita: sshhh
14:15:02 <rosmaita> if there's popular demand
14:15:06 <rosmaita> sorry
14:15:06 <flaper87> don't you know sigmavirus24 is back ?
14:15:13 <flaper87> don't get him started
14:15:19 <nikhil> stage sounds good to me
14:15:20 <rosmaita> sigmavirus24 wants to call it the "yak pen"
14:15:31 <nikhil> but not sure if it's a noun or verb
14:15:32 <flaper87> lol
14:15:38 <rosmaita> nikhil: exactly!
14:15:45 <rosmaita> it's both
14:15:47 <nikhil> :)
14:15:48 * sigmavirus24 is being  quiet
14:15:50 <nikhil> thought so
14:15:51 <flaper87> BAM! mindblown
14:15:52 <jokke_> then we can call the working dir in the worker code "backstage" ... sounds good to me :)
14:16:06 <flaper87> jokke_: LOOOOOOL, love that
14:16:06 <nikhil> green room?
14:16:08 <flaper87> hahahahhaha
14:16:12 <sigmavirus24> are tasks stage hands now?
14:16:16 <flaper87> ok ok, let's move on
14:16:25 <flaper87> Cross project updates
14:16:29 <flaper87> nikhil: floor is yours
14:16:38 <nikhil> So, that one got feedback
14:16:40 <flaper87> so many updates, this is good
14:16:42 <nikhil> and there are two things
14:16:52 <nikhil> it's hard to get the lib on list of exceptions
14:16:57 <nikhil> lib == glance_store
14:17:06 <nikhil> as things are we will see when we hit a situation
14:17:18 <nikhil> as the process is sorta complexly variable
14:17:31 <nikhil> but overall I like the idea of governance tag
14:17:39 <nikhil> and about to add +1 to that idea
14:18:03 <nikhil> overall the spec ( https://review.openstack.org/#/c/226157 ) is in good shape
14:18:40 <flaper87> mmhh, but that's not a tag, though. it's a x-proj spec. The tag exists already and it's called assert:follows-standard-deprecation
14:18:45 * nikhil done. was thinking wrongly, spec was  linked.
14:18:49 <flaper87> unless they are talking about a new tag and I missed that part
14:18:59 <flaper87> nikhil: thanks for the updated
14:19:02 <jokke_> no I think flaper87 you are correct
14:19:06 <nikhil> I don't know which tag they are talking about
14:19:12 <nikhil> it's a comment from doug
14:19:30 <flaper87> ah, I probably missed that comment
14:19:34 <jokke_> I think that plan will be reverted next cycle again (branchless clients and libs) because all the hell will break loose but lets see
14:19:35 <flaper87> I'll read through
14:19:51 <flaper87> ok, let's move on
14:20:07 <flaper87> #topic New home for release schedule (flaper87)
14:20:09 <flaper87> Just a heads up that the release schedule home has changed. It's not longer in the wiki page but in the openstack docs url. Here's the link:
14:20:11 <flaper87> #link http://docs.openstack.org/releases/schedules/mitaka.html
14:20:13 <flaper87> I'll be updating that schedule to add Glance's timelines and schedule activities.
14:20:49 <flaper87> questions? feedback? Just wanted to make  sure you were aware of this
14:21:12 * flaper87 wants a per-project .ics with scheduled activities just like we have fro meetings
14:21:20 * flaper87 will propose that
14:21:26 <jokke_> ++
14:21:43 <flaper87> ok, moving on
14:21:45 <jokke_> that would be super handy
14:21:54 <flaper87> #topic glance_store's drivers deprecation (flaper87)
14:21:56 <flaper87> #link http://lists.openstack.org/pipermail/openstack-dev/2015-December/081966.html
14:21:58 <flaper87> I sent that email out a couple of minutes ago. I don't expect folks to have read it already but I'd like to encourage everyone to do so. Feedback would be awesome as that's going to make some people sad/mad and it'd be great to have the community on the same page so that we can provide the best feedback to consumers of the library and, of course, stand behind on the decisions made.
14:22:31 <nikhil> I noticed swift wasn't in the list of glance-maint
14:22:56 <flaper87> nikhil: I knew you would be one of them :D
14:23:00 <nikhil> and I just found out the explanation
14:23:03 <jokke_> ;)
14:23:17 <flaper87> hope the reasoning makes sense but I'm happy to discuss that further
14:23:18 <kragniz> so the plan is to run all glance functional tests against master glance_store?
14:23:26 <kragniz> (I think that's a good idea)
14:23:32 <flaper87> yeah
14:23:43 <nikhil> master & stable!?
14:23:45 <flaper87> pretty much the same way cinder does w/ third-party drivers
14:23:50 <flaper87> nikhil: yup
14:23:58 <kragniz> flaper87: sounds good
14:24:46 <flaper87> happy to discuss this now if folks have read the email already or we can add it back to next week's meeting due to the short notice
14:24:56 <flaper87> or both
14:24:59 <flaper87> :P
14:25:22 <nikhil> next meeting sounds good to me to be able to ponder on things
14:25:29 <flaper87> ++
14:25:31 <flaper87> ok, I'll add it there
14:25:35 <rosmaita> wow, that's some email!
14:25:38 <kragniz> I'm good with the rest of it
14:25:45 <nikhil> yeah, I thought so too
14:25:53 <kragniz> what happens if we don't get people to volunteer?
14:26:01 <flaper87> okidoki, let's move on :D
14:26:12 <flaper87> kragniz: the email says, we'll remove that driver
14:26:15 <sabari> me too, looks good and wasn't a surprise since we have been talking about 3rd party CI for sometime
14:26:24 <nikhil> kragniz: we will! or the drivers go in a cycle or two :)
14:26:29 <ativelkov> I'll try asking Mirantis's ceph team if they want to volunteer maintaining the ceph driver
14:26:40 <kragniz> cool, in O
14:26:42 <flaper87> ativelkov: sounds awesome!
14:26:43 <nikhil> kragniz: passive reach out to get more open source upstream friendly
14:27:10 <nikhil> more people*
14:27:14 <flaper87> ok, let's move one
14:27:23 <flaper87> #topic Release notes
14:27:27 <flaper87> jokke_: was that you?
14:27:30 <jokke_> yeah
14:27:49 <flaper87> floor is yours
14:27:52 <jokke_> so quick heads up for people. We moved to utilize reno for release notes
14:28:01 <flaper87> w0000000h000000
14:28:04 <jokke_> #link http://docs.openstack.org/developer/reno/
14:28:36 <kragniz> all our projects have now moved, correct?
14:28:42 <kragniz> (store + client)
14:28:42 <jokke_> tons of small files ahead so please look into the documentation and prepare yourselves that Liberty and Mitaka+ will require those
14:28:52 <flaper87> I think yes, glance_store was the last one to join
14:28:56 <kragniz> cool
14:29:06 <jokke_> so lets start including those release notes into the changes, please
14:29:30 <nikhil> so searchlight team added some good guidelines for when and how to add notes
14:29:32 <nikhil> #link https://github.com/openstack/searchlight/blob/master/doc/source/feature-requests-bugs.rst#release-notes
14:29:36 <flaper87> jokke_:anything reviewers should keep in mind ?
14:29:50 <flaper87> nikhil: ++ thanks
14:29:55 <flaper87> we should probably have that as well
14:29:59 <flaper87> in the contirbuting docs
14:30:10 <nikhil> besides there's this:
14:30:15 <nikhil> #link http://docs.openstack.org/project-team-guide/release-management.html#how-to-add-new-release-notes
14:30:17 <kragniz> shouldn't these be somewhere common and link to that?
14:30:19 <flaper87> contributing*
14:30:28 <jokke_> flaper87: nothing special comes up to my mind atm. good idea ofc check the output of the rel notes job to verify that they actyally get included
14:30:33 <nikhil> kragniz: that was project specific
14:30:41 <nikhil> openstack specific is the link above
14:31:07 <flaper87> awesome stuff! glad to see the rel-notes process improved
14:31:09 <jokke_> other than that lets get that going so we can later on agree requiring those and providing - votes for not including them
14:31:46 <flaper87> ++
14:31:51 <kragniz> one thing to remember is who these notes are for: end users and deployers
14:32:03 <flaper87> sounds good to me! Any questions? objections?
14:32:05 <jokke_> that's it from me
14:32:22 <flaper87> kragniz: ++
14:32:25 <nikhil> more descriptive the better (explicit vs implicit)
14:32:26 <kragniz> extra noise in release notes makes things harder for them to pick out important things
14:32:41 <jokke_> kragniz: specially service & client
14:32:52 <nikhil> yeah, but good meta-info clears that confusion too!
14:32:59 <jokke_> store is bit there and there ... they are more for us ;)
14:33:02 <kragniz> (for example, end users don't care about us refactoring tests)
14:33:03 * flaper87 likes that kragniz always brings that up as a nice reminder
14:33:21 <kragniz> flaper87: if I say it enough times!
14:33:46 <sigmavirus24> kragniz: jokke_ we should make a gate check for those release notes
14:34:02 <flaper87> kragniz: re tests, that's debeatable. Some consumers of these libraries use the tests shipped in the library
14:34:05 <sigmavirus24> We should automate that kind of stuff instead of relying on reviewers to remember to -1 things
14:34:07 <kragniz> sigmavirus24: what would it check?
14:34:16 <jokke_> kragniz: but deployer does care if we refactor the test to validate that it still tests their use-case
14:34:16 <sigmavirus24> kragniz: that the commit includes release notes?
14:34:46 <flaper87> but I agree "fixed a typo" is not useful
14:35:25 <jokke_> sigmavirus24: let's get the people used to that first and then we can see how we gate it fitering those typofixes etc. out
14:35:40 <kragniz> sigmavirus24: do you mean for all commits?
14:35:46 <kragniz> flaper87: okay, I guess so
14:35:50 <sigmavirus24> kragniz: gate checks can be skipped
14:36:03 <sigmavirus24> It would probably take some tuning but we could certainly do it
14:36:49 <flaper87> (unless the typo is in a function name)
14:37:03 <jokke_> as said lets think that _after_ we get the community used to this (and everyone having at least their first rel note merged)
14:37:09 <kragniz> sigmavirus24: it's an interesting idea
14:37:21 <kragniz> but yeah, we should get used to the process first
14:37:39 <flaper87> anything else on this topic?
14:37:44 <kragniz> that's all from me
14:37:57 <jokke_> ditto
14:38:07 <flaper87> coolio
14:38:13 <flaper87> #topic Open Discussion
14:38:24 <flaper87> nikhil: ?
14:38:36 <nikhil> so this one
14:38:47 <nikhil> #link https://review.openstack.org/#/c/243348
14:38:54 <flaper87> cli stuff, right?
14:39:09 <nikhil> yes, sorry. the title is:
14:39:10 <nikhil> Deprecate individual CLIs in favour of OSC
14:39:26 <nikhil> It's gaining good traction
14:39:30 <nikhil> lots of +2s
14:39:34 <flaper87> it'd be great totget people's feedback on that spec
14:39:35 <nikhil> and I overall like the idea
14:39:44 * flaper87 +2'd it and jokke_ is going to hate him for that
14:39:44 <nikhil> I have been thinking about one thing though
14:39:55 <jokke_> thanks nikhil
14:40:05 <jokke_> flaper87: that's your call ... will -1 it myself ;)
14:40:21 <kragniz> I'm +1 on that
14:40:29 <kragniz> it's a pain to use all the different clis
14:40:31 <flaper87> nikhil: what's that?
14:40:33 <nikhil> besides the import stuff
14:40:39 <nikhil> the location management stuff
14:41:07 <nikhil> I find it hard to believe it's out there on the stage with configuration etc at the glance backend
14:41:24 <flaper87> I don't think anything will happen until N (or  even O) but t's good to keep in mind that's likely going to happen
14:41:33 <nikhil> the UX is pretty bad and am not sure if it's interop fussy topic
14:42:25 <flaper87> nikhil: that's related to OSC, right?
14:42:29 <nikhil> anyways, it just seems like a bad idea to port that to OSC
14:42:33 <nikhil> yes
14:42:37 <flaper87> it'd be great to bring all this feedback to the m-l and the OSC team
14:42:51 <jokke_> as said before I'm happy to spin off glancecli project forking the last version of cli we ship if we're going to this direction :P
14:43:01 <nikhil> I have always been of the opinion that location management is for the case where operators trust their users (private cloud)
14:43:05 <flaper87> nikhil: I'm curious to know how all that will work on OSC
14:43:29 <nikhil> exactly
14:43:41 <sigmavirus24> jokke_:  you're welcome to do that :P
14:43:49 <nikhil> so, I am not sure at this point if we can remove the glanceclient CLI 100%
14:43:50 <flaper87> cool, do let me know when you have some extra feedback
14:44:00 <flaper87> erm, some answers for that
14:44:07 <flaper87> that was a hell of a freaudian slip
14:44:29 <kragniz> nikhil: I don't think people want to remove it right now
14:44:30 <flaper87> nikhil: perhaps a new thread on the m-l about this?
14:44:46 <flaper87> kragniz: I think nikhil meant "entirely and not when that will happen
14:44:46 <kragniz> nikhil: more tell people that the recommended thing is OSC
14:44:46 <nikhil> ok, noting it down
14:45:13 <nikhil> flaper87: right, that's what I meant
14:45:21 <flaper87> the spec says it'll stay for 2 more cycles after it's marked as deprecated
14:45:37 <kragniz> flaper87: okay
14:45:58 * kragniz only skimmed the spec, sorry :(
14:46:02 <flaper87> ok, one more heads up from me: The spec freeze date is approaching so, spec writeers, please, I beg you ,address comments in a timely manner so we can work with you on getting those merged
14:46:49 <flaper87> There have been reviews to specs and quite some lag on addressing those feedbacks
14:46:52 <jokke_> well the spec proposes clearly 2 cycles to remove native clients
14:47:01 <flaper87> I've mentioned this in the email I sent to the m-l last night
14:47:27 <flaper87> jokke_: you have 2 cycles to fork the CLI </troll>
14:47:57 <flaper87> anything else? anyone?
14:48:34 <nikhil> I want to propose a video conference for artifacts.
14:48:58 <flaper87> nikhil: to demo it or to talk about the new API ?
14:48:58 <nikhil> sometime before the holidays (depending on your locality)
14:49:07 * sigmavirus24 has to cut out early
14:49:17 <nikhil> and after 16th dec (when Mike is back and settled hopefully)
14:49:26 <ativelkov> Sounds good to me
14:49:33 <nikhil> flaper87: no, to increase momentum and get early feedback
14:49:35 <ativelkov> Mike will be back on Monday, I think
14:50:01 <nikhil> anything that we need to talk about it actually
14:50:06 <flaper87> I'm happy to join and schedule it. WE can use my bluejeans bridge as we did for the import process
14:50:13 <nikhil> I can propose some agenda and send out etherpad
14:50:17 <ativelkov> nikhil: I like the idea. Need to try to invite the guys from community app catalog
14:50:25 <nikhil> ativelkov: +1
14:50:35 <flaper87> nikhil: please do, I'll setup the meeting on bluejeans so we can record it and what not
14:50:54 <jokke_> oh yeah ... FYI I'll be out of picture between Tue 15th and Tue 5th of Jan
14:50:58 <nikhil> great
14:51:10 <nikhil> oh noes
14:51:19 <nikhil> flaper87: I will sync offline when I have something ready
14:51:21 <jokke_> so don't expect reviews, actions, e-mails, replies etc. from me during that time :D
14:52:09 <flaper87> jokke_ please, enjoy your holidays. If we see an email, review, rant, joke from you on that period of time, we'll revoke your -2 rights and just leave you with +1 and +2
14:52:22 <nikhil> I hope we have another one later in the cycle when things are more through the gate and jokke_ will be there then
14:52:26 <flaper87> actually, just +1
14:52:33 <flaper87> and no +2
14:52:36 <flaper87> :P
14:52:40 <flaper87> +A*
14:52:42 <jokke_> flaper87: ninja reverts ... you won't even notice them :P
14:52:53 <rosmaita> jokke_: +1 on enjoying your holidays
14:53:17 <jokke_> flaper87: I promise to stay more within the Holiday scope than you did
14:53:21 <jokke_> :)
14:53:30 <flaper87> touche
14:53:39 <flaper87> damnit, ppl always use that against me
14:54:05 <flaper87> ok,if there's nothing else, we can call it a meeting
14:54:29 <flaper87> thanks everyone! see y'all next week.
14:54:33 <nikhil> thanks all!
14:54:35 <flaper87> #endmeeting