19:00:33 <stickster> #startmeeting Insight
19:00:34 <zodbot> Meeting started Mon May  2 19:00:33 2011 UTC.  The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:00:35 <stickster> #meetingname Insight
19:00:35 <zodbot> The meeting name has been set to 'insight'
19:00:40 <stickster> #topic Roll call
19:00:42 * stickster 
19:00:46 * asrob too
19:01:11 * stickster is hoping pcalarco might be around for this
19:01:25 * jsmith-busy lurks
19:03:00 * stickster wonders if nirik had the chance to install backup_migrate from epel-testing on the production server for us
19:03:19 * nirik checks.
19:04:29 <stickster> #chair asrob
19:04:29 <zodbot> Current chairs: asrob stickster
19:04:39 <stickster> #topic Action item status
19:05:13 <stickster> #link http://meetbot.fedoraproject.org/fedora-meeting-1/2011-04-25/insight.2011-04-25-19.01.html <-- last week's notes
19:05:27 <stickster> Unfortunately I was on travel all last week after our meeting and didn't complete all my action items
19:06:01 <stickster> #info stickster got the puppet change made in staging -- but it won't work automagically until drupal6-backup_migrate package is in stable repo.
19:06:40 <nirik> ok. You need that installed on stg? or production? or both?
19:06:41 <stickster> Our sudo powers only apply to insight.dev as far as I know, so we need someone with more sudo-superpowers to install that package on insight.fp.o and insight.stg.fp.o
19:06:48 <stickster> nirik, ^^
19:06:57 <nirik> so, both?
19:07:05 <stickster> nirik, Yes, please, thank you sir :-)
19:07:34 * stickster is proud at least of the fact that we are doing the proper packaging work required!
19:08:17 <nirik> ok, it's on both. I had installed it on stg, but not prod yet.
19:08:26 <stickster> Thanks nirik!
19:09:56 <stickster> #info stickster has enabled backup_migrate on the insight.fp.o host -- so we can take snapshots for the development as needed now.
19:09:59 <stickster> asrob, ^^
19:10:02 <asrob> \o/
19:11:05 <stickster> asrob, So right now, remember that snapshots should only be going one way, *except* as we get changes approved by the team as set out in the change process
19:11:32 <stickster> i.e. we snapshot content back from insight.fp.o -> insight.dev.fp.o
19:11:54 <asrob> I got it
19:11:55 <stickster> #action stickster needs to complete https://bugzilla.redhat.com/show_bug.cgi?id=698590 which he will do right after this meeting
19:12:41 <stickster> asrob, We still need to have a discussion on the list about whether, and how, we're going to use Features module for rolling out development.
19:12:59 * stickster has been using it some to get a feel for how it works
19:13:10 <asrob> ;)
19:13:11 <asrob> OK
19:13:56 <stickster> asrob, I'm looking to you to drive that discussion. The goal is to get a working document that describes in simple terms how features are going to be controlled and rolled out
19:15:05 <stickster> One way to do that would be to draft something on the wiki and get comments. Another way might be to simply start the discussion on the list, and put together a draft based on that. I tend to think the first is more effective, but it's completely up to you
19:16:01 <asrob> ah, I see, I will create a draft page on the wiki
19:16:46 <stickster> asrob, One thing you can look at for a model is the theme development for Insight
19:17:45 <asrob> but we need to talk about how to organize our Features, for example: Super Insight Gallery or Phase2 Development?!
19:17:54 <stickster> It seems to me we could use roughly the same model on the back end -- a git repo, with upstream releases and packaging that goes into the Infrastructure repo since a collection of features wouldn't be useful to package since it's more general
19:18:07 <stickster> asrob, Sure, that's a question that the discussion can answer
19:18:39 <asrob> yeah
19:18:45 <stickster> #action asrob Drive discussion on logistics list on how to use Features to manage our development/deployment
19:19:18 <stickster> #topic Current deployment status
19:19:44 <stickster> So right now we have a number of tickets outstanding, but now that backup_migrate is in place we should be able to make quick headway on fixing most of them.
19:19:55 <asrob> absolutely
19:20:46 <stickster> asrob, Would you agree that we can gather/create Features (notice capital "F") post facto where we've already made fixes?
19:21:03 <stickster> IOW, we don't need to block fixes for the site on our discussion about how to manage Features with development
19:21:10 <asrob> +1
19:21:12 <asrob> sure
19:23:09 <stickster> #agreed We can proceed with fixes, and roll them into Features (with a capital "F") later without a problem
19:23:42 <stickster> asrob, Do you have membership in the sysadmin-insight group now?
19:23:47 <stickster> .fasinfo asrob
19:23:49 <zodbot> stickster: User: asrob, Name: Peter Borsa, email: peter.borsa@gmail.com, Creation: 2008-06-27, IRC Nick: asrob, Timezone: Europe/Budapest, Locale: en, Extension: 5109099, GPG key ID: , Status: active
19:23:49 <asrob> stickster: I could not test FAS module on my test instance, probably I made a few mistake so I would test it on our dev. server, what do you think?
19:23:53 <zodbot> stickster: Approved Groups: sysadmin-insight sysadmin sysadmin-test fedorabugs packager gitfedora-insight-theme cmsadmin cla_fedora cla_done
19:23:54 <asrob> stickster: yeah, I am a member
19:23:59 <stickster> nifty
19:24:54 <stickster> asrob, what happened when you tried to test it?
19:25:40 <asrob> stickster: I could not login my username, there is not anyone else just my admin account
19:26:08 <stickster> asrob, And you pointed it at which instance? FakeFAS or real FAS? And did you use the verification section to test?
19:27:24 <asrob> I used FakeFAS url, no, I did not
19:27:38 <stickster> asrob, Remember that FakeFAS doesn't use the same credentials as real FAS
19:27:49 <stickster> And you probably have to turn on the option for trusting invalid SSL certs
19:27:50 <asrob> I used this url, Location of FAS instance:  https://fakefas01.fedoraproject.org/accounts
19:28:08 <stickster> You want to cut off the 'https://' at the beginning
19:28:40 <stickster> Also, make sure that the "trust invalid SSL certs" option is on... and ensure you can login properly at the FAS instance itself at https://fakefas01.fedoraproject.org/accounts
19:29:29 <asrob> "trust invalid SSL certs", where is this?
19:29:57 <stickster> asrob, it should be in the configuration page for AuthFAS settings
19:30:12 <asrob> hmm, it is weird, I cannot see this
19:30:35 <stickster> asrob, Do you have the latest authfas installed?
19:30:48 <stickster> Should be 0.2.3-1
19:31:41 <asrob> stickster: yeah, asrob@alpaca [~/insight.asrob.net/sites/all/modules/authfas]# git pull
19:31:43 <asrob> Already up-to-date.
19:32:20 <asrob> stickster: http://rookery9.aviary.com.s3.amazonaws.com/7874500/7874601_092d.png
19:33:01 <stickster> asrob, in your /sites/all/modules/authfas, run this command:
19:33:04 <stickster> cat .git/refs/heads/master
19:33:23 <asrob> stickster: 86704e458d10550eaa55e9aac1d2de129f16eb5a
19:33:40 <stickster> asrob, That's back a bit from current head I think
19:33:54 <asrob> :(
19:34:49 <stickster> asrob, do:  git remote -v
19:35:03 <asrob> origin  git://fedorapeople.org/home/fedora/pfrields/public_git/drupal-authfas-6x.git (fetch)
19:35:05 <asrob> origin  git://fedorapeople.org/home/fedora/pfrields/public_git/drupal-authfas-6x.git (push)
19:35:05 <stickster> It should be pointing at git.fedorahosted.org/git/drupal6-authfas
19:35:12 <stickster> You're pointing at an old repo
19:35:16 <asrob> oops
19:35:49 <stickster> That's probably why it's not working -- the certs trusting wasn't available back when we moved that repo
19:36:19 <asrob> I see, then I will clone that repo and try it again
19:36:23 <stickster> OK
19:36:43 <stickster> #action asrob pull current repo and try authfas locally again... should work this time
19:37:00 <stickster> asrob, You can just edit .git/config and then do another pull, and I think it will work
19:37:29 <stickster> You'll want to be pointing instead at:   git://git.fedorahosted.org/git/drupal6-authfas.git
19:38:11 <stickster> asrob, Email the list if you have any trouble and we can get it sorted out quickly
19:38:44 <asrob> ah, got it, it works, thanks
19:38:48 <stickster> cool
19:38:50 <stickster> #topic Events calendar and GSoC
19:39:09 <stickster> So this past weekend I saw this:
19:39:17 <stickster> #link http://k3rnel.net/2011/04/27/gsoc-fedora-events-system-2/ <-- blog on a Fedora Events System
19:39:28 <stickster> nirik, Not sure if you heard anything about this? ^^
19:39:48 * nirik looks
19:40:14 * stickster is hesitant about custom web apps from scratch when we have a number of good frameworks already out there
19:40:22 <stickster> see comments. I'm not sure Nushio'
19:40:22 <nirik> I had heard of it, but not too many details.
19:40:23 <stickster> oops
19:40:46 <stickster> see comments. I'm not sure Nushio's last comment makes sense to me. If someone wants to build a web events system, why would you *not* leverage a known platform?
19:42:03 <nirik> sounds like it might be good to get into a more realtime dialog with those folks.
19:42:42 <stickster> nirik, Nushio said he would attend today's meeting to discuss -- not sure if he's around though.
19:43:21 <nirik> ok. cool.
19:43:45 <stickster> nirik, I suspect there is some partial work already out there in the Drupal community to do this very thing -- and it makes sense as a free software imperative to at least look at that work and build on it if possible
19:43:54 * nirik nods.
19:44:18 <stickster> "Recreate from ground up" has some very distinctive risks involved
19:45:26 <stickster> I notice that hiemanshu is working with Nushio -- and I *know* hiemanshu is aware of Insight and Drupal features that could be leveraged for this purpose
19:46:04 * stickster would be totally thrilled to give them access to the dev host and let them develop alongside our other work
19:47:05 <stickster> #action stickster invite Nushio to logistics list as well (hiemanshu is already there IIRC) to discuss his GSoC project
19:47:13 <stickster> That's all I've got for today really
19:47:16 <stickster> #topic Open floor
19:47:55 <asrob> stickster: I found an error when I logged in
19:47:58 <asrob> stickster: "warning: Invalid argument supplied for foreach() in /home/asrob/insight.asrob.net/sites/all/modules/authfas/authfas.module on line 268."
19:48:24 <stickster> asrob, Let's discuss offline after meeting then
19:48:28 <asrob> okay
19:48:34 <nirik> I have something.
19:48:39 <stickster> nirik, Go right ahead sir!
19:48:52 <nirik> herlo whipped up: https://fedoraproject.org/wiki/Fedora_Calendar_Project
19:49:02 <nirik> as requirements for a calendar server, etc.
19:49:11 <nirik> I'm sure it could use more tweaking... but it's a start.
19:49:56 <stickster> It's a great start -- and if Nushio's work is for a Fedora Events System, then it should take those rqeuirements into account
19:50:20 <stickster> I'm not sure where else they're gathering requirements, but that's something we can ask. nirik, you're on the logistics@lists.fp.o list, correct?
19:50:24 <nirik> yeah, so do add to/tweak that and see if we can get something that meets those needs.
19:50:35 <nirik> not sure I am. ;) I guess I should subscribe to that one
19:51:33 <stickster> nirik, Yeah, it's generally low traffic and likely of interest to you
19:51:55 <stickster> #action asrob stickster visit https://fedoraproject.org/wiki/Fedora_Calendar_Project and edit requirements as needed
19:52:11 <stickster> #action nirik join logistics list for mo' betta Fedora fun
19:52:21 <stickster> Anything else to cover today?
19:52:25 <asrob> nothing
19:52:41 * nirik has nothing.
19:53:25 <stickster> Okey doke, closing in :30 then
19:55:07 <stickster> #endmeeting