18:00:36 <stickster> #startmeeting Fedora Insight
18:00:36 <zodbot> Meeting started Wed Jun  9 18:00:36 2010 UTC.  The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:36 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:40 <stickster> #meetingname Fedora Insight
18:00:40 <zodbot> The meeting name has been set to 'fedora_insight'
18:00:46 <stickster> #topic Roll call
18:00:48 * stickster 
18:00:51 * rbergeron is here sort of
18:01:05 * heffer doesn't know what he's doing here :D
18:01:50 * stickster not sure if smooge is available Wed at this time
18:02:02 <rbergeron> by sort of i mena - via blackberry, sitting in salon waiting for her hair color to be fixed from the first try today :/
18:02:07 <rbergeron> ah
18:02:37 <stickster> #agenda https://fedoraproject.org/wiki/Insight#Meeting_agenda
18:02:42 <stickster> oops :-)
18:02:46 <stickster> #info Agenda: https://fedoraproject.org/wiki/Insight#Meeting_agenda
18:02:51 <rbergeron> yeahhh
18:03:12 <stickster> #topic Action item review
18:03:54 <stickster> smooge and ke4qqq were going to document the process for making code changes, testing, and deployment -- that way we don't have people making uncaptured changes randomly and losing their work
18:04:14 <stickster> I'm guessing ke4qqq is busy with SELF coming up. smooge doesn't seem to be around.
18:04:30 <smooge> stickster, I am working on the reboots of systems at the moment
18:04:30 <stickster> smooge was going to tell rbergeron when stg.fp.o is ready
18:04:31 <smooge> sorry
18:04:36 <stickster> smooge: Ah, thanks smooge
18:04:44 <smooge> once we have rebooted I will be working on stg
18:04:54 <ke4qqq> basically it was all smooge - /me hasn't done any work  other than talking with smooge.
18:04:54 * gwerra is here, and hates being pinged(all)
18:04:58 <smooge> should be done by tomorrow
18:05:12 <stickster> gwerra: :-)
18:05:48 <stickster> rbergeron, I know you did testing as seen here: https://fedoraproject.org/wiki/Fedora_Insight_Testing#Testing_-_Morning.2C_6.2F7.2F2010
18:05:59 <stickster> It looks like comments are the only thing that are questionable right now
18:06:13 <stickster> I can get a new EZComments rolled from the 2.0.0 that was just changed upstream
18:06:25 <stickster> That's a little quirky, I'll talk about that shortly
18:06:30 <rbergeron> right - basically everything works but the 2nd-time commenters stuff
18:06:36 <stickster> Cool, good to hear
18:06:47 <rbergeron> or third, 15th, etc.
18:07:00 <rbergeron> all the fas stuff seems to work
18:07:10 <rbergeron> which was the really crucial part :)
18:08:00 <stickster> right
18:08:20 * stickster continues to look at action item list
18:08:42 <stickster> There's also an item for documenting how to put general news on Insight that rbergeron and I hold
18:08:57 <stickster> #info smooge will have stg.fp.o ready shortly
18:08:59 * rbergeron sits with chemicals on head
18:09:14 <stickster> #info rbergeron FAS testing complete, comments are dependent on resolving EZComments 2.0.0 upgrade
18:09:15 <rbergeron> yes - that's on our list
18:09:28 <stickster> #action stickster to finish EZComments upgrade based on new upstream tag
18:09:58 <stickster> #action rbergeron to take up general news workflow docs, stickster will ride shotgun too
18:10:09 <stickster> All right, that's everything from last week.
18:10:16 <stickster> #topic Current platform status
18:10:32 <stickster> #info stickster got us upgraded to 1.2.3 and it was relatively painless
18:10:57 <stickster> #info The RPM and SRPM packages used are in koji, also stickster held onto copies
18:11:10 <stickster> #link http://koji.fedoraproject.org/koji/buildinfo?buildID=176966
18:11:42 <stickster> drak has confirmed that 1.2.3 will continue to work fine with current PHP on RHEL-5
18:12:12 <stickster> We need to explore what Drak keeps referring to as "CI" which I think is "continuous integration"
18:12:34 <stickster> Wait, let me backup, I jumped topics there
18:12:41 <stickster> Back to what's changed in the last week.
18:12:49 <stickster> EZComments has a new release 2.0.0 that came out.
18:12:59 <stickster> It's supposed to fix the problems we've been having in comments, as rbergeron noted.
18:13:21 <stickster> I started working on packaging last night, and found a couple things that were odd:
18:13:46 <stickster> * There is no package at all in Fedora or EPEL repos, even though it's apparently approved for our package repositories
18:14:12 <stickster> * It doesn't exist in the infrastructure repo either, although I found the matching RPM/SRPM
18:15:28 <stickster> Oops, my fault, that's not true
18:15:35 <stickster> It does exist in the infrastructure repo, I just couldn't find the SRPM
18:15:51 <stickster> * I located the matching RPM/SRPM in mchua's stuff
18:16:23 <stickster> So... I tried packaging up the new 2.0.0 and discovered that there was a weird licensing issue in one of the included javascripts
18:16:42 <stickster> (which was kind of a blast from the past given our previous work in the area of licensing) :-)
18:16:58 <stickster> Upstream EZComments, which includes mateo by the way, rolled up a new 2.0.0
18:17:08 <stickster> So I should be able to package that and get it installed today
18:17:24 <stickster> But what was odd to me is the really lax release management from upstream
18:17:36 <stickster> Keep in mind that EZComments upstream is not the same as Zikula upstream, it's a community module of course
18:18:01 <stickster> But also keep in mind that we're relying on some of these community modules as well.
18:18:18 * rbergeron nods
18:18:25 * stickster feels like he's monologuing. rbergeron, tell me you're at all interested in what I'm saying :-D
18:19:03 <stickster> (I know you're only semi-here, not asking for constant feedback, I just want to know this meeting is at all useful :-)
18:20:42 <rbergeron> no - its helpful to me
18:20:55 <stickster> OK, I'll keep going, but feel free to stop me or say "slow down" or "shut up" :-)
18:20:57 <rbergeron> and any other prospective participants :)
18:21:15 <rbergeron> i keep getting disconnected from bberry also :)
18:21:20 <stickster> heh
18:21:41 <rbergeron> so - when you say "keep in mind community modules"
18:22:04 <rbergeron> - that means those things are subject to change
18:22:22 <rbergeron> and/or not as much support - or possibly response
18:22:28 <rbergeron> as maybe zikula friends
18:22:36 <rbergeron> but could well be fine.
18:22:37 <stickster> What I mean is, it's important to note that Zikula core devs have a way of working, and community module devs aren't necessarily the same people
18:22:51 <rbergeron> right
18:22:57 <stickster> We just need to keep that in mind if we're relying on that kind of module.
18:23:25 * stickster not sure how other CMS communities handle that. Certainly there's always a "core" product, and things around it, but is it always the case that module devs do their own thing? I truly don't know.
18:23:32 <rbergeron> right - at least helpful for when probs arise (if) to remember
18:23:39 <rbergeron> shampoo time
18:23:42 <rbergeron> brb :)
18:23:43 <stickster> Anyway, the weird part was that the EZComments maintainers just moved the '2.0.0' release to mean a different revision of code than it was a few days ago
18:24:14 <stickster> Which struck me as not very kosher in terms of how collaborative development normally works -- who knows how many people downloaded it in the meantime
18:25:59 <rbergeron> yeah - i tried figuring out their release stuff
18:26:13 <rbergeron> when looking through the bugs
18:26:18 <stickster> #info stickster concerned that we need to keep a close eye on a few different upstreams
18:26:25 <stickster> #undo
18:26:25 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x26c6f250>
18:26:40 <stickster> #info stickster thinks that we need to keep a close eye on a few different upstreams
18:26:43 <rbergeron> on the plus - most bugs are closed - everything is most
18:26:44 <stickster> We might want to see if we can gather the upstream module RSS in a special hidden feed on Insight so when we login, we can find out if there is any new code release we need to worry about
18:26:53 <rbergeron> ...ly enhancement tasks
18:27:02 <stickster> rbergeron: Right
18:27:14 <rbergeron> so that's a good sign.
18:28:02 <stickster> I know there have been some theme tweaks discussed, and we should be able to handle that as we go
18:28:38 <stickster> When I go to the pt6 site, I don't see anything wildly out of place
18:29:13 <stickster> I think the area we need to work on most is just organizing things properly
18:29:22 <rbergeron> is new instance going on pt6 as well?
18:29:32 <rbergeron> i guess so since we're upgrading?
18:29:42 <stickster> rbergeron: Actually, an upgrade doesn't affect the data.
18:29:53 <rbergeron> right - i caught that
18:30:30 <stickster> Did you mean, are we going to put a new instance in so that we can see how well we captured everything?
18:30:55 <rbergeron> well - in parallel maybe
18:30:59 <rbergeron> i just wasnt sure
18:31:01 <stickster> stg.fp.o is somewhat supposed to tell us that
18:31:02 <rbergeron> basically
18:31:04 <rbergeron> :)
18:31:14 <rbergeron> ahhh
18:31:28 <stickster> When smooge gets stg.fp.o ready, we're supposed to see something that looks almost exactly like what's on pt6 -- with the *possible* exception of a little data
18:31:42 <stickster> (story data)
18:31:54 <rbergeron> ok
18:32:11 <stickster> If we don't, that means we've missed something along the way, and we have to figure out what we missed, capture it properly in an RPM or setup instructions, and try again.
18:32:20 <rbergeron> i mean - i of course want to think everything will upgrade smoothly
18:32:56 <rbergeron> but... hope for the bes, expect the worst, i guess :)
18:33:01 <rbergeron> best, too
18:34:40 * stickster nods
18:35:13 <stickster> rbergeron: I don't know what else I have to talk about at this point in terms of current status. Mainly I have to get EZComments spruced up, get it into the infra repo, and see if that takes care of things.
18:35:42 <stickster> If it doesn't, we'll need to turn comments off until we have a well-tested fix or replacement.
18:36:05 * stickster regrets he's been a little low on time for lots of things lately, getting ready for both SELF and the Red Hat Summit.
18:36:23 <stickster> Neither drak nor mateo are here :-(
18:36:56 <stickster> rbergeron: Did you have any business you want to capture in the log before we adjourn?
18:37:14 <rbergeron> nada.
18:37:20 <stickster> OK then.
18:37:23 * stickster holds gavel for 30
18:37:23 <rbergeron> :)
18:37:30 <rbergeron> thanks for hosting :)
18:37:54 <rbergeron> ohh - maybe i missed this
18:38:12 <rbergeron> how long do you think to getting everything ready for retesting?
18:38:23 <stickster> rbergeron: By tonight easily I think
18:38:26 <rbergeron> or can i expect a mail from you when ready
18:38:36 <stickster> rbergeron: I'll email the list when EZComments is upgraded successfully
18:38:39 <rbergeron> or you can expect a beer from me at self :)
18:38:47 <stickster> #action stickster to email list when EZComments is upgraded successfully
18:39:16 <stickster> rbergeron: Are you interested in setting aside a little time for you, me, and anyone else interested talk about Insight at SELF?
18:39:17 <rbergeron> cool. thanks :)
18:39:20 <rbergeron> that's it
18:39:23 <rbergeron> from me :)
18:40:06 <stickster> rbergeron: ^^
13:41  * stickster wondering if rbergeron fell off her BooBerry again
13:41 < rbergeron> nope
13:41 < rbergeron> oh
13:41 < rbergeron> yes!
13:41 < stickster> Cool!
13:41 < rbergeron> let's do that
13:41 -!- mthompson [~Michelle@nat/redhat/x-wfjdwsnoqpwlswoj] has quit [Ping timeout: 252 seconds]
13:42 < stickster> #action stickster and rbergeron to gather for an Insight powwow at SELF, consist of some tech insight/training but also some strategery
13:42  * rbergeron gets in tomorrow at 2
13:42  * rbergeron leaves monday night
13:42  * stickster gets in something like 3 or so he thinks
13:42 < rbergeron> lots o time
13:42  * stickster leaves Monday super-early
13:42 < rbergeron> ah
13:42 < stickster> So we will definitely have some time
13:42 < stickster> Cool
13:42 < rbergeron> super early was another zillion dollars
13:42 < stickster> :-)
13:42 < stickster> All right, I'm going to draw a curtain here
13:42 < rbergeron> sounds good.
13:42 < stickster> #info We should be returning to standard Thursday meeting time next week.
13:43 < stickster> #info Email to list will confirm that.
13:43 < stickster> #endmeeting