18:00:00 #startmeeting Fedora Insight -- Agenda: https://fedoraproject.org/wiki/Insight#Meeting_agenda 18:00:00 Meeting started Thu Jul 29 18:00:00 2010 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:06 #topic Roll call! 18:00:10 * rbergeron 18:00:19 * stickster 18:00:30 #chair rbergeron 18:00:30 Current chairs: rbergeron stickster 18:00:39 thanks, i needed to sit down :) 18:01:23 * rbergeron looks around 18:01:27 here 18:01:39 * mizmo Máirín 18:02:00 * jsmith lurks 18:02:25 (Teaching a class for my ex-employer this week, but keeping an eye on the channel) 18:03:05 Is gwerra around? 18:03:18 he was like... a very short time ago 18:03:39 * stickster gives 30 sec and then will move on 18:03:54 * rbergeron just hailed him back in -mktg even though he's here, too 18:04:06 OK, moving on 18:04:14 #topic Review action items 18:04:21 #link http://meetbot.fedoraproject.org/fedora-meeting/2010-07-22/fedora_insight.2010-07-22-18.01.html <-- last week's minutes 18:04:35 #info 1 <-- done 18:04:54 smooge and I talked about the FakeFAS, it did disappear from pt3 but we are going to set up a new one on pt4 18:05:10 smooge is fixing a sudo problem for me so I can work on that :-) 18:05:23 #action smooge Finish fixing sudo problem on pt4 18:05:48 how did it disappear? 18:05:54 I think it happened during a rebuild 18:05:57 not to be offtopic - but 18:05:58 ahh 18:05:59 * gwerra is here 18:06:08 * rbergeron just wonders if we did something incorrectly, or something. 18:06:08 Hi gwerra! 18:06:21 rbergeron: Nope, I think it was missing dependency info that we were using it. 18:06:27 ahhhh. 18:06:37 #action stickster to set up new FakeFAS, with help from smooge, and make sure pt4 info page shows we're using it. 18:06:50 #info 2 <-- underway 18:06:53 stickster, let me know if its not working now 18:06:57 smooge: Thanks! 18:07:22 smooge: Working fine now, thanks! 18:07:42 OK, #3 is the Insight page and plan 18:07:54 I will confess I had very little time to work on this in the past week because of other $DAYJOB stuff 18:08:02 But I am putting some muscle into it tomorrow and the weekend. 18:08:38 #info 3 <-- stickster was too bogged to do this, but is working on it over the next few days 18:08:51 #action stickster to work on [[Insight]] wiki page and updated project plan 18:08:53 you mean the insight wiki page? 18:08:56 ah, you clarified. :) 18:08:58 :-) 18:09:31 #info 4 <-- done/worksforme 18:09:35 OK, that's it for review stuff 18:09:39 Shall we move on? 18:09:44 yes plz. 18:09:45 :) 18:09:53 #topic Test instance 18:10:13 OK, the big news is that smooge got us a new public test box built 18:10:26 #info Test instance is now on publictest4.fedoraproject.org 18:10:45 I'll be adding a Drupal 6 installation to that box, in accordance with the wiki instructions 18:11:55 #action stickster to add drupal6 from the RPM package pending (and almost finished) in review 18:12:32 Also, I'll be adding FakeFAS as seen eariler, so we can fiddle with people and groups without disturbing any of the production systems 18:12:53 #info important note: People should use *different* passphrase for FakeFAS than what they use for the real FAS system 18:13:04 It shouldn't be considered secure. 18:13:08 * rbergeron nods 18:13:23 #info Important(er) note: Don't use any passphrase you care about someone knowing :-) 18:13:26 will the new FAS be a copy /restore of old FAS or completely new? 18:13:50 of oldFakeFas 18:13:52 i mean :) 18:14:02 rbergeron: I don't know if there's any value in sync'ing it, unless lots of other people need to use it (in which case they could build their own instances, I suppose) 18:14:09 smooge: What do you think? 18:14:45 one sec 18:14:55 completely new 18:15:11 smooge: Yeah, I agree 18:15:14 stickster: we should make a new one 18:15:16 okay :) 18:15:17 I don't think I can copy stuff from existing fas. will have to ask mmcgrath what populatesit 18:15:58 smooge: Do you have to do some sort of copy to just get a new one off the ground? Or is that only required if we wanted to copy in some data? 18:16:50 * stickster would suspect starting a brand new instance with no one in it shouldn't need any copying, since it's intended to work that way for any project that decides to use FAS 18:17:10 * rbergeron nods 18:17:14 stickster, I have no idea. this is my first time dealing with this 18:17:20 smooge: OK, we'll figure it out 18:17:45 We have the action item above already, this is just one aspect of that work :-) 18:17:51 * stickster may just try it and see how it goes 18:18:03 The worst that happens is we start over, and the best is that I can learn and document FAS setup 18:18:32 Oh, I should #topic. 18:18:34 #topic FakeFAS 18:18:55 #info See above for action item on FakeFAS. smooge and stickster will try their hand at it, and learn/document in the process. 18:19:31 #info the FakeFAS is being set up so that we can use/test the AuthFAS plugin too. 18:20:07 gwerra: Since you're here also, and I know you were keen to work on theme stuff, let's talk about that a bit, is that OK? 18:20:32 stickster: sure 18:20:33 #topic Themes, modules and devel SOP 18:20:52 What we want to do is *not* to just edit stuff in the /usr/share/drupal6 area directly. 18:21:09 That's a sure route to confusion, don't want to go down that road 18:21:34 (1) Theme and module development to live in /etc/drupal6/all/ 18:22:03 gwerra: In fact, here's what I did when I was working on AuthFAS... 18:22:12 stickster: well /etc is usually just configs, we can use /var/drupal or something 18:22:35 gwerra: Actually, using /etc is how the packages are set up for both drupal and drupal6 IIRC 18:23:17 Here's what I did 18:23:31 1. Start a git repo for my work 18:23:43 2. Clone it into /etc/drupal6/all/modules/ 18:23:44 stickster: Fix the drupal6 package then :) , /etc/drupal6/* doesn't look like a good idea to me 18:23:57 gwerra: You're welcome to comment on the review bug :-) 18:24:05 stickster: bug number? 18:24:13 gwerra: Don't recall, but search for 'drupal6' 18:24:30 * stickster thinks this is bikeshedding 18:24:35 Regardless of where the stuff goes... 18:24:50 2. Clone repo into 18:25:34 3. Use branches for rough tries, and check them out onto pt4 to try work periodically 18:25:42 When happy, merge and push 18:26:34 Which makes a lot more sense to me than just 'sudo $EDITOR /usr/share/drupal6/stuff' which can break the RPM database integrity and other yuckiness. 18:26:44 smooge: gwerra: What do you think? 18:27:07 #link https://bugzilla.redhat.com/show_bug.cgi?id=569833 <-- drupal6 review 18:28:08 correct /usr is verbotten. whehter it is /etc/ or /var or /var/www/site/ does not matter that much to me 18:28:44 stickster: that sounds good to me (sorry I was too busy reading the review) 18:29:01 smooge: Me neither, and I'm not going to bother the reviewer about it. It would also require a change in SELinux policy to move stuff too 18:29:22 s/reviewer/packager+reviewer/ 18:29:48 OK, so shorthand: 18:30:03 greetings all 18:30:06 stickster, correct. I will let the FPC deal with that 18:30:15 pcalarco: hello 18:30:23 #info Team will use repo to manage theme and module stuff, and will not edit things live on /usr to avoid losing work in case of a rebuild or outage 18:30:28 #undo 18:30:28 Removing item from minutes: 18:30:31 #agreed Team will use repo to manage theme and module stuff, and will not edit things live on /usr to avoid losing work in case of a rebuild or outage 18:30:40 Oh, I should have chaired more people 18:30:45 Hi pcalarco! It's great to see you! 18:30:53 #chair gwerra smooge mizmo pcalarco 18:30:53 Current chairs: gwerra mizmo pcalarco rbergeron smooge stickster 18:31:17 So it's good to have agreement there, before we do any real work. 18:31:22 What's equally important is... 18:31:24 stickster: btw do we have mockups for the theme? I can start working next week 18:31:37 gwerra: I think we can continue with the original mockups 18:31:59 It looked great, we just have to do some fiddling to make it work on a diff. platform 18:32:08 Yup 18:32:16 * stickster finds his thought back again... 18:32:21 So it's good to have agreement there, before we do any real work. 18:32:23 What's equally important is... 18:32:27 #topic Project plan 18:32:46 Stepping back a little, we really want to start with a plan that helps us judge our progress better. 18:33:06 We kept running into problems where it was hard to say whether we were on target 18:33:35 mizmo: I'm glad you came by for this meeting, because one of the things I want to do in the plan is to take into account uses people will have beyond just "publish the news" 18:34:18 We don't want to try and do everything at once, but it will be good to have some people paying attention to the project who are thinking about what we can provide w/Drupal later on 18:34:44 yeh 18:34:48 * stickster is trying to do this in a lightweight, Fedora-like process but with something resembling some order 18:34:55 the new article series in the website would be well-managed by a system like drupal 18:34:58 i.e. get all the requirements/targets down on the wiki first 18:35:11 it could also provide a great gateway for new contribs to follow mailing lists 18:35:17 Yup 18:35:44 And we'll need to get some idea of how long putting all these things will take, before we decide on scope for the first bits, vs, what we add in later stages 18:36:00 * stickster thinks FWN is a shoe-in, because we promised that first. 18:36:13 But regardless, we don't need to make the whole list here in this meeting 18:36:23 I'm going to propose something via the wiki, and then write to the logistics@ list about it. 18:37:01 kk 18:37:02 #action stickster to put the proposed plan on the wiki (linked from the [[Insight]] page) and then we'll edit/come together on the details. 18:37:45 I have to run now, got some college work to finish before I crash 18:37:53 gwerra: Understood -- thanks for being here 18:37:59 gwerra: You're on logistics list, right? 18:38:05 * stickster asks in general if everyone is 18:38:11 * rbergeron is 18:38:23 stickster: yup 18:38:25 is 18:38:32 We're trying to keep conversations there so that people from lots of teams can see what's going on without a lot of cross posting. 18:39:02 is 18:40:05 OK, good on us then :-) 18:40:45 Did anyone want to say or ask anything about the project plan? 18:40:58 * rbergeron raises hand 18:41:28 rbergeron: You're on, fire away! 18:41:34 Can we - and maybe this isn't the right place for it - but somewhere detail the plan wrt development spot and some guidelines - checking things in and out, not doing them live, etc? 18:41:54 rbergeron: Yes, definitely. 18:42:06 because I think we had a lot of trouble with that last time around - and I think setting up some expectations up front, either in "the plan" or elsewhere - or having that stuff discussed as a point on the project plan - would probably save us time in the long run. 18:42:19 Now that we have those ground rules established above, I'll make sure to detail them in or linked from the plan. 18:42:37 #info stickster will definitely include the development process in or linked from the project plan 18:43:02 That way we don't end up with people making changes in a bunch of different ways to the point that we can't figure out where the "live" or "recorded" changes rae 18:43:03 *are 18:43:26 * stickster holds floor open for a minute for anyone else 18:43:37 Anything else on project plan? 18:44:23 #topic AOB (all other business) 18:44:40 OK, anything not on the agenda that we need to start thinking about, that's not part of planning?