20:00:01 <suehle> #startmeeting
20:00:01 <zodbot> Meeting started Mon Nov 25 20:00:01 2013 UTC.  The chair is suehle. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:01 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:06 <suehle> #meetingname Fedora marketing
20:00:06 <zodbot> The meeting name has been set to 'fedora_marketing'
20:00:10 <suehle> #topic roll call
20:00:20 <croberts> .fas chrisroberts
20:00:21 <zodbot> croberts: chrisroberts 'Chris Roberts' <croberts@cintrixhosting.com>
20:00:22 <suehle> .time
20:00:24 <zodbot> suehle: 08:00 PM, November 25, 2013
20:00:30 <suehle> Thanks, zodbot! :D
20:00:31 <jzb> .fas jzb
20:00:32 <zodbot> jzb: jzb 'Joe Brockmeier' <jzb@zonker.net> - jzbl 'Denise Gant' <denise2gant@gmail.com>
20:00:37 <mitzie> .fas mitzie
20:00:38 <zodbot> mitzie: mitzie 'Zacharias Mitzelos' <zacharias.mitzelos@gmail.com>
20:00:45 * jzb wonders if there's a way to limit it to just matching "jzb"
20:00:58 <suehle> We could just start calling you Denise.
20:01:05 * roshi is here
20:01:08 <suehle> 743997
20:01:12 <suehle> sigh
20:01:33 <suehle> I don't think I even touched the side of the computer that time.
20:01:42 <roshi> lol
20:02:00 <suehle> #topic Fedora Magazine theme
20:02:51 <suehle> Don't everybody talk at once. :)
20:03:03 <jzb> sorry, multitasking
20:03:24 <mitzie> !
20:03:32 <jzb> so we've been having a conversation about a new theme, and I also raised a question of whether we might consider moving away from WordPress altogether.
20:03:50 <jzb> though I don't know if there's a lot of love for that idea.
20:03:56 <croberts> :P If we are going to stick with Wordpress, maybe we could either get design to help us with a theme, or we could find some nice themses and maybe have a vote for one like we did with the F20 wallpapers
20:04:16 <suehle> Tatica, i.e., design, did make this one
20:04:25 <mitzie> I was trying  new plugins that we could use as slideshows in the magazine at the weekend, tried ~10 and non would work on the specific theme
20:04:35 <roshi> I'm not against moving from WP - but I'm new, and also know the work that can go into a migration
20:05:12 <roshi> how many hits does the magazine get currently? day/week/month
20:05:13 <croberts> roshi: we can handle a migration :)
20:05:38 <mitzie> I wouldn't suggest getting rid of wordpress, as we have many plugins we could use any time we want something specific
20:05:41 <croberts> we did have an addon for that but we disabled it due to it crashing the site
20:05:50 <jzb> mitzie: the problem with plugins
20:05:54 <croberts> but we do get quite a few hits each day when i looked at it last
20:06:00 <jzb> mitzie: 1) they aren't maintained at the same pace as WP
20:06:12 <jzb> mitzie: 2) sometimes they don't play well with other plugins
20:06:27 <jzb> mitzie: 3) they still require the heft of WordPress.
20:06:43 <roshi> well, we also need to consider what kind of extensibility we need
20:07:04 <mitzie> BTW I was able to complete  the migration succesfully to a new gear, (horay!!) But then I deleted the new gear, as we were discussing about a new theme
20:07:04 <jzb> well, the main things we need are 1) ability to publish content, and 2) calendar
20:07:14 <jzb> mitzie: ?
20:07:17 <croberts> roshi: I agree add sit functionality but also keep plugin count low
20:07:18 <roshi> is WP the minimum? or could we do something simple with flask/sinatra/django
20:07:19 <suehle> I thought we enabled stats?I don't see them on the dashbaord.
20:07:27 <jzb> mitzie: you were able to get a medium gear going?
20:07:34 <croberts> sit was meant to be basic*
20:07:48 <roshi> stats crashed things AIUI
20:08:21 <mitzie> yes, upgraded to medium gear, but it was after discussing about the new theme. ANyway I could do it again, and get the med. gear while we decide about the new theme
20:08:36 <jzb> mitzie: yeah... in the interim, we need that regardless.
20:08:44 <mitzie> But it would also require infra to point the domain to the new site
20:08:53 <croberts> suehle: we did have a plugin that tatica found for our stats, but one of the weekends the site crashed and it had to be disabled to get the site fixed.
20:08:59 <mitzie> Ok, I can start it now
20:09:06 <croberts> I was able to fix the site thought :)
20:09:09 <croberts> though*
20:09:20 <roshi> doesn't the openshift instance give some indication as to b/w usage?
20:09:28 * roshi isn't familiar, though it's on his list...
20:09:37 <jzb> roshi: I don't *think* so , but I don't know.
20:09:48 <croberts> roshi: /me checks
20:10:02 <roshi> I know they don't care about bandwidth - but wasn't sure if they would monitor it
20:10:06 <roshi> seems like a basic metric
20:10:18 <croberts> i dont see a spot for it
20:10:22 <jzb> we could spin up a Piwik instance in another gear and use that for stats, if we needed.
20:10:28 <mitzie> So jzb about the question you said earlier, could you bring up some examples of plugins not working with wordpress? I think if we update the wordpress site a few weeks after the update comes out, the new versions of the plugins we a re using will be out as well and we will be ok updating
20:10:34 <croberts> +1 jzb
20:10:55 <roshi> well, I feel like we should have a test-suite for the magazine
20:10:55 <jzb> mitzie: we shouldn't wait weeks to update WP, though. Usually new releases have security updates.
20:11:02 <mitzie> jzb, you mean in another cartidge?
20:11:11 <roshi> then we can test updates to plugins, maybe contribute upstream
20:11:16 <jzb> mitzie: whatever the proper metaphor is :-)
20:11:36 <roshi> anyone here familiar with selenium tests?
20:11:40 <croberts> roshi +1 with openshift we can accomplish this since we have GIT access
20:11:49 <jzb> roshi: do we have bandwidth (people) for that?
20:11:55 <mitzie> true, but while updating, I never met any problems with the plugins
20:12:16 <roshi> I'm fine for writing some basic tests - but it would take time for a full suite for testing WP
20:12:18 <jzb> roshi: I'd love to, and I can get to that if we can create a 28-hour day.
20:12:20 <mitzie> as we use a few of them that are working good. And btw we ould use even less in the new site
20:12:38 <roshi> but something so that we can at least tell if something will break
20:13:22 <croberts> we could create a msql replication between our site and a new test site spun up on another gear
20:13:35 <croberts> so that way data can be passed and be in sync so we can test
20:13:41 <croberts> mysql
20:13:44 <roshi> makes sense
20:14:17 <jzb> if we're going to continue doing WP, we really ought to set it up so we have two gears / whatever running with load-balancing between them.
20:14:37 <roshi> at the minimum - I would say with a test instance as well
20:14:42 <mitzie> yeah jzb, while migrating I added 2 medium gears
20:14:44 <croberts> jzb: that can we setup :)
20:15:00 <jzb> I'm still pretty sure that the site will fall right over the first time we actually hit Hacker News or something, even with a medium gear.
20:15:19 <croberts> with scalabilty we could try a large gear
20:15:21 <mitzie> and if we complete the migration and delete the current small gear we have for the magazine, wecould have 3 medium gears for the new mag gear
20:15:33 <jzb> croberts: we don't have a large gear :-)
20:16:11 <croberts> jzb: well for now we could setup a medium gear with scalabilty if we needed a large gear we would little downtime
20:16:44 <jzb> croberts: OK, well I will leave that to you + mitzie
20:16:53 <jzb> so then the question becomes one of adjusting the theme
20:17:00 <roshi> so, as it stands we want to spin up another gear (at least)
20:17:22 <croberts> roshi: yes for testing/upstream purposes
20:17:25 <mitzie> jzb about the hacker news, I think 3 gears are perfect to handle traffic
20:17:36 <mitzie> *3 medium gears
20:17:43 <jzb> mitzie: you haven't seen a Hacker News flood ;-)
20:17:47 <croberts> :P
20:18:03 <mitzie> ok... :S
20:18:28 <jzb> mitzie: IIRC something like 10K page views an hour
20:18:32 <jzb> back when I was doing RWW.
20:18:58 <mitzie> :S
20:19:00 <roshi> sheesh
20:19:17 <jzb> and I will be a sad panda if we don't hit that occasionally in 2014
20:19:34 <roshi> yeah
20:19:40 <mitzie> roshi, I could start a wordpress site in our openshift account so we could start testing themes I guess
20:19:52 <roshi> that could work mitzie
20:20:10 <croberts> jzb: I am def hoping we hit that in 2014
20:20:14 <roshi> I'll see what kind of time I can devote to magazine stuff
20:20:17 <croberts> we have come along way with the magazine
20:20:35 <mitzie> croberts, true since August
20:21:27 <mitzie> But making a new wordpress site for testing purposes, we will have to delay the migration, as there will be no gears left
20:22:02 <croberts> suehle: is it possible to get funding for an upgrade in openshift to a large gear?
20:22:49 <jzb> croberts: we don't pay for it, per se.
20:22:57 <croberts> true
20:23:04 <jzb> croberts: I can request additional gears, if we really need them.
20:24:10 <mitzie> We could request to have 5-6 total gears, instead of 3 that we have now.. But I think for the time being we a re covered
20:24:14 <mitzie> croberts?
20:25:12 <croberts> i think we should get the test site setup and get the plugins we need and then look at getting more gears
20:25:51 <croberts> mitzie and roshi: if you are going to install another instance of wp can you please install the phpmyadmin cartridge
20:27:27 <mitzie> yeah sure croberts
20:27:53 <slut_tits> Hello
20:28:08 <jzb> croberts, mitzie do you guys have sufficient next steps?
20:28:17 <mitzie> jzb about what?
20:28:41 <croberts> jzb: i can get with him by email/irc to work on getting it setup
20:29:18 <jzb> mitzie: wordpress
20:29:22 <roshi> croberts: why do we want phpmyadmin?
20:29:28 <mitzie> the test site?
20:29:35 <jzb> mitzie: was thinking we might want to move to next topic
20:30:00 <mitzie> agree with roshi here, as the phpmyadmin url can be publicly accessed
20:30:11 <mitzie> it is like: domain.com/phpmyadmin
20:30:22 <roshi> it's a whole new attack vector
20:30:26 <roshi> something else to lock down
20:30:35 <jzb> croberts: do we really need phpmyadmin?
20:30:38 <roshi> where does our data live anyway?
20:30:45 <jzb> roshi: THE CLOUD
20:30:47 <croberts> roshi: true
20:30:49 * jzb couldn't help it.
20:30:53 <roshi> lol
20:31:04 <roshi> ah, so on someone *elses* computer :p
20:31:05 <croberts> mitzie: please dont install phpmyadmin
20:31:26 <mitzie> ok ;)
20:32:16 <roshi> croberts: the httpd logs are in <cartridgename>/logs
20:32:20 <slut_tits> Dip
20:32:26 <slut_tits> Sup
20:32:27 <roshi> so, we can see what kind of traffic we get
20:32:50 <roshi> slut_tits:, is there something we can help you with? This is the Fedora Marketing Meeting
20:32:51 <croberts> roshi: ok thinks i will start to work on a report for that and get it to the marketing team
20:33:02 <roshi> if you have Fedora related questions, #fedora might help
20:33:35 <croberts> I think the reports would be benefical for everyone on marketing/infranstructure to see
20:33:48 <roshi> yeah - but scrub them first
20:33:56 <croberts> +1
20:33:56 <roshi> not sure what gets logged on those instances
20:34:41 <croberts> #action croberts to start working on a report for the Marketing team to see the traffic we are getting for the magazine site
20:35:41 <croberts> I agree with jzb though i think we got off the topic of theme a little :P
20:36:11 <mitzie> so jzb, to wrap it up, I will start the site and make a common admin account and email you guys the pass so we could work on the theme
20:36:30 <croberts> +1 mitzie
20:36:39 <croberts> can you email me the mysql username/password
20:36:48 <croberts> so i can start to work on the replication
20:37:35 <mitzie> sure croberts, altough you could see it by loging in the openshift acc.
20:37:52 <jzb> are we ready to move to release notes, etc.?
20:38:02 <croberts> +1 jzb I think so
20:38:08 <croberts> and trac tickets :)
20:38:26 <jzb> #topic Tasks for Fedora 20
20:38:46 <jzb> suehle: maybe you have to do the topic?
20:38:59 <suehle> #chair jzb
20:38:59 <zodbot> Current chairs: jzb suehle
20:39:08 <jzb> anyway... I've started the Fedora 20 release announcement
20:39:13 <jzb> https://fedoraproject.org/wiki/F20_release_announcement
20:39:34 <jzb> mostly copied from the beta announcement at this point, but will be sprucing up the rest of it tomorrow, I hope.
20:40:15 <jzb> we also have "One Page Release Notes"
20:40:20 <jzb> http://fedorapeople.org/groups/schedule/f-20/f-20-marketing-tasks.html
20:40:30 <jzb> in conjunction with Docs, I believe?
20:40:58 <jzb> are we done with screen shots?
20:41:09 <jzb> I seem to recall a lot of activity on that earlier this month.
20:41:19 * roshi has been slacking on the screenshots
20:41:55 * jzb wags finger at roshi
20:42:02 <croberts> roshi: i most of mine uploaded
20:42:03 <jzb> roshi: is there a lot left to do?
20:42:03 <slut_tits> Oh
20:42:05 <croberts> :P
20:42:09 <roshi> sorry, I'm a bad person
20:42:16 <roshi> I don't even know
20:42:23 <roshi> hence, "been slacking"
20:42:25 <roshi> lol
20:42:41 <croberts> suehle: do you have a link to the release screenshot wiki page, so i can start moving from the trac ticket to the wiki?
20:42:46 <suehle> Yes, Docs handles RN
20:43:03 <suehle> croberts, uno momento
20:43:22 <suehle> https://fedoraproject.org/wiki/F20_screenshots_library
20:44:16 <jzb> suehle: anything here that's missing?http://fedorapeople.org/groups/schedule/f-20/f-20-marketing-tasks.html
20:44:24 <jzb> or rather, anything that's missing from that schedule?
20:44:29 <jzb> that we should be prepping for?
20:45:24 <suehle> That should pretty much take care of it. When we're finished with those two things, we can ping John Terrill about the press release
20:45:26 <roshi> reading those charts is strangely hard for me
20:45:41 <roshi> I have to think about it way more than I would think I would
20:45:55 <jzb> roshi: I don't see why, that's cutting-edge mid-90s formatting there.
20:46:10 * roshi is just slow he guesses
20:46:22 <jzb> any other f20 stuff we need to discuss?
20:46:52 <suehle> #topic 10th anniversary
20:47:28 <jzb> we should have a second 10th anniversary piece coming up shortly. I think croberts was working on that.
20:47:33 <jzb> croberts: how's that going?
20:47:41 <jzb> did you need any help there?
20:48:44 <croberts> jzb: its coming along at a slower than i wanted pace with things that have come up, i could use some help on it
20:49:08 <jzb> croberts: do you have a current draft, notes, or...?
20:49:39 <croberts> jzb: i will have to look when i get at home, its on my laptop
20:49:55 <jzb> OK
20:50:03 <jzb> croberts: if you can post what you have tonight, we can see who else can chip in.
20:50:19 <jzb> croberts: bonus points if some is already written and/or there's an outline.
20:51:03 <croberts> jzb: I know i started the outline :) just need help with the ifno
20:51:09 <croberts> info
20:51:40 <jzb> croberts: OK. Groovy
20:52:06 <jzb> croberts: pro tip, if you're unsure of any details, write them without checking, then post to -devel. You'll get your correction in no time. ;-)
20:52:49 <croberts> jzb: ok sounds good :) its not as long as the statement on the wiki but at least we have something to work with
20:53:10 <jzb> groovy
20:53:37 <jzb> I've also noticed that the Fedora twitter account has been kinda quiet lately.
20:53:51 <jzb> last tweet was 6 November.
20:54:04 <suehle> Do we have the magazine autotweeting new posts?
20:54:14 <jzb> suehle: apparently not. I thought that it did.
20:54:45 <mitzie> We could also do it manually for some important posts in the fb page as wel
20:54:50 <mitzie> *well
20:54:52 <suehle> I thought it did too
20:55:07 <jzb> I'll take the action to find out whuck is going on there.
20:55:50 <jzb> #action jzb follow up on Twitter posting for magazine.
20:56:00 <jzb> that's all I've got this week - anybody else?
20:56:46 * roshi has nothing
20:57:05 * croberts croberts does not have anything else
20:57:10 <suehle> #endmeeting