12:05:33 #startmeeting 12:05:33 Meeting started Thu Feb 26 12:05:33 2015 UTC. The chair is tigert. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:05:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:05:53 Any agenda set, or let's improv (I have a draft idea)? 12:05:56 # topic Gluster website and connection with the community 12:06:11 please do if you want 12:06:17 lets not make the bot the big issue here 12:06:27 please share your idea 12:07:21 alright... I was thinking of fist talking about the landing page here & the technical part of it, then move on to the connection it establishes with other portals? 12:07:23 (don't write too long lines or irc will chop the end off :) 12:07:53 uh oh, what's the limit? (my client is okay with ~50 words) 12:08:00 ok, what I wanted to touch also, is the "backend" being the community activity 12:08:11 I guess that is a good limit 12:08:28 if you write several lines worth it chops the end 12:08:40 but you can mostly tell it from the context anyway that something is missing 12:09:12 tigert: heh, anyways... 12:09:16 yeah 12:09:24 does the bot support subtopics? 12:09:32 https://wiki.debian.org/MeetBot 12:09:55 #info this adds a line to the minutes 12:10:04 everything else is not logged I guess 12:10:47 #topic landing page 12:10:47 cool, I'm familiar with meetbot - would be okay now! 12:11:03 but lets go with the front page 12:11:10 you had some thoughts for that? 12:11:18 tigert: the build system that's there now, you figure we can move to client-side only code? 12:11:31 instead of needing to generate the static site? 12:11:47 I don't think the technology is the big culprit 12:11:53 the reason we have the middleman-based thing 12:12:11 I was thinking on the line of using github to host & gh-pages to stage the sites 12:12:12 is that we try to have something common within our community web efforts we do in my team 12:12:22 completely clientside code will make it a breeze 12:12:28 but you need to have the content there anyway? 12:12:31 what would we be missing? 12:13:01 what would client side solve? 12:13:07 tigert: managing a github fork shouldn't be trouble, no? 12:13:22 explain a bit what would that mean in practice 12:13:26 tigert: 1. readily demoable/stages pages 12:13:33 2. no build environment setup 12:13:43 3. easy bugs for the newbies to fix 12:14:00 4. less development overhead 12:14:24 5. wider group of developer finding the repo familiar to contribute to 12:14:29 being the top ones 12:14:37 #idea client-side pages 12:15:27 so hmm, 12:15:29 #info GitHub's gh-pages as web-page staging platform https://pages.github.com/ 12:15:41 (good to do the #info stuff, yeah) 12:16:06 how would you do the content? 12:16:07 yeah, just as bullet points (it gets tricky to traverse through the entire log :P) 12:16:12 some markup in the git module? 12:16:27 no, plain HTML/CSS/JS you write... 12:16:39 then if pushed to gh-pages branch, github will host it 12:16:54 hchiramm: ping? 12:17:05 (many do actually host their websites from there) 12:17:15 Debloper: yeah 12:17:18 easy to add CNAMEs as well, works like charm. 12:17:18 JustinClift, pong 12:17:25 Debloper: what kind of content would you have on the front page? 12:17:30 tigert: maybe I didn't get the question 12:17:38 hchiramm: you wanted to point out something with the the website posts? 12:17:39 tigert: oh, sorry :P 12:18:06 tigert: well, I was thinking of 3-4 scrollable sections on the landing page 12:18:12 I sent a mail to gluster-infra 12:18:34 1st section, the big GlusterFS wordmark, logo & catchphrase - and an invite to explore further 12:18:35 tigert, old articles from Niels blog is getting pulled to our social networking sites 12:18:50 hchiramm: eep 12:19:19 hchiramm: I reset the feed since I suspected something in the plugin settings was wrong 12:19:29 hchiramm: did it re-pull everything? 12:19:43 scroll down, and you get the basic pitch of what's the goal of GlusterFS project (scalable distributed NAS with commodity hw) 12:19:52 you have quite a chained automation there? :P 12:20:13 sorry got disconnectde 12:20:32 hchiramm: did it re-pull everything? 12:20:37 tigert, I think currrent feed url is the default one I believe - I mean without any tag 12:20:53 so it synced all other articles from ndevos's blog 12:21:02 and the call that we're a foss community 12:21:11 ok, I am sorry if I messed it up :/ 12:21:41 third would be listing our presence, to follow on social media (as in where all to find/join us) 12:21:44 http://fpaste.org/190805/14249522 tigert 12:21:48 huh? 12:22:16 hold on 12:22:33 I am getting confused and distracted since I am trying to hold a meeting here at the same time 12:22:34 fourth is the listing of our portals: docs, code etc. for further involvements 12:22:47 hchiramm: is something broken that requires action? 12:23:02 Debloper, please wait 12:23:03 hchiramm: we have a website meeting going here now :P 12:23:12 tigert, I understand .. 12:23:13 so lets hold this for a sec 12:23:18 I figure that's a #gluster channel content :P 12:23:44 the log will be interesting :D 12:23:46 discussing it anywhere stops the meeting since I need to read it 12:23:55 yeah, screw the log for now 12:24:11 tigert: take your time, and we'll get back maybe - if that's urgent 12:24:19 hchiramm: so are you talking about the blog.gluster.org stuff? 12:24:30 not really 12:24:30 look at this url 12:24:34 https://www.facebook.com/GlusterInc 12:24:35 hchiramm: or the content in my glustermm-tigert site? 12:24:50 #endmeeting 12:24:51 ah right 12:25:01 Debloper: ok 12:25:12 Debloper: yeah, sorry 12:25:36 no worries 12:26:10 I should've also been a bit more objective here... (may be with the contents pre-written, than writing them now) 12:26:33 Debloper: it's a start :) 12:26:38 tigert: :) 12:26:45 btw, you need to call the endmeeting 12:26:52 #endmeeting