20:00:28 <rbergeron> #startmeeting
20:00:28 <zodbot> Meeting started Tue Jun  8 20:00:28 2010 UTC.  The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:28 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:00:36 <rbergeron> #meetingname Fedora Marketing
20:00:36 <zodbot> The meeting name has been set to 'fedora_marketing'
20:00:47 <rbergeron> #chair mchua_afk stickster
20:00:47 <zodbot> Current chairs: mchua_afk rbergeron stickster
20:00:49 <rrix> moin
20:01:05 <rbergeron> rrix: hai - did you see the mail i sent you and zgiles?
20:01:12 <rrix> Yeah :\
20:01:15 <rbergeron> #topic Roll Call!
20:01:26 * stickster 
20:01:30 <rrix> \o.
20:01:36 <ianweller> o hai
20:01:36 * rbergeron is here
20:01:47 <rbergeron> ianweller, o wiki czar, how art thou?
20:02:01 <ianweller> decent
20:02:14 <rbergeron> #topic Agenda
20:02:24 <NourishedCloud> I'm here
20:02:30 <rbergeron> #link http://fedoraproject.org/wiki/Marketing_meetings#Agenda
20:02:57 <rbergeron> #info Agenda Items - Trac tickets, Microblogging / Twitter/ Identi.ca stuff
20:03:18 <rbergeron> stickster: I saw you added the microblogging stuff to the agenda, do we want to start there?
20:03:32 <stickster> rbergeron: It's up to you
20:03:46 * stickster can report on current status and ome suggestions
20:03:48 <stickster> *some
20:03:57 <rbergeron> that would be great.
20:04:00 <stickster> OK
20:04:01 <rbergeron> #topic Microblogging status
20:04:21 <stickster> #info We now have possession of the Twitter @fedora account, access is shared by several people through HootSuite
20:04:44 <stickster> #info We also should have the Identi.ca @fedora account returned to action soon
20:05:10 <rbergeron> woot.
20:05:12 <stickster> The latter was maintained by a community member but has been dormant since around F-11.
20:05:40 <stickster> I tried several times to contact the maintainer but with no response -- status.net has now taken over that task and I'm talking directly with their staff
20:06:28 <rrix> hmmm
20:06:42 <stickster> rbergeron: In terms of what's on the agenda
20:06:48 * rbergeron nods
20:06:59 <stickster> There were 4 questions, but I think that some of them are answered already, I can go through them one by one if it helps
20:07:00 <NourishedCloud> I can be on Identica Fedora patrol if you want, since I'm always on there...
20:07:17 <stickster> NourishedCloud: The access will be shared by a group of people, and you're welcome to be one of them!
20:07:39 <stickster> We need to avoid single points of failure, or duty rotation. Neither works well historically.
20:07:46 * NourishedCloud nods
20:08:02 <rbergeron> stickster: i think it would be helpful to go over it, briefly - mostly because we've had some talk in the channel about how to do some microblogging stuff via scripting / etc (using free tools, essentially)
20:08:04 <stickster> rrix: Did you have something to add?
20:08:13 * stickster missed the earlier hmmm
20:08:23 <rbergeron> and I think it would be helpful to clarify what our -current- plan is, so that people konw there is a current plan of attack
20:08:23 <rrix> Oh, no. :)
20:08:39 <rrix> I have had less than stellar support requests in the past from statusnet, and am quite pleased to see this actually working :)
20:08:42 <stickster> rbergeron: Do you have a link to that page?
20:08:50 <rbergeron> http://fedoraproject.org/wiki/Marketing_meetings#Agenda ?
20:08:56 <rrix> and I can throw my hat into the identi.ca ring since even NourishedCloud has to sleep :p
20:08:56 <stickster> https://fedoraproject.org/wiki/Marketing_social_networks#Strategy
20:09:02 <rbergeron> ah, that one
20:09:02 <NourishedCloud> I never sleep
20:09:07 <NourishedCloud> :P
20:09:16 <rrix> NourishedCloud: pffff
20:09:43 <rrix> nb: You around?
20:09:51 <rbergeron> #info above link has our current strategy - if we want to re-think tools, we need to have a discussion on the mailing list about what / how we'd change things, and if our requirements would still be met.
20:09:54 <stickster> rbergeron: My questions on the agenda mostly concerned transitioning use of @fedora_linux to @fedora instead.
20:10:02 <rrix> nb I think had the best plan of attack for the implementation of microblaggery
20:10:03 <rbergeron> stickster: let's cover that stuff.
20:10:06 <stickster> OK
20:10:15 <rbergeron> rrix: I think we already have a plan of attack, is the issue here ;)
20:10:30 <rbergeron> We can either backtrack, or go forward with what we have and develop something in parallel
20:10:35 <stickster> First question was whether we want to establish a FAS group or a mail alias of some sort for social networking
20:10:47 <rbergeron> the problem with the scripting thing is that I don't see it providing a solid way to provide interactivity
20:10:50 <NourishedCloud> that seems excessive
20:11:11 <rbergeron> nourishedcloud: why?
20:11:22 <stickster> The point being, we want direct notices and other contacts to go to a group of people
20:11:29 <NourishedCloud> scripting sucks, the most sucessful uses of these kinds of things are like palm on twitter who actuall interact with the community
20:12:06 <rbergeron> stickster: I agree - do we need a FAS group for that? Or will mail aliaswork just fine?
20:12:37 <stickster> rbergeron: A FAS group is easier to regulate and we get free email groups with it
20:12:45 <stickster> I think gwerra mentioned that, and he was right
20:13:10 <NourishedCloud> is it worth further splitting up power just for a microblogging account though?
20:13:17 <rbergeron> stickster: ah
20:13:33 <rbergeron> I don't know that it's a "power" thing as it is having a smaller gorup of people who are committed to responsibility
20:13:40 <stickster> NourishedCloud: It's not splitting up power, though -- it's no different than listing responsible people on a wiki, only this way something useful can be done with that list automatically :-)
20:14:06 <stickster> i.e. they all receive direct notices or other information and can act accordingly
20:14:13 <rbergeron> the more people there are "responsible" - if we have 50 people, it's harder to know who is doing what, or really, to not say - one of those other 49 people are probably taking care of it ;)
20:14:14 <NourishedCloud> fair enough
20:14:33 <stickster> The "Someone Else's Problem" problem :-)
20:14:34 <rrix> I'm gonna +1 on a microblogging FAS group
20:14:48 <NourishedCloud> I'll +1 too as long as I get to join ;)
20:14:50 <rbergeron> that said, having 50 awesomely fully committed people being totally interactive would be win, of course.
20:15:13 <stickster> OK, sounds like we're agreed on the FAS group then
20:15:15 <rbergeron> stickster: can you take the action to create a fas group?
20:15:22 <stickster> #agreed Establish FAS group for social media, called "fedora-socialmedia"
20:15:32 <stickster> #action stickster create the FAS group mentioned above
20:15:45 <rbergeron> Second item was - Who has access, and how? Document it.
20:15:59 <rrix> hmmm
20:16:16 <stickster> rrix: Out with it, young man.
20:16:21 <rrix> Should it just be on an "ask and you shall receive so long as you have some sort of Fedora karma?"
20:16:28 <rrix> stickster: yessir!
20:16:37 <NourishedCloud> Fedora karma --> Fedorma
20:16:43 <NourishedCloud> sounds like a curry
20:16:47 <stickster> rrix: I think membership should be pretty open
20:16:48 <rrix> Fedharma?
20:16:58 <rrix> stickster: +1, but not 'too' open
20:17:12 <stickster> Remember that membership in this group gives you notices but it doesn't 'do' anything with regard to the social media services themselves.
20:17:15 <NourishedCloud> should being an active member of the marketing team be a stipulation?
20:17:40 <stickster> NourishedCloud: For a reasonably broad definition of 'active', sure.
20:17:55 <NourishedCloud> yes
20:18:01 <rrix> what about ambassadors?
20:18:02 <stickster> Mainly we're just interested in knowing who cares enough about getting social media notices to actually help manage the feeds.
20:18:07 <rbergeron> yes - what about ambassadors?
20:18:21 <rrix> do they get to embrace the goodness?
20:18:31 <NourishedCloud> hmm
20:18:32 <stickster> rrix: We're not going to add all the ambassadors to the group.
20:18:41 <stickster> That's a tragedy of the commons waiting to happen.
20:18:41 <rrix> well, of course :))
20:18:49 <stickster> rrix: What are you suggesting exactly?
20:18:51 <rbergeron> I think he's saying - could someone in ambassadors, but not marketing
20:19:09 <rrix> but not all ambassadors are marketers, but some could be really … useful? in fedora-socialmedia
20:19:19 <rrix> eggsactly
20:19:20 <rbergeron> A lot of ambassadors do great work in outreach.
20:19:31 <stickster> Yes, but they also have their own feeds in that regard
20:19:36 <stickster> We can easily follow them and retweet :-)
20:20:03 <rrix> this is true
20:20:09 <stickster> Ambassadors have a lot on their plates already, we don't want to spread people too thin. This is really Marketing work.
20:20:15 <rbergeron> I think having it stay sort of marketing-group people means we can at least have discussions re: social media
20:20:18 <rbergeron> during meetings
20:20:20 <stickster> Yes.
20:20:25 <rrix> good point
20:20:29 <rbergeron> without having to feel like we're missing people - or schedule a separate meeting
20:20:39 <stickster> OK, so what I'm proposing is to add the group of people currently listed on the wiki to the FAS group.
20:21:06 <stickster> https://fedoraproject.org/wiki/Twitter_SOP#Access
20:21:11 <NourishedCloud> and me, since I don't know where the wiki page is
20:21:17 <stickster> NourishedCloud: ^^
20:21:18 <NourishedCloud> ah
20:21:25 * rrix addself
20:21:45 <stickster> rbergeron: I'm going to make you, Matias, and Jonathan sponsors in that group as well.
20:21:56 <rrix> hmm
20:22:04 <rbergeron> stickster: do we want to make marketing a dependency to being added to fedora-socialmedia FAS group?
20:22:11 <rbergeron> in FAS, i mean
20:22:27 <rbergeron> just to avoid any issues - or having people have to double check, etc.
20:22:52 <rrix> or having random newbies who just registered pick the ten shiniest groups to register for without looking at their wiki pages ;)
20:23:04 <stickster> It can be
20:23:15 <stickster> rrix: Although we're looking at other ways to solve that problem, making FAS a little less self-service
20:23:26 <rrix> that would be nice
20:23:26 <stickster> rbergeron: OK, so we'll make marketing a requirement for that group
20:23:52 <rbergeron> #agreed make marketing a FAS dependency for being in fedora-socialmedia
20:24:35 <stickster> #agreed Add everyone currently listed on [[Twitter SOP]] wiki page to group, rbergeron, Matias, and ke4zvu3 as sponsors to avoid siloing
20:24:50 <stickster> OK, that brings us to transitioning users
20:25:46 <rbergeron> stickster: are we going to document the FAS group bits on https://fedoraproject.org/wiki/Twitter_SOP#Access when the group is set up? I can take that on.
20:25:57 <stickster> rbergeron: That would be TREMENDOUSLY AWESOME.
20:26:32 <rbergeron> #action rbergeron to document access information WRT FAS groups on https://fedoraproject.org/wiki/Twitter_SOP#Access
20:26:36 <stickster> cool
20:27:18 <rbergeron> So - I think wrt transitioning users - we've agreed that we will start that -after- RH summit
20:27:23 <rbergeron> Which is june 22 - 25, IIRC
20:27:29 <stickster> I think that's the best idea, really
20:27:35 <rbergeron> Yes, I agree
20:27:37 <stickster> Because of item #3
20:27:47 <rbergeron> The -how- is the question ;)
20:28:00 <stickster> I had some conversations with social media mavens who suggested that the easiest way to transition in our case was (1) send out a few regularly spaced notices to follow @twitter, then (2) send a last notice to @fedora_linux saying "You can now follow us on @fedora, see you there!"
20:28:26 <ke4zvu3> #agreed yeah that seems pretty logical, nothing complex
20:28:37 <rbergeron> yay, ke4zvu3 ;)
20:28:55 <stickster> Moving people en masse *might* be possible -- but it also gets us into the risky territory of changing people's followings without asking
20:29:09 <stickster> I don't want Fedora to have the PR of Facebook  :-)
20:29:11 <rbergeron> And - keep tweeting the same thing to both @fedora and @fedora_linux? or....
20:29:12 <ke4zvu3> stickster: how is even possible to change what other people follow ?
20:29:21 <stickster> rbergeron: No, stop using @fedora_linux entirely.
20:29:38 <rrix> ke4zvu3: going through Twitter support
20:29:46 <stickster> ke4zvu3: Really, only by actually changing @fedora_linux to @fedora
20:29:51 <ke4zvu3> rrix: oh. wow. yeah. that might be overkill.
20:30:13 <ke4zvu3> stickster: yeah. perhaps bset to own both so someone won't come back and squat @fedora_linux later
20:30:22 <ke4zvu3> s/bset/best
20:30:30 <stickster> ke4zvu3: I don't think it's a big worry -- Matias owns that, and he's a friend
20:30:42 <ke4zvu3> #agreed
20:30:51 <stickster> OK, so
20:30:57 * rrix -> wake-up business, coffee and whatnot, bbl
20:31:09 <stickster> #agreed We'll wait until after RH Summit to transition accounts, by which time we should have Twitter and Identi.ca with the same name (yay!)
20:32:04 <stickster> #agreed We'll send out a few regularly spaced notices to follow @fedora, and then send a last notice to @fedora_linux saying "You can now follow us on @fedora"
20:32:17 <stickster> We can also ask Matias to put that in the profile for the @fedora_linux account
20:32:35 <rbergeron> yes, let's make a note to actually do that
20:32:41 <rbergeron> if he's willing of course :)
20:32:42 <stickster> rbergeron: Can I have you echo that stuff into a ticket that we can pull after the RH Summit?
20:32:55 <rbergeron> yup.
20:32:57 <stickster> So we'll revisit this issue in about three weeks?
20:33:03 <stickster> 2010-06-29 meeting
20:33:28 <rbergeron> #action rbergeron to put twitter @fedora_linux ramp-down info in ticket, will revisit details from this meeting at 2010-06-29 meeting.
20:33:33 <stickster> Cool!
20:33:56 <stickster> I also wanted to note... We're going to try to send notices via Identi.ca and hook Twitter to that account
20:33:59 <stickster> So we're being as free as possible
20:34:07 <rbergeron> stickster: cool.
20:34:10 <stickster> The HootSuite account is still useful because it allows us to share access among many people
20:34:32 <stickster> There aren't good tools in the 100% FOSS side for this yet, but at some point we hope there will be and we can adapt as needed.
20:34:44 <NourishedCloud> build one ;)
20:34:52 <stickster> NourishedCloud: You're talking to the wrong guy for that! :-D
20:35:01 * rbergeron hands stickster a cup o' spare time
20:35:07 <stickster> Hey, thanks!
20:35:12 <rbergeron> oh, crap, i needed that!
20:35:13 <rbergeron> ;)
20:36:36 <stickster> Darn it
20:36:42 <rbergeron> :)
20:36:46 <stickster> I had another point I wanted to throw in about microblogging but I've forgotten it now.
20:36:50 <rbergeron> Okay. Does that wrap up the microblogging questions?
20:36:51 <rbergeron> oh.
20:36:59 <stickster> Go ahead, it will come back up at some point.
20:37:01 * stickster eof
20:37:03 * rbergeron tells stickster to think of other things, and it will immediately come back to you.
20:37:24 <rbergeron> stickster: have you played around at all with hootsuite yet?
20:37:33 <stickster> I have
20:37:45 <rbergeron> I have not, short of looking at it.
20:38:17 <stickster> It's very easy to use
20:38:18 <rbergeron> ie: no playing or retweeting yet
20:38:32 <stickster> rbergeron: I'll show you at SELF if you want
20:38:39 <rbergeron> stickster: that would be awesome
20:38:44 <stickster> We can move on if you like, there's more agenda
20:38:48 <stickster> Sorry for taking up so much of it
20:38:58 <rbergeron> no problem. Needed to be taken care of ;)
20:39:17 <rbergeron> #topic Marketing Trac tickets
20:39:41 <rbergeron> #link https://fedorahosted.org/marketing-team/query?status=new&status=assigned&status=reopened&keywords=%7Emeeting&order=priority
20:39:47 <rbergeron> oh, dear that's quite a link
20:40:14 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/33 - Wiki pages on Free Media distribution
20:40:46 <rbergeron> #info yn1v has been reassigned this ticket as he offered to look into it - he can't get around to it for a few weeks, so that is fine.
20:41:00 <rbergeron> #action rbergeron to take https://fedorahosted.org/marketing-team/ticket/33 meeting out of keywords for a few weeks, then revisit status.
20:41:30 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/35 - Marketing / Ambassadors "stuff" - release events, etc.
20:42:21 <rbergeron> I need to follow up with Ambassadors on this stuff; most of the things I worked on at FADNA were related to marketing collateral / deliverables
20:42:25 <NourishedCloud> F13 has already been released..?
20:42:32 <rbergeron> it's a ticket that got moved over.
20:42:39 <rbergeron> From F12, actually.
20:42:44 <rbergeron> opened up 9 months ago. ;)
20:43:01 <NourishedCloud> yes but what work needs to be done on that issue
20:43:06 <rbergeron> #action rbergeron needs to follow up on ticket 35
20:43:17 <stickster> What's required to follow up?
20:43:49 <stickster> NourishedCloud: are you interested in helping with that? rbergeron, is that possible?
20:43:51 <rbergeron> stickster: I think we need a plan of attack for having more promotions for release events.
20:44:09 <rbergeron> s/more/some in general - posters, press / blogs, etc. Something.
20:44:16 <stickster> NourishedCloud: Interested?
20:44:24 <rbergeron> More collaboration between ambassadors and marketing on this stuff -
20:44:30 <NourishedCloud> I would like to help with that if I knew exactly what needs doing :) we need to develop a better action plan for release deliverables?
20:44:38 <stickster> NourishedCloud: Not for deliverables
20:44:43 <rbergeron> This is more specific to release events
20:44:49 <rbergeron> i think there are a few things here:
20:44:54 <NourishedCloud> providing resources for release events?
20:45:09 <stickster> For release events -- the gatherings in specific towns or localities where Ambassadors give out a Fedora release, have a little party to celebrate the new release
20:45:12 <rbergeron> #1 - We need to figure out a way to get the word from ambassadors to marketing that people are doing release events
20:45:24 <rbergeron> so that we can promote - via microblog, blog, whatever.
20:45:38 <rbergeron> #2 - If they need posters, signage, etc. - we can help coordinate those items with design
20:45:39 <NourishedCloud> Sure, I'll help out with that :)
20:45:52 <rbergeron> but we need to have them ready far prior to when release parties actually occur.
20:45:56 <stickster> rbergeron: Brilliant summary of what's needed.
20:46:06 <rbergeron> I'll just paste that into the ticket. ;)
20:46:08 <stickster> which means now is a *great* time for NourishedCloud to head this up, if I read you right :-)
20:46:28 <stickster> He can pick up lessons from what just happened, and apply that to the plan for F14
20:46:37 * NourishedCloud nods
20:46:57 <rbergeron> nourishedcloud: in fas you're....
20:47:00 <NourishedCloud> reality
20:47:01 <rbergeron> reality?
20:47:02 <rbergeron> yes
20:47:11 <stickster> NourishedCloud: Shall we check in with you in a week for progress, then? Two weeks?
20:47:28 <rbergeron> and any questions discussion - take to the list ;)
20:47:32 <NourishedCloud> A week will be alright
20:47:34 <rbergeron> questions or discussion
20:48:11 <rbergeron> Cool!
20:48:15 <rbergeron> It's been assigned.
20:48:23 <NourishedCloud> thanks :-)
20:48:29 <rbergeron> #info Release Events ticket #35 has been sent to Nourishedcloud.
20:48:42 <rbergeron> #action Nourishedcloud to follow up on trac ticket #35 next week
20:49:04 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/107 - Brand Book / Story book
20:49:08 <rbergeron> ianweller: ping
20:49:19 <ianweller> rbergeron: hi
20:49:31 <rbergeron> ianweller: have you harassed the great spevack about a brand book fad ;)
20:49:55 <ianweller> we haven't talked too much about it, i'll talk with him tomorrow
20:50:14 <rbergeron> ianweller: we can do it together at SELF if that's easier
20:50:26 <ianweller> rblol if we have time
20:50:27 * rbergeron grins
20:50:29 <rbergeron> lol
20:50:30 <rbergeron> yes
20:50:32 <rbergeron> indeed
20:50:45 <ianweller> i know that having it around the summit would likely conflict with KU new student orientation
20:50:55 <rbergeron> #info Ticket 107 - still in talking about the brand book FAD.
20:51:07 <rbergeron> ianweller: okay, let's scratch that idea then - we can do it elsewhere, some other time
20:51:24 <ianweller> in other news, guidelines are coming along
20:51:37 <ianweller> ETA is 12 daysish
20:51:44 <rbergeron> ianweller: awesome.
20:51:53 <NourishedCloud> guidelines for what?
20:52:06 <rbergeron> Branding / Logo usage / etc.
20:52:10 <NourishedCloud> ah
20:52:19 <rbergeron> colors
20:52:22 <rbergeron> whitespace
20:52:24 <ianweller> fonts are still up in the air
20:52:31 <rbergeron> no putting the fedora logo on red hats
20:52:33 <rbergeron> etc ;)
20:52:38 <ianweller> but everything else is relatively under control
20:53:28 <rbergeron> ianweller: cool, thanks for the update - I know the branding / guidelines stuff isn't a marketing-driven thing but we do appreciate the updates :)
20:53:46 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/114 - Marketing Postmortem
20:54:13 <rbergeron> sooo - i still haven't gotten all of this stuff loaded into the wiki yet from the meeting last week, it's on my plate for airplane time and such.
20:54:24 <rbergeron> #action rbergeron still needs to put marketing postmortem stuff in wiki
20:54:49 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/37 - Release Events Poster
20:55:13 <rbergeron> Nourishedcloud, Do you want to take this on or have me add this stuff to the other release events ticket that you just picked up?
20:55:28 <rbergeron> We'd realistically be having design do this actual work - but we'd need to add it as part of the process to hand off
20:55:54 <rbergeron> Since it's basically part of that other ticket.
20:56:07 <rbergeron> I'm not actually sure why it's somewhat duplicated - I guess one is related to process.
20:56:10 <NourishedCloud> the work for this ticket being what? adding it to the plan developed for the other ticket I took?
20:56:24 <rbergeron> Actually... hrmmmmmm
20:56:46 <rbergeron> Well - part of what we talked about was making sure that ambassadors have the collateral they'd need, including posters / signage
20:56:58 <rbergeron> But we wouldn't actually be making the signage - that would get sent to design
20:57:05 <rbergeron> I'll just hang onto it for now
20:57:14 <NourishedCloud> fair enough
20:57:22 <rbergeron> Until we decide... what we're doing ;)
20:57:38 <stickster> rbergeron: Once we do that, we do have the ability to schedule a task for this or anything else for release events
20:57:41 <rbergeron> #topic https://fedorahosted.org/marketing-team/ticket/63 - generic Fedora slogan
20:57:49 <rbergeron> stickster: exactly
20:57:55 <rbergeron> stickster: have you seen this?
20:57:58 <rbergeron> ticket?
20:58:03 <stickster> I have, I think I was there when it was filed.
20:58:18 <stickster> It concerns our mockup
20:58:32 <stickster> #link http://duffy.fedorapeople.org/temp/woot/page1.png <-- mockup for next-generation main fp.o page
20:59:17 <NourishedCloud> what's the release slogan selection method (since it says to use one similar to that)?
20:59:18 <stickster> #info The top has a generic slogan -- it is just filler right now. We haven't decided whether we want to put a release-specific slogan there, or have something more general so we don't need to do another banner each release.
20:59:27 <stickster> NourishedCloud: It's on the wiki, search for 'slogan' for best results
20:59:44 <NourishedCloud> stickster: thanks
20:59:55 <rbergeron> We could just, you know, use "rock it" forever. I wouldn't be opposed to that. ;)
20:59:58 * rbergeron kids
21:00:01 <stickster> Heh
21:00:19 <stickster> rbergeron: So the question to ask first is, whether Design cares about the extra work of changing that slogan each release.
21:00:34 <rbergeron> right
21:00:34 <stickster> There's something to be said for a site where the biggest message is always fresh
21:00:46 <stickster> But at the same time, we don't want to add another dependency/task if we don't have to.
21:00:50 * stickster looks at clock
21:01:02 * rbergeron doesn't think there's anything wrong with the more permanent pseudo-slogan of freedom, friends, features, first
21:01:03 <stickster> rbergeron: Why don't you lay this one on me
21:01:14 <rbergeron> because I think a lot of people associate that.
21:01:29 <rbergeron> having two perma-slogan lines seems... yeah
21:01:29 <stickster> I have to talk to mizmo and the Design team about our next steps for the main fp.o site, this is just one factor we need to consider
21:01:34 <rbergeron> okay.
21:01:54 <rbergeron> #action rbergeron to assign slogan ticket to stickster
21:02:03 <stickster> I just took it :-)
21:02:09 <rbergeron> Sorry, can not save your changes. This ticket has been modified by someone else since you started
21:02:12 <rbergeron> ;)
21:02:13 <rbergeron> indeed, you have!
21:02:14 <stickster> hee hee
21:02:47 <rbergeron> Okay.
21:02:56 <rbergeron> mmm, only 2 minutes past. Stickster, anything else?
21:03:02 <rbergeron> #topic AOB? open floor!
21:03:05 <stickster> Nothing here
21:03:10 * stickster is hastily getting ready for SELF
21:03:15 <NourishedCloud> nope
21:03:24 <rbergeron> #info Fedora Insight - Meeting notice - rescheduled for tomorrow. Wed, 2010-06-09 at 1800 UTC (2:00pm US-eastern)
21:03:46 * rbergeron is hastily doing laundry for SELF, as in, herself and boy for self, and kids for trip to grandma's.
21:04:29 <rbergeron> okeedokee then.
21:04:40 * rbergeron counts down in her head to end of meeting
21:04:45 <rbergeron> 28....
21:04:47 <rbergeron> 15....
21:04:49 <rbergeron> 5...
21:04:59 <rbergeron> #endmeeting