Remaining FI platform blockers

[Mel Chua]

For Fedora insight, we've got a "move stuff to staging" deadline of 
September 20 (https://fedoraproject.org/wiki/Fedora_Insight#Schedule), 
which is this Sunday. So I want to make sure we all know where we stand...

Mo, Simon, and I agreed to list the remaining FI platform (read: 
non-content, non-workflow - this includes the infra/skin/design) 
blockers in order to try to minimize bottlenecks. We're hoping this will 
allow other people to take some of the load off our plate (as some 
people have already started doing - thank you for stepping in with 
module packaging, Toshio!)

Here's my first pass at it, also reflected in reflected in 
https://fedorahosted.org/marketing-team/query?status=new&status=assigned&status=reopened&component=Fedora+Insight&order=priority; 
Mo and Simon will chime in shortly with additions/modifications to the 
list. If anyone else knows something that's missing, please chime in - 
or better yet, add a https://fedorahosted.org/marketing-team/newticket 
with the Fedora Insight component. I'll make sure the tickets stay 
up-to-date with any responses to this thread, but both emailing /and/ 
making a ticket makes my life easier. ;)

* Simon needs to walk a packager through packaging the filterutil module 
and packaging an updated pagemaster module. Toshio has taken a first 
pass at it, so Simon needs to figure out whether this clears the blocker 
(and if not, specify what is required to clear the blocker). The 
packages will also need to be reviewed and deployed. 
https://fedorahosted.org/marketing-team/ticket/25

* Mo needs to finish v.1.0 development of the skin and create tickets 
for any blockers that prevent her from doing so, so that others can 
resolve them (for instance, "I can't find the tag that does $foo," or 
"$module doesn't work.") This skin will also need to be packaged, 
reviewed, and deployed. https://fedorahosted.org/marketing-team/ticket/27

* Mel needs to make sure that everything is set with Infra (mmcgrath) 
for deployment; I think this means a draft SOP listing the packages to 
be installed (which implies all packages are available), usage of that 
SOP to get stuff onto staging, load-testing on staging, and then 
movement to production. https://fedorahosted.org/marketing-team/ticket/28

* Mel needs to get zikula-module-EZComments reviewed and deployed on 
pt6. https://fedorahosted.org/marketing-team/ticket/36

* Simon needs to fix the bug that pops up when the Feeds module is 
installed; it claims to be a PHP segfault (...key word here is "claims" 
- this isn't actually possible). This involves manually importing SQL, 
and doing so in a way that's reproducible (I'm guessing via the 
package's spec file?) https://fedorahosted.org/marketing-team/ticket/38

That is all I can think of. Mo? Simon? Others? What non-content, 
non-workflow things do we need to make this a go for a September 28 launch?

Thanks to everybody for your *tremendous* help so far in getting this up 
and running - Simon, Mo, Eric, Rahul, David, Paul, Bob, Robyn, Mike, 
Toshio, Keiran, and Ricky, to name a *very* partial list (if I've missed 
you on this list, *please* let me know because I want to make sure 
everyone knows who's responsible for our awesome launch in 2 weeks. ;)

--Mel