August 2009 - logistics - Fedora mailing-lists

Fwd: Fedora Insight Zikula Instance - please help us find a packager
by Robert 'Bob' Jensen 28 Aug '09

28 Aug '09

----- Forwarded Message ----- From: "Robert 'Bob' Jensen" <bob(a)fedoraunity.org> To: "For discussions about marketing and expanding the Fedora user base" <fedora-marketing-list(a)redhat.com> Cc: logistics(a)lists.fedoraproject.org Sent: Wednesday, August 26, 2009 3:41:45 AM GMT -06:00 US/Canada Central Subject: Re: Fedora Insight Zikula Instance - please help us find a packager ----- "Mel Chua" <mel(a)redhat.com> wrote: > Marketing folks: > > We need packaging (or packager-recruiting) help. I'm going to be > traveling in some way for the next 12 hours, but in that time we need > to > find someone to do two simple packages (it looks like they'll be > extremely fast for an experienced packager, and Toshio stands ready to > > review them tonight whenever they are ready). > > We need the two modules listed at > http://lists.fedoraproject.org/pipermail/logistics/2009-August/000185.html > > for Fedora Insight, preferably within the next 24 hours. We need these > > packages in order to have RSS feeds and events blocks on the F12 > deployment of FI. > > Can anyone package or help find someone who can package? > > Thanks! > The always awesome Chitlesh Goorah is working on zikula-feeds. -- Bob

4 8

New FasAuth package for Zikula
by David Nalley 27 Aug '09

27 Aug '09

http://ke4qqq.fedorapeople.org/zikula-module-fedora-fasauth-0.2-1.fc11.src.… This has Simon's changes to fasauth as of 0100 UTC 28 August

1 0

Re: Docs Meeting 2009-08-26 IRC Log
by Mel Chua 26 Aug '09

26 Aug '09

> 00:12:49 quaid: yep, zikula theme is all rolling for FI > 00:13:07 mizmo is in progress on the theme: > http://publictest6.fedoraproject.org/zikula/ > 00:13:17 and Zikula is getting rolled out to staging > 00:13:35 and things are prepared in the repo (ideally) so she can > have related Docs theme in there to make a Docs-specific RPM of the > theme (AIUI) For the record: we just (literally; the infrastructure ticket just hit my inbox) got an svn* repo for Ziklua themes. svn+ssh://svn.fedorahosted.org/svn/fedora-zikula-theme (It's empty right now, but will contain one core/default Fedora theme - the one Simon put together - and subfolders that are variants on that Fedora theme for things like docs, FI, and whatever else we need.) The commit groups is svnfedora-zikula-theme and right now I am the only group admin (though this will change to include Mo and Simon shortly) so now you know who to ping if you need access. :) --Mel *why svn? a few reasons: (1) easier to deal with subfolders, (2) Mo likes it, (3) lower barrier to entry for designers, who can get tortoisesvn and drag and drop and click buttons instead of having to learn arcane git syntax and the command line just to contribute to an icon. (The eventual goal is to get Design folks to use version control for evvvverything as well.)

1 0

Fedora Insight status
by Mel Chua 26 Aug '09

26 Aug '09

To keep everyone in the loop - here's what's up (see log at end of email). As promised, I'll be updating the actual project page to reflect status later tonight (must find food first; stomach rumbly) - progress is *extremely* rapid right now, so keeping everything in sync will be a challenge. For future reference for where these discussions will be taking place: zikula-deployment-related things (modules, packaging, infrastructure, theming, etc) will all be on the logistics list. FI-content/workflow-related-things will all be on the marketing list. There will be a lot of overlap for the next few weeks, since the modules we're working on for deployment heavily affect the workflow we'll be using for our content. If you're on both lists, you'll get everything. If you're only concerned with zikula deployment and don't care about the details of how FI content will function, watch logistics. If you're only concerned with FI as a platform for marketing materials and don't care about the details of how that platform gets set up, watch marketing. We might have a few torrents of information on this over the next few weeks, as I will be erring on the side of transparency (information on what is happening available to everybody all the time). In particular, IRC conversations on FI zikula deployment will be summarized (and logged when possible) and sent to list - thanks to Rahul for the transparency-poke. We're moving fast, so things are chaotic. Thanks for keeping up and putting up with the construction mud and noise - I am *amazed* at how this is progressing. You folks rock. --Mel --- itbegins> mchua: Work overtook me the last couple of nights - how are we doing with Zikula? <mchua> itbegins: hey! mmcgrath was looking for you in #fedora-admin earlier about that, actually. <mchua> itbegins: he's getting it up on staging for us, but the fasauth plugin isn't working - it seemed to work when manually installed (grab source from git repo, stick in modules folder) but when the package was yum installed. <itbegins> mchua: Shoot, the package is out of date <itbegins> mchua: The code changes I made need to be mirrored into the package <itbegins> I completely forgot <mchua> itbegins: EvilBob went packager-hunting last night, and was successful - Chitlesh packaged at least one of the two modules you were looking for. * mchua looks to see which one. <mchua> itbegins: zikula-feeds. and mether is going to submit them for review. <mchua> itbegins: afaik, we still need pagemaster packaged and submitted and all that. <itbegins> If we get pagemaster done, we might be able to do this properly the first time - I can work on pulling it all together and walk mizmo through converting her templates <itbegins> if we just have feeds, that satisfies mizmo's biggest need when she was templating things <mchua> itbegins: this strikes me as a decent summary of activity in the last 24 hours, so I'm going to send the last few lines of this log to the marketing and logistics mailing list as a holdover for the better project status updates I should be writing tonight. <itbegins> https://bugzilla.redhat.com/show_bug.cgi?id=519483 <itbegins> looks like we got both <mchua> itbegins: WOW. That... awesome. *Both* packages. Wow. *torrent of gratitude towards Bob, Chitlesh, and Rahul* <itbegins> yes, I was impresed to say the least

1 0

Fwd: Fedora Insight Zikula Instance - please help us find a packager
by Robert 'Bob' Jensen 26 Aug '09

26 Aug '09

----- Forwarded Message ----- From: "Robert 'Bob' Jensen" <bob(a)fedoraunity.org> To: "For discussions about marketing and expanding the Fedora user base" <fedora-marketing-list(a)redhat.com> Cc: logistics(a)lists.fedoraproject.org Sent: Wednesday, August 26, 2009 3:18:08 AM GMT -06:00 US/Canada Central Subject: Re: Fedora Insight Zikula Instance - please help us find a packager ----- "Mel Chua" <mel(a)redhat.com> wrote: > Marketing folks: > > We need packaging (or packager-recruiting) help. I'm going to be > traveling in some way for the next 12 hours, but in that time we need > to > find someone to do two simple packages (it looks like they'll be > extremely fast for an experienced packager, and Toshio stands ready to > > review them tonight whenever they are ready). > > We need the two modules listed at > http://lists.fedoraproject.org/pipermail/logistics/2009-August/000185.html > > for Fedora Insight, preferably within the next 24 hours. We need these > > packages in order to have RSS feeds and events blocks on the F12 > deployment of FI. > > Can anyone package or help find someone who can package? > > Thanks! > > --Mel > Well I have spent several hours pimping this around in a couple venues to several potential victims. Suggested that they reply to this message to prevent duplication of efforts, lets hope for the best. -- Bob

1 0

Fedora Insight Zikula Instance - Module Packaging
by Simon Birtwistle 25 Aug '09

25 Aug '09

I've been regularly chatting to mizmo on IRC for the past few nights and we came to the conclusion an additional couple of modules would be useful (both for usability purposes and functionality). I realise we're bumping up very close to deadlines etc, and I'm not sure what the effort in packaging new modules would be at this stage. So, I think we need to treat these as optional-but-very-desirable. The two are Feeds - for displaying RSS feeds in sideblocks or on separate pages. This is a very simple module URL: http://community.zikula.org/module-Extensions-display-ot-component-component id-28.htm Source: http://code.zikula.org/parked/browser/trunk/interesting/CategoryModules/Feed s/Core-12 PageMaster - for custom content types (this is especially useful for the events postings, though we may yet come up with a better solution for these...) URL: http://community.zikula.org/module-Extensions-display-ot-component-component id-99.htm Source: http://code.zikula.org/pagemaster/browser/trunk/modules/pagemaster As far as I know, neither have bundled libraries. Simon

4 4

Spins page content
by Mike McGrath 25 Aug '09

25 Aug '09

So time is tight, Mo's got the mockups in good shape. I suspect the work of converting those mockups to actual HTML pages is going to be quite a process and a time consuming one at that. Should we get a specific list of things we want from the spins now so we can just plug them in when the time comes? I'm worried we'll get everything done just in time for F-12 but the spins won't have detailed pages yet. -Mike

2 2

Zikula 1.1.2
by Paul W. Frields 25 Aug '09

25 Aug '09

Looks like the inimitable David Nalley has the Zikula 1.1.2 package into testing for F-10/F-11/EL-5. The new package eliminates a bunch of bundled libs, fixes some Requires/BuildRequires stuff, and is generally awesome. I think the publictest* machines are allowed to draw on the epel-testing repo, so it might be worthwhile to update to the new package, so we're testing the latest and greatest. I don't think I have the sysadmin-noc privs needed, can someone do that? Thanks David! -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

7 11

Zikula PHP requirement change
by Paul W. Frields 20 Aug '09

20 Aug '09

David granted me commit ACL for the main Zikula package -- my purpose is to help him out with a package fix for Zikula. All the documentation on 1.1.x from Zikula states clearly that PHP >= 4.3 is required (even though they also note that the 4.x PHP branch isn't maintained anymore). So the 5.1.x that's in current EL-5 systems should be perfectly adequate. Does anyone object to my making this change, rebuilding the package, and submitting it for testing? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

2 2

Re: Zikula deployment date
by Stanley, Jon 19 Aug '09

19 Aug '09

I'm out right now but we decided that as the docs CMS, Zikula won't make it for F12. Marketing would like to have something minimally function, but I'm not sure if that's Zikula or something else right now, frankly. ----- Original Message ----- From: logistics-bounces(a)lists.fedoraproject.org <logistics-bounces(a)lists.fedoraproject.org> To: logistics(a)lists.fedoraproject.org <logistics(a)lists.fedoraproject.org> Sent: Fri Aug 14 20:18:27 2009 Subject: Zikula deployment date Do we have a solid date for when this is expected to be put into production? The Fedora Infrastructure schedule is tied, very closely to the Fedora launch. Note that we freeze two weeks prior to each pre-release. That means, as long as there's no slips, we will be frozen from September 8th through the 23rd as well as October 20th through the 4th. Just a warning from experience, these freeze zones really sneak up on you. Also, slips often get announced during one of our freeze periods so what starts as a 2 week freeze, often ends up being a 3 or even 4 week slip. Doing the math that leaves very little time during these pre-release and final release periods to get changes in. I'd strongly recommend getting zikula deployed as soon as possible, we're currently frozen for the alpha but we have a window from August 25th to September 8th where we can do this if it's ready. If not, we're pushing _really close_ to that period of time that almost never goes according to schedule. Also note the translation deadline is September 15th. Not sure if we were planning on having content that should be translated or not. -Mike, bringer of doom _______________________________________________ logistics mailing list logistics(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/logistics This message contains information which may be confidential and/or privileged. Unless you are the intended recipient (or authorized to receive for the intended recipient), you may not read, use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message and any attachment(s) thereto without retaining any copies.

10 18

Fedora 12 Alpha Release Readiness Meeting Recap
by John Poelstra 19 Aug '09

19 Aug '09

Fedora 12 Alpha Release Readiness Meeting Recap 2009-08-19 Fedora 12 Alpha Release scheduled for 2009-08-25 Invitees: Ambassadors -- David Nalley (present) Design -- Máirín Duffy (present) Documentation -- Eric Christensen FESCo -- Jon Stanley Fedora Engineering Manager -- Tom "Spot" Callaway (present) Fedora Project Leader -- Paul Frields (present) Infrastructure -- Mike McGrath (present) Marketing -- Mel Chua (belated) Quality -- James Laska (present), Adam Williamson (present) Release Engineering -- Jesse Keating (present) Translation -- Noriko Mizumoto (present) Websites -- Ricky Zhou (present) Facilitator -- John Poelstra (present) == QA == * Blocker List: https://bugzilla.redhat.com/showdependencytree.cgi?id=507676&hide_resolved=1 ** One remaining issue -- https://bugzilla.redhat.com/show_bug.cgi?id=516941 * Installation Testing ** https://fedoraproject.org/wiki/QA:Fedora_12_Alpha_RC1_Install_Test_Results ** https://fedoraproject.org/wiki/QA:Fedora_12_Alpha_RC2_Install_Test_Results <-- INPROGRESS --> ** respin for jigdo * Xorg ** Looks pretty good ** Big one was server+nouveau breakage, but both cleared now ** intel+nouveau are in better shape than f11, probably ** tracking a possible breakage in 3D acceleration on radeon, but basic functionality looks OK * Common bugs page is up and ready to go ** https://fedoraproject.org/wiki/Common_F12_bugs * no known major breakage in any other critical path components == Release engineering == * Why an RC2 ** There's a limited amount of disk space on the spin host; can't have unlimited number of composed stuff there ** Had to scrub compose tree, but needed it and the ISOs for jigdo content ** Shuffling is annoying, but it's under control now and the RC2 is pre-staged to master mirror ** Need to investigate more disk space in the future == Marketing == Short version: we're good. Long version: We aren't being blocked by any other teams for Alpha, nor (to my knowledge) are we blocking any other teams. We are on track for our schedule: http://poelstra.fedorapeople.org/schedules/f-12/f-12-marketing-tasks.html ...and you can see active tasks and their (up-to-date as of yesterday afternoon) status at https://fedorahosted.org/marketing-team/report/3. Starting work on talking points and feature profiles. Working to get Fedora Insight up and running; tight time line, but it looks like we can do it. == Infrastructure == * Everything in good shape * Meeting upcoming for all remaining details == Documentation == * Looking good, just spinning up for start of release notes process now == Translation == * Looking for feedback on ticket to FESCo https://fedorahosted.org/fesco/ticket/243 == Design == * Figured out default wallpaper and looking forward to refreshing on Friday * Overall website design for Fedora 12 ** get.fedoraproject.org ** spins.fedoraproject.org ** Need to clarify what we are targeting for Fedora 12 *** F12 -> clean up meat of the get-fedora page and spins page *** Use existing templates on site for the new designs == Websites == * Looking good == Ambassadors == * No concrete deliverables for Alpha

1 0

Updated Fedora 12 Schedule--Final Release Date 2009-11-10
by John Poelstra 18 Aug '09

18 Aug '09

As a follow-up to last week's announcement changing the date for the Fedora 12 Alpha release, https://www.redhat.com/archives/fedora-devel-announce/2009-August/msg00006.… the remaining tasks in the Fedora 12 schedule have been adjusted by one week. https://fedoraproject.org/wiki/Releases/12#Key_Milestones The new milestones are as follows: 2009-08-25 Alpha Release 2009-09-22 Software Translation Deadline 2009-09-29 Beta (Final Development) Freeze 2009-10-13 Beta Release 2009-10-27 Compose & Stage Release Candidate 2009-11-10 Fedora 12 Final Release Updated detailed schedules are available here: http://poelstra.fedorapeople.org/schedules/f-12/f-12-key-tasks.html iCal files for each team are here (files ending in .ics): http://poelstra.fedorapeople.org/schedules/f-12 John

1 0

Hosted identi.ca
by Paul W. Frields 18 Aug '09

18 Aug '09

Evan, the principal and CEO behind laconi.ca and identi.ca (Control Yourself, Inc. in Montreal), has started offering free hosted instances to some free projects. I met Evan at Open Source Bridge in Portland last month and he asked me if the Fedora Project would be interested in one. I told him we would definitely love to try it out, because of our mission of and support for 100% free and open software and services. I believe this is their status.net service, launched very recently. Now that Evan says there are some of these in existence now, I can let that cat out of the bag and start a discussion here. This would probably involve people in Infrastructure, Design, and potentially Websites and Marketing. The goals are to: (1) Find someone interested from each involved team to work with the folks at CY on getting a hosted instance established. Timeline is flexible, but I think establishing the instance probably comes before applying any design so we can try it out privately before launching it as a *.fedoraproject.org service. (2) Assuming things look good, provide a status.fedoraproject.org for our users that includes Fedora branding. There are some other issues involved like sponsorship that I can take care of either personally or with the Board, but which don't really matter in the context of this list. Details I know about the service: * The accounts would be separate from those on the normal identi.ca service, but people on identi.ca could subscribe to feeds from the hosted instance, and vice versa * The service would act as an OpenID consumer, and since FAS is an OpenID provider, that could be sufficient to establish an account I don't know yet how the public timelines can be combined. Obviously we don't want to *fragment* public status information, but on the other hand, I really like the idea of having a true Fedora Project public timeline that's always full of relevant information. Now that we have tools like gwibber and other software and services that allow you to set all status at once, the risk of sequestering our information away from the larger public are very low. We can even write an instruction guide that would help people stay connected while using this service. So, who's interested in working on this? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

10 15

Reminder: Zikula Meeting 2009-08-05 @ 15:00 UTC (11 AM EDT)
by John Poelstra 15 Aug '09

15 Aug '09

Zikula Meeting Agenda 2009-08-05 15:00 UTC == Last Meeting == * https://fedoraproject.org/wiki/Meeting:Zikula_20090722 == Packaging Status Follow up == * https://bugzilla.redhat.com/showdependencytree.cgi?id=504066&hide_resolved=1 * https://fedoraproject.org/wiki/Zikula#Module_status * '''ACTIONS:''' ** stickster to push zikula-module-News to stable ** stickster to resolve phpSmug naming, build and push ** Sparks to review license problems in scribite! to determine if he can just remove the "broken" pieces. ** ke4qqq: review stickster's renamed packages ** ke4qqq will contact upstream authors of cc-licensed js by eow and see if relicensing can happen. == Information from ke4qqq === Found yet another bundled library in Zikula - phpmenulayers. Fortunately this is already being packaged https://bugzilla.redhat.com/process_bug.cgi However, phpmenulayers bundles the following library: http://pear.php.net/package/HTML_Template_PHPLIB/ We may want to jump on that (esp since there are some relatively automated spec building tools for pear packages.) To my knowledge - everything not blocked on licensing has been approved except zikula-module-mediashare. This was waiting on a number of dependencies, (4 or 5, which have at least all been approved, if not already built) There may likewise be licensing issues, but if there are, we need to get them in front of upstream and/or fixed by us asap. === Stuff blocked by licensing: === * zikula-module-menutree https://bugzilla.redhat.com/show_bug.cgi?id=511998 Upstream said they were working on this, but I haven't heard anything in a while. Some of this is merely a set of icons, the one package with no licensing information is problematic and we might need to see what we can do with it/without it. Let's ping upstream again on this issue as well * zikula-module-mediaattach https://bugzilla.redhat.com/show_bug.cgi?id=506038 Ian has really not even started packaging this one because he found so many licensing issues. I've notified upstream, but we may need to see what we can do to purge some of this stuff. * zikula-module-content https://bugzilla.redhat.com/show_bug.cgi?id=492091 Lukas has this moving along - there is a licensing issue with lightboxXL. I fired off an email re: relicensing/dual licensing to lightboxXL's author on 22 June, but to date have received no response. It might help if a native spanish speaker sent an email explaining the situation, but it looks like this might have to get jettisoned which might involve patching source. DISCUSS: next actions and plans to resolve these blockers == Test Instance == * '''ACTIONS''': Need to set a date to template the conf files for puppet and create package lists, etc. == Project Management == * '''ACTIONS''': Poelcat to work on creating draft schedule by the first part of next week and follow through on coordinating finalizing it == Draft Zikula Schedule == --Promised skeleton is below... Poelstra needs detailed tasks from all the teams to fill in this schedule. Suggest doing this with Gobby (and possibly Fedora Talk) ASAP * DISCUSS: set time and date using--http://whenisgood.net/RKQ8tE Packaging Modules Tue 2009-06-10 ??? --when will we really be done? Start Alpha Freeze Tue 2009-08-04 Tue 2009-08-04 Alpha Public Availability Tue 2009-08-18 Tue 2009-08-18 Test Instance "Go Live" Tue 2009-08-25 Tue 2009-08-25 Performance Testing Wed 2009-08-26 Fri 2009-09-04 Final (Beta) Freeze Tue 2009-09-22 Tue 2009-09-22 Build Production Box ??? ??? Deploy Production Box ??? ??? Beta Release Public Availability Tue 2009-10-06 Tue 2009-10-06 Zikula "Go Live" for F12 Release ??? ??? GA Release Tue 2009-11-03 Tue 2009-11-03 == Next Meeting Date & Time == * Next Wednesday @ 15:00 UTC ?

6 11

Zikula deployment date
by Mike McGrath 14 Aug '09

14 Aug '09

Do we have a solid date for when this is expected to be put into production? The Fedora Infrastructure schedule is tied, very closely to the Fedora launch. Note that we freeze two weeks prior to each pre-release. That means, as long as there's no slips, we will be frozen from September 8th through the 23rd as well as October 20th through the 4th. Just a warning from experience, these freeze zones really sneak up on you. Also, slips often get announced during one of our freeze periods so what starts as a 2 week freeze, often ends up being a 3 or even 4 week slip. Doing the math that leaves very little time during these pre-release and final release periods to get changes in. I'd strongly recommend getting zikula deployed as soon as possible, we're currently frozen for the alpha but we have a window from August 25th to September 8th where we can do this if it's ready. If not, we're pushing _really close_ to that period of time that almost never goes according to schedule. Also note the translation deadline is September 15th. Not sure if we were planning on having content that should be translated or not. -Mike, bringer of doom

1 0

Zikula Meeting Recap 2009-08-12
by John Poelstra 14 Aug '09

14 Aug '09

2009-08-12 Attendees: John Poelstra, Jon Stanley, Paul Frields, Eric Christensen, Ian Weller, Susan Lauber o Held on Gobby and FedoraTalk w/ bridge to global toll-free call-in facility == Meeting Summary == o We were unable to reach any level of certainty or confidence that we can go live with Zikula for Fedora 12 due to the outstanding questions below. o No one at the meeting was opposed to the idea of postponing Zikula go-live until after GA of Fedora 12. o Meeting ended with next goal to complete all packaging by the end of Fedora 12. o Unclear whether we are going to continue to meet at regular Wednesday time slot. == Outstanding Issues/Questions == 1) What modules do we absolutely need to have to go live? --why do we need menutree? 2) Who can answer #1? --we need someone that has actually installed and admin'd a Zikula instance 3) We need at least one WYSIWYG editor that can be installed and used 4) Infrastructure freezes are coming up--when are they? - https://fedoraproject.org/wiki/Release_Infrastructure_SOP#Change_Freeze - https://fedoraproject.org/wiki/Schedule 5) Zikula upstream folks are on holiday or hard to reach right now--how can we establish better contact? 6) Given all the uncertainty and unanswered questions can we really go-live for Fedora 12? 7) What about a FAD focused on getting Zikula live sometime after GA of Fedora 12? 8) Can Documentation team continue in stop-gap mode for Fedora 12 without adverse affects? 9) Do we have a formal requirements for each of the groups? If yes, where are they documented? --------------------------------------------------------------------- Schedule for now Packaging Modules (only needed for go-live) Tue 2009-08-12 Tue 2009-11-03 (tracking in https://fedoraproject.org/wiki/Zikula)

6 8

Next Zikula Meeting 8P EDT Wednesday (0001Z Thursday)
by John Poelstra 12 Aug '09

12 Aug '09

We will meet during the docs meeting time slot to work on the Zikula schedule. A skeleton version of the schedule is already on Gobby. Feel free to start at any time. We'll also be on FedoraTalk, extension 2009. See you then, John

2 1

Zikula up on pt15
by Eric Christensen 12 Aug '09

12 Aug '09

With some help from quaid and ricky, I was able to get Zikula installed on pt15. It is a fresh install with a new database. This was to show what we need to do to make it ready. The only thing that hit me was the fedora skins aren't packaged/available. What do we need to do for that? --Eric

7 11

agenda and idea for 12 Aug meeting
by Karsten Wade 12 Aug '09

12 Aug '09

(Cross-posted to logistics & docs lists because of wider topic.) John Poelstra has proposed having the Zikula schedule discussion as the first part of the Docs meeting this week, after Paul's suggestion to preempt the Docs meeting for this important topic. Because that works best via voice, we are going to be mostly discussing on sip:2009@talk.fedoraproject.org. How about if we just *move* the Zikula coordination meeting to interact with the Docs meeting until the CMS is rolled out? How does Docs feel about that? To do that, we would want to take all of the status-of-guides notices directly to the list _before_ the meeting. Then we can discuss exceptions to the schedule in the meeting, if needed. This week, I propose that we spend the second part of the meeting discussing the Docs/L10n schedule. These goals: 1. Explain it to everyone present 2. Figure how to show key dates, etc. so it is clear to writers/editors 3. How to manage regular reminders (nagging) of upcoming dates My experience shows that a complex schedule with a distributed team requires regular reminders and continuous understanding. Talk about it often. Show how it changes over time. Make sure people don't forget key dates. That's the (permanent) agenda topic I propose, starting this week with deeper understanding for all. Since John (poelcat) will be present, he can help us explain the schedule; we can talk about presentation choices, etc. cheers - Karsten -- Karsten 'quaid' Wade, Community Gardener http://quaid.fedorapeople.org AD0E0C41

3 4

[Fwd: Zikula Schedule Meeting 2009-08-10 @ 19:00 EDT (23:00 UTC)]
by John Poelstra 12 Aug '09

12 Aug '09

I called in a few minutes late, but found no one on the phone or on gobby. Was Friday's announcement too last minute? I'm running out of ideas here in terms of how to pull this together. Anyone have anything to offer or willing to take the lead? John -------- Original Message -------- Subject: Zikula Schedule Meeting 2009-08-10 @ 19:00 EDT (23:00 UTC) Date: Fri, 07 Aug 2009 16:44:47 -0700 From: John Poelstra <poelstra(a)redhat.com> To: logistics(a)lists.fedoraproject.org The votes are in the and the best time for everyone to work out the Zikula schedule is this coming Monday at 19:00 EDT (23:00 UTC). We will be meeting on Gobby and FedoraTalk--conference room #2009 [1]. I have put a skeleton version of the schedule on gobby now so feel free to get started early. Thanks, John [1] FedoraTalk help: http://sexysexypenguins.com/2009/07/05/voip-fedora-talk-gets-talky/ http://talk.fedoraproject.org/ (this is the option I prefer... best if you have unlimited calling from a land line)

5 9

Rescheduled: Fedora 12 Alpha Release Readiness Meeting :: 2009-08-19 @ 19:00 UTC
by John Poelstra 11 Aug '09

11 Aug '09

Fedora 12 Alpha Release Readiness Meeting Date: Wednesday 2009-08-19 Time: 19:00 UTC (16:00 EDT/13:00 PDT) Location: Gobby & telephone conference bridge At a joint meeting of Development, Release Engineering, and Quality Assurance today, it was determined that the Fedora 12 Alpha release will not be ready for release on August 18, 2009, as originally scheduled. August 25, 2009, is the new date planned for the Fedora 12 Alpha release while also *tentatively* moving the final release date to November 10, 2009 (from November 3, 2009). Therefore it makes the most sense to move the Fedora 12 Alpha readiness meeting from this Wednesday to next Wednesday, August 19, 2009. We also had a request to move the time ahead two hours to 19:00 UTC. I will send the conference call information to the participants directly at the first part of next week. Two questions for all the teams here are: 1) Does moving the Fedora 12 Alpha to August 25, 2009, and all the other tasks forward by one week, including the final release date to November 10, 2009, adversely affect any of the other teams? If we do not hear from anyone by Thursday, August 13, 2009, we will assume the answer is "no" and that adding more time to the end of the schedule will not be detrimental. 2) Is there any team that cannot accommodate the new meeting time for the Release Readiness Meeting on Wednesday, August 19, 2009 at 19:00 UTC (16:00 EDT/13:00 PDT)? Thanks, John

2 1

Re: Zikula Dependency Problems on EPEL
by David Nalley 10 Aug '09

10 Aug '09

There is already a bug regarding this in bz. Install the deps without regard to version then install --nodeps On Aug 7, 2009 7:57 PM, "Eric Christensen" <eric(a)christensenplace.us> wrote: Just tried to install zikula on pt15 and discovered that there is a dependency problem. See below. Any ideas? zikula-1.1.1-12.el5.noarch from epel-test has depsolving problems --> Missing Dependency: php >= 5.2.0 is needed by package --> Missing Dependency: php-mysql >= 5.2.0 is needed by package --> --Eric _______________________________________________ logistics mailing list logistics(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/logistics

3 2

Change regular Zikula meeting time?
by Paul W. Frields 10 Aug '09

10 Aug '09

It seems like the current Zikula meeting time is really tough on a lot of the people involved. It happens during the middle of the work day, understandably making it difficult for people to be around. Should we try to fix the meeting at a different time on a regular basis? John and Toshio are on West Coast time, and I'd be happy to do an evening meeting if that makes things easier on the other contributors who want to work on getting Zikula into place. If you personally think this would make the Zikula meeting more attractive to you, please respond with a +1. If we get a couple of those, I'll set up a time matrix for figuring out a new time. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

3 4

EPEL wait time
by Paul W. Frields 09 Aug '09

09 Aug '09

Just wanted to make everyone aware of something I just learned about, since I don't enter EPEL packages often. According to Dennis Gilmore, all new packages entering EPEL have to undergo a 2-week testing period before they can be pushed to the stable repositories. So this needs to be factored into our timeline given that we are still waiting for some modules to be completed. Paul

3 2

Zikula Dependency Problems on EPEL
by Eric Christensen 07 Aug '09

07 Aug '09

Just tried to install zikula on pt15 and discovered that there is a dependency problem. See below. Any ideas? zikula-1.1.1-12.el5.noarch from epel-test has depsolving problems --> Missing Dependency: php >= 5.2.0 is needed by package --> Missing Dependency: php-mysql >= 5.2.0 is needed by package --> --Eric

1 0

Zikula Schedule Meeting 2009-08-10 @ 19:00 EDT (23:00 UTC)
by John Poelstra 07 Aug '09

07 Aug '09

The votes are in the and the best time for everyone to work out the Zikula schedule is this coming Monday at 19:00 EDT (23:00 UTC). We will be meeting on Gobby and FedoraTalk--conference room #2009 [1]. I have put a skeleton version of the schedule on gobby now so feel free to get started early. Thanks, John [1] FedoraTalk help: http://sexysexypenguins.com/2009/07/05/voip-fedora-talk-gets-talky/ http://talk.fedoraproject.org/ (this is the option I prefer... best if you have unlimited calling from a land line)

1 0

Fedora 12 Alpha "go/no go" Decision/Meeting
by John Poelstra 07 Aug '09

07 Aug '09

We have a milestone scheduled on Monday, August 10, 2009, for deciding if the Fedora 12 Alpha is going to be ready ship on time or if we need to slip one week . Task #12 http://poelstra.fedorapeople.org/schedules/f-12/f-12-pm-tasks.html This is an important decision that affects the work of several teams. I believe Release Engineering was planning to make this part of their regular meeting, but it would be good to broadcast the details here so other teams can follow along. Is the Release Engineering meting still at 18:00 UTC (11 AM EDT) on 2009-08-10 at #fedora-meeting? Thanks, John

2 1

Fedora 12 Alpha Release Readiness Meeting :: Wednesday, August 12, 2009 @ 17:00 UTC
by John Poelstra 07 Aug '09

07 Aug '09

When: 2009-08-12 at 17:00 UTC (1 PM EDT/10 AM PDT) Next Wednesday we are scheduled to have the Release Readiness meeting for the Fedora 12 Alpha. I'm hoping representatives from each of the teams will be able to attend. Please discuss with your teams to see if there are any issues they would like to bring forward. This cross team meeting is held to coordinate and discuss release day issues in real time and to make sure we are ready for a smooth release day. The following list shows the people that represented these teams in past releases. If you cannot attend or no longer wish to represent your team please coordinate and alternate and let me know. >> I still need to know who is representing the translation team << Ambassadors -- David Nalley Design -- Máirín Duffy Documentation -- Eric Christensen FESCo -- Jon Stanley Fedora Engineering Manager -- Tom "Spot" Callaway Fedora Project Leader -- Paul Frields Infrastructure -- Mike McGrath Marketing -- Mel Chua Quality -- James Laska Release Engineering -- Jesse Keating Translation -- ?? Websites -- Ricky Zhou I will send conference call information privately next week. A recap of this meeting will appear on this list. Thanks, John

5 4

Zikula Schedule Review Take II
by John Poelstra 06 Aug '09

06 Aug '09

As a followup from today's meeting, here is another calendar to gather everyone's availability. We need to specifically hear from Eric, David, and Toshio... preferably by the end of the day tomorrow (2009-08-06) http://whenisgood.net/tiUPzZ Thank you, John

3 3

Zikula Meeting Recap 2009-08-05
by John Poelstra 05 Aug '09

05 Aug '09

Zikula Meeting 2009-08-05 Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-05/fedora-meeting.2… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2009-08-05/fedora-meeting.2… Log: http://meetbot.fedoraproject.org/fedora-meeting/2009-08-05/fedora-meeting.2… ======================= #fedora-meeting: Zikula ======================= Meeting log ----------- * *LINK*: https://bugzilla.redhat.com/showdependencytree.cgi?id=504066&hide_resolved=1 (poelcat-15:04:34_) * **packaging status** (poelcat-15:04:51_) * *LINK*: https://bugzilla.redhat.com/show_bug.cgi?id=511998 (poelcat-15:12:18_) * *LINK*: http://weblog.axent.pl/examples/js.drag-drop-tree/cookie.js looks like the most important issue to resolve there (stickster-15:14:07_) * *ACTION*: stickster to make sure each licensing issue gets it's own bugzilla (poelcat-15:15:39_) * *LINK*: https://bugzilla.redhat.com/show_bug.cgi?id=506038 (poelcat-15:16:50_) * *INFO*: J5> icons just move to Tango which are public domain and we use for our default theme (poelcat-15:18:08_) * *ACTION*: Sparks to check on message on the f-docs-l that said the icons were in the public domain (poelcat-15:18:56_) * *LINK*: https://bugzilla.redhat.com/show_bug.cgi?id=492091 (poelcat-15:27:01_) * *ACTION*: for https://bugzilla.redhat.com/show_bug.cgi?id=506038 break out licensing issue + J5 to come up with fix (poelcat-15:28:10_) * *ACTION*: https://bugzilla.redhat.com/show_bug.cgi?id=492091 ke4qqq to bring plan upstream for consideration (poelcat-15:28:35_) * *ACTION*: https://bugzilla.redhat.com/show_bug.cgi?id=492091 break out licensing issue + J5 to come up with fix (poelcat-15:36:11_) * **test instance** (poelcat-15:36:24_) * *LINK*: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=505938 (poelcat-15:38:12_) * *ACTION*: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=505938 break out licensing issue + J5 to come up with a fix (poelcat-15:43:03_) * *ACTION*: ke4qqq to send email off about actions needed around test instance (poelcat-15:56:19_) * **schedule** (poelcat-15:56:32_) * *ACTION*: poelcat to send whenisgood to coordinate schedule review to happen before next meeting (poelcat-16:04:29_) .. _poelcat-15:04:34: fedora-meeting.2009-08-05-15.00.log.html#l-18 .. _poelcat-15:04:51: fedora-meeting.2009-08-05-15.00.log.html#l-20 .. _poelcat-15:12:18: fedora-meeting.2009-08-05-15.00.log.html#l-55 .. _stickster-15:14:07: fedora-meeting.2009-08-05-15.00.log.html#l-61 .. _poelcat-15:15:39: fedora-meeting.2009-08-05-15.00.log.html#l-67 .. _poelcat-15:16:50: fedora-meeting.2009-08-05-15.00.log.html#l-72 .. _poelcat-15:18:08: fedora-meeting.2009-08-05-15.00.log.html#l-81 .. _poelcat-15:18:56: fedora-meeting.2009-08-05-15.00.log.html#l-87 .. _poelcat-15:27:01: fedora-meeting.2009-08-05-15.00.log.html#l-121 .. _poelcat-15:28:10: fedora-meeting.2009-08-05-15.00.log.html#l-126 .. _poelcat-15:28:35: fedora-meeting.2009-08-05-15.00.log.html#l-130 .. _poelcat-15:36:11: fedora-meeting.2009-08-05-15.00.log.html#l-158 .. _poelcat-15:36:24: fedora-meeting.2009-08-05-15.00.log.html#l-160 .. _poelcat-15:38:12: fedora-meeting.2009-08-05-15.00.log.html#l-165 .. _poelcat-15:43:03: fedora-meeting.2009-08-05-15.00.log.html#l-179 .. _poelcat-15:56:19: fedora-meeting.2009-08-05-15.00.log.html#l-230 .. _poelcat-15:56:32: fedora-meeting.2009-08-05-15.00.log.html#l-232 .. _poelcat-16:04:29: fedora-meeting.2009-08-05-15.00.log.html#l-271 Meeting ended at 16:04:41 UTC. Action Items ------------ * stickster to make sure each licensing issue gets it's own bugzilla * Sparks to check on message on the f-docs-l that said the icons were in the public domain * for https://bugzilla.redhat.com/show_bug.cgi?id=506038 break out licensing issue + J5 to come up with fix * https://bugzilla.redhat.com/show_bug.cgi?id=492091 ke4qqq to bring plan upstream for consideration * https://bugzilla.redhat.com/show_bug.cgi?id=492091 break out licensing issue + J5 to come up with fix * https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=505938 break out licensing issue + J5 to come up with a fix * ke4qqq to send email off about actions needed around test instance * poelcat to send whenisgood to coordinate schedule review to happen before next meeting Action Items, by person ----------------------- * J5 * for https://bugzilla.redhat.com/show_bug.cgi?id=506038 break out licensing issue + J5 to come up with fix * https://bugzilla.redhat.com/show_bug.cgi?id=492091 break out licensing issue + J5 to come up with fix * https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=505938 break out licensing issue + J5 to come up with a fix * ke4qqq * https://bugzilla.redhat.com/show_bug.cgi?id=492091 ke4qqq to bring plan upstream for consideration * ke4qqq to send email off about actions needed around test instance * poelcat * poelcat to send whenisgood to coordinate schedule review to happen before next meeting * stickster * stickster to make sure each licensing issue gets it's own bugzilla * **UNASSIGNED** * Sparks to check on message on the f-docs-l that said the icons were in the public domain People Present (lines said) --------------------------- * stickster (118) * poelcat (60) * J5 (32) * ke4qqq (17) * abadger1999 (14) * Sparks_too (14) * buggbot (11) * pcalarco (3) * jwb (3) * ricky (2) * spot (1) Generated by `MeetBot`_ .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Licensing problems, solution strategy
by Paul W. Frields 02 Aug '09

02 Aug '09

Without a meeting today, it's probably best to bring this up on the list. I know that we've been reaching out to upstream to get licensing problems fixed. The responses on the couple of threads I've seen seem generally positive about us providing the licensing audits, and have usually provided some idea of what's needed to fix the problem (at least in terms of scoping out the required changes). But they don't seem to always provide firm commitments to fixing the problems, as all the normal IRL rules apply. In other words, the upstream maintainer may simply be too busy to work on the solution. I propose that we simply make the rollout a first priority. If there are licensing concerns which must be fixed to install the application somewhere, then module owners must fix the licensing problems themselves (or find someone to commit to doing it within a specific time frame). If we're able to wait for packaging until some later time, then we install now, set a date where we will have all those problems solved, and start the process of fixing them. In other words, what I'm trying to avoid is blocking on upstream if this team has the capacity to fix these problems and send them patches. Paul

4 7

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

logistics August 2009