20:00:24 #startmeeting 20:00:24 Meeting started Tue May 18 20:00:24 2010 UTC. The chair is mchua. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:01:11 I made it ... yupi!! 20:01:32 yn1v! long time no see! 20:02:18 howdy, rbergeron and gbraad 20:02:19 meeting are at work time, not always I can hide in a corner with my computer 20:02:24 #link https://fedorahosted.org/marketing-team/query?status=new&status=assigned&status=reopened&keywords=%7Emeeting&order=priority 20:02:35 yn1v: Noted... we may try to find a more convenient time for F14 meetings. 20:03:32 That link is the trac query that has our agenda for the day. 20:03:33 or I will look for other job ... hahahaha 20:03:51 And I'm trying to figure out a faster way to clean the html copy-paste up so we can have an actual topic list in this channel. 20:03:52 yn1v what timezone are you in? 20:04:10 #info: topic - one-page release notes 20:04:15 -6 GMT 20:04:27 #info topic - zonker's classroom session, followup 20:04:40 #info topic - f13 marketing postmortem 20:04:56 #info topic - preparing trac for f14 20:05:09 #info topic - press kits 20:05:16 yn1v soon I will be in gmt+8 20:05:20 :-s 20:05:27 #info topic - press release workflow (probably defer to a later date, though) 20:05:49 Any other topics people would like to bring up? yn1v, gbraad, did you want to talk about the things you'd like to do in your geos? 20:05:58 ohi 20:06:03 we haven't really covered international reach for F13 and F14 yet, and that's something we wanted to touch, I know. 20:06:07 rrix: yo! 20:06:25 mchua not yet. still too early stage 20:06:31 hello rrix 20:06:33 noted. 20:06:35 hello, NourishedCloud! 20:06:55 Yoooo Luke! 20:07:03 NourishedCloud: Can we get an introduction? :) 20:07:20 mchua I will try for a small meeting before the beijinglug meeting of June 8 to show F13 features to interested people 20:08:04 mchua July I will give a meeting about the Fedora community; partly in Chinese ;) 20:08:17 Nice! 20:08:28 Yep, I'm Luke. I introduced myself on the Marketing mailing list the other day, I'm a relatively recent comer to Fedora but want to help out because it's such a good project. Know rrix and gbraad from Identi.ca (they helped me get involved). I have a user page on the wiki too 20:09:14 * gbraad and rrix 'forced' hime to join :-D 20:09:30 * mchua grins 20:09:35 I did no such thing :) 20:09:35 Welcome, Luke! 20:09:38 hehe 20:10:00 mchua: thanks :) 20:10:22 Okay, let's get started then! 20:10:31 #meetingname weekly marketing meeting 20:10:31 The meeting name has been set to 'weekly_marketing_meeting' 20:10:49 This meeting may be slightly boring since it's the end of the release cycle and we're just in 'get everything done!!!!' mode. ;) 20:10:54 #topic one-page release notes 20:11:08 #info One-page release notes are done except for screenshots, and ianweller is going to do the final layout. 20:11:34 #info we need help with screenshots! 20:11:39 #link http://lists.fedoraproject.org/pipermail/marketing/2010-May/012872.html 20:11:48 mmchua, have we looked at any of teh screenshots nelson made 20:11:56 in his fedorapeople directory 20:11:57 #info the above link shows how to help with screenshots - and NourishedCloud has already offered to help out, so thanks, Luke! 20:12:05 rbergeron: Ooh, not yet. Where are those? Can haz link? 20:12:13 #info Nelson has some screenshots in his fp.o space 20:12:22 #action mchua see if we can use some of Nelson's screenshots 20:12:30 http://nmarques.fedorapeople.org/upload/ 20:12:45 #link http://nmarques.fedorapeople.org/upload/ 20:12:47 Thanks! 20:12:54 * mchua doesn't want to spend too long on the one-pager, just noting progress and moving on 20:12:57 awesome. 20:13:07 i think it's mostly related to color management stuff 20:13:09 * mchua nods 20:13:11 oh, great! 20:13:21 #topic press release workflow 20:13:24 #info deferring to next meeting 20:13:30 #topic press kit 20:13:40 #info deferring to next meeting (unless wonderer pipes up mid-meeting, then we'll come back to it ;) 20:13:50 #topic F13 postmortem, and getting ready for F14 in trac 20:14:03 rbergeron: Did you want to say something about both of these? I believe the tickets came from you. :) 20:14:20 ummmmm. well, F13 postmortem will be coming... when f13 is out. 20:14:30 so proably one of the following tuesdays. 20:14:44 I'll start getting trac retooled with f14 milestones when we ... have those dates 20:15:02 so we can start filling in tickets for delvierables at least 20:15:21 #info F13 postmortem to come once F13 is actually relased (so we're deferring that a bit ;) 20:15:31 #info F14 Trac-fu waiting for F14 dates 20:15:37 same for wiki stuff - i'll be adding in the F14 links / templates over the next couple weeks. 20:15:47 for teh standard deliverable locations 20:15:49 rbergeron: Usually the way that works is that poelcat will poke each team and say "hey, when do you want milestones?" 20:15:55 so that should come up pretty soon. 20:15:58 moving around the marketing to-do-list stuff 20:16:02 mchua: okeedokee. 20:17:28 #info poelcat typically pings teams at the start of the release cycle to come up with their own schedule for the next release 20:17:35 rbergeron: Cool. Feeling good about F14? :) 20:17:37 stickster: if you're here, i has a question for you 20:17:50 mchua: of course. :) 20:17:52 * stickster here, just divided up a few ways :-) 20:18:13 stickster: you mentioned SSSD feature profile? can we talk about that at some point in the meeting :) 20:18:30 rbergeron: Yes, whenever it's the right time 20:18:34 okay. 20:18:39 * stickster has a hard stop at the hour 20:19:29 * rbergeron would also like to note that fedora-advisory-board is asking for teams / team leads to come forth and talk about their groups upcoming goals / etc, so we'll be doing that at some poitn in the future to talk about f14. 20:19:33 :) 20:19:40 sorry, random interjection there, but thought i'd say it while thinking about it. 20:19:57 mchua: go forth :) 20:20:10 woo! 20:20:23 rbergeron: Does that mean you and/or mchua want to come do that on Thursday? 20:20:29 This Thursday? 20:20:32 correct 20:20:36 no. 20:20:43 Okey doke 20:20:43 * rbergeron will e on teh plane to FAD NA 20:20:50 otherwise i'd volunteer 20:21:05 well, someone else can, but 20:21:14 * rbergeron doesn't mean to put the kibbosh on it for all marketing peepz :) 20:21:32 but we should all probably talk during postmortem time to figure out what we want to commit to for f14 20:21:33 * mchua could, but wonders if a less-frantic time would be more optimal? 20:21:39 before we go advertising it to F-A-B :) 20:21:57 * rbergeron wonders if mchua ever has less-frantic-time :) 20:22:50 * mchua grins 20:23:02 stickster: I think you should put marketing down for a "after May 25th, please" slot :) 20:23:10 Sure thing 20:23:17 #info Marketing would love to do a f-a-b townhall... *after* release day. 20:23:32 Maybe the first team session in June then 20:24:52 That would likely work for me. 20:25:49 yup. 20:26:25 oh, wait 20:26:31 are you doing them every other week? 20:26:42 * mchua would like to move on so we can spend a good chunk of time on zonker's classroom followup, since we're a bit overdue on that 20:26:45 and release is coming up 20:26:47 sure thing. 20:27:09 * rbergeron is heading to SELF on a thursday in june, and suspects stickster and many others might be as well 20:27:12 Sweet. 20:27:24 #topic Zonker's classroom session: what's actionable! 20:27:27 #link http://meetbot.fedoraproject.org/fedora-classroom/2010-04-27/fedora-classroom.2010-04-27-19.00.log.html 20:27:34 I'll give folks a few minutes to read and think about that. :) 20:27:39 Not sure who was able to make it. 20:27:53 But I wanted to ask if people had any thoughts/feedback (other than a BIG THANK YOU to Zonker) 20:27:57 * stickster will be there! 20:28:05 on whether we should be doing anything immediately to react to his Classroom session. 20:28:31 ahhh. 20:28:59 * rbergeron is bringing the sig0, watch out :) actually more like he's bringing me... 20:29:04 mchua: so, i had some notes..... 20:29:40 oen thing is: he brought up the "usual suspects" points wrt journalists 20:30:02 so - i'm not sure if stickster has some magic he does here, or if RH helps qutie a bit - but are we reaching out to those folks every time? 20:30:13 or at least thinking, they haven't contacted me yet - maybe i need to reach out? 20:30:15 stickster: le pingity? 20:30:39 9:12:19 You basically have two or three groups of journalists 20:30:39 19:12:34 the first group are the usual suspects 20:30:39 19:12:45 Ryan Paul, myself, SJVN, LWN, 20:30:39 19:12:51 that you probably don't need to pitch very hard 20:30:39 19:12:56 to get coverage with 20:30:39 Who are the usual suspects you are referring to? 20:30:43 Ah 20:30:57 rbergeron I think it would be wise to poke them about who you are 20:31:30 well - i think we don't want to double-poke here, is what i'm getting at 20:31:45 rbergeron: Here's what I would suggest. 20:31:49 i'm not sure what happens behind the magic of press@fp.o email. 20:31:54 :) 20:32:31 Draw up a list. Start with community sites such as Slashdot, OSNews, and others -- You can look back in the archives to see where Adam Williamson summarized a list he used previously for Mandriva. 20:32:38 Post that to the marketing list and we can de-dupe there. 20:32:55 this is making a list of sites to send press releases to? 20:32:57 while stickster answersw - i think one thing jzb pointed out that we could really focus on for F14 is his point about making feature descriptions more understandable - why are these features important 20:33:08 NourishedCloud not just press releases 20:33:34 * mchua wonders if this should be on the wiki somewhere ;) 20:33:49 NourishedCloud generally about marketing, if they have questions related to a release 20:33:54 mchua: 'zactly -- in a release announcement SOP. 20:33:57 yeah, i think this is one of those it would be nice to talk to kara and figure out what she does, so we're not duplicating. 20:34:12 so having a wiki page where we've identified people 20:34:41 would be a good start. 20:35:42 Should we try to do this for F13 before release, or after? 20:35:52 9:06:14 Others are going to need more detail to see 1) what has changed between releases, 2) how to enable features, 3) see what to focus on. 20:35:55 19:06:22 Fedora is pretty good about this. Actually, Fedora is one of the best distros when it comes to providing this information. 20:35:58 19:06:38 The talking points and feature pages are great - providing that journalists can find them. 20:36:01 19:06:57 What I haven't noticed so far is outgoing efforts to get in touch with individual journalists 20:36:04 19:07:05 or a press list similar to KDE's 20:36:07 19:07:09 those are good things on both counts 20:36:07 * mchua thinking about "after" (I can do that while rbergeron ramps up on F14 stuff, as part of the transition) since we'll want journalistic buzz for some weeks after the release anyway 20:36:08 ummmm. i think trying to squeeze that in before next week is going to be ... interesting. 20:36:12 19:07:31 Having one or more folks in the community that has developed personal relationships with journalists is a very good idea. 20:36:12 rbergeron: Yeeeah. 20:36:26 it might be good to have a draft before the release of F13 20:37:01 mchua: most of the pages which explain functionality are up. It could be wise to approach some of those people, like ryan pual, to point them at these pages 20:37:24 because it could enhance the release of F13 :) 20:37:34 well - as jzb pointed out - ryan is one of the people who get it 20:37:42 * stickster comes back from split attention 20:37:46 there's a world of generalized tech writers who ... don't know where to start looking. 20:37:51 gbraad: you mean things like talking points and such? 20:37:53 rbergeron: I think the main thing to do to avoid duplication is just to have a de-duped list. 20:38:07 Then we can proceed as *we* feel is appropriate without worrying about or blocking on Red Hat 20:38:44 And the job of the FPL is to make sure that any PR work Red Hat does is in line with what we do as a community 20:38:46 stickster: okay 20:38:59 stickster: among 4 billion other jobs :) 20:39:04 mchua feature pages (not sure if these are the talking points) 20:39:06 * rbergeron hugs stickster for being teh awesomes 20:39:13 There are a few of those 4 billion that are the critical path, and this is one of them. 20:40:37 * stickster eof, proceed! 20:40:50 right - and i want to make sure taht what we're doing as a community is organized, centralized, etc - not a mess of ad hoc stuff. 20:40:54 * mchua echoes rbergeron re teh awesomeness of stickster 20:41:05 I'm just a squirrel tryin' to get a nut 20:41:06 so - i think back to what we were saying - i think having a name list is a starting point 20:41:13 stickster: So if we set up a "what reporters have we contacted and how?" page, would that help you, or be a bother? 20:41:17 whoops. 20:41:22 * mchua shuts up and lets rbergeron take the helm :) 20:41:31 lol 20:41:55 and figuring out what messages we want to have to those folks, and when, can be next steps. 20:41:57 rbergeron +1 20:42:12 by "what messages" i mean - essentially press-friendly versions of deliverables 20:42:21 not "what is fedora" or that kind of thing. :) 20:42:50 rbergeron: oh, like a press kit ;) 20:43:03 well, yes, and no, i suppose 20:43:12 * gbraad searched for the press kit :-s 20:43:18 i see press kit as something that comes with big events or releases 20:43:27 press release is .... well, one thing. 20:43:40 one item, message, whatever. 20:43:54 maybe we send a press kit the first time we have community press corps contact 20:44:06 but ongoing - sending the same thing over and over gets redundant and unlooked at 20:44:38 if only one teeny piece has changed 20:45:09 so - let's make an action item / ticket to start working on press list contacts 20:45:31 mchua, am i a chair or can you action me 20:45:36 #chair rbergeron 20:45:36 Current chairs: mchua rbergeron 20:45:45 and we can start figuring out what magic we want to do... in a week or two 20:46:05 tip: as what we normally, we collect [In the news] items. it would be wise to register these on the same wiki page and compare for potential targets we might have missed. Too bad we do not have such a thing as 'Fedora Buzz' yet to monitor it 20:46:21 well, we could potentially put that stuff on Fedora Insight 20:46:34 oh, you're talking about buzz 20:46:39 rbergeron: Can I insert something here? 20:46:43 The proposal for which is here: https://fedoraproject.org/wiki/Fedora_Buzz 20:46:44 * stickster should have said, 20:46:45 stickster: of course 20:46:46 * stickster ! 20:47:07 I think we should separate the short-term from the medium-term. 20:47:16 #link https://fedoraproject.org/wiki/Fedora_Buzz 20:47:39 A list is something that can be done in very short term, using the information Adam Williamson provided back in the archives about a list of community sites of /. ilk 20:47:53 * rbergeron nods 20:48:07 Then I would recommend that we send a copy of the announcement, as one of the regular release day SOP items for Marketing, to that list of contacts. 20:48:15 and i think we can cross ref that list against... who is currently reporting on stuff already. 20:48:29 (I'd also recommend letting Adam know we're doing it, so he doesn't duplicate effort.) 20:48:43 so - adam is also sending out mail to press people? 20:48:52 rbergeron: That's not what I'm suggesting. 20:49:02 He did it previously because he realized no one in Marketing was doin git. 20:49:04 *doing it 20:49:18 it eing mailing press people or it being making a list :) 20:49:20 I am suggesting that become part of the Marketing team's deliverables, to be done on release day once the announcement goes out on our announce list. 20:49:46 rbergeron: I was answering your question, "it" == "sending out mail to press people" 20:50:15 who's on first! 20:50:16 :) 20:50:41 * mchua willing to execute tasks spec'd out by someone else in advance ;) 20:50:44 So, action item #1 is the list, which can be compiled from Adam's mail on the marketing list at some point around our previous release cycle. 20:50:47 in other words, I will follow an SOP given to me! 20:51:02 * mchua does not have much brain-bandwidth this week, but can blindly follow instructions :D 20:51:11 rbergeron: so, action me and SOP me if ye like :) 20:51:36 action item #2 is to make sure that Marketing has a documented task for release day of sending copies of the official announcement, once it hits our public announce list, to that list of press people. 20:51:46 * stickster eof 20:51:59 #action mchua to locate adam williamson's email to compile a list of press contacts. 20:52:29 #action mchua and rbergero to make SOP of sending copies of official announcement to list of press people. 20:52:49 #undo 20:52:49 Removing item from minutes: 20:52:55 #action mchua and rbergero to make SOP of sending copies of official announcement to list of press people on release day 20:53:25 w00t! 20:54:04 okay - back to jzb's stuff 20:55:00 i think we could go on and on aout things we could take from that - maybe we should remail logs to list and make a wiki page of "what did you get out of these logs as things we could be doing" - because i think we just spend 20 minutes discussing one thing and i think there is a lot more to get out of his classroom session. 20:55:15 food for thought? 20:55:22 +1. 20:55:25 I agree with rbergeron 20:55:28 I've got the link open, I'll forward the logs. 20:55:38 #action mchua remail jzb logs to list, ask for comments 20:55:41 cool. 20:55:55 are we to AOB now? 20:56:56 #topic SSSD Feature profile 20:57:21 Stickster - are we still able to do this? If so, I'll put some highlighting material up at the top. 20:57:32 generalized information / introduction / etc. 20:57:41 #link http://fedoraproject.org/wiki/SSSD_in_Fedora_13 20:57:59 #info stickster said yesterday there is a possiblity of having another slot for a feature profile sometime next week in the RH press blog. 20:58:10 rbergeron: It was this week, actually 20:58:21 I had pinged to see if you were interested in drafting a press blog entry to be published this week. However, time is pretty short now, but it's not a big deal 20:58:23 #info stickster said yesterday there is a possiblity of having another slot for a feature profile sometime this week (thursday) in the RH press blog. 20:58:31 yeah, i didn't see it till late last night. 20:58:44 Here's what I would suggest 20:58:51 We can easily publish one the week *after* Fedora release 20:59:00 stickster: do you actually draft those press blog pieces? 20:59:03 If you're interested in drafting an entry, Kara would be happy to work with you to review them 20:59:04 Yes. 20:59:06 or does kara write that 20:59:09 yes, i would love to learn. 20:59:19 Cool 20:59:26 I'll email kara and see what we can do. 20:59:55 rbergeron: Superb, I would offer to do something around June 1, that's Tuesday following release day 21:00:07 s/I would/I would recommend you/ 21:00:17 #action rbergeron email kara - talk about doing a press blog entry for post-f13 (june 1-ish) on SSSD. 21:00:24 * stickster runs to phone 21:00:25 coooool. 21:00:30 * rbergeron waves at stickster 21:00:57 okay. 21:01:22 * mchua notes time 21:01:34 * rbergeron notes lots of new marketeers working on awesome new stuff 21:01:53 does anyone have any questions / guidance / help / needs right now?? 21:02:06 not that i am all knowing, but i hear mchua is. :) 21:02:07 rbergeron: general? 21:02:10 * rbergeron grins 21:02:30 general, specific, whatever. i'll hear your birthday wish list, even. :) 21:02:36 * mchua makes it all up as she goes along ;) 21:02:37 I know NourishedCloud wants to point out the idea he proposed on the mailinglist 21:02:45 indeed. 21:02:47 ooh 21:02:57 #topic Fedora Buzz 21:03:10 nourished, you have a moment? 21:03:24 Yes 21:03:32 * rbergeron hopes she isnt' mixing up ideas with the wrong people, that would be -really- bad form. :) 21:03:44 it's a tough place to be in. awesome new folks with lots of ideas. :) 21:04:08 I basically saw the call for ideas on how we can track how the marketing team is doing on the wiki, and I think how much people are talking about fedora is a good way of measuring marketing success 21:04:55 that is correct - or at least one piece of measuring success. :) 21:05:16 rbergeron therefore, as you point it, your vision on it is welcomed 21:05:37 rbergeron you might also know other measuring criteria ;-) 21:06:02 rbergeron but for now; we thought of Buzz to monitor the blogosphere and identiverse 21:06:31 yup. and those are key places we need to be looking 21:06:42 I would like to develop the idea more, pin down method of implementation (moksha or whatever?) and then get started on it if you guys think it's a good enough idea? 21:07:04 so - tbh, i'm totally not the person to recommend any method of implementation 21:07:07 another is of course click count and referer info for the wiki pages, but Infrastructure could help us with this 21:07:18 since, as i always say, i can't shell script my way out of a cereal box. 21:07:38 yes, if we put out bit.ly links we can then track the amount of clicks on them 21:07:44 and they have an api too 21:07:49 rbergeron and the rest, please take a look at the website and add suggestions 21:08:05 yes - and ginns is also working on things like keyword optimization - i don't know if there is a synergy there, to use a marketing cheese word, but there may be. 21:08:18 NourishedCloud: I think it's a great idea :) maybe at some point we should actually have a Marketing-tool-code-development FAD for things like this, Identigator, Fedora-tour 21:08:26 yes 21:08:31 * mchua wonders if this might make a fun circle of hackfests for the next FUDCon 21:08:49 mchua: i think we have enough people dedicated to the cause at this point that waiting 6 months would be silly :) 21:09:04 it could provide ambassadors a reference for topics to talk about which are not hot, but important 21:09:53 * rbergeron tries to think, i'd proably do better in an email 21:09:56 we could also assign official hashtags to things too and distribute those with marketing materials 21:10:20 an ideal way to also bring together ambassadors and marketing ;-) 21:10:42 so i think we have a two-pronged thing here: one is - the social marketing piece abotu getting the word out - and ke4zvu3 has been working on that. 21:11:06 and then taking what we're sending out - seeing how it's getting out in the community, along with tracking buzz / what people are saying /etc and tracking that. 21:11:19 along with the links, tracking, that stuff. 21:11:57 to allow targetting 21:11:59 * mchua has to run, needs to make a call 21:12:03 okay. 21:12:04 well hopefully it would also have a shiny public-end for showing off the "buzz" :) 21:12:08 bye mchua! 21:12:09 right 21:12:09 * gbraad waves at mchua 21:12:13 rbergeron: can you wrangle the rest? 21:12:19 mchua: indeedlydoodly 21:12:26 * mchua will send the jzb log email first, but aye 21:12:28 thanks! 21:12:29 * mchua waves 21:13:23 it would be a good thing to point out what earlier attempts were and what could be considered. this will also give me and NourishedCloud a better overview 21:13:59 gbraad: +1 21:14:03 hmm 21:14:19 we used link tracking for the last release, didn't we? 21:14:39 or within the last six months, something added to fedoraproject.org 21:14:54 sorry, i just got disconnected 21:15:00 actually, my battery went out 21:15:14 rbergeron welcome back, didn't notice BTW 21:15:14 so, it's good you are doing this as an open marketing exercise 21:15:23 quaid: yes, we did - i don't know that we did much with it 21:15:29 in that FOSS users are a varied bunch when it comes to "we are tracking you" 21:15:32 or did much with it -consistently- i should say 21:15:45 we are tracking public communications though 21:15:45 short story for example ... 21:15:48 we have notice Luke Macken produced a lot of information already from the infra 21:16:18 once upon a time there were no solutions or attempts to track beyond what *.fedoraproject.org told us 21:16:34 i.e., Apache logs, download stats, etc. -- none of which includes data from the mirrors. 21:17:22 then there was a Fedora release and the Docs Team realized we owned /usr/share/doc/index.html, which is the page displayed by default in any web-browser 21:17:28 so - here's what i'm going to do - i'll put together an email and wiki page sort of concatenating all the information and ideas we have about social media outreach, and incoming tracking of links from social media sites and general buzz discussion. 21:17:34 because there is a lot out there 21:17:38 (FIrefox, galeon, Konq, etc.) 21:17:55 so we updated that page with links to docs, resources, etc. 21:17:59 and from that email we can try and work on figuring out what our next steps are as far as what we have, what we need to do, what tools we need / want to build 21:18:07 and somewhere in there the discussion came up of putting a tracking image on the page 21:18:14 an invisible PNG that pulled from fedoraproject.org 21:18:25 * rbergeron notes that it would be awesome to have it as a nice open platform for other projects to use as their own open social marketing toolset. 21:18:28 quaid: old trick, but quite effective 21:18:28 :D 21:18:36 a few of us were insistent that this would be perceived as a privacy violation because of the surprise factor 21:18:44 rbergeron: I was thinking that today 21:18:47 people were being tracked by Apache when the chose to go to fedoraproject.org 21:19:04 +1 to us gluing and developing open marketing tools that others can use 21:19:12 agreed 21:19:17 +1 21:19:25 great place where Fedora is/can be leading and an upstream to benefit others 21:19:42 #action rbergeron to put together information in email and on wiki about inbound / outbound social marketing usage and assessment as well as discussion about possible markers / indicators / goals / etc. 21:20:24 gbraad: NourishedCloud mind that I'm putting this story in the logs? or do you want to get it post-meeting? 21:20:24 quaid: that's my pie in the sky, along with getting every company to someday freely publish their server and pc shipment numbers so that people don't have to pay idc 6000 dollars to figure out what their market is. :) 21:21:00 someday, someday 21:21:05 quaid: I don't mind 21:21:32 no prob 21:21:43 ok 21:21:43 quaid: IMO - marketing tools is just another thing we could offer to make fedorahosted an even better place to grow innovative projects 21:22:08 so we put aside the invisible png until we had a chance to talk with people about it before implementing 21:22:14 * rbergeron notes a soapbox stuck to her feet :) 21:22:28 'people can be disappointed, but don't surprise them' 21:22:37 so you reckon we could get fedorahosted to give us hosting for an open platform for social media tracking marketing tools? 21:22:50 NourishedCloud easy to arrange 21:22:52 https://www.theopensourceway.org/wiki/Stuff_everyone_knows_and_forgets_anyway#It.27s_okay_to_be_disappointed_but_never_okay_to_be_surprised 21:23:00 well - if we build our own thing, we certainly would develop it there. 21:23:06 I don't know how picky they are :) 21:23:06 by the time we got around to the next release 21:23:08 we had better ideas 21:23:11 smolts.org for example 21:23:13 NourishedCloud can be arranged in a few seconds if people in infra respond ;) 21:23:24 which does opt-in at install and gets more than a PNG gets you 21:23:31 but the point is this: 21:23:35 hardware profile, valuable! 21:23:39 nourishedcloud: although i'd recommend trying to sort out what you want to do and getting some agreement on things before starting :) 21:23:40 gbraad: we should probably have a better idea of what exactly the design will be first 21:23:48 exactly. 21:24:01 gbraad: doesn't fedora have a hardware profile sender on the install? Other distros do 21:24:17 NourishedCloud: smolt is 21:24:18 and beyond that, if we could figure out how to duplicate it as something that other fedorahosted projects can use 21:24:36 then even extra awesome. 21:24:43 rbergeron: it may turn into several packages combined then 21:24:59 well - i think we focus on ourselves first. 21:25:09 we want to want to be able to say that we're successful :) 21:25:14 yes, but build it in a generalised way too 21:25:16 rbergeron: we will create a breakdown of tasks and a rough schedule for this as idea is formalized 21:25:48 right - so there's the stuff you guys are talking about, and then we have other peices elsewhere too - what ke4zvu3 is doing, other existing stuff, etc. 21:25:49 rbergeron: target is marketing first 21:25:57 so i'll mail that info out - 21:26:03 as everyone develops schedules and so forth 21:26:05 and their ideas 21:26:18 we can get everyone together (maybe a FAD, don't know) and see what the commonalities are 21:26:23 quaid still typing? 21:26:58 so for you - i haven't had a chance to look at the fedora buzz page yet, but i will - but some schedule / ideas / milestones etc. are helpful. 21:27:08 identifying what we want to solve, etc. 21:27:23 I'll work on expanding that over the next few days 21:27:26 sorry, IRL distractions 21:27:35 rbergeron: currently we are in brainstorm mode. suggest ideas 21:28:02 rbergeron: based on that we will make a list of features and the rest... 21:28:07 ok, ready to say my point: 21:28:15 make sure we are telling people right now 21:28:19 as loudly as possible and all over 21:28:20 well - i'll take a look and let you know what brainstorms i have 21:28:33 what we are doing, how it works, where it is, what the data is for, etc. 21:28:45 quaid: open and transparent :) 21:28:52 + proactive 21:29:03 quaid: user is in control 21:29:14 presume people won't like it, but it only really matters if they are surprised by it and haven't had a chance to say anything constructive. 21:29:27 people == a subset, but occasionally vocal :) 21:29:37 ok, that's the story I reckon, a bit scattered 21:29:48 why won't people like it? 21:30:37