1:32 a.m.
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=assig...;
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
8:38 a.m.
On Wed, Sep 16, 2009 at 02:32:25AM -0400, Mel Chua wrote:
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=assig...;
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?
Making sure the editor issue from Toshio and Eric's previous
conversation is on that list:
http://lists.fedoraproject.org/pipermail/logistics/2009-September/000228....
--
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:50 a.m.
Making sure the editor issue from Toshio and Eric's previous
conversation is on that list:
http://lists.fedoraproject.org/pipermail/logistics/2009-September/000228....
Added, https://fedorahosted.org/marketing-team/ticket/47
"I'm setting this as 'major' rather than 'blocker' because we can
launch
without it, but it will make our lives much easier. (Worst case
scenario: no wysiwyg editor at the beginning, and we spend a bunch of
tedious man-hours converting text from emails/wiki pages/blog posts into
html until the module is packaged and deployed.)"
In other words, it's *really* nice to have this, but if push comes to
shove, I want information-consumption features like publishing articles,
commenting on articles, and feeds working first.
My $0.02.
--Mel
6:08 p.m.
On Wed, Sep 16, 2009 at 11:50:55AM -0400, Mel Chua wrote:
> Making sure the editor issue from Toshio and Eric's
previous
> conversation is on that list:
>
> http://lists.fedoraproject.org/pipermail/logistics/2009-September/000228....
Added, https://fedorahosted.org/marketing-team/ticket/47
"I'm setting this as 'major' rather than 'blocker' because we
can launch
without it, but it will make our lives much easier. (Worst case
scenario: no wysiwyg editor at the beginning, and we spend a bunch of
tedious man-hours converting text from emails/wiki pages/blog posts into
html until the module is packaged and deployed.)"
s/a bunch of tedious man-hours/extra time/
The kind of content we're working on isn't going to take that much
time to convert. This said as someone who *has* spent so many hours
at such conversion that I can be said to be nearly proficient. ;-)
But, yeah, as you know, the bigger risk is scaring people away who
aren't nearly as proficient. Just the idea of touching HTML is scary
to some of the very people we want to draw to write on Fedora Insight.
Let's make sure we advertize that i) the wyiswyg editor will be in
place ASAP as a top priority following launch, and ii) there are
people such as me who are willing to do foo-to-HTML for other people
so they don't run away at the site of <markup>. :)
- Karsten, who has heard "And you have to write in HTML!" as an
epithet in non-technical business teams. Ironically, also in
technical teams, but for different reasons ...
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
8:21 p.m.
s/a bunch of tedious man-hours/extra time/
+1
Let's make sure we advertize that i) the wyiswyg editor will be
in
place ASAP as a top priority following launch
Yes. As we drop features for F12, we need to make sure the ones for F13
are prioritized; right now wysiwyg, a translation workflow, and an
events calendar are the ones I can think of.
and ii) there are people such as me who are willing to do
foo-to-HTML
for other people so they don't run away at the site of<markup>. :)
I'm up for this as well. (Fun side note: doing this sort of thing
frequently was the reason why I first learned sed,
http://www.grymoire.com/Unix/Sed.html.) I also know my
impatience/tolerance level is low enough that if I'm forced to manually
do foo-to-HTML conversion until a wysiwyg solution is deployed, that
wysiwyg solution is going to be deployed *fast.* ;)
--Mel
9:48 p.m.
*All* FI platform blockers are up at
https://fedorahosted.org/marketing-team/query?status=new&status=assig...
- and thanks to Simon's work tonight, they're nearly all doc'd to a
degree that should let anybody with the requisite
CSS/packaging/sysadmin/etc. skills (or the desire to obtain them ;) pick
them up. (If you encounter a FI ticket that isn't, please complain
loudly here, and that situation shall be fixed.)
The only exception is
https://fedorahosted.org/marketing-team/ticket/54#comment:2, which needs
someone with CSS skills to be available to put that feature in with
Simon from 2100-2200 UTC in #fedora-mktg - if you can take this, please do!
Heck, if you can take any of the tickets - particularly the blockers,
since our schedule calls for having those cleared out by Monday - please
do - the zikula work we do now is going to make it *much* easier to
deploy zikula for other things (like docs) later on.
If you've seen new people introducing themselves on various mailing
lists, point them towards these tasks and help them get started!
(Particularly pertinent for new Design-with-a-CSS-bent, Websites, and
Infra folks.)
Thanks, everyone. We're almost there...
--Mel
11:54 a.m.
On 09/16/2009 02:32 AM, Mel Chua wrote:
* 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
I need to step away from this for a while to work on the www.fpo mocks.
I filed a bunch of tickets from my notes on what more needs to get done.
Here are the things I consider blockers for the skin:
= Blockers =
• 'read more' link for bottom of article previews shown on front page of
insight (ticket #56)
• static image hack (ticket #58)
• fpo.org banner rotation JS doesn't work with zikula (ticket #53)
We also need browser testing..... I'm sure there must be a few CSS bugs
here and there :(
---
Here are other work items I really wanted to get to but we could live
without I think (although without them Insight is a lot less awesome and
yeh it would work without them, but then we lose the opportunity to go
live with something as slick as it could be):
• Planet Fedora Feed - broken (#ticket 46)
• RSS output - there was a block to give the overall RSS for the site
before. It disappeared at some point today. I don't know how or why.
(ticket #49)
• RSS output - we can output one feed for everything in Insight, but
AFAIK we cannot to an RSS feed per category, which blocks having an
actual podcast feed. (ticket #48)
• permission to grant comments has been granted to everyone including
non-logged in users. not sure if we want to stick with this policy or
put something else in place but it's something we need to decide.
(ticket #50)
• the footer for fedora insight hasn't been created yet. you can see a
mockup here http://fedoraproject.org/w/uploads/c/ce/FooBar.png (ticket #51)
• no way to associate images with articles - right now displaying images
on the front page is a fragile, ugly hack (ticket #52)
• would like to get category images for insight articles working (ticket
#54)
• need to add podcast preview sidebar to insight (ticket #55)
• author icons (ticket #57)
• top story and secondary headlines block types / templates need
character length limiting (ticket #59)
• article tags display is messy (ticket #60)
• event listings need fragile html structure to display correctly in
fedora insight (ticket #61)
---
Some notes about how you'll need to cajole the fragile setup we have now
into showing its best externally (although the hackishness of how it
works internally makes me weep o_O):
= Featured Stories =
Featured stories are meant to be the three articles that are
thematically linked to the current 'issue' of Fedora Insight, be it
monthly or quarterly or whatnot. Only three will display at a time, and
their description field is limited to 100 characters. You fill in the
description that displays in the 'featured stories' widget by filling in
the lead page teaser text in the article itself. Beware - if you add an
image to that form field, the site's template will blow up. Please try
to keep the description as brief as humanly possible.
Once you'd written an article for the 'featured stories' block, you can
get it to display there by putting it in the 'featured stories' category
= Top Stories =
Directly below the featured stories blue box with mmcgrath, there's a
section that I call the 'top stories' section. It calls out one top
story, and two supplementary/secondary top stories.
You need to add an img tag to the image for your top story in the 'lead
page teaser' text field in the article editing page. It needs to be the
first item in that text field. You can use an image of any size - the
CSS will automagically resize it to the size it needs to be.
Please try to be careful to watch the length of the 'lead page teaser'
text for both the top story and the secondary top stories. Because they
use custom templates, there currently isn't a way to limit and ellipsize
their legnth.
if you want a story to be the 'top story' put it in the 'top story'
category. the newest article in the 'top story' category will be
displayed as the top story.
if you want a story to be one of the supplementary/secondary top
stories, put it in the 'secondary headlines' category. the most recent 2
articles in that category will display on the front page.
for stories in either category, please uncheck the 'display on lead
page' checkmark on the article's edit screen. otherwise the same
articles will display twice on the front page.
= Upcoming Events =
If you want to list an upcoming event to display in the sidebar...
well... it's hacky.
Here's the format you need to follow when posting an upcoming event....
I'll give an example for FUDcon Toronto 2009, which is Dec 5-7 2009 in
Toronto.
* the 'title' field of the article is what will show up as the event
name. for this event i'll use 'FUDCon Toronto 2009'
* place the article in the 'Upcoming Events' category
* for lead page teaser you need to put the event date and location in a
special format. Here's what i have for fudcon:
<div class="date">Dec 5-7 2009</div>
<div class="location">Toronto, Ontario Canada</div>
* the details of your event should go in 'article body'. if you like you
can add images, links, etc here.
= Event Reports =
Nothing special to watch out for these, just make sure you use the
'event reports' category.
= Getting your name to show up as author =
You have to dig thru the admin UI and explicitly set your 'Real Name'.
The FAS plugin doesn't populate this automagically.
I'm sure there's other gotchas.... but that's all I can think of for now.
~m
5346
days inactive
5347
days old
logistics@lists.fedoraproject.org
6 comments
4 participants
participants (4)
-
Karsten Wade -
Mel Chua -
Máirín Duffy -
Paul W. Frields