20:03:36 #startmeeting 20:03:37 Meeting started Tue Feb 2 20:03:36 2010 UTC. The chair is mchua. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:03:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:03:45 Meeting time! Who's here? 20:03:49 are we meeting in here again? 20:03:50 #topic roll call 20:03:52 oh, okay :) 20:03:56 .fas rrix 20:03:56 * rbergeron is here 20:03:57 rrix: rrix 'Ryan Rix' 20:04:04 * JonRob 20:04:06 #info we're meeting in here for the indefinite future, since fesco has taken #fedora-meeting at this time 20:04:34 All righty, let's get started. 20:04:37 mchua: can I suggest #fedora-meeting-1 for next week? 20:04:44 (before we get started ;) ) 20:04:48 rrix: Sure, if you can get the rest of the list to migrate over :) 20:04:55 ah, okay :) 20:05:01 #action rrix to get our meeting to migrate to #fedora-meeting-1 for next week, and make sure zodbot is there 20:05:05 #link https://fedoraproject.org/wiki/Marketing_meetings#Agenda 20:05:29 * yn1v is here for the meeting 20:05:30 So, first, I should note that this starts to draw near the end of our "normal meetings" 20:05:33 hey neville! 20:05:42 #info zodbot's in #fedora-meeting-1 20:05:54 ...because feature freeze is coming soon, which means we will be moving from our "gear up infrastructure" phase 20:05:59 (which we've actually been moving quite well on) 20:06:10 into our "get release deliverables out" phase 20:06:10 yay for moving forward! 20:06:27 so one of the things that will be happening in the next 7 days is the creation of all the SOPs - I'll be driving those on the list. 20:06:37 #action mchua get us to complete all SOPs by next week's meeting for review 20:06:45 #link http://blog.melchua.com/2009/12/24/whats-marketing-doing-for-f13-anyway-a-show-with-dancing-penguins/ 20:06:59 for reference for folks who may be new or coming back after a while, on how this fits into the Grand Plan For F13. 20:07:07 * rbergeron cheers 20:07:15 Anyway - on with the agenda. 20:07:18 #topic agenda 20:07:21 mchua: what SOPs need to be created? 20:07:23 # Open items for Marketing FAD? 20:07:23 # Discussion: phpESP - does it meet our needs ( Robyn should probably make a list of those), what would be a realistic timeline to deploy, what design / skinning work is needed if we want to use it, etc. Issue tickets! Make magic! 20:07:24 oh, sorry 20:07:27 # Infrastructure status 20:07:30 * Limesurvey (I think we'll put this on hold for this week, obviously) 20:07:32 * Fedora Insight 20:07:34 rrix: no, it's a good question! 20:07:37 * Fedora-Tour 20:07:38 #link https://fedoraproject.org/wiki/Marketing#Release_deliverables 20:07:40 # Linux.com distro blog (stickster, at the end) k 20:08:04 #info we have 5 deliverables - talking points, slogan, feature profiles, screenshots library, and one-page release notes (aka tour). 20:08:12 * rbergeron took liberty to add to agenda this week 20:08:16 * mchua saw :) 20:08:18 mchua: also, Limesurvey /does/ have some updates from what ke4qqq talked with the limesurvey folks. 20:08:26 ok, we'll get to limesurvey down the line 20:08:32 yup 20:08:41 let's just start going through the agenda and we'll see how fast we can finish and if we have extra time we'll do whatever people wnat to do. 20:08:45 like dance! 20:08:46 * mchua being silly 20:08:48 um. 20:08:51 #topic Open items for Marketing FAD? 20:08:53 hampster dance? 20:09:00 (none from me - we're set, as far as I'm concerned.) 20:09:09 Open items... wrt? 20:09:18 anything that needs to be done 20:09:21 * mchua continuing to get locals to intro themselves to list, haven't been successful with that yet but continuing to poke. 20:09:23 ah 20:09:25 on the list of things to do before the fad 20:09:27 * rrix is silent 20:09:33 * rbergeron was just checking :) 20:09:34 #action mchua keep poking locals to intro to list for FAD 20:09:38 #link https://fedoraproject.org/wiki/Marketing_FAD_2010 20:09:38 since it's coming up. 20:09:48 JonRob, others who are popping back after an absence ^^ for context 20:09:51 * mchua nods 20:10:02 mchua: thanks 20:10:04 #info we'll be testing the remote participation infrastructure from the Events FAD at the Marketing FAD 20:10:15 \o/ 20:10:16 video streaming? 20:10:21 Yes, among other things. 20:10:49 * rbergeron notes to add makeup to list of things to pack... hah 20:10:54 That's something I'm taking care of with the other Events FAD folks, so you may see some of them on our list helping make sure we're set up with that 20:10:59 but no action needed. 20:11:23 Anything else on the FAD? I'm very happy with where we are, we're quite well prepared at this point imo. 20:11:51 I'm sure that a week or two before the FAD date we'll have naother flurry of last-minute arrangments on the list, but that's not something we need to worry about now. 20:12:03 ...okay! 20:12:05 Moving on. 20:12:07 wonderer wants to go to walmart ... btw 20:12:10 :) 20:12:19 wonderer: put it on the agenda ;) 20:12:27 Hey, AamirBhutto! Welcome! 20:12:28 bahaha 20:12:31 Next topic! 20:12:33 hi AamirBhutto 20:12:36 #topic # 20:12:39 Sorry am late 20:12:41 whoops 20:12:44 Hello. 20:12:55 #topic Discussion: phpESP - does it meet our needs 20:13:05 rbergeron: go for it. 20:13:07 ke4qqq: ^^ 20:13:08 okay. 20:13:23 so ... i'm going to be sort of talking around the limesurvey infrastructure status stuff too, here 20:13:34 AamirBhutto: http://meetbot.fedoraproject.org/fedora-mktg/2010-02-02/fedora-mktg.2010-02-02-20.03.log.txt is our log so far 20:13:42 rbergeron: sounds good. 20:13:47 basically during events FAD it got determined that packaging limesurvey is going to be complete ... fail in any short time period 20:14:02 rbergeron: walmart? I think over there it will be a bit "bigger" as here... 20:14:02 thanks 20:14:08 because they have bundled libraries, and some of those libraries are forked. 20:14:11 * rrix pops out for a second, ping if needed 20:14:30 so while we could help them out in resolving those issues 20:14:48 (basically it looks like some of their bundled packages are forked because of non-responsive maintainers / bug issues in those packages) 20:14:56 it would take time. 20:15:13 alternately, i've been informed that we could also.... fork their forks 20:15:17 to make it work for us. 20:15:35 so in the meantime, a new survey package called phpESP has come up as an alternative. 20:15:43 basically, limesurvey isn't going to be completed before we need a survey solution to be up for F13-ness? 20:15:53 #link http://www.butterfat.net/wiki/Projects/phpESP/ 20:15:56 right. 20:16:06 basically, limesurvey would be............ a ways out. 20:16:14 it's a lot of work :( 20:16:14 i'm guessing months. 20:16:28 plural, yes. 20:16:33 phpESP, from what i understand, has no issues and can be packaged really easily. 20:16:38 and deployed fairly easily. 20:16:47 and it has been put on publictest....something 20:16:51 * rbergeron will fish for the link in a minute 20:16:57 so I've been playing with it a bit. 20:17:07 * mchua greps through logs in the meantime to see if I can find that link (keep going) 20:17:13 Basically we have a few needs for a survey package: 20:17:34 we need it to be able to support multiple surveys / survey deployers 20:17:41 (so that other groups can do their own surveys if they want) 20:17:45 which phpesp meets 20:18:02 #link http://publictest16.fedoraproject.org/phpESP/admin/manage.php 20:18:08 it seems to perform well speed-wise, etc, and it installs, which is good ;) 20:18:13 #info phpESP has been deployed on publictest16 for playing-around-with 20:18:28 the major thing is whether or not it can handle dependencies in questions 20:18:49 such as 20:19:01 if the answer to question five is Yes, then, also ask them this set of questions. 20:19:14 #info phpESP test user: root, test pass: esp 20:19:28 which phpESP handles.... although, it is pretty archaic. 20:19:41 for example, from what i understand, it can't handle something like 20:20:09 "if the answer to this question is "cars," then direct to a set of questions about cars, but if the answer is Y, direct elsewhere, and if the answer is Z, then skip a bunch of stuff. 20:20:31 Conditions 20:20:44 exactly 20:20:53 which....... well, kind of sucks. 20:20:55 rbergeron: it can handle that, I think 20:21:10 rbergeron: there are -some- sorts of conditional test possible 20:21:16 rrix: from what i gather on the forums, not to more than one level 20:21:20 ah 20:21:28 unless you start doing things like 20:21:41 "do you have a car", yes / no, then, yada yada yada. 20:21:51 i did a question yesterday like 20:22:13 if the answer to this question is this radio button, or that radio button, then they get to go to the question 11 20:22:22 and then the test took me straight to 12 20:22:30 heh 20:22:39 umm 20:22:39 also, the practice run testing was pretty fail 20:23:10 A few questions: 20:23:12 1. Is the "marketing research: next step" == "get software working," and is "get software working: next step" == "see if phpESP works for us and if we can bend it to our will," or is there something else we need to be targeting in the next week? 20:23:19 and then 20:23:21 2. What is the goal for next week wrt marketing research/survey software, and what can people do to help? 20:24:00 i made a practice test, and once you get to the conditional question, it doesn't take you to the next page to test further. unless you activate the test, and then you can only do it once, and you can't edit it anymore and then you have to start over.... and when you make a copy of a test, it doesn't copy the conditions settings. 20:24:43 I think 1 is right. 20:25:02 the question is whether or not bending it to our will is going to take more or less effort than fixing the limesurvey stuff 20:25:12 limesurvey has more flexibility, more features, and works .... more intuitively 20:25:22 also has a significantly larger, much more active community 20:25:30 with international forums and the whole nine yards 20:25:32 Righto. 20:25:47 i mean, we can take into consideration whether or not it would be a beneficial thing to have in fedora in general 20:25:53 or we can skip that part 20:25:59 :) 20:26:04 phpESP i think works 20:26:07 functionally enough 20:26:10 my question about this survay thing would also be how the questions get in and the answers get out. because if we want to change the survaytool and evaluate the survays there could be a compatibilityproblem. So maybe that also have in mind... 20:26:43 Questions get in via basic forms in the web tool. 20:26:52 answers can be exported as csv 20:26:59 Output on both is in .... data files that are pretty much compatible with normal stuff 20:27:04 rbergeron: Ok. So what's the goal for next week, and what can people do to help? (Are there immediate blockers people can clear for ya, any things you'd like to see explored?) 20:27:06 what rrix said 20:27:35 basically, if anyone else would like to do some test runs with it, that would be awesome. 20:27:44 I'm going to try and recreate the fudcon survey in it 20:27:53 and see how it is, if i can get it to work. 20:28:02 in the long run, we'd like other groups to be able to do their own surveys 20:28:28 ! 20:28:30 so if it's not .... easy 20:28:32 then that is bad. 20:28:46 we want people to be able to be self sufficient :) 20:28:50 myself included! 20:28:51 hmm, input just webbased? Hmm, if we maybe have 2-5 survays (one at marketing, one at ambassadors, one in england, one in spain, etc.) and then with several conditions ... I do not think that could be handled per copy & past of several hundered lines of questions. answers via csv sounds good. 20:29:30 several hundred lines of questions in a survey is bad news, nobody fills them out :) 20:29:35 what was i going to say 20:29:38 rbergeron: Ok - so perhaps the call for help is "try implementing a simple survey for something you're curious about, get a few folks to take it, and then let us know if the software does something that you don't want it to do (or doesn't do something you need). 20:29:40 so basically the other thing i think we should do 20:29:54 is try to figure out... if we did deploy phpESP 20:30:08 could get get it up and running for a survey to be deployed by March 1. 20:30:34 rbergeron: a real survay or test-survay? 20:30:50 Because if we can't, then I would vote that we stick with limesurvey, go the route of buying responses or negotiating something with them like "we're helping you get in fedora so let's share the love and have some free responses" 20:30:56 Are there options we'd like to evaluate other than phpESP, or are we hitching our cart to this horse for the time being? 20:31:01 and work through them to fix their issues 20:31:08 And what will happen with our limesurvey work - continue with lower priority? drop? 20:31:48 I'm not sure about the limesurvey work. I'd like to see it continue, because I think it is better, but I can't do that work :) 20:32:03 I've looked for other open source survey stuff. it's not out there, 20:32:10 unless you count things like "do a poll in drupal" and things like that. 20:32:21 Not so much for the scale we're thinking about :) 20:32:22 Which isn't really sufficient, obviously 20:32:49 So I think we should investigate what effort would be needed for phpesp deployment 20:32:59 how long it will will realistically take to test and do all that magic 20:33:06 and i mean very realistically :) 20:33:16 and get it up and running publicly 20:33:21 hmm, reminds me ... is it possible to get a survay "plugiN" for zikula...? just an idea.. 20:33:33 rbergeron: Ok - is that something you need help with? :) 20:33:43 * mchua trying to get to the "here's what we're doing next week, here's how everyone can help!" point ;) 20:34:00 mchua: i think others know those ropes and people better than I do to get it done in a more efficient fashion quickly 20:34:01 :) 20:34:50 meanwhile, I'll go ahead with testing stuff, and anyone else can as well, and i can aim for a "status on whether or not this is adequate for long-term" by... Friday. 20:35:27 * stickster is off 3pm call 20:35:37 if it's not adequate, I say we go the long limesurvey route, if we can get people to agree to help. 20:36:14 * wonderer relaises that its 22:00 at this side of the world... 20:36:25 rbergeron: sounds good :) 20:36:27 no 20:36:30 its 21>34 20:36:32 They had 14,000 downloads in november. I think it would be beneficial for it to work on Fedora :) 20:36:37 s/>/: 20:36:42 #action rbergeron survey status update by Friday with call-to-action stuff 20:37:17 * mchua would also like to encourage marketing folks to blog - rbergeron has been doing this of late and it's been *awesome* in terms of the increased visibility the stuff our team is doing is getting with the rest of the Fedora community. 20:37:22 * mchua should blog more, too. :) 20:37:39 mchua would have to not travel for 10 seconds :) 20:37:39 rbergeron: I have volunteer to create and run a test-survey 20:38:03 awesome. do you have what you need? 20:38:13 i can make a user / pw for you if you'd like 20:38:13 #action yn1v to coordinate with rbergeron on testing the survey software 20:38:15 Yes 20:38:17 :) 20:38:27 I will retain a bit with that blog thing :-) 20:38:31 y'all ready to loop through the rest of the agenda? we can come back to the survey stuff at the end if we have time. 20:38:36 bad moods in the past :-D 20:38:39 the only thing I need is what instance to try 20:38:43 also, you can make a survey in the demo on limesurvey if you'd like. 20:38:52 wonderer: although - your blog post on the Marketing FAD when we started planning that helped kickstart planning, which was awesome. 20:39:01 (the demo on phpESP's website is broken, which is why we put it on our own stuff.) 20:39:17 ok, y'all ready to loop through the rest of the agenda? we can come back to the survey stuff at the end if we have time. 20:39:22 (which also doesn't inspire a lot of love considering how much complaining has been done about it on mailing lists / forums) 20:39:31 yes. Sorry. wordy robyn :) 20:39:32 mchua: THAT one, yes ... but ... I think some of you missed that. Its a thing for red-wine in the hotel lobby I think ;-) 20:39:32 (I've got my FI update queued up ready to go, so it should be quick) 20:39:35 nah, it's good :) 20:39:50 rrix: queue up the fedora-tour update while I'm spewing ;) 20:39:52 #topic Fedora Insight 20:39:58 Status update on Fedora Insight (FI): 20:39:58 #link https://fedoraproject.org/wiki/Fedora_Insight 20:40:00 mchua: also I mention some on my weekly FWN in german. 20:40:00 alrighty :) 20:40:05 FI is on staging, which is the final step before production - the missing parts are (1) a short URL system with some SEO-fu, which affix has been working on, and (2) the theme working, which hiemanshu and the websites team has been working on. 20:40:09 #link https://stg.fedoraproject.org/insight/ 20:40:14 Our first target is actually getting FWN up and running on the FI platform, because they have a known content workflow, and it'll be a pure test of the software infrastructure (or as close as we can get it). 20:40:19 That's not a marketing thing to worry about, but it's notable because FWN will be the first users of FI and we will be the second (so as soon as they're clear, we need to quickly learn from them and get our stuff up as well). 20:40:21 loquacious is the word i'm looking for actually :) 20:40:23 #action mchua to follow up with pcalarco about getting FWN on FI 20:40:25 #info Our next FI milestone is to migrate the Fedora Weekly News workflow and publication to Fedora Insight before Alpha Public Availability (March 2, 2010). 20:40:28 #info The milestone after that is to get all pre-beta F13 Marketing deliverables published on Fedora Insight before Beta Release Public Availability (April 6, 2010). 20:40:31 So the latter milestone is the thing we need to look at. 20:40:32 #link https://fedoraproject.org/wiki/Fedora_Insight#How_to_help 20:40:38 ...is a list of instructions you can look at if you'd like to help us get there faster. 20:40:46 #info From the Marketing side, we have two big things to do for FI: the first is to be ready to go with content (i.e. release deliverables) so that we don't need to worry about scrambling to make those, and can concentrate on the "what does it mean for this to get published on FI?" question 20:40:54 #info The second thing is to figure out how to implement our content workflow - similar to how FWN has an editorial workflow with beat writers posting things by a certain time each week, and an editor (pcalarco) pulling it together and publishing it each week, etc. we need to figure out who's filling what roles in the below diagram. 20:40:59 #link https://fedoraproject.org/wiki/Fedora_Insight#Content_workflow 20:41:01 ...also so we're ready to go the moment FI gets ready to handle Marketing stuff. 20:41:04 If you'd like to help us get to the "we're ready for Marketing!" point faster, see https://fedoraproject.org/wiki/Fedora_Insight#How_to_help and join another team we're blocking on. ;) 20:41:08 EOF 20:41:09 any questions? ;) 20:41:15 * rrix asplodes 20:41:16 #action mchua blog FI update 20:41:53 * rbergeron reads back after answering door from kids going door to door asking for donations for keeping kids off drugs. 20:42:09 drugs are bad, mkay? 20:42:36 it didn't seem very official. a little bizarre. 20:42:39 anyway. 20:42:42 mchua: Substantial update -- thanks for that, and for cleaning up the wiki page 20:42:43 no questions mchua! 20:42:57 stickster: thanks for helping me work through getting this stuff in order the other day! 20:43:21 Anyway, yeah, FI for Marketing is "hold tight - we're getting ready for you, have your deliverables ready, and pitch in on another team that's working on FI now if you'd like us to get to you faster." 20:43:25 mchua: I feel like you had it 90% there and were mostly looking for confirmation, happy to help :-) 20:43:30 * mchua grins 20:43:34 soooo that's Insight 20:43:42 rrix: fedora-tour? 20:43:45 #topic fedora-tour 20:44:06 yup 20:44:10 so, we're having weekly meetings 20:44:13 (after this, the only remaining topic is stickster with the linux distro blog) 20:44:18 * mchua listens 20:44:25 in #fedora-meeting, to discuss development, and getting things done 20:44:42 Awesome. Where are these meetings logged? 20:44:44 do you guys have a separate mailing list? 20:44:47 or sending logs 20:44:55 * rbergeron is mentally connected to mchua. 20:44:57 #link https://fedorahosted.org/fedora-tour/wiki/meeting-logs 20:45:06 #link https://fedoraproject.org/wiki/Fedora-tour 20:45:07 almost like the borg, but way cooler. 20:45:13 no mailing list, I could probably have infra set one up, but we have #fedora-tour IRC channel 20:45:28 hiemanshu decided to join our little acting troupe, and is along for the ride, which is Good thing! 20:45:43 martha stewart approved. 20:45:54 meetings are saturday at... 9:30 am MST, so 11:30 am EST, and something UTC 20:45:55 * mchua would love to see links to these logs get sent to list - I see them once in a while when I read backchannel and go "ooh, these are great, I think others would be interested in seeing them!" 20:46:13 #action meeting logs to list 20:46:22 #info fedora-tour meetings in #fedora-meeting weekly at 9:30am MST (11:30 AM EST, 16:30 UTC) 20:46:32 I guess that's about it, I missed the last meeting becuse of ISP issues (growl) 20:46:39 no doubt 20:46:43 Questions? :) 20:46:45 rrix: for the record, you folks are totally doing things the Right Way 20:46:54 transparent development, regular meetings that are publicly logged, etc. 20:46:59 so keep it up :) 20:47:14 awesome :) 20:47:16 rrix: same question as for the survey stuff (1) what's the target for next week, and (2) how can people help? 20:47:21 (with that target for next week) 20:47:51 mchua: I haven't the slightest. I guess just get a few ears at the meeting saturday morning would be a Good Thing. We're still organizing our resources and planning our design 20:47:54 .win 30 20:47:56 grah 20:48:19 but, yes, meetings! they're awesome! 20:48:40 kinda hard to find a sane time for them though, with hiemanshu and franciscod in india, Subfusc in UK and me here ;) 20:48:47 lol 20:48:59 right :) 20:49:05 ok, so... 20:49:18 #info if you'd like to help with fedora-tour, show up at the next meeting 20:49:19 mm. that reminds me: mail to list about occasionally varying mktg-meeting time to accommodate ww contributors? 20:49:34 or adding varying time meeting once or twice a month? 20:49:35 rbergeron: If you want to bring it up now, sure. 20:49:40 I might wait until the FAD. 20:49:49 mchua: i think that is a good idea. 20:49:59 but yeah, make sure that's on the agenda for some day or other. 20:50:11 It's a good chance for us to take stock of where we're headed as a team, what we would like to do, etc. 20:50:25 * rbergeron thinks the todo list is starting to look like santa's naughty and nice list :) 20:50:27 and get some of those "ehhh we've been thinking about this but never sat down to Do Something" little things like meeting time. 20:50:36 rrix: anything else on fedora-tour? 20:50:41 nein 20:50:43 EOF 20:51:25 #topic distro blogs 20:51:28 stickster: you're on. 20:51:50 * mchua heard about this for the first time last week, and only vaguely knows "there are distro blogs and we have one and should use it" but knows basically no further details 20:52:02 Hiya folks 20:52:12 * mchua choruses "hi, Paul!" 20:52:14 * rrix waves at stickster 20:52:17 So we have access to a "distroblogs" section at Linux Foundation 20:52:19 hi 20:52:23 * wonderer laola... 20:52:32 The new linux.com reworking included this site: http://linux.com/distrocentral/distroblogs 20:52:53 #link http://www.linux.com/distrocentral/distroblogs 20:53:02 they actually have a big box saying 20:53:10 Right now, that site is seeded from an RSS produced by a dedicated wordpress.com site. Any RSS can be included, right now that is what we are using. 20:53:12 "get insight from distro leaders!" 20:53:22 We'll provide Insight all right ;-) 20:53:30 muhahaha 20:53:30 \o/ 20:53:42 In all seriousness 20:53:55 the long-term plan is that Fedora Insight can and should provide a steady RSS feed of content to that area. 20:54:10 +1 20:54:13 We *simplify* at Fedora Insight, and *amplify* through the distroblog site. 20:54:14 ...since most other distros are representing there 20:54:18 BIG +1 :-) 20:54:35 We actually have content there too, but the problem is that in the *short term* 20:54:45 we are providing content through a manually managed wordpress.com site. 20:55:03 And rbergeron's question about the distroblog site tells me that I've been remiss in not spreading that access further 20:55:24 So I would be thrilled to open access to more people, but I do warn you that the process of updating the site is less than fun 20:55:42 And I'm not interested in simply gating every Planet post to the distroblog feed. 20:55:51 no. 20:55:57 stickster: are you the only person with access to that site right now? how do we hook $contentstream to it, when $contentstream (read: FI) is ready? 20:56:01 We have a good deal of irrelevant information that would end up there, and from time to time, things that I don't even like seein gon *our* planet 20:56:10 mchua: I can give access to anyone who opens a free wordpress.com account 20:56:25 it seems like most of what is getting fed there is updates, releases, weekly news, etc. 20:56:27 To hook a content stream to the distroblogs, we just have to provide a new RSS link. 20:56:51 stickster: is there any particular way you'd like to handle the access-granting (for the temporary "before we have FI up" phase, or should we just ignore it 'till we have FI up?) 20:57:10 mchua: I'd like to handle access granting this way 20:57:18 stickster: is the wordpress blag managed by infra or is it a wordpress.com account? 20:57:27 rrix: It's wordpress.com 20:57:31 ahh 20:57:42 Outside our infrastructure, because I didn't want to feedback into the planet from things already on the planet 20:58:04 So here's how I'd like to get access spread around: 20:58:12 1. If you're interested in helping, make a wordpress.com account 20:58:14 must it be wordpress.com or can it be a wordpress Instance on an dedicated server? 20:58:35 stickster: independent of existing wordpress accounts that are personal, i take it? 20:58:39 wonderer: It can be any RSS feed. That being said, there's no reason to switch things around if we're going to have Fedora Insight to manage this shortly. 20:59:00 rbergeron: Actually, I use my normal wordpress account, and see no reason other people couldn't do the same 20:59:38 stickster: that was the background of the question. if we have FI runnijng we can "tag" or "flag" the relevat posts and let them fly to linux.com 20:59:40 2. I'll write a wiki page that describes the kind of material worth selecting into the feed, and the procedure for putting material there. 20:59:43 as long as the wordpress account isn't "Robyn the awesome Marketing Chick" or something? Real Names +1 20:59:51 wonderer: Refer to my "long term" plan above 20:59:58 :) 21:00:14 (sorry rbergeron, threw ya under the bus :P) 21:00:15 wonderer: We'll simply tag something as "distroblog" (or some tag) in Fedora Insight, and the RSS feed for that tag will feed distroblog 21:00:17 * rbergeron has no problems advertising her awesomeness so long as she can live up to it? :) 21:00:54 mchua: make sense? 21:01:08 stickster: ayup. will you be looping this into the mktg list? 21:01:22 * stickster notes that there are some people with access currently but he's ended up doing most of the content vetting, so will be very happy to have help! 21:01:22 * mchua is honestly less worried about this because we're going to be using Insight for it in a month or so anyway 21:01:26 mchua: Yup, that's on me 21:01:39 #action stickster set up the "how we're going to use the linux distro blogs" convo on-list 21:01:43 yay! 21:01:45 mchua: I think the key is that we need *plenty* of regular content to make Fedora Insight the only place feeding distroblogs. 21:01:46 Anything eles? 21:01:52 * mchua nods 21:01:55 stickster: I'm definitely interested in helping out on such a thing, keep us posted :-) 21:02:00 will do 21:02:35 Ok - I think that might be a wrap for the meeting today. 21:02:40 Anyone have anything else they wanted to discuss? 21:02:48 mchua: you are good at planning these :) 1h on the dot 21:02:53 #info next week we'll start by reviewing the SOPs to gear up for our deliverable sprint 21:02:57 rrix: lots of practice ;) 21:03:04 aaaand closing in... 5... 21:03:06 4... 21:03:08 3... 21:03:10 2... 21:03:13 1... 21:03:15 0.5... 21:03:17 thanks everyone! 21:03:20 #endmeeting