Insight project plan

This page is a light project plan for Fedora Insight.

Objective

To deploy a content management system for the Fedora Project; and to build around it a team of Fedora contributors who are passionate about maintaining it and serving other contributors with it.

Project name

Fedora Insight

Stakeholders

Project team

• Paul W. Frields (stickster) - Project manager/contributor
• Peter Borsa (asrob) - Project contributor
• Andrea Veri (averi) - Project contributor
• Robyn Bergeron (rbergeron) - Marketing team
• Pascal Calarco (pcalarco) - Fedora Weekly News team
• Jef van Schendel (schendje) - Design team
• Mairin Duffy (mizmo) - Design team
• Hiemanshu Sharma (gwerra) - Websites team
• Stephen Smoogen (smooge) - Infrastructure team
• Buddhika Kurera (smooge) - Ambassadors team

Others?

Receivers

• Jared Smith - FPL
• Stephen Smoogen - Interim Infrastructure team lead

Customers

Primary

• Marketing team
• Fedora Weekly News team
• Media (journalists, reporters, bloggers)
• Fedora community members
• Fedora users

Secondary

• Documentation team
• General public

Deliverables

Phase 1

A working content management system at http://fedoraproject.org/insight, with the following functionality:

• Authentication to FAS
• Group assignment through FAS
• Working theme as prepared by the Design team
• Publication procedure for Fedora Weekly News
• The ability to select items from configured RSS feeds to be promoted to publication and other tagging

Phase 2

The following additional functionality:

• Adding a built-in calendar system into Drupal where all Fedor's teams and projects can post their meetings. (it should look like this or this). (I can take care of packaging it when we will decide to deploy it on Insight, need to package following modules, Calendar and Date) (Andrea Veri)
• Ability to share access to the @fedora Identi.ca feed through a FAS group (fedora-socialmedia) | Proposed module or modules: (twitter module) need to test it.
• The ability to publish and attach podcasts to a story | Proposed module or modules: (filefield module) or (filefield podcaster module) need to test them.
• Post announcements of podcast publication | Proposed module or modules: (rules module) need to create a rule.
• The ability to take items posted to the Fedora Marketing list that are news items (usually tagged with [in the news] in the subject) and post them to Insight. Or better yet, get people to just post those items to insight rather than the marketing mailing list. This does a few things for us:
  • People are already posting the details (link, title) to the marketing list - this allows people to add it with just as little effort, but make the list available to see in a way that doesn't require a lot of overhead. Right now I (Robyn) go through and add the items bit by bit to a wiki page, which doesn't scale well, and takes a lot of time.
  • Allows people who are interested in news but not necessarily on the mailing list a quick way to see "what other people are saying about Fedora."
• Ability for candidates for Fedora offices (Board seats, FESCo seats, and FAmSCo seats for example) to self-nominate via Insight. That way, only they would be able to make changes to their nomination page, and we could have slightly more control about people adding themselves to the list after nominations have closed. (Not sure this really fits with the rest of the stuff going on in Insight, but thought I'd suggest it.)

Requirements

FWN

• Handle multiple beats
• Handle arbitrary number of beats per issue
• Publish new issue to front page with issue summary
• Link issue to ToC for easier reading
• Provide issue as a combined single page
  • May need Views module
  • q.v. http://drupal.org/node/614882#comment-2266600

???

• Add another content type here and what we want from it

Tasks

• Determine all requirements
• Scope requirements into phases
• Determine whether platform meets requirements
  • If not, select modules and package for drupal6 in EL-5 (with eye toward EL-6 too)
• Deploy test instance
• For each requirement in phase:
  • Assign responsible contributor
  • Document procedure for fulfillment on wiki
  • Create appropriate facility in the platform
  • Have appropriate stakeholders test and accept
• Test -> Stage
  • Recreate facilities in staging instance
  • Have stakeholders test for consistency and accept
• Stage -> Production