19:03:08 <catherineD> #startmeeting refstack
19:03:09 <openstack> Meeting started Tue Mar 28 19:03:08 2017 UTC and is due to finish in 60 minutes.  The chair is catherineD. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:03:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:03:13 <openstack> The meeting name has been set to 'refstack'
19:03:34 <pvaneck> o/
19:03:50 <mguiney> o/
19:03:50 <catherineD> hi everyone ,  sorry I started the meeting at the wrong channel
19:04:18 <mguiney> it happens!
19:04:38 <catherineD> #link meeting agenda and notes,  https://etherpad.openstack.org/p/refstack-meeting-17-03-28
19:04:56 <catherineD> yup start the meeting at the openstack-channel :-)
19:06:14 <catherineD> let's start ..
19:06:33 <catherineD> #topic      Emergency RefStack site update made last Friday ( Mar 24, 2017 )
19:06:37 <sslypushenko_> o/
19:06:49 <catherineD> sslypushenko_: hello
19:07:53 <catherineD> so last week we found that there is an OpenID change in user name (replacing space with dot) that affected RefStack  ...
19:08:34 <catherineD> thanks to pvaneck: the issue was handle quickly ...
19:09:26 <mguiney> nice! good job pvaneck
19:09:32 <catherineD> also thanks to sslypushenko_:  merged the code quickly so we could make  update to the website on Friday
19:09:35 <pvaneck> yea, doubt many people were affected
19:09:36 <luzC> o/
19:10:12 <pvaneck> just happened to affect both catherine and I hah
19:10:12 <sslypushenko_> catherineD:  I'm at your service :)
19:10:35 <catherineD> sslypushenko_: thank you very much!
19:11:01 <catherineD> The affect is that I suddenly see none of my data as if the data was lost ...
19:11:11 <catherineD> losing data in never a good thing ...
19:12:19 <catherineD> I want to mention the issue here so the team know about that incase some one else would see the error . but the issue is fixed now
19:12:40 <catherineD> again thank pvaneck: for the quick fix ...
19:12:47 <catherineD> moving on ...
19:13:01 <catherineD> #topic Displaying RefStack documentation
19:13:51 <catherineD> A quick summary on last week's agreement
19:14:40 <catherineD> There are 2 types of documents for RefStack 1) RefStack project document 2) RefStack user (test & upload data) document
19:15:13 <catherineD> it was decided last week that type 1 doc will be published to the OpenStack doc website
19:15:31 <catherineD> type 2 doc (RefStack user doc) will be published at the RefStack website
19:16:06 <sslypushenko_> Sounds good to me
19:16:40 <catherineD> and we understand that tools for type 2 doc will be oneoff developed by RefStack
19:17:22 <catherineD> so for the tools to host the doc at RefStack site
19:17:46 <catherineD> pvaneck: is investigating ...
19:18:00 <catherineD> pvaneck: any update
19:18:15 <pvaneck> http://refstack.mybluemix.net/#/about a sample of what it might look like with rsts converted to html, then placed on about page
19:20:03 <mguiney> Nice! looks really good
19:20:09 <catherineD> pvaneck: is docutils used ?
19:20:27 <luzC> pvaneck: it looks good :)
19:21:08 <pvaneck> catherineD: yes, i used docutils to give a full fledged html file for each rst, then only keep the body contents
19:21:23 <catherineD> pvaneck: that is great !
19:21:33 <pvaneck> just the body contents are desired
19:21:57 <catherineD> yes it looks nice ...
19:22:26 <catherineD> how hard is it to include a content table ?
19:22:58 <pvaneck> the nav bar is essentially a content table
19:24:08 <catherineD> so instead of having the tabs we can replacing those with a content table with links  ..  I expect we would have more links and the tabs maybe too busy ... but it looks good now
19:24:13 <pvaneck> unless you'd prefer somehting like this: https://kubernetes.io/docs/getting-started-guides/ with the links on the side
19:25:23 <catherineD> Personally I like that (the kubernetes doc ..)..
19:25:29 <sslypushenko_> +1
19:25:37 <catherineD> how about everyone else?
19:25:53 <luzC> +1
19:25:58 <mguiney> +1
19:26:03 <sslypushenko_> This style is pretty coomon
19:26:07 <pvaneck> sure, can change it
19:26:38 <catherineD> pvaneck:  that is great ..thanks!
19:26:49 <catherineD> I think we finally getting there ...
19:27:17 <mguiney> \o/
19:27:37 <catherineD> alright let's move on ...
19:28:14 <catherineD> for hosting the project doc at the openstack doc site ...
19:28:30 <catherineD> I think luzC: pretty much have the patches to do so ..
19:29:02 <catherineD> we just need to decide on the content ...
19:30:10 <catherineD> for me, I do not mind just published all RefStack rst doc on the OpenStack site  .. that is we will have duplicate doc displace on both side but since the source is the same .. I really do not mind ...
19:31:04 <catherineD> your thoughts?
19:31:20 <luzC> I agree
19:31:31 <luzC> publish it as it is
19:31:39 <mguiney> +1
19:31:40 <catherineD> luzC: yea
19:32:55 <catherineD> any other discussion on this topic ?
19:34:14 <catherineD> alright moving on ...
19:34:26 <catherineD> #topic Update existing certified data with the verified flag
19:34:37 <catherineD> mguiney: any update?
19:35:42 <mguiney> yep! chris (who does not appear to be in today bc of travel) had me abandon the patch, because it is not a built-in part of refstack
19:36:00 <catherineD> ?
19:36:07 <mguiney> rather a tool that works on a spreadsheet that is external
19:36:38 <mguiney> i do have it on github, and can link that if anyone wants to test, but that is the current state of the project
19:37:48 <catherineD> we can look at the tools but since these touch the RefStack db ... we think it would be better to go throught the review process ..
19:38:38 <catherineD> pvaneck: luzC: sslypushenko_: your thoughts?
19:38:58 <mguiney> ah ok. I can ping him and ask, then
19:39:06 <sslypushenko_> +1 for having it on gerrit
19:39:25 <mguiney> your point about the review process is a good point. I can always just reactivate the patch in the meantime
19:39:47 <pvaneck> yea, can use it for review
19:39:49 <mguiney> but it does deal more with the data spreadsheet than with refstack's internal db
19:40:17 <catherineD> I do not mind the spreadsheet part to be reveal ...
19:40:40 <catherineD> reveal -- > reviewed ...
19:41:10 <catherineD> I meant we do not need to review the spreadsheet part ... because to me that is just the source of data ...
19:41:39 <catherineD> but as soon as you call the RefStack API to update the RefStack db ... that is what we need to review ..
19:41:55 <mguiney> yes of course, and data can be pulled from any sheet with the same type of data
19:42:26 <mguiney> i will un-abandon that for the time being, then, and ping chris to confirm
19:42:37 <catherineD> and we do not care the format of the spreadsheet ..
19:43:09 <catherineD> as said the spreadsheet is just the source of data ..
19:43:30 <catherineD> so have you get  to the point where you call the RefStack API?
19:44:25 <mguiney> i have not. that would be used to update the status of the results, correct?
19:44:41 <mguiney> aka, to make sure that there are no newer results?
19:45:02 <catherineD> I agree with Chris that the tools to manipulate the spreadhseet does not need to be reviewed.
19:46:42 <catherineD> So Chris has a list of RefStack links.  Those are the verified data ...
19:47:59 <catherineD> we want to identify those links in RefStack and update the field field to "true" ( verified data ).
19:48:25 <mguiney> ok, that made sense to me as well, which was why i was a bit confused.
19:48:39 <mguiney> that makes sense, thank you
19:49:01 <catherineD> mguiney: we can have separated meeting to go in more detail with you ..
19:49:19 <mguiney> sounds good, thank you
19:49:49 <catherineD> mguiney: np .. just let me know when you are ready ... we can walk you thru what needed to be done ..
19:50:48 <mguiney> I am ready whenever you have time, I definitely want to get this straightened out so that I can get a patch pushed :)
19:51:28 <catherineD> mguiney: alright let me ping you off line about a meeting ...
19:51:42 <catherineD> moving on ...
19:51:54 <catherineD> #topic Pending reviews
19:52:08 <catherineD> #link     Spec for adding RefStack docs to the website natively (  https://review.openstack.org/#/c/437175/ )
19:52:57 <catherineD> mguiney: do you mind update the spec describing the 2 types of documents and the location to publish them as we discuss here ?
19:53:43 <mguiney> can do, was planning on updating after meeting
19:53:58 <catherineD> mguiney: Thank you
19:54:09 <catherineD> #link     Change doc references from DefCore to Interop Working Group  (  https://review.openstack.org/#/c/390881/  )
19:54:25 <rockyg> oops  I think I missed the meeting :-(
19:54:32 <catherineD> luzC: I guess we still waiting for DefCore repository to move to the new one
19:54:57 <catherineD> rockyg: hello
19:55:03 <luzC> yes, plus it is in merge conflict, so I'll take a look
19:55:16 <luzC> rockyg: hi :)
19:55:34 <catherineD> luzC: maybe just wait until they move and then do it all at one time :-)
19:55:48 * rockyg waves to everyone
19:56:02 <luzC> that's true, I'll waity
19:56:07 <luzC> *wait
19:56:22 <catherineD> moving on ..
19:56:26 <catherineD> #link     Add scripts for running refstack-client in docker (  https://review.openstack.org/#/c/430701/  )
19:56:40 <sslypushenko_> I will update patch soon
19:56:49 <catherineD> sslypushenko_: I still can not get this to work for me but luzC: got it ...
19:57:08 <catherineD> I need to debug my env
19:57:21 <catherineD> sslypushenko_: I will wait for the new update then?
19:57:35 <sslypushenko_> catherineD:  yeap
19:57:41 <catherineD> great ... thx
19:57:54 <catherineD> #link  (WIP) Adding refstack to openstack-projects.html (  https://review.openstack.org/#/c/446615/ )
19:57:55 <sslypushenko_> I hope next version should work
19:59:00 <catherineD> luzC: now we have decided to host the doc at 2 places so these patches would really help us to publish at the OpenStack doc site ..
19:59:46 <luzC> yes, I'll remove the WIP
20:00:00 <catherineD> luzC: +1
20:00:25 <catherineD> thank you everyone !
20:00:32 <catherineD> we need to end the meeting now ...
20:00:38 <catherineD> bye!
20:00:43 <mguiney> have a good day!
20:00:49 <catherineD> #endmeeting