Tuesday, 2015-07-07

*** woodster_ has quit IRC01:01
openstackgerritwuhao proposed openstack/api-wg: Add description of pagination parameters  https://review.openstack.org/19074301:50
openstackgerritwuhao proposed openstack/api-wg: Add description of pagination parameters  https://review.openstack.org/19074301:58
*** e0ne has joined #openstack-api05:22
*** gmann has quit IRC05:33
*** terrylhowe has quit IRC05:37
*** e0ne has quit IRC05:44
*** ig0r_ has joined #openstack-api05:52
*** ig0r__ has quit IRC05:55
*** gmann has joined #openstack-api06:19
*** fifieldt has joined #openstack-api06:43
*** e0ne has joined #openstack-api06:57
*** e0ne has quit IRC07:04
*** cdent has joined #openstack-api07:33
*** e0ne has joined #openstack-api07:36
*** fzdarsky has joined #openstack-api07:47
*** e0ne is now known as e0ne_08:01
*** lucasagomes has joined #openstack-api08:02
*** e0ne_ is now known as e0ne08:03
*** e0ne is now known as e0ne_09:11
*** e0ne_ is now known as e0ne09:24
*** e0ne is now known as e0ne_10:07
*** e0ne_ is now known as e0ne10:21
*** lucasagomes is now known as lucas-hungry11:01
*** fzdarsky is now known as fzdarsky|lunch11:05
*** e0ne is now known as e0ne_11:25
*** e0ne_ is now known as e0ne11:45
*** lucas-hungry is now known as lucasagomes12:07
*** terrylhowe has joined #openstack-api12:16
*** fzdarsky|lunch is now known as fzdarsky12:23
*** terrylhowe has left #openstack-api12:25
*** e0ne is now known as e0ne_13:37
*** e0ne_ is now known as e0ne13:39
*** annegentle has joined #openstack-api13:42
openstackgerritKen'ichi Ohmichi proposed openstack/api-wg: Add generic name of each project for terms  https://review.openstack.org/19691813:47
*** annegentle has quit IRC13:57
*** sigmavirus24_awa is now known as sigmavirus2413:57
*** annegentle has joined #openstack-api14:02
*** annegentle has quit IRC14:07
*** annegentle has joined #openstack-api14:32
*** woodster_ has joined #openstack-api14:39
*** annegentle has quit IRC14:43
*** annegentle has joined #openstack-api15:04
*** Apoorva has joined #openstack-api15:06
*** annegentle has quit IRC15:13
*** e0ne is now known as e0ne_15:16
*** annegentle has joined #openstack-api15:21
*** e0ne_ is now known as e0ne15:26
*** cdent has quit IRC15:28
*** annegentle has quit IRC15:56
*** salv-orlando has joined #openstack-api15:58
salv-orlandohi people. I've noticed many folks are not putting APIImpact on the commit message for specs defining new APIs. Should I ask to add this tag or should it be put only on the code patches?16:00
elmikoi think it's nice to have on specs, assuming that the author(s) want to engage the wg16:01
elmikoby the time it gets to a code patch, it would be difficult to re-architect the api if things don't make sense16:02
ryansbDefinitely ask. It could save them rewriting some code16:02
*** annegentle has joined #openstack-api16:03
*** annegentle has quit IRC16:10
salv-orlandothanks ryansb & elmiko - I will unleash my pedantry on those specs16:25
sigmavirus24salv-orlando: pedantry++16:26
*** fzdarsky has quit IRC16:31
*** e0ne has quit IRC16:33
* ryansb braces self for pedantry16:34
*** annegentle has joined #openstack-api16:40
*** annegentle has quit IRC16:44
*** lucasagomes is now known as lucas-dinner16:52
*** salv-orl_ has joined #openstack-api17:08
*** e0ne has joined #openstack-api17:09
*** salv-orlando has quit IRC17:11
*** e0ne is now known as e0ne_17:18
*** e0ne_ is now known as e0ne17:21
*** e0ne is now known as e0ne_17:26
*** e0ne_ is now known as e0ne17:27
*** annegentle has joined #openstack-api17:30
*** e0ne is now known as e0ne_17:33
*** annegentle has quit IRC17:35
*** e0ne_ is now known as e0ne17:39
*** e0ne is now known as e0ne_18:17
*** salv-orl_ has quit IRC18:22
*** Apoorva has quit IRC18:33
*** e0ne_ is now known as e0ne18:39
*** Apoorva has joined #openstack-api18:42
*** salv-orlando has joined #openstack-api18:49
*** e0ne has quit IRC18:50
*** annegentle has joined #openstack-api18:56
*** e0ne has joined #openstack-api19:54
*** lucas-dinner has quit IRC20:08
sigmavirus24So someone was trying to tell me that version negotiation for an API via the headers is harmful for devices trying to interact with APIs from the Internet of Things20:13
sigmavirus24And they refuse to explain their reasoning20:13
elmikohuh20:14
sigmavirus24Yeah20:14
sigmavirus24I am tempted to say they're just making it up because they like URLs with the version in it better for subjective reasons20:14
elmikoso... version negotiation only through rest calls? that seems worse20:15
elmikoLOL20:15
sigmavirus24elmiko: more along the lines of how GitHub does it20:15
sigmavirus24Accept: application/vnd.github.v3.full+json20:15
sigmavirus24That's what github3.py sends by default to get any user-text as plain-text, html, and the original text submitted20:15
elmikooh, using content type?20:15
sigmavirus24Yeah20:15
sigmavirus24Like the client chooses the version if it knows it and sends that in the headers20:16
sigmavirus24Doing that kind of stuff with middleware in Ruby with Sinatra is pretty easy20:16
elmikoyea, i'm scratching my head as to why using the headers is bad20:17
elmikoor really worse than bad, "harmful" ;)20:17
*** fzdarsky has joined #openstack-api20:18
*** salv-orlando has quit IRC20:20
*** lucasagomes has joined #openstack-api20:21
elmikoetoews: heads up, i won't be able to make the cross project meeting tonight.20:23
etoewsk. i'll be around.20:25
sigmavirus24elmiko: yeah I don't get their argument20:25
sigmavirus24but they haven't really made one tbh20:25
* sigmavirus24 shrugs20:26
sigmavirus24no biggie20:26
etoewselmiko: i'll actually be around for the late meeting tomorrow. you?20:26
elmikoetoews: yea i'll be there20:26
elmikoactually, you just reminded me to update the agenda ;)20:27
etoews\o/20:27
etoewsi put a couple of things in there already20:27
elmikocool, i think we need to talk over a few of the finer points on the 5xx stuff20:27
*** lucasagomes has quit IRC20:27
ryansbIoT can't send headers?20:27
ryansb???20:27
sigmavirus24ryansb: apparently20:28
elmikolol20:28
sigmavirus24ryansb: IoT can't do crypto either20:28
sigmavirus24so20:28
sigmavirus24I care not about it20:28
sigmavirus24something something TLS is bad something something20:28
ryansboh, right.20:28
sigmavirus24Call me when the IoT is secure and usable. Kthnxbai20:29
elmikoha!20:29
ryansbI didn't want any privacy anyway. My internet-enabled appliances should multicast everything and CC the NSA20:29
sigmavirus24Am I a bad person for wanting everything to use HTTPS?20:29
sigmavirus24ryansb: the NSA is a BCC sir20:29
sigmavirus24or20:29
sigmavirus24reverse-BCC?20:29
elmikosigmavirus24: no, no you are not20:29
ryansbsigmavirus24: ok, I want lots of things to use https, but there's some stuff that I don't think needs to be.20:30
sigmavirus24ryansb: I don't care if it needs to be =P20:30
ryansbExample: my blog. It has no auth, no comments, nothing. I don't mind allowing http20:30
etoewsseptember 14! https://letsencrypt.org/2015/06/16/lets-encrypt-launch-schedule.html20:31
elmikobut ryansb, what if someone mitm's your blog to post inaccurate info?20:31
elmiko;)20:31
ryansbelmiko: then they deserve it, I guess. If my readers need verified content they could use https20:32
sigmavirus24ryansb: and if people don't want passive observers to know they're reading your blog?20:32
ryansbthen they can still choose to use https20:32
elmikook, fair20:32
ryansbI'm just saying it isn't required for a large portion of what the average user does20:33
ryansbe.g. get weather forecasts, peruse headlines about pop stars20:33
ryansbplay candy crush20:33
* ryansb has no idea what people do on the internet20:34
sigmavirus24lol20:34
sigmavirus24facebook and candy crush are probably two of the biggest20:34
sigmavirus24for what it's wroth20:34
sigmavirus24I do think news outlets should use HSTS20:34
sigmavirus24New York Times, etc. should all have HSTS because modifying that content can really screw up things20:34
sigmavirus24Those are trusted resources for facts but the facts are transmitted in plain-text20:35
ryansbYeah, good point20:35
ryansbor we could teach everyone to use GPG20:35
ryansbthat'd go swimmingly20:35
sigmavirus24we can't even teach technical people to use GPG20:35
elmikolol20:35
elmikoneeds more signing parties20:35
ryansb...I'm not sure that's what it needs.20:36
elmikohehe20:36
elmikodidn't you see the matrix, dance parties make everything better ;)20:36
ryansblol20:36
*** fzdarsky has quit IRC20:37
*** e0ne has quit IRC20:44
sigmavirus24requests team had a signing party with our downstream liasons at PyCon20:49
sigmavirus24Well20:49
sigmavirus24requests team - Kenneth20:49
sigmavirus24Cory and I handle all security reports and fies20:50
sigmavirus24*fixes20:50
ryansboh, nice20:51
sigmavirus24ryansb: oh you didn't realize openstack has a requests core developer working on it?20:56
ryansbI didn't, I suppose. I was saying "nice" about the "having a keysigning at PyCon" part though20:57
ryansbhaving a requests dev aboard certainly isn't bad20:57
sigmavirus24for you20:58
sigmavirus24there's a reason I stay away from the clients a lot of the time20:59
elmikolol20:59
sigmavirus24openstacksdk is the only client I'd like to work on but I don't have time for it20:59
sigmavirus24If the alcohol didn't kill me, I'm pretty sure the project teams would kill me for refactoring how they abuse requests21:00
sigmavirus24The tamest reaction I had to https://github.com/openstack/python-glanceclient/blob/master/glanceclient/common/https.py was http://i.imgur.com/z4zwFXw.gifv and https://review.openstack.org/#/c/189344/ is going to make things all better21:01
ryansbwait, did they do...cert validation themselves?21:02
sigmavirus24yep21:03
ryansb(╯°□°)╯︵┻━┻21:03
sigmavirus24YEP21:03
ryansbthat ain't right man, that just ain't right21:03
sigmavirus24I mean21:03
sigmavirus24I don't see a way in which it was broken21:03
sigmavirus24So that's good at least, right?21:03
sigmavirus24It's just frustrating that they did that21:04
ryansbwe should rename #openstack-api to #http-curmudgeons21:04
sigmavirus24no21:05
sigmavirus24That's #python-requests21:05
ryansbA++21:05
sigmavirus24Also, if you want to complain about flake8, ##python-code-quality21:05
sigmavirus24(Because I'm the core developer of flake8)21:06
sigmavirus24code-quality mailing list at python.org is something I run and is generally the better place to complain about linters and such21:06
sigmavirus24It's the mailing list for pylint, pep8, mccabe, pyflakes, flake8, and other stuff21:06
sigmavirus24I might have a problem21:07
ryansband the problem is too many linters21:07
sigmavirus24lol21:09
stevelleah but who lints the linters21:09
sigmavirus24stevelle: so flake8 runs against itself21:09
sigmavirus24pylint does the same21:10
stevellechickens guarding the henhouse!21:10
* stevelle dons tinfoil21:10
sigmavirus24I've been thinking of running pylint against flake8 in the gate just for shits and giggles21:10
*** annegentle has quit IRC21:18
*** salv-orlando has joined #openstack-api21:22
*** salv-orlando has quit IRC21:29
*** salv-orlando has joined #openstack-api21:30
ryansblol21:30
ryansbthat'd be top notch21:30
sigmavirus24I'd probably want to drink myself to death while trying to configure pylint to just work21:35
*** annegentle has joined #openstack-api21:57
*** Apoorva has quit IRC22:26
*** annegentle has quit IRC22:29
*** annegentle has joined #openstack-api23:12
*** salv-orlando has quit IRC23:26
*** Apoorva has joined #openstack-api23:27
*** Apoorva has quit IRC23:31
*** annegentle has quit IRC23:34

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!