19:00:06 <stickster> #startmeeting Insight
19:00:06 <zodbot> Meeting started Thu Feb  3 19:00:06 2011 UTC.  The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:06 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:10 <stickster> #meetingname Insight
19:00:10 <zodbot> The meeting name has been set to 'insight'
19:00:13 <stickster> #topic Roll call!
19:00:22 * schendje present
19:00:29 * averi too
19:00:46 <asrob> hi
19:01:08 <stickster> #link http://meetbot.fedoraproject.org/fedora-meeting/2011-01-27/insight.2011-01-27-19.01.html <-- Last meeting's minutes
19:01:59 <stickster> #link https://fedoraproject.org/wiki/Fedora_Insight#Meeting_agenda <-- Meeting agenda
19:02:19 * stickster gives pcalarco a minute
19:03:03 <smooge> here
19:03:14 <stickster> #chair averi asrob smooge schendje
19:03:14 <zodbot> Current chairs: asrob averi schendje smooge stickster
19:03:23 <stickster> #info Present: averi asrob smooge schendje smooge
19:03:27 <stickster> oops
19:03:28 <stickster> #undo
19:03:28 <zodbot> Removing item from minutes: <MeetBot.items.Info object at 0x2b025e26a990>
19:03:32 <stickster> #info Present: averi asrob smooge schendje stickster
19:03:36 <stickster> I have smooge on the brain apparently :-D
19:03:45 <stickster> #topic Round-up from FUDCon Tempe
19:03:59 <stickster> So... thanks to the Infra guys we are now properly set up on a new EL-6 server
19:04:09 <stickster> #info Testing is now on a new EL-6 box
19:04:15 <schendje> yeah, sorry I had to break my promise and couldn't be there :/
19:04:17 <stickster> #link http://publictest09.fedoraproject.org/drupal
19:04:40 <stickster> schendje: It's OK :-) Everyone who's been to a FUDCon knows that it's easy to get double- or triple-booked :-)
19:05:18 <stickster> schendje: I was wondering what you thought about making the Insight theme programming part of a design bounty
19:05:29 <schendje> stickster: yes, I read that
19:05:37 <stickster> #idea Insight theme programming... worthwhile design bounty?
19:05:44 <schendje> it's interesting for sure
19:05:56 <wwoods> argh, themes
19:05:58 <schendje> though maybe a bit heavy on the CSS side
19:06:10 <stickster> wwoods: HOTDOGLOVE
19:06:47 <schendje> but I'll have a look at it and post something to the Design mailing list
19:06:57 <schendje> see what the others think
19:07:21 <stickster> schendje: That would be great -- I'd really like to see if we can get that finished up in the next few weeks
19:07:31 <schendje> stickster: definitely, me too
19:08:03 <stickster> asrob: averi: Have you guys been able to do everything you need to with the new pt09 instance?
19:08:46 <smooge> yes I am interested in if pt09 is useful?
19:09:07 <averi> stickster, me and asrob had to meet up but we never had the possibility. All modules should be set up on pt9 anyway.
19:09:19 <asrob> +1
19:09:21 <stickster> smooge: I can tell you for one thing that some of our modules depend on newer PHP which EL-6 provides
19:09:47 <averi> stickster, we've discussed one or two times about the calendar thingy I told you about
19:09:55 <stickster> smooge: There's actually a php53 stack available in EL-5, but the problem is that the package requirements for Drupal don't allow us to use that.
19:10:15 <stickster> averi: Yes, I think it would be a great addition for Phase 2
19:10:34 <smooge> ugh
19:10:52 <stickster> smooge: Yeah. So EL-6 made a big difference for us.
19:11:14 * stickster notes that all the required modules are installed/available now, per his action item from last meeting
19:11:40 <averi> stickster, I heard a lot of people asking for a calendar to set up and have things well organized. Today we skipped our l10n-it meeting cause of that, so count on me for everything related to it. (from packaging to setting it up)
19:11:51 <averi> stickster, what's missing on pt9?
19:11:54 <stickster> averi: Will do -- have you added that to the project page?
19:12:17 <averi> stickster, sure
19:12:55 <averi> stickster, https://fedoraproject.org/wiki/Insight_project_plan
19:13:38 <stickster> averi: Not sure I understood your question about what's missing -- do you mean modules? content? something else?
19:14:10 <averi> stickster, yes, I meant what is missing to have a mirror of what the production website will be
19:14:35 <averi> we're ok with modules as said above, what else is missing?
19:15:24 <stickster> averi: I think we may be at the point where we have everything, other than the working theme
19:15:25 <asrob> averi: stickster, we use date, calendar and views modules in http://drupal.hu/esemenynaptar
19:15:46 <asrob> date and calendar are not packaged
19:16:02 <stickster> asrob: averi: Were you guys able to port all the view definitions and other customizations needed?
19:16:26 <asrob> stickster: done, https://fedoraproject.org/wiki/Insight_content_configuration
19:16:36 <stickster> asrob: I saw those this morning -- great job!
19:17:29 <averi> brb
19:18:59 <stickster> No problem averi
19:19:30 <stickster> asrob: If those modules need to be packaged for the calendar, make sure to note that in the Phase 2 requirements on the project plan
19:19:56 <asrob> stickster: okay
19:21:25 <stickster> #topic Packaging
19:22:00 <stickster> https://bugzilla.redhat.com/showdependencytree.cgi?id=662103&hide_resolved=1
19:22:31 <stickster> #info Above is the remaining modules that are on our blocker. Note that both Views and CCK need to be built. I believe those are both limb's packages.
19:22:54 <stickster> #action stickster poke limb about builds for EL-6
19:24:41 <stickster> I just ran the following command:
19:24:43 <stickster> bugzilla query -p Fedora -c 'Package Review' -t NEW,ASSIGNED --boolean_query='short_desc-substring-drupal'
19:24:55 <asrob> stickster: I put Calendar's dependencies into project plan phase2
19:24:57 <stickster> It shows some additional Drupal modules that need review. I took the two rename reviews for -date and -calendar
19:25:07 <stickster> Thanks asrob, good job!
19:25:39 <stickster> #action stickster do reviews for BZ 646612 and 646614
19:26:53 <stickster> asrob: What else do we need package-wise before we're ready for staging, in your estimation?
19:27:57 <asrob> stickster: I think nothing
19:28:18 <stickster> smooge: You saw it here ^^
19:28:26 <stickster> That brings us to...
19:28:31 <stickster> #topic Infrastructure stuff
19:28:44 <smooge> one sec sorry ... multitasking fail
19:28:52 <stickster> smooge: np. :-) One of our last pending pieces is the puppetizing of this box... IIRC you were working on that.
19:29:18 <smooge> yes. there are other issues now that we have moved ot EL-6
19:29:31 <smooge> like none of our core infrastructure is EL-6 nor will be soon
19:29:57 <smooge> so I need to look at what we have to do
19:30:30 <smooge> which is basically instead of having this on an app server having some sort of new class of boxes
19:31:39 <smooge> so we are back to resource management issues.
19:31:46 <stickster> smooge: Hm, that sounds like a pretty big job :-\
19:32:22 <stickster> smooge: The alternative is, get the drupal package's requirements fixed (if that's even possible) so that php53 packages satisfy them
19:32:39 <stickster> smooge: That would allow us to stage on EL-5
19:32:49 <smooge> that doesn't help because you can't run php53 and php5 on the same server
19:33:06 <smooge> so EVERYTHING php related (mediawiki etc) gets borked
19:33:32 <stickster> smooge: Ah, you're right -- that would be a problem. Unless this ran on a different class of box too?
19:33:55 <stickster> er, different subclass using EL-5...?
19:34:34 <smooge> the "price" of setting of a seperate EL-6 versus EL-5 is not much.
19:34:46 <smooge> it is more of setting of a seperate class of servers
19:34:47 <stickster> #info We have to solve an impasse issue here -- Infra is not yet ready to roll out core boxes on EL-6, and if we use EL-5 we need to be able to use the php53 stack instead of php
19:35:09 <stickster> smooge: I see -- so at this point, we might as well proceed with EL-6 then?
19:35:11 <ricky> Hi :-)
19:35:20 <asrob> hi
19:35:27 <smooge> yes. it is more of an impasse of tangible resources than intangible
19:35:28 <ricky> One thing we were actually talking about was splitting out apps more - I think it'll be fine to go for EL6
19:35:57 <rbergeron> oh-hai
19:36:04 <asrob> hi :)
19:36:06 <ricky> Also, is this a good time to talk about long-term maintenance of Drupal on infrastructure?
19:36:14 <smooge> yes
19:36:35 <ricky> We have little expertise on PHP/drupal on infra, and we're already spread pretty thin on the rest of our apps
19:37:01 <ricky> So we'd like to sponsor some new people to run drupal, keep up with security updates, etc.
19:37:05 <stickster> ricky: That's what this team is here to do :-)
19:37:17 <stickster> asrob, averi, myself, and pcalarco have all been learning for this purpose.
19:37:30 <ricky> Perfect :-)
19:37:50 <asrob> :)
19:37:52 <ricky> So at some point, we'll want to get you all through http://fedoraproject.org/wiki/Orientation_Infrastructure_SOP
19:37:55 <stickster> ricky: We've been packaging modules so that we can do "in-Fedora" style updates (incl. EPEL)
19:38:02 <ricky> And used to working on our infrastructure
19:38:12 <smooge> so we would build a set of insight servers that would be run by sysadmin-insight that could run things
19:38:18 * skvidal is curious
19:38:30 <skvidal> is there a doc stating the resource requirements for insight?
19:39:41 <stickster> skvidal: https://fedoraproject.org/wiki/Insight_project_plan is our project plan, but we're light on infrastructure details. That was one reason for having smooge at these meetings back when we started them
19:40:03 <stickster> If by requirements you mean allocated storage, RAM, etc.
19:40:09 <smooge> I don't think I have filled out my parts so I need to do so
19:40:10 <averi> back, sorry
19:40:11 <skvidal> ricky, smooge: would insight make a good item to try out some of our new plans on?
19:40:19 <skvidal> ie: app specific db
19:40:24 <skvidal> perhaps replicated db
19:40:31 <skvidal> maybe even external hosting?
19:40:45 <smooge> external hosting runs into the fas issue.
19:41:38 <ricky> In a perfect world, external hosting + openid would solve the FAS issue
19:41:51 <skvidal> is the limit on authing outside of phx technical or policy?
19:42:10 <smooge> I think it is also out of scope for this meeting. something we can talk about after their business is done.
19:42:17 <skvidal> ok
19:42:22 <skvidal> that's fair
19:42:22 <stickster> ricky: FWIW there is an OpenID authentication plugin in Drupal, part of its core IIRC.
19:42:26 <smooge> sorry I just want to keep it to their weeds versus ours :)
19:42:31 * abadger1999 not familiar with a  fas issue and external hosting
19:42:34 <fenrus02> stickster, yep.  works.
19:42:34 * stickster +1 smooge
19:42:38 <asrob> stickster: yes, you're right
19:43:08 <stickster> Let's let the Infra guys figure out what they want to try out, and I think I speak for the team when I say we're OK with being guinea pigs
19:43:15 <stickster> Any +/-1 team members?
19:43:23 <asrob> +1
19:44:46 <averi> fine for me :)
19:44:52 <stickster> OK.
19:45:16 <stickster> smooge: Can you be responsible for letting us know what, as guinea pigs, we need to do next?
19:45:40 <ricky> If you're ready to move to staging, I think the next step is getting the entire team through Fedora Infrastructure orientation
19:45:53 <ricky> And by the time that's ready, we'll have servers built for you guys to work on
19:46:02 <smooge> yes. I will bring it up in the next meeting and will have a answer by Monday
19:46:05 <stickster> ricky: We're *almost* ready. The theme still needs to be finished. But we can do orientation anyway, I think.
19:46:17 <asrob> +1
19:46:41 <ricky> I'm already talking to averi about joining FI, see the rest of you soon :-)
19:46:57 <stickster> #action smooge let the Insight team know whether we can proceed with an orientation for FI, or other tasks
19:47:44 <stickster> That's all I have for today, so...
19:47:51 <stickster> #topic Open floor, all other business
19:48:30 <averi> stickster, forgot to ask, what have we decided about internalization?
19:48:55 <averi> stickster, will we use the drupal module for doing that?
19:49:07 <stickster> averi: Yes, but it's complex enough that we may not be able to add this until Phase 2.
19:49:12 <asrob> stickster: I'm going to set up old imported contents' automatic deletion
19:49:22 <stickster> asrob: Can you #info that please?
19:49:30 <stickster> Oh, I forgot schendje's action item earlier, sorry
19:49:45 <averi> stickster, out of curiosity, when phase 2 will be applied?
19:49:47 <schendje> stickster: np, i've got nothing to report really
19:49:48 <stickster> #action schendje Bring "theme as a bounty" idea to the Design Team
19:49:57 <schendje> ah that one :)
19:50:04 <schendje> i'll work on the theme a bit more tonight
19:50:06 <asrob> stickster: I'll do that after meeting ;)
19:50:22 <stickster> averi: We can start on it after Phase 1 enters production
19:50:56 <stickster> averi: That's on purpose, so we don't scope creep forever while we figure out how to do new and interesting things.
19:51:12 <asrob> stickster: because I'm enabling/configuring rules module now
19:51:19 <averi> stickster, simply great! i think i'll know coordinate with asrob on how to move on our side. (/me still needs to know what's missing our side)
19:51:36 <stickster> For instance, a question I have regarding i18n/l10n is whether we can leverage existing workflow so that we're not maintaining a separate translation interface and workflow.
19:51:52 <stickster> We should look at whether/how we can hook into Transifex for this.
19:52:20 <stickster> asrob: For old content deletion -- the 30 days for old RSS feed items we talked about -- should be no problem
19:52:30 * stickster notes he has hard stop in 3 minutes
19:52:31 <asrob> stickster: I got it ;)
19:52:42 <stickster> #action asrob work on auto content deletion for >30 day old feed items
19:53:15 <stickster> #action averi start looking into how we can leverage existing i18n/l10n workflow, such as Transifex, with Insight
19:55:05 <averi> stickster, sure, will ask how it managed for other services like fedora website etc. (I am a bit stuck with the current(?) tx migration
19:55:54 <stickster> averi: I understand. The migration shouldn't be a make-or-break, though... you can still probably find out how we can hook translations to an external system like Tx
19:56:39 <stickster> The point is to figure out what it will cost translators to be able to help with our content. I think they might benefit if we make it easy for them in the system they already use
19:56:46 <averi> stickster, sure thing, will take care of how existing website is hooked to tx
19:57:02 <averi> * checking how
19:57:25 <averi> stickster, of course this applies to non-issues translations, correct?
19:57:38 <stickster> averi: Let's not constrain it yet
19:57:46 * stickster needs to move on, let's end the meeting
19:57:52 <stickster> in 30
19:58:07 <averi> stickster, ok, sorry :)
19:58:20 <stickster> #endmeeting