Wednesday, 2016-02-17

*** galstrom_zzz is now known as galstrom00:15
*** galstrom is now known as galstrom_zzz00:24
*** galstrom_zzz is now known as galstrom01:30
*** galstrom is now known as galstrom_zzz01:57
*** FallenPegasus has joined #openstack-defcore02:11
*** FallenPegasus has quit IRC02:11
*** edmondsw has quit IRC02:12
*** cjvolzka has joined #openstack-defcore02:19
*** cjvolzka has quit IRC02:19
*** markvoelker has quit IRC02:27
*** markvoelker has joined #openstack-defcore03:27
*** rob__ has quit IRC03:31
*** markvoelker has quit IRC03:33
*** rob__ has joined #openstack-defcore03:36
*** rob__ has quit IRC03:50
*** rob__ has joined #openstack-defcore04:03
*** galstrom_zzz is now known as galstrom04:20
*** galstrom is now known as galstrom_zzz04:35
*** markvoelker has joined #openstack-defcore05:29
*** markvoelker has quit IRC05:33
-openstackstatus- NOTICE: A problem with the mirror used for CI jobs in the rax-iad region has been corrected. Please recheck changes that recently failed jobs on nodes in rax-iad.06:48
*** markvoelker has joined #openstack-defcore07:30
*** markvoelker has quit IRC07:34
*** pcaruana has joined #openstack-defcore08:42
*** pilgrimstack has joined #openstack-defcore08:56
*** markvoelker has joined #openstack-defcore09:31
*** markvoelker has quit IRC09:35
*** catherineD has quit IRC09:52
*** gema has quit IRC09:52
*** Fred_Li has quit IRC09:52
*** lifeless has quit IRC09:52
*** purp has quit IRC09:52
*** reed has quit IRC09:52
*** blogan has quit IRC09:52
*** purp has joined #openstack-defcore09:52
*** gema has joined #openstack-defcore09:52
*** reed has joined #openstack-defcore09:52
*** lifeless has joined #openstack-defcore09:53
*** catherineD has joined #openstack-defcore09:53
*** blogan has joined #openstack-defcore09:53
*** Fred_Li has joined #openstack-defcore10:00
*** johnthetubaguy has quit IRC10:03
*** johnthetubaguy has joined #openstack-defcore10:05
*** gema has quit IRC10:08
*** mordred has quit IRC10:08
*** gema has joined #openstack-defcore10:08
*** mordred has joined #openstack-defcore10:09
*** hockeynut has quit IRC10:49
*** VanL has quit IRC10:49
*** hockeynut has joined #openstack-defcore10:49
*** VanL has joined #openstack-defcore10:54
*** hockeynut has quit IRC11:04
*** Fred_Li has quit IRC11:04
*** blogan has quit IRC11:04
*** reed has quit IRC11:04
*** hockeynut has joined #openstack-defcore11:04
*** blogan has joined #openstack-defcore11:04
*** reed has joined #openstack-defcore11:07
*** Fred_Li has joined #openstack-defcore11:19
*** markvoelker has joined #openstack-defcore11:31
*** markvoelker has quit IRC11:36
*** reed has quit IRC11:39
*** reed has joined #openstack-defcore11:40
*** pilgrimstack has quit IRC11:50
*** galstrom_zzz has quit IRC11:50
*** notmyname has quit IRC11:50
*** hurricanerix has quit IRC11:50
*** galstrom_zzz has joined #openstack-defcore11:50
*** pilgrimstack has joined #openstack-defcore11:50
*** hurricanerix has joined #openstack-defcore11:51
*** notmyname has joined #openstack-defcore11:51
*** openstack has joined #openstack-defcore12:04
*** thingee has quit IRC12:07
*** hogepodge has quit IRC12:07
*** Fred_Li has quit IRC12:24
*** rob__ has quit IRC12:24
*** kbaikov has quit IRC12:24
*** jroll has quit IRC12:24
*** rob__ has joined #openstack-defcore12:25
*** jroll has joined #openstack-defcore12:25
*** kbaikov has joined #openstack-defcore12:25
*** kbaikov has quit IRC12:25
*** kbaikov has joined #openstack-defcore12:25
*** hockeynut has quit IRC12:32
*** openstackgerrit_ has quit IRC12:32
*** openstackgerrit has quit IRC12:32
*** eglute has quit IRC12:32
*** eglute_s has joined #openstack-defcore12:32
*** openstackgerrit has joined #openstack-defcore12:33
*** openstackgerrit_ has joined #openstack-defcore12:34
*** hockeynut has joined #openstack-defcore12:36
*** Fred_Li has joined #openstack-defcore12:47
*** cjvolzka has joined #openstack-defcore13:27
*** cjvolzka has quit IRC13:29
*** markvoelker has joined #openstack-defcore13:29
*** cjvolzka has joined #openstack-defcore13:31
*** dhellmann has quit IRC13:44
*** dhellmann has joined #openstack-defcore13:47
*** cjvolzka has quit IRC13:47
*** cjvolzka has joined #openstack-defcore13:50
*** cjvolzka has quit IRC13:50
*** thingee has joined #openstack-defcore14:00
*** hogepodge has joined #openstack-defcore14:00
*** edmondsw has joined #openstack-defcore14:04
*** cjvolzka has joined #openstack-defcore14:13
*** flaper87 has quit IRC14:54
*** flaper87 has joined #openstack-defcore14:54
*** dhellmann has quit IRC15:05
*** dhellmann has joined #openstack-defcore15:05
*** mfisher_ora has joined #openstack-defcore15:11
*** galstrom_zzz is now known as galstrom15:50
*** dwalleck has joined #openstack-defcore15:53
*** ChanServ sets mode: +v purp15:54
gemawhere is the meeting today?16:00
gemanevermind found it16:01
*** pcaruana has quit IRC16:35
catherineDo/16:59
eglute_so/16:59
catherineDtopic is vendor information ..17:00
eglute_sok17:00
catherineDso in RefStack vendor will be of type private, official , and few other internal vendor types17:01
eglute_sok17:01
catherineDthe intention is if a vendor is of type official ... anyone (including aninymous users) can list vendors17:01
markvoelkerwith you so far17:02
catherineDthe question is what information should be list  ... or more important what information should not be listed for anonymous users17:02
catherineDshould we list ...creator? date created? date updated?17:03
catherineDof course all information will be listed for the users belong to the vendor17:03
eglute_sis this for results?17:03
eglute_sor vendor info?17:03
catherineDno this is for vendor info17:03
eglute_si think updated is good17:04
eglute_sthe date updated17:04
catherineDhow about create date?17:04
*** dwalleck has quit IRC17:04
eglute_si think both date created and date updated are good17:05
markvoelkerI don't see any real harm in including it, but I'm also not sure I see a real use case for anyone needing it.17:05
eglute_sif i had to pick one, i would pick updated17:05
catherineDmarkvoelker: the vendor admin may need those info for internal checking ..17:05
eglute_sright, i think both dates would show if there is any activity for that particular vendor17:06
catherineDfor vendor users .. all info will be listed ...17:06
markvoelkerOh, wait...let me make sure we're talking about the same thing here. =)17:06
catherineDthe linited info is only applicable to anonyous user17:06
markvoelkerWhen you say "vendor info" here, you're talking about information pertaining to the vendor entity?  Like, say, the company name, link to it's website, that sort of thing?17:07
markvoelkerOr you're talking about information about users affiliated with that vendor? (assuming that a vendor admin is making the call here)17:07
catherineDmarkvoelker: yes vendor infor only not user of the vendor17:08
catherineDbut on vendor infor ... we log we created the vendor (creator) and the date the vendor is created ..17:08
markvoelkerOk.  So in that case I guess I'm still not sure of the use case for fetching either of those by an anonymous user really.17:09
catherineDs/we log we /we log who/17:09
markvoelkerIt again seems like something that a refstack admin/foundation staff might care about17:09
markvoelkerBut not really the causual user17:09
markvoelkerSo I'm sort of inclined to err on the side of keeping it private until we have a real use case for exposing it.17:10
* markvoelker may just have a tin foil hat on today17:10
catherineDmarkvoelker: the thoughts is RefStack will create one more tab next the the "community results" tab today with a list of vendors17:10
catherineDor the question should be : should we even need this tab?17:11
eglute_si think it is ok to list vendors for anonymous users, as well as updated info. Unless Vendors can choose to be invisible or not listed?17:11
markvoelkercatherineD: yeah, that's fine.  But I'm not sure why that tab would show things like the date the vendor entity was created in RefStack.  Or why it should show the last time the vendor's info was updated17:11
catherineDmarkvoelker: that is my question :-)17:11
eglute_sit is definitely NOT a high priority right now for us17:12
markvoelkerThe company name, website, stuff like that seems fine...the date it was created/updated in refstack doesn't seem useful17:12
catherineDI can see vendor admin need that ..17:12
catherineDbut not other users17:12
markvoelker+117:12
eglute_s+117:13
catherineDmarkvoelker: more important ... is are these data (create date, creator, update date) private or public17:13
markvoelkerMy general line of thought is: unless there's a use case for making it public, leave it private.17:13
catherineDfor UI we can limited the data display ... but for REST API should we also limit those data by user roles (foundation, vendor user ...)17:14
eglute_screator should be private17:14
eglute_sdates, dont matter much i think17:14
markvoelkercatherineD: limiting by user roles makes sense.  I'll leave the question of whether it's a seperate API or a different response to the same API based on role to you. =)17:15
catherineDmarkvoelker: that is my thought ... data privacy is important ... it is better to be conservative ... but that means more work for RefStack at the API level.... but I think we should be careful with data17:15
markvoelkercatherineD: agreed17:15
eglute_s+117:15
catherineDI guess that we agree that creator is private17:16
eglute_s+117:16
catherineDcreate date and update date can be public but not useful?17:16
eglute_swell, updated i think is useful, but not high priority17:17
markvoelkercatherineD: I'd just leave them private, following that "leave it private unless there's a good reason to expose it" mantra17:17
eglute_ssame with created.17:17
eglute_si am ok with either approach17:17
catherineDmarkvoelker: ++++17:17
eglute_sdates show how "stale" something is, so i like that17:17
catherineDok I got it ... Thank you so much for staying overtime for this discussion17:18
markvoelkerMaybe it would be helpful to draw up an etherpad or a spec listing out what you're thinking about exposing to each role?  That way we could discuss specifics more easily.17:18
eglute_sany time. glad to help17:18
catherineDmarkvoelker: yes we have specs .. I will do some clean up  ...17:19
markvoelkereglute_s: I guess staleness depends on the data though.  E.g. if the info being updated is stuff like company name and website...well, a company like IBM isn't likely to need to do that much, so "staleness" doesn't really indicate anything. =)17:19
eglute_svery true!17:19
markvoelkerThat's why I'm thinking it'd be easier to discuss specifics.17:19
eglute_sagreed17:19
catherineDfor users https://review.openstack.org/#/c/277313/17:19
catherineDfor vendor https://review.openstack.org/#/c/274837/17:20
catherineDwill ping you for review after I clean up per our discussion today17:20
eglute_sthanks catherineD!17:20
markvoelkercatherineD: that'd be great.  Thanks!17:20
catherineDThank you sooooooo much!17:20
catherineDbye17:20
eglute_sbye!17:21
*** hockeynut has quit IRC17:35
*** eglute_s has quit IRC17:35
*** eglute has joined #openstack-defcore17:39
*** hockeynut has joined #openstack-defcore17:39
*** edmondsw has quit IRC18:00
*** edmondsw has joined #openstack-defcore18:45
*** galstrom is now known as galstrom_zzz21:23
*** galstrom_zzz is now known as galstrom21:25
*** galstrom is now known as galstrom_zzz22:31
*** edmondsw has quit IRC23:48

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