18:00:57 <stickster> #startmeeting Fedora Insight
18:00:57 <zodbot> Meeting started Thu Apr  1 18:00:57 2010 UTC.  The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:59 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:01:07 <stickster> #meetingname Fedora Insight
18:01:07 <zodbot> The meeting name has been set to 'fedora_insight'
18:01:13 <stickster> #topic Roll call
18:01:15 * stickster 
18:01:20 * ke4qqq 
18:01:26 * GeroldKa geroldka
18:01:30 <pcalarco> .fasinfo pcalarco
18:01:31 <zodbot> pcalarco: User: pcalarco, Name: Pascal Vincent Calarco, email: pcalarco@nd.edu, Creation: 2007-12-17, IRC Nick: , Timezone: US/Eastern, Locale: en, Extension: 5102791, GPG key ID: C7E2DF87, Status: active
18:01:34 <zodbot> pcalarco: Approved Groups: marketing cla_fedora cla_done ambassadors @news
18:01:51 <kushal> kushal
18:02:11 * rbergeron is here
18:02:16 <rbergeron> WHEW
18:02:48 * stickster gives another 30 sec for roll call
18:03:17 <stickster> #info present stickster ke4qqq GeroldKa pcalarco kushal rbergeron
18:03:21 <nmarques> I have to bail, sry, I can't attend, already had something scheduled for 19:15
18:03:27 * stickster wonders if mchua is around perchance... I know she was really busy
18:03:29 <stickster> nmarques: Thanks
18:03:30 <stickster> np
18:03:57 <stickster> OK, might as well push on then
18:04:14 <stickster> #topic Intro (very short!)
18:04:39 <stickster> OK, last night pcalarco, rbergeron and I hammered out this agenda to see if we can't get things on track and maximize our impact over the next few weeks in an attempt to get to production readiness
18:04:56 <stickster> If you see things that need to be added, let's hold them for the list and the next meeting agenda.
18:05:01 <stickster> It's pretty aggressive already!
18:05:11 <stickster> any objections there?
18:05:18 <pcalarco> #link https://fedoraproject.org/wiki/Fedora_Insight#Meeting_agenda:_2010-04-01
18:05:37 * rbergeron just updated meeting agenda with ticket for fasauth status if anyone needs to refresh, fyi
18:05:39 <stickster> #chair pcalarco rbergeron mchua
18:05:40 <zodbot> Current chairs: mchua pcalarco rbergeron stickster
18:05:49 <stickster> Great rbergeron! Thanks.
18:05:54 <stickster> #topic Logistics
18:06:21 <stickster> #link https://fedorahosted.org/marketing-team/ticket/109 -- need to test FASauth
18:06:34 * hiemanshu is kinda here
18:06:40 <stickster> Hi hiemanshu!
18:06:48 <stickster> ke4qqq: What can you tell us about that ticket?
18:06:59 <hiemanshu> stickster: I am going to push pagemaster package today
18:07:05 <ke4qqq> itbegins hacked on it last night with mchua
18:07:05 <hiemanshu> stickster: my home system is down
18:07:17 <ke4qqq> I grabbed what I believe to be "all the changes"
18:07:30 <ke4qqq> and committed that to git
18:07:35 <ke4qqq> and branched 0.3
18:07:41 <ke4qqq> and churned out a new srpm
18:07:49 <rbergeron> and that fixes... the fasauth admin thing?
18:07:57 <ke4qqq> and then pushed srpm to jds2001 who pushed it into infras repo
18:08:04 <ke4qqq> rbergeron: that's my understanding
18:08:06 <stickster> OK, so it's available in infra repo
18:08:08 <ke4qqq> I have done zero testing
18:08:12 <rbergeron> or does that add us some capability to have editors in FAS link to editors group in zikula?
18:08:26 <ke4qqq> I thought that was the fix we were looking for rbergeron
18:08:30 <rbergeron> itbegins implied that would take some hardcoding
18:08:43 <pcalarco> do we need to establish a new test FAS group and link it to this to do some further testing?
18:08:46 <ke4qqq> my understanding is that it's in a config file
18:08:51 <ke4qqq> pcalarco: no it already exists
18:09:15 <stickster> ke4qqq: OK, so what we need in that ticket is specific information on how to secure the working copy and test the new package
18:09:37 <ke4qqq> yes - and I don't have it off the top of my head - I don't recall where the config is stored
18:09:41 <stickster> Unless I'm totally alone in looking at that ticket and saying, "I have no idea where to start doing this."
18:09:55 <stickster> ke4qqq: Do you mean, puppetize it?
18:10:04 <ke4qqq> though the module is stored in %{_datadir}/zikula/modules/AuthFAS
18:10:04 <stickster> ke4qqq: Or are you talking about some other type of securing?
18:10:26 <ke4qqq> I don't want to break it in the course of our testing
18:10:38 <ke4qqq> though we shouldn't break it.
18:10:45 <stickster> ke4qqq: So you mean, puppetize the configuration so that in the event it breaks we can restore it?
18:10:48 * stickster looking for details, please
18:10:59 <ke4qqq> more back it up so we can puppetize
18:11:02 <stickster> OK
18:11:16 <stickster> ke4qqq: So wouldn't it be sufficient to simply put it in a fedorapeople.org space somewhere we can reach it?
18:11:26 <stickster> If needed, restore from <URL>
18:11:28 <ke4qqq> stickster: that'd be fine with me - I just want to find all the pieces first
18:11:33 <stickster> OK
18:11:50 <ke4qqq> or someone to find them all
18:11:54 <stickster> ke4qqq: So would you agree the next action is "Locate all the pieces of changeable configuration and back them up"
18:11:54 <stickster> ?
18:11:55 <ke4qqq> doesn't have to be me
18:12:00 <ke4qqq> stickster: yes
18:12:14 <ke4qqq> and tack on as well as the module itself
18:12:24 <ke4qqq> in case there are changes that have been made that we don't know about
18:12:33 <stickster> #action stickster ke4qqq itbegins Locate all pieces of changeable configuration and back them up
18:12:42 <stickster> ke4qqq: If it's other pieces of the module, wouldn't rpm -V tell us that?
18:13:13 <ke4qqq> stickster: it should - but seems like there might be a config file we don't have 'upstream' yet
18:13:30 <stickster> ke4qqq: Who would be able to discern that?
18:13:42 <ke4qqq> itbegins I'd imagine
18:13:45 <stickster> OK.
18:14:05 * ke4qqq notes drak also volunteered $army of devs from zikula to help us if we need it
18:14:07 <stickster> When you say "upstream" you mean configurations that should be part of our SRPM?
18:14:16 <stickster> Or should they be somewhere even more upstream?
18:14:28 <ke4qqq> stickster: yes - at least config file - and upstream in our git repo is fine
18:14:31 <stickster> OK
18:14:33 * rbergeron plays timekeeper and notes we're past 10 minutes
18:14:42 <rbergeron> just to FYI :)
18:14:44 <stickster> Thanks rbergeron -- I suspect we're going to go over, I'll hit that in a sec :-)
18:14:51 <stickster> much appreciated, TRULY.
18:15:02 <rbergeron> k - beta meeting is cancelled so i think that frees a lot of us up if we do go over
18:15:17 <stickster> #action itbegins Help us figure out if there is any configuration that is not yet upstream in fasauth module that needs to be
18:15:27 <stickster> #info itbegins will be around today ~2000 UTC at last report
18:15:38 <stickster> ke4qqq: Any chance you'll be around at some point after that?
18:15:53 * stickster knows ke4qqq has a $DAYJOB and can't spend all his time with us, as much as we'd love it :-)
18:16:15 <ke4qqq> I'll do my best to be
18:16:25 <stickster> #chair ke4qqq
18:16:26 <zodbot> Current chairs: ke4qqq mchua pcalarco rbergeron stickster
18:16:30 <stickster> That's all you can do!
18:17:03 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/2006 <-- Create forms in Zikula on staging for FI content workflow
18:17:19 <rbergeron> who owns this ticket? it's currently assigned to "webmaster"
18:17:21 <stickster> So we have these forms in pt6 right now, but not yet on staging?
18:17:59 <pcalarco> that's me; I think this ticket will be fulfilled when we move ove packages and DB to staging
18:18:21 <pcalarco> similar to ticket #2007
18:18:27 <stickster> pcalarco: ke4qqq: Which I'm guessing -- happens when we finish FASauth testing and all the other fiddly bits we're still figuring out.
18:18:44 <stickster> Once those happen, we can recreate from scratch on a true staging instance. Correct?
18:18:47 <ke4qqq> stickster: that's the only blocker I am aware of
18:18:51 <stickster> OK.
18:18:51 <pcalarco> stickster: correct, yes
18:18:54 <stickster> Thanks guys!
18:18:57 <stickster> You make me feel so confident.
18:18:58 <stickster> :-)
18:19:14 <pcalarco> stickster: :)
18:19:19 * rbergeron refrains from "secret deodorant" jokes
18:19:22 <stickster> #info We can deal with this after FASauth and any other leftover bits are in place. Not a technical challenge.
18:19:25 <stickster> heh
18:19:31 <rbergeron> ;)
18:19:33 <stickster> #topic Meeting OVERTIME WARNING
18:19:42 <stickster> OK, I detect with my spidey sense we're not going to make it in 60 minutes.
18:19:53 <stickster> Is there anyone who strenuously objects to running until :30 past the hour?
18:20:06 <stickster> I believe this is the *only* time we will have to do this, if we are careful and attentive :-)
18:20:15 <pcalarco> I can stay as long as needed
18:20:31 * rbergeron can stay
18:20:50 <stickster> #info The F13 Beta readiness meeting is postponed until next week 2010-04-08 UTC 1900, so hopefully less conflict
18:20:50 * ke4qqq can stay I think
18:21:34 <stickster> OK. Subject to all other pressures of course. You guys are here out of love and dedication, and I appreciate it. If something gets in the way, don't let us keep you.
18:21:57 <stickster> #agreed meeting will run until 1930 UTC.
18:22:00 <stickster> #undo
18:22:00 <zodbot> Removing item from minutes: <MeetBot.items.Agreed object at 0x2b03b17d12d0>
18:22:03 <stickster> #agreed meeting will run until 1930 UTC if needed.
18:22:12 <stickster> #topic Theming and Design
18:22:26 <stickster> #link https://fedorahosted.org/design-team/ticket/66 <-- FI Zikula skin
18:23:06 <stickster> hiemanshu: The latest comment in that ticket asks if your questions are answered about "userprofile".
18:23:46 * stickster not sure hiemanshu is around now
18:23:48 <hiemanshu> stickster: yes, I am not at my home computer, so I cant really check
18:23:56 <hiemanshu> if I had the fix
18:24:25 <stickster> hiemanshu: Do we need to ask itbegins about this?
18:24:46 <hiemanshu> stickster: not for now
18:25:11 <stickster> hiemanshu: This is marked as "critical"
18:25:25 <stickster> We'll have itbegins here later, so if we can use his time today to help move things ahead, we'll be glad to do it.
18:25:42 <hiemanshu> stickster: yes, I will need to get home to check, I am using my uncles computer, no ssh key here
18:25:46 <stickster> If you have to do some more work personally to move things ahead, that's fine too
18:25:49 <stickster> OK
18:26:24 <stickster> I just wanted to see whether this was something you needed to do personally -- I want you to feel like you can get help, if you want it
18:26:25 <hiemanshu> stickster: I did understand it, so you can say question is answered
18:26:27 <stickster> OK
18:26:34 <stickster> Great, because I didn't understand it! :-D
18:26:39 <hiemanshu> I did
18:26:46 <hiemanshu> it has to do with templates :)
18:26:48 <stickster> Awesome
18:26:53 <stickster> hiemanshu: Feel free to answer in that ticket then
18:26:56 * rbergeron is glad everyone else knows what's up :)
18:26:58 <hiemanshu> sure I will
18:27:11 <stickster> #info hiemanshu thinks he has the answer, and can move forward with user profile links as needed
18:27:38 * hiemanshu is helping uncle setup fedora
18:27:41 <stickster> hiemanshu: And earlier, you said you'd be pushing out a pagemaster package -- when you get back to a computer you can use :-)
18:27:49 <stickster> Thanks for giving that status earlier, much appreciated!
18:28:03 <hiemanshu> stickster: yup, I just need to get home
18:28:08 <stickster> #action hiemanshu to push out a pagemaster package tonight after he gets home
18:28:41 <stickster> hiemanshu: While I'm busy bothering you :-)
18:28:47 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/2007
18:28:54 <hiemanshu> also with the dates slipping we have an extra week to work
18:28:58 <stickster> #info Theming for FI on staging server
18:29:06 <stickster> hiemanshu: Yes, for us it's kind of a blessing in disguise!
18:29:15 <hiemanshu> stickster: well I completed this
18:29:18 <stickster> hiemanshu: You indicated that ticket 2007 can be closed?
18:29:20 <hiemanshu> the theme has been moved
18:29:27 <hiemanshu> we need to move the DB
18:29:28 <stickster> Awesome, want to close that ticket, or shall I?
18:29:31 <hiemanshu> to get the same structure
18:29:35 <hiemanshu> I am just closing it
18:29:40 <stickster> Oh super
18:29:50 <stickster> hiemanshu: Will you be moving the DB then?
18:29:54 <hiemanshu> stickster: yes
18:30:07 <hiemanshu> stickster: once, we have FASauth etc setup the way we want
18:30:12 <stickster> Makes sense
18:30:16 <pcalarco> that should be after we complete all the theming as well
18:30:45 <stickster> #action hiemanshu will move DB to staging once the FASauth and theming on the pt6 server are done. That will duplicate everything needed.
18:30:56 <stickster> hiemanshu: ^^ does what I just wrote make sense and sound correct?
18:31:02 <hiemanshu> stickster: yup
18:31:04 <stickster> awesome!
18:31:10 * stickster getting smarter by the second thanks to you guys
18:31:25 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/2009
18:31:47 <stickster> So this seems like something that hiemanshu can do *when he gets some time*, but it would be good to find help with it.
18:32:02 <pcalarco> this one I think is ready for some more folks to start subscribing to the RSS feed and verify that it looks as expected in their clients
18:32:09 <pcalarco> #link http://publictest6.fedoraproject.org/zikula/index.php?theme=RSS
18:32:16 <stickster> thanks pcalarco, great link!
18:32:41 <hiemanshu> stickster: yes, I am going do this along with when I update the theme package with the changes I make for FWN later this week
18:33:03 <hiemanshu> that dint sound right, but I hope you understand what I meant
18:33:15 <stickster> hiemanshu: I did, thank you very much sir!
18:33:18 <pcalarco> hiemanshu: changes for the RSS template for FWN pubtype?
18:33:50 <hiemanshu> pcalarco: nope, it will be a part of the fedora theme package, which I will repackage, after FWN pubtype is fixed
18:34:01 * stickster just put RSS in his Google Reader and it seems fairly straightforward. May need a "Click here to read more" link, but that's probably a 30-sec operation to add.
18:34:53 <stickster> #info RSS template will be part of the Fedora theme package and will automatically come over to staging as well
18:35:04 <stickster> Anything else on this topic? Questions, concerns?
18:35:17 <hiemanshu> yes, did you order a bigger boat for more people to join?
18:35:32 * rbergeron just lost internet - on via slowberry
18:35:42 <pcalarco> the only thing to note is that the RSS feeds work for general news pubtype now but not FWN pubtype
18:35:48 * hiemanshu looks innocently at stickster
18:35:52 <stickster> #action stickster Get paperwork going for bigger boat for community people to join
18:36:04 <stickster> #action stickster look for loose change in sofa cushions too
18:36:20 <hiemanshu> #info hiemanshu to check stickster works properly
18:36:37 <hiemanshu> pcalarco: right now I see it empty?
18:36:41 <pcalarco> itbegins and I ran out of time on that, so I will ask him when he joins us at 2000
18:36:54 <stickster> pcalarco: hiemanshu: OK, let's pursue that outside this meeting then
18:37:08 <stickster> #action pcalarco hiemanshu Check to see that RSS feeds are working for both (all) pubtypes properly
18:37:16 <stickster> If needed you can file a separate ticket for it
18:37:33 <hiemanshu> I wont be here for long, have college to attend tomorrow
18:37:48 <stickster> Thanks hiemanshu -- noted. You are awesome and we appreciate all your help!!!
18:37:56 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/2057
18:38:10 <stickster> I think this is the last ticket for design/thee
18:38:11 <stickster> *theme
18:38:20 <stickster> Weighting doesn't seem to work properly.
18:38:26 <stickster> Can we get itbegins to look at this today?
18:38:45 <hiemanshu> brb need to reboot
18:38:54 * stickster wants to make sure that when itbegins arrives, we have a clear set of actionable tasks he can help us with
18:39:03 <pcalarco> right.  Itbegins and I were working on this too, and I can't seem to make the FWN articles appear in an explicit order with the weighting, so this is something for me to follow up with hiom too
18:39:10 <stickster> pcalarco: OK, let's add that here
18:39:39 <stickster> #action itbegins Debug article weighting with help from pcalarco
18:39:53 <stickster> I think that brings us to the end of theming and design.
18:40:08 <pcalarco> https://fedorahosted.org/fedora-infrastructure/ticket/2010
18:40:16 <pcalarco> we skipped this one
18:40:17 <stickster> Oops, did I miss one?
18:40:19 <stickster> sorry!
18:40:34 <pcalarco> #link https://fedorahosted.org/fedora-infrastructure/ticket/2010
18:40:36 <stickster> #link https://fedorahosted.org/fedora-infrastructure/ticket/2010 <-- Pagemaster customization for FWN pubtype
18:40:40 <stickster> #undo
18:40:40 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x2b03b1b2a450>
18:40:48 <pcalarco> I also need to follow up with itbegins on this too
18:41:25 <pcalarco> we may or may not be able to accommodate this change
18:41:37 <pcalarco> but it would make editors lives easier
18:41:47 <stickster> OK, this seems like an open question where we need him to answer and we'll record and fix appropriately
18:41:57 <pcalarco> stickster: yes
18:42:09 <stickster> #action itbegins Tell us whether we can swap fields as shown in ticket 2010, and if so, itbegins and pcalarco will set up appropriately
18:42:17 * ke4qqq sees lots of customizations going in - how do we ensure that we capture all of this and get it puppetized?
18:42:42 <stickster> ke4qqq: It will all be contained in the theming or DB that's packaged
18:42:58 <ke4qqq> ok
18:43:03 <stickster> That's how I understand these customizations to work.
18:43:13 <stickster> pcalarco: Say something if I'm off base here :-)
18:43:27 <pcalarco> yes, it will all be contained in the DB
18:43:31 <stickster> awesome.
18:43:37 <stickster> OK then, shall we move on?
18:43:43 <rbergeron> yes :)
18:43:46 <pcalarco> stickster: yes
18:43:49 <ke4qqq> ahhh /me read pagemaster customizations as changing code - /ignore me :)
18:43:52 * stickster notes we're not doing terribly badly but will probably end up using most of the extra 30 min. Thanks for sticking with us guys.
18:44:04 <stickster> #topic Content workflow and testing
18:44:26 <stickster> #info Need to identify editors who have accepted and set up timeline for cross-training
18:44:29 <rbergeron> that's me.
18:44:41 <hiemanshu> stickster: I am getting my brother to power on my system, so I might be able to push pagemaster right away
18:44:45 <rbergeron> I have editors from the marketing side.
18:44:45 <stickster> My understanding right now is that pcalarco is lead for FWN, rbergeron for marketing content for now.
18:44:50 <stickster> hiemanshu: Thank you for the update!
18:44:59 <pcalarco> k34qqq: yes, these are really just template changes
18:45:01 <rbergeron> I just need to know where to add them - FAS group, or in zikula.
18:45:14 <rbergeron> Also, if we want to have a wiki page documenting that - we should decide.
18:45:28 <stickster> pcalarco: Once we have things in a fairly finished state, will you be able to add adamw, rislam and others to the roster for people helping you?
18:45:45 <rbergeron> We can either say "here is the list of peple" on a wiki page - or just say, "look at FAS to find out" - much less redundancy in terms of where we have to update lists of names and such.
18:45:49 <stickster> rbergeron: Once we know that FASauth works, the answer to that should be FAS group.
18:45:57 <rbergeron> okay.
18:46:34 <stickster> That is in fact the sole purpose of having a FAS auth plugin -- to simply make FAS the place where we handle groups of people, and then we tell Zikula to look to FAS to identify whether people are in a specific access group.
18:46:34 <pcalarco> stickster: adamw I know will be eager
18:47:04 <pcalarco> stickster: no on else on news team has stepped up otherwise
18:47:33 * rbergeron nods
18:47:33 <stickster> So Zikula will know "the 'mktg-editors' group can do X, Y, and Z," and it will ask FASauth to see if e.g. pcalarco is in that group
18:48:06 <rbergeron> are we going to delete the fas group that contains the people who are editors for the l.com distroblogs?
18:48:10 <stickster> pcalarco: OK -- I will hazard that I can help on a Tuesday or Wednesday evening if needed
18:48:13 <stickster> rbergeron: No need
18:48:24 <rbergeron> one group can be a group of another group?
18:48:33 <rbergeron> multiple groups for that in zikula?
18:48:52 <stickster> rbergeron: If not, I have the power to transfer people as needed, I have 'accounts' power there
18:49:02 <stickster> #info stickster can help with group membership shuffling as needed
18:49:23 <stickster> #info rbergeron and pcalarco have identified people for editing both content types at this point; group setup to follow as needed.
18:49:40 <stickster> #topic Content workflow and testing - FWN progress
18:49:57 <stickster> pcalarco: Is anything still needed for the FWN pubtype to function properly?
18:49:59 <pcalarco> for documentation sake, which FAS group will editors apply to?
18:50:15 <ke4qqq> cmsadmin
18:50:31 <pcalarco> stickster: just the open tickets discussed in theming, I think at this point
18:50:32 <stickster> ke4qqq: pcalarco: I fear this is a rabbit hole, I have some opinions but it will take us off track
18:50:38 <stickster> Can we hold off on this until after the meeting?
18:50:44 <pcalarco> ke4qqq: thanks
18:50:56 <pcalarco> ok
18:51:01 * stickster thinks editors and admins ought to be separate groups, but people can be both if needed.
18:51:08 <stickster> we'll come back to that.
18:51:14 <pcalarco> stickster: I agree
18:51:17 <stickster> #agreed We'll talk about some group separation later
18:51:43 <stickster> pcalarco: About FWN pubtype... is there anything you're blocked on that we haven't covered already in logistics or design/theme?
18:51:51 <stickster> Or do you feel like things are ready?
18:51:55 <pcalarco> stickster: no
18:52:19 <pcalarco> stickster: once we get the above theming tickets resolved, we are ready with FWN
18:52:27 <stickster> #info pcalarco says FWN is good to go, previous tickets aside -- this item can be removed from future agenda.
18:52:31 <stickster> Thanks pcalarco!
18:52:45 <stickster> #topic Content workflow and testing - Marketing content
18:53:03 <stickster> Do we have any workflow bits created yet for general marketing content?
18:53:30 <pcalarco> stickster: there is a pubtype 'general news' which can be used for marketing et. al.
18:53:43 <stickster> pcalarco: Ah, and FWN is sort of a subclass of that?
18:54:23 <pcalarco> the one item that I need to check with itbegins is whether the general news pubtype goes to an editor first or just gets immediately published; we want to make sure the former
18:54:44 <stickster> *nod
18:54:53 <stickster> I suspect I'll be learning a lot this afternoon :-)
18:54:56 <pcalarco> stickster: FWN has its own pubtype because it is an aggregation of multiple individual beats into an issue
18:55:08 <stickster> Ah, OK, and the beats are treated more like a general news pubtype then?
18:55:47 <pcalarco> no, the FWN pubtype submissions get aggregated and published as a general news type (I think);
18:55:58 <stickster> OK.
18:55:59 <pcalarco> sorry for not expressing this clearly
18:56:12 <stickster> Not at all. I'm taking us down another rabbit hole here I think :-)
18:56:15 <stickster> Backing up...
18:56:35 <stickster> So the answer is, there's a general news pubtype, we can use it suitably for at least rudimentary marketing content right now.
18:56:37 <pcalarco> there is also an events pubtype defined, although I do not know if we need it
18:56:43 <pcalarco> yes
18:56:46 <stickster> We can add other pubtypes as needed, as we go.
18:56:48 <stickster> Yes?
18:56:56 <pcalarco> stickster: yes
18:57:12 <stickster> #info General news pubtype will work for marketing content now. We can add more later as we go to support specific presentation or content
18:57:16 <stickster> OK, moving on then!
18:57:40 <stickster> Whoa, I think we made up some time there, unless I really skipped something
18:58:09 <rbergeron> i don't see anything skipped
18:58:41 <stickster> yay!
18:58:49 <stickster> #topic Documentation
18:58:56 <pcalarco> chua and I started working on documenting workflow; this is in process, and I also need to clear up previous iterations on workflow linked from the FI page as well as from FWN wiki pages
18:58:58 <stickster> #link https://fedorahosted.org/marketing-team/ticket/108
18:59:05 <stickster> #link http://fedoraproject.org/wiki/Fedora_Insight_Workflow
18:59:28 <stickster> OK, this is an excellent start
18:59:33 * rbergeron nas no clue why she put the marketing trac report in documentation.....
18:59:37 <stickster> Right now there's more background on the page than instructions, but that's totally OK.
18:59:38 <rbergeron> lol
18:59:52 <stickster> rbergeron: No, that was the right section
18:59:54 <pcalarco> stickster: is the timeframe appropriate, or do we need this p[rior to beta?
19:00:06 <stickster> rbergeron: Because the ticket is all about *documenting* how we should interact with FI
19:00:38 <stickster> pcalarco: I think we'll need this prior to Beta -- beacuse ideally we want to start practicing with the content at least a short while before we have to push to staging and then production
19:00:46 <stickster> pcalarco: Is that do-able?
19:00:56 <rbergeron> stickster: i'm not talking about #108, i'm talking about the link i have to "alllll marketing tickets"
19:00:57 <stickster> pcalarco: I may be able to lend some time here
19:01:02 <stickster> rbergeron: Ah!
19:01:26 <pcalarco> stickster: when is beta now?  I am travelling 4/16-4/27 overseas
19:01:46 <stickster> pcalarco: Beta will now be issued 4/13 -- a week from next Tuesday
19:02:01 <pcalarco> I think I can meet that
19:02:03 <stickster> So that gives us about 12 days more or less
19:02:25 <stickster> #action pcalarco and stickster to finish [[Fedora Insight Workflow]] wiki page with full instructions
19:02:39 <stickster> pcalarco: Helping with that page will help me learn.
19:02:44 <stickster> Kosher?
19:02:56 <pcalarco> stickster: yes, thanks for the help!
19:03:05 * stickster thinks pcalarco has a lot of #action on him, but hopefully most are short or shared with itbegins
19:03:34 <pcalarco> stickster: yes, I think it is manageable
19:03:44 <stickster> I'm going to do my best to cut some time for FI the next few weeks -- I'm also trying to help out in Docs so I may get a bit stretched at times -- don't be afraid to ping me whenever needed
19:04:01 <pcalarco> stickster: ok, will do
19:04:12 <stickster> rbergeron: Should we go through the marketing tickets?
19:04:26 <stickster> Or are those all "creation of content" that doesn't have to do with actually getting FI working?
19:04:49 <rbergeron> I think they're mostly related to content creation.
19:04:51 <stickster> (other than #108, #109, which we've already covered I believe)
19:05:34 <stickster> rbergeron: Maybe we should add a "Content" topic to this meeting, and put them there in the next agenda.
19:05:54 * rbergeron nods - i will take that action.
19:06:13 <stickster> #action rbergeron Add marketing-team tickets for FI content to a "Content" topic for next meeting agenda.
19:06:15 <rbergeron> #action rbergeron to add "content" topic to agenda and add content-tickets from marketing trac
19:06:15 <stickster> Superb!
19:06:18 <rbergeron> err
19:06:18 <rbergeron> #undo
19:06:19 <stickster> ha
19:06:20 <zodbot> Removing item from minutes: <MeetBot.items.Action object at 0x17e52d50>
19:06:28 <stickster> You almost outgunned me!
19:06:36 * rbergeron is training every day :)
19:06:37 <stickster> 'The Man Who Shot Liberty Bergeron"
19:06:55 <stickster> OK
19:07:24 <stickster> *whew* -- I think we actually covered our agenda here. Do you guys feel like this meeting helped *you* understand what's next and how we're doing so far?
19:07:34 <stickster> I know it helped me, but I want to hear from you guys.
19:07:52 <stickster> #topic Wrap up
19:08:02 <pcalarco> stickster: yes, it is really good is clearly see what is need and make them actionable
19:08:25 <pcalarco> to clearly see, rather
19:08:48 <rbergeron> yes, although i still feel like i don't know the details of some of the infrastructure stuff
19:08:55 <stickster> rbergeron: I think that's normal
19:08:58 <rbergeron> but i think some of that is just lack of technical understanding
19:09:02 <rbergeron> and i trust that they know what they're doing :)
19:09:05 <pcalarco> we need to document zikula internals for FI
19:09:11 <ke4qqq> who is "they"
19:09:50 <pcalarco> hiemanshu knows some, itbegins knows all, I know nothing about internals
19:09:51 <stickster> pcalarco: To some extent, yes -- I don't want to write a new manual for Zikula but we should capture the precise pieces that we need to Get Things Done
19:10:13 <pcalarco> stickster: agreed
19:10:23 <stickster> I would suggest that for specific training needs -- like "How does this work?" general stuff -- we can use Fedora Talk to do quicker brain dumps
19:10:45 <stickster> That's more useful if we know only a few people are going to be helped by the training. If it's something of broad import, we should find better ways of sharing it.
19:11:23 <stickster> A lot of times, what I see happen is that IRC slows down the process by a factor of about 10 or more, so it's not always the best way of transferring short-term, specific knowledge
19:11:32 <pcalarco> pagemaster seems key to everything we are going to do with FI, for example, so it would be useful at some point to know everything we can about pagemaster templating
19:11:53 <stickster> At the same time, we have to be careful that we don't shortcut ourselves out of getting help... documenting on the wiki and using other methods helps us show other people how to help immediately.
19:11:59 <stickster> pcalarco: I agre
19:12:01 <stickster> *agree, even
19:12:34 * stickster might suggest that depending on what itbegins schedule and setup look like -- we could get him on the phone for more efficient use of his time
19:12:50 <stickster> on a short-term basis with the specific goals of tackling today's #action items.
19:13:13 <pcalarco> stickster: good idea
19:13:38 <stickster> Since those are one-time actions, in a lot of cases, it seems less of a priority to do a bunch of wiki-izing or zodbot capturing around it
19:13:38 <rbergeron> ke4qqq: they being anyone who is doing packaging, building, staging, installing
19:13:45 <rbergeron> basically everyone but me :)
19:13:54 <pcalarco> and me lol
19:13:56 <stickster> pcalarco: Maybe itbegins will be able to point us to docs on pagemaster
19:14:01 <stickster> me three! :-)
19:14:18 <stickster> OK, I think we've beat this horse into the ground.
19:14:31 <stickster> #agreed This meeting is very worthwhile and we will continue to hold it.
19:14:53 <stickster> Does the 1800-1900 UTC time (2pm-3pm US Eastern) basically work for us for now?
19:15:04 <stickster> Obviously hiemanshu can't be here the whole time, so we'll front load his pieces.
19:15:25 <pcalarco> I have this time blocked out on my schedule weekly, yes
19:15:29 <stickster> rbergeron: When you're twiddling the agenda, will you move design/theming up to the top?
19:15:57 <stickster> Er, never mind!
19:16:00 <stickster> I'll just do it now :-)
19:16:17 <stickster> #action stickster Move design/theme in agenda to top of meeting for hiemanshu's sake
19:17:11 <stickster> ke4qqq: rbergeron: mchua: Any objections to same bat-time, same bat-channel?
19:17:29 <rbergeron> this time works for me.
19:17:45 <ke4qqq> none from me
19:17:45 <rbergeron> we should remember that next week we will be having the beta meeting though -
19:17:48 <rbergeron> so we definitely can't go over
19:17:54 <stickster> Absolutely right rbergeron
19:17:58 <stickster> #agreed Meeting will stay at Thursdays 1800-1900 UTC (2-3pm US EDT) -- next meeting 2010-04-08 UTC 1800
19:18:07 <stickster> #info Strict 60 minute time limit starting next week
19:18:17 <stickster> I think that's all folks.
19:18:25 * stickster holds gavel for 30
19:18:47 <pcalarco> stickster: thanks so much!
19:19:02 <stickster> Thanks for your extra time and devotion everyone. I feel energized and ready to tackle stuff!
19:19:04 <stickster> 5
19:19:07 <stickster> 3
19:19:08 <stickster> 2
19:19:09 <stickster> 1
19:19:11 <stickster> #endmeeting