Fedora 12 Alpha Release Readiness Meeting Recap
by John Poelstra
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
14 years, 8 months
Hosted identi.ca
by Paul W. Frields
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
14 years, 8 months
Reminder: Zikula Meeting 2009-08-05 @ 15:00 UTC (11 AM EDT)
by John Poelstra
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 ?
14 years, 8 months
Zikula deployment date
by Mike McGrath
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
14 years, 8 months
Zikula Meeting Recap 2009-08-12
by John Poelstra
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)
14 years, 8 months
Next Zikula Meeting 8P EDT Wednesday (0001Z Thursday)
by John Poelstra
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
14 years, 8 months
Zikula up on pt15
by Eric Christensen
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
14 years, 8 months
agenda and idea for 12 Aug meeting
by Karsten Wade
(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
14 years, 8 months
[Fwd: Zikula Schedule Meeting 2009-08-10 @ 19:00 EDT (23:00 UTC)]
by John Poelstra
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)
14 years, 8 months
