15:00:33 #startmeeting 15:00:37 #chair poelcat 15:00:48 #topic Zikula CMS Solution Meeting 15:00:51 poelcat: go 15:00:52 :) 15:01:04 * ianweller 15:01:09 * Sparks is here 15:01:17 who else is here? 15:01:19 * JonRob 15:01:31 * ke4qqq is here 15:01:33 * ianweller *just* woke up so is still a little... wonked out 15:01:41 * poelcat knows the feeling :) 15:01:54 * Sparks thinks ianweller is always a little wonked out 15:02:02 does anyone know Simon's nick? 15:02:07 * laubersm is lurking but not 100% paying attention 15:02:08 itbegins 15:02:11 poelcat: http://wiki.debian.org/MeetBot 15:02:34 * ke4qqq waves at laubersm - long time no see 15:03:25 # topic Introduction 15:03:36 (no space between # and topic) 15:03:48 #topic Introduction 15:04:14 a couple of weeks back some folks asked if i would help lead a cross-team meeting to 15:04:21 work on getting Zikula live 15:04:28 obviously I said "yes" :) 15:04:56 i am not a subject matter expert at all, I am just here to help facilitate the meetings and track progress, etc. 15:05:16 so i'll need a little help with topics that need to be covered etc. 15:05:43 As I understand things the first usage of Zikula will be by the docs team 15:05:55 but in time will be rolled out for and affect other teams 15:05:58 * Sparks can probably help as well as ke4qqq 15:05:59 is that correct? 15:06:06 yes 15:06:17 * poelcat bats 1000 15:06:18 This will be a replacement for docs.fp.o... 15:06:32 and will be used by others in the same fashion later. 15:06:51 marketing is very interested too, as a possibe use as backend for $foobar that we're looking to get going in the next 3/4 months 15:07:12 althoguh we're exploring all possibilities 15:07:30 our first topic was to set a regular meeting time, but we need Simon for that 15:07:35 so we'll wait and see if he appears 15:07:53 any more on the "intro" ? 15:08:00 * Sparks thought mizmo would be here to discuss artwork and design... 15:08:13 ianweller is covering that 15:08:16 cool 15:08:36 #topic Module Packaging Status 15:08:59 so as I understand things we can't go live with zikula until it is fully packaged 15:09:11 is there a wiki page tracking progress on this? 15:09:16 or a tracker bug? 15:09:19 there is a bug ticket... 15:09:22 * Sparks goes to find it 15:09:47 hello everyone 15:09:50 sorry I am late, got help up 15:09:58 itbegins: welcome 15:10:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=504066 15:10:19 Bug 504066: medium, high, ---, david, ASSIGNED, CMS for docs.fp.org 15:10:33 that's the tracker right? 15:10:36 Yes 15:10:49 There should be blockers against it for all the modules and such. 15:11:10 do all of the bugs have to be closed to go live? 15:11:12 * Sparks counts fourteen tickets blocking it. 15:11:47 yes and some that aren't even open yet 15:11:51 * ricky is here, sorry 15:12:03 are these bugs just for incomplete packaging requsts or there are other TODOs? 15:12:05 im here 15:12:13 mizmo: :) 15:12:13 ke4qqq: Can we create task tickets for those items that haven't been opened? 15:12:24 IOW where would other teams file RFEs and other needs? 15:12:30 poelcat: There are TODOs and Packaging requests 15:12:53 they are not-yet-tackled package reviews from my standpoint 15:13:22 mainly bundled libraries 15:13:31 * poelcat would suggest bugzillas for packaging and needed code changes... wiki task list for other things 15:13:46 though we have a ton of existing modules and dependencies waiting on reviews 15:14:00 ke4qqq: do we have an easy way to query them? 15:14:28 or is that the tracker bug? 15:14:29 the stuff that's not yet tackled?? or the stuff waiting on reviews? 15:14:34 both 15:14:39 poelcat: That's the tracker. 15:15:28 just searching for zikula in BZ shows most of the outstanding reviews - the stuff not yet tackled - not really - at least not yet. 15:16:34 part of it is that you don't know about the bundled libraries until you start looking at the stuff you are packaging 15:16:50 so the tracker bugs has the MUST HAVES? 15:17:05 * poelcat trying to get a sense of scope and what needs to be tracked/tackled 15:17:08 and if you miss it, the first notice might be when someone reviews, or when infrastructure audits the package 15:17:12 poelcat: I tink so 15:17:27 I think, too 15:17:43 okay, so it seems best to focus on the tracker for the near term? 15:19:13 * poelcat takes silence as "yes" 15:19:31 silence is assent 15:19:53 what is the process for clearing open bugs/package reviews? 15:20:07 are you actively seeking out reviewers? 15:20:24 We actually have reviewers that are helping us out. 15:20:35 So that's not so much of a problem right now. 15:20:38 I was hoping that the same group that packaged them would review them - but haven't seen that happening - I closed a few of them. 15:20:47 it isn't??? 15:20:53 have I missed something? 15:21:12 ke4qqq: Between ianweller and... someone... My packages have been getting regular attention. 15:22:15 ahhh yes - there are some where certain packagers need prodding (/me just looked at the reviews) 15:22:26 there are also two packages awaiting a sponsor 15:22:45 toshio... 15:22:59 You, ianweller, and toshio have been working my packages. 15:23:03 from two different people 15:23:17 those may need some attention we can't give 15:23:18 gack 15:23:23 * jds2001 forgot about this meeting. 15:23:48 working backwards from the intended "go live" and when package reviews need to be done... has a go live date been selected? 15:24:16 I'd think it needs to be a few weeks before first draft of RN hits docs.fp.o 15:24:22 poelcat: 60 days from the FAD @ SELF was the projected time. 15:24:25 ke4qqq: Yes! 15:24:36 Sparks: is that still realistic? 15:25:44 poelcat: if we could get all of the packaging (and the outstanding licensing and bug issues) fixed in a week - it might be.... 15:26:39 poelcat: maybe 15:26:42 ke4qqq: what is percentage chance of that happening? 15:27:53 if we could as a group dedicate sometime to it this weekend, we could likely get the majority of it accomplished. The two unknowns right now are the continued licensing issue - and a hash function bug that I am running into - ohhh and the people needing sponsors 15:28:15 ke4qqq: what is percentage chance of that happening? 15:28:18 I'd say I'd guves us 40% 15:28:23 give even 15:28:45 so while it is "possible" not "probable" 15:28:48 ? 15:29:06 might be slightly less - some of those needing sponsors have lingered for a bit. That's a correct statement 15:29:34 what is the task # here http://poelstra.fedorapeople.org/schedules/f-12/f-12-docs-tasks.html that relates to the RN on docs.fp.o ? 15:30:10 8 15:30:11 * poelcat notes there are no "wrong" answers here, we're just trying to figure out where were are at so we can figure out an honest end date :) 15:31:02 what action items/owners/dates should we set around completing this topic? 15:31:24 where "this topic" 15:31:27 = package reviews 15:32:37 I'd like to say all of the non-sponsor-needing package reviews done by this time next week - the balance we need to get the sponsees in high gear or go through the deadreview process 15:32:46 which will take a minimum of 7 days 15:33:08 who is responsible for that task? 15:33:29 ke4qqq: 15:33:34 so we know who to check back w/ next meeting 15:33:44 as in who is going to carry the whip - or who is doing the actual work? 15:34:02 ke4qqq: who is carrying the whip and can give status at our next meeting? 15:34:09 ke4qqq carries the whip... there are a number of others, including ke4qqq, doing the actual work 15:34:35 * ke4qqq spews his drpepper 15:34:58 what? Is it something I said? 15:34:59 I see my role here as helping to guide things forward from a high level, but probably not able to able to crack the whip at all of the lower levels :) 15:35:06 hopefully you all agree 15:36:10 * poelcat still isn't clear on completion date for package reviews? 15:36:44 for everything but the reviews needing sponsors the goal is next week at Wednesday no later than 11:36am 15:36:48 Eastern 15:36:52 :) 15:36:59 * ianweller blinks 15:37:10 Eastern Daylight or just Eastern? 15:37:35 that could be CEST ;-) 15:38:04 :) 15:38:28 okay we'll check back on packaging next week 15:39:31 what other things need to be done successfully reach go live on 2009-08-18 ? 15:39:32 oops - forgot a few things - mind if I drop those on you 15:39:53 * poelcat realizes that is a big question... maybe more suitable for a wiki list 15:40:25 so first - there are 2-3 fedora-specific modules that zikula guys have done for us (mainly itbegins) we need to get source code for those in fedorahosted - and get those packaged in the infra repos. 15:40:47 Yes, there's the theme, the FASAuth and the docs publishing module 15:40:57 the last of that list isn't complete yet, to my knowledge 15:41:10 The theme probably needs input from websites 15:41:20 FASAuth 'just works' 15:41:31 are we tracking these other modules in bugzilla? 15:41:33 can we get that pushed up today? everything as it stands now 15:41:45 poelcat: we aren't yet 15:42:12 who would like to be own creating the bugzillas? 15:43:26 I can 15:44:01 I have a bit of an issue at the moment - I've had 3 laptops die on me over the last couple of weeks and have no linux machines running at the moment. So, I'll have to re-establish all my Fedora stuff before I can commit anything to the repositories 15:44:21 Sparks: thanks 15:44:24 itbegins: ouch! 15:44:24 itbegins: how long? 15:44:34 I can email the code elsewhere for someone else to do quicker 15:45:08 otherwise, as I'm also packing for relocation to the US I can't see it happening for a while 15:45:09 ok - email it to me (and Sparks) if you don't mind - one of us will get it up by end of the day 15:45:40 we will? 15:45:41 will do 15:45:45 I mean... we will. 15:45:46 * poelcat notes we have 15 min left 15:45:50 :) 15:46:05 #topic Next Meeting Time 15:46:31 can we continue to meet at this time/day ? 15:46:41 this time is ok, i just have to learn to go to bed at not 3am the night before 15:46:46 poelcat, I can't... 15:46:53 but I don't know when I can 15:47:06 +1 for timing 15:47:11 Okay for me. 15:47:28 * poelcat wonders if we can do a few meetings at this time until we are really blocking on itbegins? 15:47:40 That's fine by me 15:47:47 hopefully by then itbegins has a better idea on availability? 15:47:48 I can read the logs and follow up on any questions 15:47:57 I should know better in a week or so 15:48:01 perfect 15:48:01 ok to go back to your question - we need to create the puppet manifests - I am sure infra will want to audit all of that, including the code ( abadger1999 has already done a ton of that and found problems) - we need a decent testinstance running that we can beat on (that's generated by puppet, not installed by hand) and then I guess we need to work on publishing everything in test and get that incantation squared away. 15:48:41 ke4qqq, afaik, only licensing so far, right? 15:49:16 I ran into a hash issue I have been meaning to talk to you about when I unbundled some stuff - we can do so after the meeting if you want) 15:49:44 it's a php4 v php5 issue - and I prolly just need to patch it myself and submit it upstream 15:51:16 ready to move on? 15:51:24 i love to help too, but need to learn things first, are people allowed to learn things to work with the team? 15:51:38 yes 15:51:43 and rislam: yes 15:51:53 how? 15:52:07 rislam: lets talk after the meeting 15:52:28 #topic Important Cross Team Dependencies 15:52:43 what things should we be tracking on this topic that we aren't already? 15:52:51 or what things do different teams need to be thinking about? 15:53:02 art team/websites approval of the theme? 15:53:25 ianweller: Yes and anything that infra needs 15:53:33 yeah we'll need art/design/websites help and blessing 15:55:18 anything else on this topic or others in the remaining 5 minutes? 15:57:45 If anyone needs to know anything about Zikula (from other teams etc) just email me 15:57:55 I'm happy to answer any questions 15:59:18 thanks everyone for coming 15:59:21 #endmeeting