15:02:33 #startmeeting Community Meeting 2017-08-30 15:02:33 Meeting started Wed Aug 30 15:02:33 2017 UTC. The chair is kshlm. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:33 The meeting name has been set to 'community_meeting_2017-08-30' 15:02:39 Welcome everyone! 15:02:51 Who all are in today? 15:02:52 hello @kshlm 15:03:02 Hey Snowman_ :) 15:03:04 me is here 15:03:14 * kkeithley is here 15:03:14 oh hi 15:03:28 Hey kkeithley & amye 15:03:28 hello all 15:03:34 zoom. :) 15:03:45 * ivan_rossi lurking 15:04:05 * ndevos _o/ 15:04:07 oh, it's ivan_rossi! Hi! 15:04:23 hi all! 15:05:02 Nice turnout today! 15:05:07 Welcome again everyone. 15:05:19 o/ 15:05:31 I'll wait 1 more minute and start. 15:05:42 We have a couple of topics on the meeting pad already. 15:06:05 If anyone else has topics they want to discuss please add them to the pad. 15:07:11 Okay let's start. 15:07:24 #topic Docs updates and long-term strategy 15:07:37 This one's mine. 15:07:48 The floor is yours nigelb 15:07:51 Two announcements that are connected to this which i've sent out. 15:08:06 a) search is working again, but JS dependent. 15:08:22 We place a heavier load onto the RTD servers by making everyone download the search json file. 15:08:29 But it doesn't have old entries anymore. 15:08:37 b) We're setting up a new domain at docs.gluster.org. 15:08:59 This is already up. 15:08:59 The old URLs will continue to work for the forseeable future. They both point to the same thing. 15:09:18 There's some more fixes with the domain change that need to go out like setting canonical URL to docs.gluster.org 15:09:33 That way search engines will always refer to docs.gluster.org 15:09:41 Oh. Okay. 15:09:43 especially useful if somoene puts a clone up on RTD. 15:09:59 (which they have, glusterfs.readthedocs.io is not owned by us) 15:10:03 I'm guessing that shouldn't take long. 15:10:21 (no one would ever fork the documentation for fun :D) 15:10:24 The long term strategy (from infra team point of view) is to own the hosting ourselves. 15:10:51 RTD is an overworked team. We haven't been able to gather much support for issues in the past. 15:11:06 The domain and all these pieces lead to us hosting our docs say a year or so from now. 15:11:29 But this would still be rtd based right? 15:11:37 (or whatever rtd is using) 15:11:47 It will be mkdocs based, but hosted on our servers. 15:11:52 That's step 1. 15:12:00 That will solve *a lot* of problems. 15:12:15 please. :) 15:12:25 Then we have the option of thinking about a different platform. 15:12:34 Right now we can't do anything without breaking URLs. 15:13:03 If we host things ourselves, we have the option of setting 301 redirects and monitoring 404 logs. 15:13:13 None of these options exist right now. 15:13:44 At some point, once things are stable, we'll have that conversation. 15:14:02 But for now, we're working a long-term plan to move out of RTD and host on our own domain. 15:14:32 If there are concerns, please raise them now or get in touch with me via email. 15:14:38 We can figure out how to solve them. 15:14:45 nigelb, Seems to me you've got this all under control :-) 15:15:06 I don't have anything, I'd like to make sure we have google analytics working so that we can see what our most searched for things are. 15:15:11 That is a nice to have and not a concern. 15:15:35 That we can do independent of the move. Ping me tomorrow and I'll figure out what can be done. 15:15:58 Super. I will write you an email because I'm liable to forget. 15:16:00 I remember someone adding a tracking code some where. 15:16:20 yeah, there's a tracking code in either mkdocs.yml or on rtd backend. 15:16:22 It is in there, but there's some tuning we can do for it to make sure it's tracking what's searched for. 15:16:23 Or was that the google webmaster tracking code (I'm not so clear) 15:16:28 Same thing. 15:16:33 Ah okay. 15:16:43 hello 15:16:53 nigelb, This sounds like a good plan to me. 15:16:57 * loadtheacc is here. apologies for tardiness 15:17:14 Excellent. 15:17:25 I'll push on ahead in going ahead. 15:17:39 please do, and let us know if you need more assistance, nigelb 15:17:48 Even if we host docs.gluster.org on our own domain, we will find a way to make sure gluster.readthedocs.io continues to be up to date. 15:17:55 I'm a fan of running things myself, so I'm happy with this. I'll help out wherever I can. 15:18:00 At least for another year. 15:18:12 I don't want users to hit a 404 for as long as I can pull off. 15:18:23 Appreciated 15:18:38 Thanks nigelb! 15:19:03 Over & out from me on this topic 15:19:13 Does anyone have any questions for nigelb? 15:19:27 If not I'll move on to the next topic. 15:19:50 Thanks again nigelb 15:20:04 #topic New website launching soon: gluster.wpengine.com is the current staging URL. 15:20:15 We finnnnally have this ready to go 15:20:15 amye, This is yours 15:20:25 I will change the documentation links to reflect docs.gluster.org 15:20:38 But at this point, we 'll be able to move forward with changing content easily 15:20:48 This replaces www.gluster.org and blog.gluster.org 15:20:59 The intention is to have nearly everything look the same. 15:21:33 I'm planning on putting out a call for volunteers again to help redo content and structure over the next three months, planning to change things by FOSDEM. 15:21:37 Questions? 15:22:05 Looks good. 15:22:36 But I see some minor inconsistencies. 15:22:40 It's WordPress and it'll be hosted on WordPress Engine. They'll take care of updates for core and security. 15:22:58 What I want to know is: do we want to keep glusterweb as an issue tracker? 15:23:25 I was just about to ask where to report bugs. 15:23:25 for things like the inconsistencies, kshlm. Because I want a way to have other people help fix things too. :) 15:23:49 I vote to keep glusterweb around for issues. 15:23:53 I'm perfectly fine with keeping the github issue tracker and note that the code is deprecated 15:24:21 I'll take an action item to add the github issue tracker as 'report a website bug' on the new website. 15:24:37 Can I report them now? 15:24:45 Please do :) 15:24:53 Okay will do. 15:25:16 I'll also need volunteers to help maintain this in case I get hit by a bus, but it'll be easy. 15:25:40 Anything else? 15:25:56 Don't get hit by a bus! 15:26:04 :point_up: 15:26:06 Well yes, but vacation, etc :D 15:26:27 also good documentation for how to maintain the install 15:26:56 DR documentation? 15:26:56 Back to you, kshlm. 15:27:17 DR? There's some tricky bits to how the layout works in here, but not the end of the world. 15:27:29 What is DR? 15:27:35 Disaster Recovery 15:27:41 Oh. Okay. 15:28:05 Yes, that will be helpful as well. WPEngine maintains many many backups for us. 15:28:36 I've used WPEngine in the past. The fact that I can call them up and get things sorted is a huge help in many cases. 15:28:50 It was my best option that I found. :) 15:29:32 I read that a CfVolunteers for content is happening - is that planned or, underway? Sorry, missed a bit of scrollback 15:29:38 * ndevos drops off, ttyl! 15:29:54 sankarshan, Planned. 15:30:13 ah! thank you. 15:30:29 I'll let the group that volunteered for website review be set free and will do a separate CfV for content now that we have something to look at. 15:31:52 I had one more question. Would the new consistent look also be applied to the docs? 15:32:20 I would really _like_ this to happen but I am not sure. I have theming files for the WP instance and colors, etc. 15:32:30 I don't know if rtd supports it, but once we start hosting the docs, it should be consistent with the rest of the gluster websites. 15:32:51 That's what I'd want to find out. nigelb, does RTD support theming? 15:32:56 Kinda? 15:33:03 Basically we have to override everything. 15:33:09 I can't put a theme name and expect it to work. 15:33:23 Hmm. Does that put more load on RTD than is acceptable? 15:33:41 I was thinking it may be easier to wait until after we're hosting it. 15:33:53 docs.gluster.org <-- looks like our website 15:34:02 That's what I was considering. 15:34:07 gluster.readthedocs.io <-- looks vastly different with same content. 15:34:23 amye: suppose that I want to change some content regarding me in the site. Do I have to contact you? 15:34:42 ivan_rossi, go ahead and file a bug in glusterweb on github 15:35:01 Ok, Thx 15:35:09 That's the proposed tracking for that because I'd like to be able to have this go to a group of people, not just me. 15:35:19 Also a ticket is a good way to make sure I remember it. 15:35:36 If you have ideas for what you'd want to see, sky's the limit. 15:35:55 One thing I'd like to implement is 'put yourself on the map' where people can come in and tell us where they're using Gluster and how. 15:36:31 +1 15:36:47 Not that we can do -everything- with WordPress, but we can do a lot. 15:37:18 espresso? 15:37:22 snerk 15:37:39 Sorry, we've wandered off a bit, so any other topics? 15:38:23 Sorry. I wandered off for a bit. 15:38:36 (I did too. :P) 15:39:15 Thanks amye! 15:39:22 Any other topics? 15:39:23 One other cool thing, since we have no other topics, the website can also host forms for us. So if we want to do a survey that's not just the mailing list, we can do that through the main gluster.org site. 15:39:51 Oh. Cool. 15:40:16 So start thinking of what you've always wanted. 15:41:26 Sure thing. 15:41:33 I've got something to share. 15:41:59 We will be doing a demo/presentation on GD2 tomorrow in Bangalore. 15:42:08 Super! Can you record it? 15:42:20 This is mainly aimed at developers, and will be streamed as well. 15:42:34 It will be recoreded too. 15:42:43 If you send me the link, I will publish this out on the social medias. 15:43:16 I'll be sending it out to the mailing lists after we're done. 15:43:25 That works. 15:44:03 The demo is followed by a hackathon. This initial one is internal RH Bangalore. In the future we will involve everyone else. 15:44:26 These hackathons are planned to drive integration effort between GD2 and the rest of GlusterFS. 15:44:32 ++ 15:44:52 We'll provide more details on them, on the lists. 15:45:15 I'm done now. 15:45:21 Thank you kshlm 15:45:27 Anyone else have things to share/discuss? 15:46:13 Shyam and Vijay are in meetings today so that's why none of them, but 3.12 should go out next week. 15:46:27 Probably Tuesday, as I don't want to post things on an American holiday 15:46:49 Yup. Got notifications of the tagging a little while before. 15:46:56 The 3.12 *announcement* will go out? 15:47:07 Attempting to make sure all the builds are done before the announcement. 15:47:10 Correct, kkeithley. 15:47:22 builds are building now 15:47:36 will be done later today 15:47:47 Awesome 15:49:02 Thanks amye & kkeithley 15:49:28 If we have no more topics, I'll end the meeting. 15:49:39 Fedora, CentOS, Ubuntu are done. Started debian, will finish after lunch, plus SuSE 15:50:33 Is there an official docker image? 15:50:58 JoeJulian, https://hub.docker.com/r/gluster/ 15:51:20 We have automated images built on centos and fedora. 15:51:26 +1 15:52:41 Though they need to be updated to the latest releases. 15:54:00 I'm ending the meeting on the count of 3 15:54:13 3! 15:54:25 Thanks for coming in today everyone! 15:54:30 See you all next time. 15:54:35 Thanks kshlm 15:54:46 Hi 15:54:47 The meeting mail weill be sent out tomorrow! 15:54:56 #endmeeting