18:02:09 #startmeeting Fedora Insight 18:02:10 Meeting started Thu Apr 8 18:02:09 2010 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:02:13 #meetingname Fedora Insight 18:02:15 The meeting name has been set to 'fedora_insight' 18:02:15 stickster: I will be here for some time though 18:02:21 #chair pcalarco mchua hiemanshu rbergeron 18:02:22 Current chairs: hiemanshu mchua pcalarco rbergeron stickster 18:02:28 #topic Roll call 18:02:30 pcalarco: hola 18:02:30 * stickster 18:02:33 * hiemanshu is kinda here 18:03:05 * mchua 18:03:11 pcalarco 18:03:36 #info Present: stickster pcalarco mchua hiemanshu 18:03:57 #link https://fedoraproject.org/wiki/Insight#Meeting_agenda:_2010-04-08 <-- Agenda 18:04:24 I'm going to be moving really fast. I have a 3pm today, and a bunch of things I have to finish before that happens that unfortunately don't involve Insight :-) 18:04:35 #topic Theming/Design 18:04:49 hiemanshu: Want to tell us where we stand on theming/skin/etc.? 18:05:16 stickster: we have some open tickets 18:05:17 (If you have time, this is really all we're looking for -- don't let us keep you from other responsibilities.) 18:05:31 and I will only have time this weekend, because I am stuck between college and $dayjob 18:05:49 I think a sprint this weekend will work well 18:05:59 if pcalarco is fine with it 18:06:15 Looks like ticket 2007 is closed, 2009 is still pending right? 18:06:22 Yes 18:06:29 .ticket 2009 18:06:30 hiemanshu: #2009 (Create RSS functionality for Fedora Insight content) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2009 18:06:35 I can't devote much time this weekend, but if we can define a window to work in that works here 18:06:50 pcalarco: any specific time? 18:06:55 2009 is ready to close as far as I am concerned 18:07:02 RSS works in my testing 18:07:21 I can do things if given instructions. 18:07:32 pcalarco: So we have RSS separate feeds for each pubtype now? 18:07:33 hiemanshu: I will contact you after the meeting 18:07:47 pcalarco: work for me 18:07:51 mmcgrath was here earlier asking if we were going to (1) be ready for F13 and (2) have RSS feeds for start.fp.o to consume (a feed of the headlines, basically). 18:07:52 stickster: AFAIK yes 18:07:53 we have a main RSS feed for everything that hits the main page' 18:08:00 * rbergeron is back... sorry i'm late 18:08:15 eventually we may want that to be more nuanced, but I think it is fine for launch 18:08:26 pcalarco: OK, we need a separate ticket to create separate feeds then. 18:08:42 That ticket is confusing because it's trying to capture two separate needs, one of which is longer-term 18:08:44 stickster: correct, when those get articulated 18:08:53 pcalarco: Can you file a new ticket for the "one feed per pubtype" need? 18:09:01 Then we can close 2009 18:09:02 stickster: will do 18:09:19 #action pcalarco File a new ticket for enhancement of separate RSS feed per pubtype 18:09:25 #undo 18:09:25 Removing item from minutes: 18:09:30 #action pcalarco File a new ticket for enhancement of separate RSS feed per pubtype, cc itbegins 18:09:32 Is there a way to get a feed of just the headlines, for mmcgrath and the start.fp.o page? 18:09:38 * mchua can make another ticket if that's another ticket 18:09:51 mchua: The RSS feed will have a headline embedded with each item, that seems like just an extraction problem 18:09:55 mchua: yes that would be another ticket 18:09:57 The same way that your reader does it 18:10:12 pcalarco: I don't think it's necessarily a separate need 18:10:25 I think it's handled -- for instance, I saw a "FWN 220" title in my reader already 18:10:32 mchua: Does that make sense? 18:10:45 * mchua is a bit puzzled. 18:10:50 The RSS itself is XML content, and there's an element in each item in the feed that alrady gives a headline (title). 18:11:11 Oh, ok, so that can just be parsed. No problem. That's #2009 that I should point Mike towards? 18:11:14 mchua: Right 18:11:22 Thanks, I should have said "parsing" and it would have been clearer. 18:11:23 * mchua will do that. 18:11:24 thanks. 18:11:40 #action mchua will point mmcgrath at ticket 2009 to see that RSS now provides headline/title 18:12:11 #action pcalarco hiemanshu will close ticket 2009 18:12:29 I see the weighting problem is back, pcalarco reopened that bug (properly) 18:12:39 itbegins thought he fixed that last week 18:12:57 stickster: I can't figure out how this is supposed to work, just need some guidance from itbegins 18:13:10 pcalarco: Maybe I can help with that, it would have to be tomorrow though. 18:13:23 If it's just a "how does it work" problem maybe our two heads will be better than one 18:13:33 Or we can both give up and email him, no worse right? 18:14:03 I put in each beat in the order it should be published in, and applied a lower number so that they would be in explicit order, and it is a bit of a mess 18:14:09 Yup 18:14:11 #link http://publictest6.fedoraproject.org/zikula/index.php?module=pagemaster&tid=4&filter=issue:eq:220 18:14:22 pcalarco: Yeah, that looked really icky. 18:14:31 pcalarco: Shall we get together tomorrow to look at this problem again? 18:14:34 stickster: yes, that would work, thanks 18:14:52 stickster: agreed. I will email you offline to look at times. I am flexible 18:15:03 OK 18:15:28 #action pcalarco email stickster to set up a time on Friday 2010-04-09 to look at weighting problem, and then figure out if we need to ask itbegins for more work 18:15:41 I think that's it for design/theming 18:15:46 Anything else here? (30 sec) 18:15:54 not here 18:16:19 #topic Logistics 18:16:28 FASAuth status 18:16:30 #link https://fedorahosted.org/marketing-team/ticket/109 18:17:07 who owns the testing part of this? 18:17:35 it's not assigned - i'm not sure if ke4qqq was going to do it or maybe hiemanshu 18:18:14 We got our answers about the configuration from itbegins, so that part's good to go. 18:18:17 rbergeron: wasn't me 18:18:41 does it actually work with multiple levels of FAS groups and such? 18:18:48 we could recruit some of our editors to apply to cmsadmin or a new FAS group and test 18:19:00 rbergeron: I don't think figured that out yet. 18:19:05 okay - 18:19:09 rbergeron: Could you write that question in the ticket so we don't lose it? 18:19:17 yup 18:19:27 * stickster thinks that ticket needs to capture any unresolved questions, so that we know what to do with it. 18:19:37 being a member of cmsadmin seems to give one admin rights only in Zikula 18:19:38 Otherwise we keep scratching our heads each week asking, "What does this mean?" 18:19:57 pcalarco: In a good sense? 18:20:29 in a bad sense, meaning we can't use that FAS group to distinguish between different authorization levels in Zikula 18:20:41 pcalarco: If there's a question you have about how FASAuth should work, that we need to assess and test, put it in that ticket too please! 18:20:43 i'm basically blocked on writing documentation on how to get poeple in until we either (a) get multiple levels of permissions or (b) just make the call on if everyone is going to be in the cmsadmin group 18:20:44 writer, editor, Zikula admin 18:20:57 * rbergeron will keep cutting and pasting 18:20:59 pcalarco: We should really create separate FAS groups foreach of those. 18:21:01 into the ticket 18:21:12 I think I noted that previously -- maybe rbergeron can capture that as a TODO in that ticket. 18:21:20 stickster: yes, agreed 18:21:21 cmsadmin, cmswriter, cmseditor 18:21:23 yes - i think that was originally the intent of the ticket 18:21:27 rbergeron: Cool 18:21:28 or getting into this ticket 18:21:36 then we discovered that the fas to cmsadmin part was broken 18:21:44 so that i believe is what is fixed thus far - 18:21:46 And I think that's supposed to be fixed now 18:21:48 right 18:21:54 biut the multiple layers of permissions is unknown 18:22:03 yes 18:22:53 who wants to take this ticket / issue? 18:22:57 Can we agree to dive into that before Monday? Make groups, assign people, try them out? 18:22:58 cmswriter could be anyone with CLA signed; cmseditor would require sponsorship, etc. 18:23:12 We'll hash out the details for that outside this meeting. 18:23:50 I am willing to help test with this but need help from whomever setting the FAS groups up and such 18:23:55 #action stickster rbergeron pcalarco to examine Fedora Insight access levels by Monday to exercise/test FASAuth. 18:24:07 i have 'accounts' membership which means I can create groups and move people around and such. 18:24:10 stickster: shall we see if we can even do that? i was under impression that the FAS to zikula groups needed to be hardcoded 18:24:31 rbergeron: Let's make that part of the work. 18:24:34 yup 18:24:39 but this would still work for me 18:24:40 Can we agree that cmsadmin, cmswriter, cmseditor are the FAS groups we need 18:24:42 err 18:24:48 at a basic level? 18:24:56 we can at least get them set up in FAS 18:25:00 so we can start testing tomorrow 18:25:05 or "before monday" 18:25:06 :) 18:25:06 rbergeron: Sure, to start with. I can see that later we might even have writer/editor groups for each pubtype. 18:25:09 * hiemanshu is sorry about the wrong window typing 18:25:11 But those three work for now. 18:25:16 np hiemanshu :-) 18:25:34 #agreed Make groups for cmsadmin, cmswriter, cmseditor and work with them for nwo. 18:25:36 #undo 18:25:37 Removing item from minutes: 18:25:38 #agreed Make groups for cmsadmin, cmswriter, cmseditor and work with them for now. 18:25:49 UGH, i hate trac - how did i just do that 18:26:00 * rbergeron put everything into description instead of comments 18:26:04 fail, fail fail 18:26:13 actually, i love trac, i just am silly 18:26:51 OK, and itbegins commented on ticket 2006 -- the workflow will come in with the rest of the content in the DB 18:27:06 I think that answers the ticket properly, correct pcalarco? 18:27:13 .ticket 2006 18:27:14 stickster: #2006 (Create forms in Zikula on staging for Fedora Insight content workflow) - Fedora Infrastructure - Trac - https://fedorahosted.org/fedora-infrastructure/ticket/2006 18:27:37 I am continuing to test with newissues of FWN 18:28:12 once the weighting issue is resolved, FWN is ready to rock 18:28:16 Excellent! 18:28:24 OK, anything more on Logistics then? 18:28:39 stickster: yes, 2006 18:28:44 See above 18:28:58 stickster: yes this answers it 18:29:02 awesome! 18:29:13 OK, I did a crummy job of updating our agenda, but I'm working through it and will do better next week. 18:29:17 Anyhow 18:29:30 * stickster using last meeting's notes to get through 18:29:48 #link http://meetbot.fedoraproject.org/fedora-mktg/2010-04-01/fedora_insight.2010-04-01-18.00.html 18:30:04 Oh, this was supposed to be cleared from the agenda! 18:31:18 * mchua commented on workflow on the meeting notes 18:31:21 er, content workflow 18:31:35 when it gets to that point - I made that diagram, so can answer questions and do stuff with it if stuff needs to get done. 18:32:17 OK, mchua, it seems like the only next thing that needs to happen is whoever owns that content workflow needs to jump in to Zikula and define how it works. pcalarco, you did that for FWN right? 18:32:38 I will work on documentation this weekend, I should be able to finish it then 18:33:00 The workflow, AIUI, simply defines who's allowed to create/change content, who can approve it for publication, and things like that. 18:33:03 workflow docs that it 18:33:22 * mchua not sure if this means she's supposed to do something, or if pcalarco has the diagram and can run with it. 18:33:30 i.e. it's based on rules in the interface that any admin can set up. Is that correct? 18:34:11 mchua: I think we're trying *not* to add more Insight/Marketing things to your plate. 18:34:14 yes, this and the pubtype templates 18:34:17 but...... we need to have the groups set up, yes? 18:34:35 rbergeron: It would probably be helpful. 18:34:52 * mchua nods. 18:34:54 appreciated. :) 18:35:00 #info Setting up further workflows probably require or would be very much helped by groups. 18:35:08 yes, groups needed 18:35:27 * stickster proposes that he will plan to spend time on Zikula on Saturday afternoon. 18:35:42 Maybe Sunday too. 18:35:59 My meeting schedule of late is just too heavy for me to do much during the week. 18:37:02 OK, we'll try to look at groups tomorrow afternoon, and then move on to trying to set up another workflow just to make sure we understand it. 18:37:10 Does that work? 18:37:33 sounds good. 18:37:40 sounds good 18:37:46 OK 18:38:03 #action stickster to drive Friday afternoon session on groups, likely around 4:00pm Eastern or after 18:38:28 #topic Documentation 18:38:46 pcalarco already talked a bit about the FI workflow documentation needed, that flows right out of the last topic. 18:39:10 I'm supposed to help with that, should be easier if we're working on it tomorrow at a set time :-) 18:39:42 my schedule is open, I can move meetings around tomorrow 18:39:42 rbergeron: You had an item to add any outstanding marketing-team tickets to the Content topic for the next agenda (er, this one) -- can you do that for next time, if there are any? 18:40:15 pcalarco: Awesome... I have a 3pm tomorrow I believe 18:41:01 stickster: yes 18:41:12 #action stickster and pcalarco to finish [[Fedora Insight Workflow]] with instructions that come out of tomorrow's (2010-04-09) work 18:41:30 #action rbergeron Add marketing-team tickets for FI content to the "Content" topic for next meeting agenda on [[Insight]] page 18:41:50 Yikes. I feel like we didn't get very much done this past week on FI beyond itbegins fixing a couple things for us. 18:41:51 But 18:42:10 He did say, specifically, that he *really* appreciated that we had clearly outlined the precise things we needed him to work on and answer. 18:42:23 That very much helped him laser-focus on them and bang them out on Thursday evening. 18:42:30 So good work on that, guys! 18:43:08 I tooled around FI a little while he was working, trying to learn a bit about the system. I know about 15% more than I did before, which is... well, better but not good enough yet. 18:43:31 But I watched itbegins make a few changes, and that helped me understand what he was doing and how it worked. 18:43:33 Somehwat. 18:43:53 :) 18:44:09 I'll try to devote more time to this over the next 5-6 days. 18:44:44 The Board SWG looks to be close to done, which means a bit more time will open up for me. Or rather, I'll be less overextended than before! 18:44:48 Either way is good :-) 18:45:20 OK, moving topic... 18:45:25 #topic All Other Business (AOB) 18:45:51 I want to suggest that if we are not substantially ready to roll in about 2 weeks, we are going to need to wave FI off until after F13 release. 18:46:19 By "ready to roll" I mean, have moved to official staging and are resolving minor problems, as opposed to missing functionality 18:47:00 The missing functionality right now: 18:47:04 * A few styling issues 18:47:15 * FASAuth more questions than answers at this moment, but might be simpler than we think 18:47:39 oops 18:47:44 Wrong key! 18:47:58 lol 18:48:00 * Weighting problem 18:48:12 That's the biggies as I see it. 18:48:23 I'm projecting that we'll be ready to have FWN on the feed and not much else yet. 18:48:36 The "general marketing content moves to FI" stage would come post-F13 18:48:50 I don't know that fasauth is going to be a huge blocker - we could certainly at least work around it for a bit if absolutely necessary 18:48:52 Is there anyone who wants to add to or correct that list? 18:48:59 i should say 18:49:07 s/is going / has to be 18:49:24 Well... basically you're right, rbergeron, and I agree. 18:49:33 We could carry around a separate database for authentication. 18:49:33 i just hate to keep pushing out FI - having a sense of urgency really helps us to need to get it done 18:49:37 Yeah 18:49:47 I'm really hopeful that FASAuth is not as big a deal as we think 18:49:51 me too 18:49:56 and that part of the problem is just having the groups up and tested. 18:51:00 #idea Big Come to $DEITY meeting next week to see if we have *substantially* advanced our progress to the extent that we're feeling good about rolling out to staging. 18:51:32 I'm guessing that hiemanshu will help us with the moving of stuff from pt6 -> stg 18:51:38 * rbergeron nods 18:51:44 Now that we know exactly what to back up and carry from one host to another. 18:51:48 Anything it would be useful to relay up to the zikula list for help? 18:52:01 itbegins suggested shouting-out to http://groups.google.com/group/zikula-discussions 18:52:20 mchua: For which type of help? 18:52:27 I've got that context email I can send out in a moment if people want to follow up on it with a more updated version of things we need to know. 18:52:36 stickster: Anything we'd normally ask itbegins for, that could be answered by any other zikula-hacker. 18:52:58 I don't think we're lacking knowledge of Zikula so much as testing our own specific Fedora piece (FASAuth) and learning the cotton-pickin' system so that we can run it. 18:53:09 sorry, s/knowledge/hacking/ 18:53:47 All of us (other than mchua) will need to roll up sleeves and jump in if we want this to be ready. 18:53:59 Otherwise the urgency is somewhat of a red herring :-) 18:54:04 * rbergeron nods 18:54:19 But I think on the whole everyone here understands that 18:54:37 And we'll use part of the next 5 days to do said jumping/plunging! 18:54:58 OK, I'm set for another meeting in ~5 min 18:55:14 I'll leave the floor open for a minute to see if there's any other AOB 18:55:56 stickster: i think the word you're looking for is "plow"... not jumping / plunging :) 18:56:02 plow! 18:56:02 ploowwwwwing. 18:56:03 There you go 18:56:06 LORD OF THE PLOW. 18:56:08 stickster: yes I will be doing that 18:56:18 hiemanshu: Thank you sir! 18:56:46 hiemanshu: I have a minimum amount of puppet skill and may be able to lend a hand if needed 18:57:36 stickster: I am sure nb can help with tat 18:57:45 cool! 18:57:50 All right, I think that's all for today then 18:57:52 #endmeeting