From Fedora Project Wiki

Fedora Insight (FI) is a website that serves as a place to publish and share news, articles related to Fedora and Fedora marketing materials in various formats. It makes it easy for users, developers, and journalists - people who aren't yet a part of the Fedora contributor community - to keep up with the goings on of the community without following a dozen different blogs and mailing lists.

This wiki page is for people interested in working on and contributing to Fedora Insight itself; the site is a project that requires collaboration between many teams (FWN, Marketing, Websites, Design, Infrastructure, etc.), so this is our central landing spot.

Project status

Production

There is no live production instance yet (we are working on the first one).

Staging

https://stg.fedoraproject.org/insight/

This instance is set up by the Infrastructure team according to the instructions at How to set up a Zikula sandbox. Login/authentication is hooked to your normal FAS account.

Publictest

http://publictest6.fedoraproject.org/zikula/

This instance is available to experiment with, and is accessible by anyone with access to the sysadmin-test FAS group. Login/authentication is hooked to the test FAS instance.

Important.png
Do not use your regular Fedora account (FAS) credentials.
Make a test account in the test FAS instance.

How to use:

  1. Make a test account on the public-test instance of FAS at https://publictest3.fedoraproject.org/accounts .
  2. Log in to https://publictest6.fedoraproject.org/zikula/ using your FAS test account.
  3. Play!

Next target

Our next target is to migrate the Fedora Weekly News workflow and publication to Fedora Insight before Alpha Public Availability (March 2, 2010).

The target after that is to get all pre-beta F13 Marketing deliverables published on Fedora Insight before Beta Release Public Availability (April 6, 2010).


Teams involved

Design

List of FI tickets in Design trac

The repo is located at git://git.fedorproject.org/git/fedora-insight-theme.git.

You can checkout the theme anonymously using

git clone git://git.fedoraproject.org/git/fedora-insight-theme.git

People who are a part of the (FAS) group gitfedora-insight-theme can check out using

git clone ssh://git.fedoraproject.org/git/fedora-insight-theme.git

To use the theme on your local copy of zikula just copy over the fedora folder inside the git repo and paste in the /path/to/zikula/theme folder and change the settings in the Admin Panel.

If you make any change in the theme directly on the server (pt6) make sure that you copy over the changes you made to the theme and to keep the git repo updated always.

Infrastructure

The master ticket is at Infrastructure Trac #1615, but if you're looking to help out, it's best to see our the Trac query.

Marketing

multiple tickets in marketing Trac.

FWN

Packaging

Goals

F12 Goals

  • Centralized content-finding: Have a central place to publish Fedora Marketing content, This draws from "upstream" sources such as Planet Fedora, FWN, existing deliverables like feature profiles and release announcements, and content that we currently don't consistently create, like podcasts and multimedia.
  • Support the content schedule: Provide a platform that makes it easier to see what needs to be produced for a given Fedora release cycle, the timeline for each, and the progress towards each item.
  • User-centered web design: Serve as an attractive, informative, Journal-format, user-friendly face for informing people interested in Fedora, but not yet contributing to it.
  • Standardized feeds: Feeds available for each content tag and media type (audio/video/text).
  • Enable the Fedora news distribution network (NDN) process: Host the materials the NDN will send out.

Beyond F12 Goals

  • Translation workflow and setup
  • Develop strategies for syndicating media on social networks/news sites

Content

Content categories

this is a draft, for discussion - please edit!

  • interviews with community members
  • feature focus/update (tour)
  • howto (for experienced users)
  • upcoming event announcement/reminder
  • past event report
  • neutral reporting on debates
  • rawhide report
  • meeting coverage - upcoming-meetings calendar, minutes
  • interviews with companies/people which use Fedora (aka. success stories)

Content examples

these are drafts, for discussion - they were taken mostly from Planet headlines on the day we looked (at the beginning of June). Please add/remove/edit/comment - what do you think should be here? Mel Chua 12:38, 25 July 2009 (UTC)

Yes

  • What's new in Fedora 11 from SELinux
  • Western Digital MyBook as a Backup System (Fedora-specific existing-user tutorial)
  • "you should vote; here are upcoming elections" posts
  • "people voted, here are election results" posts
  • Fedora 11 Release Party Wau Report
  • npov coverage of things like "there is a debate on dropping cd media, here are links to several views expressed"
  • Read All About the Fedora 11 Retrospective (past event coverage)

No

  • HAPPY BIRTHDAY SPACEWALK! (not Fedora-specific)
  • lolcats
  • "I voted!" posts
  • "Initial KMS support for radeons merged to Linus tree" (the blogpost-as-commit-message)
  • SoaS for the XO-1 uses Fedora
  • State of the Poulsbo Address
  • Chinese translation of [a book I wrote] is being worked on
  • So you’re looking for a hosting provider?
  • Social Desktop contest
  • Announcing kernelpodcast.org
  • The downfall of modern civilization... (on the 'drop cd media?' debate - we're not looking for editorials, but npov coverage)
  • Simplez! Simple Pairing support now in gnome-bluetooth. (more of a blog-as-commit-message than a feature report)

Content workflow

 +-------------------------+    +-----+ +-------+ +-------------+ +-----------+
 |Things that automatically|    |Press| |The Web| |Fedora Planet| |Original FI|
 |get sent to the moderator|    +-----+ +-------+ +-------------+ |content    |
 |queue for annotation     |        |       |           |         +-----------+
 +-------------------------+        |       |           |               |
 | * Board meeting minutes |        +-------+-----+-----+---------------+
 | * FESCo meeting minutes |                            |
 | * FAmSCo meeting minutes|                            |
 | * etc.                  |                            |
 +-------------------------+              +----------------------------+
             |                            | Discovered by interested   |
             |                     +----->| person, or submitted by    |   
             |                     |      | original author into...    |   
             |          resent to  |      +----------------------------+   
             |          submitter  |                    |                            
             |          with rationale                  |                             
             |                     |          +------------------+                        
             +---------------------+--------->| Moderator  Queue |         
                                   |          +------------------+         
                                   |          | Selects content  |         
                                  <NO>--------| and annotates    |          
                                              | selected content |
 +-------------------------+                  +------------------+
 |Things that automatically|                           |
 |get published (no mod)   |----+                    <YES>      
 +-------------------------+    |                      |             
 | * Fedora Weekly News    |    |       +----------------------------+
 | * Fedora-announce-list  |    +------>| Published in Fedora Insight|
 | * etc.                  |            +----------------------------+
 +-------------------------+                           |           
                                                       |
                                                   (READERS!)

Platform specs/requirements

Marketing Requirements

  • Allow multiple editors
  • Allow multiple contributors
  • Separate feeds for different media - podcast, written, video etc
  • Easy integration of rich media - see above
  • Tags/Categories
  • "Push" capabilities. From kanarip: if i have to look it up, as in, actively, it's a fail; it needs to be pushed in my direction somehow; rss feeds will suffice for that purpose

News Requirements

(Extrapolated from the [this fedora-news-list thread] - please correct me if I've misinterpreted. Mel Chua 18:44, 14 July 2009 (UTC))

  • graphical branded presence
  • syndication
  • potentially retaining the FWN name? (has name recognition... open question for discussion.)
  • keep current FWN sections. "Certainly Ambassadors, Planet, Art/Design, Translation, Development. Dale's virtualization beat is a creation unto itself, covering several different areas."
  • easy workflow - currently, FWN is edited as one block of text, which is easier on editors than working on many separate posts.

Design requirements

  • mizmo: lets you add custom CSS across the whole site design. i think its just going to be one blog (or maybe one per feed - text / audio /video ) so i dont think user level css would come into play.
  • mizmo: lets you modify html output
  • mizmo: tagging - to support the way we laid the mockup up, you either need multiblogs or better tagging, and tag based feeds. so like we were talking about, having a developer of the month interview, would be good to tag it with 'interview' and 'dotw', and then for each tag to have its own feed. it could be accomplished with separate blogs too, but that would then split related content, like if you had a dotw blog and an interview blog, when you do an interview for dotw it won't be in the interview blog feed
  • Ability to easily pull archives, by month and year and list out (see footer of mockup)
    • Same for latest posts per category, in footer of mockup
  • Rawhide Weather report ability?
  • live Identi.ca feed?
  • allows for the pulling-in of external feeds/items or the super-easy creation of plugins to add special features - for instance, Mo's idea of the "rawhide weather report" (or Jeff Spaleta's variant of forest fire levels) may be automatically generated from buildbot logs (or something) - how can that get implemented? Mel Chua 23:34, 14 July 2009 (UTC)

General Requirements

  • FAS_Auth integration
  • Themable (presumably by Design Team)
  • Software *and* required plugins packaged - including theme?
    • software + plugins packaged, theme isn't necessarily a strict requires but it's kind of nice --Ian Weller 16:13, 8 July 2009 (UTC)
    • Why is it not a strict requires? (JonRob - who doesn't know how to do ianweller's funky signature)
    • Regardless, the theme was packaged for Docs, IIRC an adapted skin from the existing Fedora websites look --Quaid 20:03, 18 August 2009 (UTC)

This is a brainstorm list - what would you want a Fedora Insight platform to have and do? Please add to the list below.

Why Zikula

  • stickster: there's a great deal of crossover between what Fedora Insight proposes, and what the new CMS (Zikula) can/will accomplish. Fedora Insight sets out a lot of Marketing-specific goals, and I think most or all of them can be achieved through an implementation via the CMS.
  • ke4qqq (Dave Nalley) summarizes Zikua: After a long period of input, eval, and testing by multiple groups (primarily Docs, but also Infrastructure and others), Zikula has been chosen as a CMS. It has a responsive upstream that's developing new modules for our needs and has even joined fp lists to help us collaborate on getting this up. It wil first be used for docs.fp.o, which currently has no CMS; FPC and F-Legal are also interested in using it - but we haven't mapped out that really well thus far - but it's after docs.fp.o makes the move. polecat (John Poelstra) has stepped up to coordinate teams for a production schedule and some meetings.
  • If zikula fits all of our requirements, or can/will be modified to do so, I would be strongly in favor of going with this and working with the existing cross-team effort - it just makes sense to Work Together. I think sitting down with someone who knows Zikula's feature set well, and going through our requirements list (once that is more solidified) with them, would enable us to make a final yes/no decision. Mel Chua 14:45, 13 July 2009 (UTC)


Sketches

Here's a mockup by mizmo of what this might look like. (Click for full size.)

FooBar.png

Workflow