Line 44: | Line 44: | ||
== Deliverables == | == Deliverables == | ||
A working content management system at http://fedoraproject.org/insight, with the following functionality | === Phase 1 === | ||
A working content management system at http://fedoraproject.org/insight, with the following functionality: | |||
* Authentication to FAS | * Authentication to FAS | ||
* Group assignment through FAS | * Group assignment through FAS | ||
* Working theme as prepared by the [[Design]] team | * Working theme as prepared by the [[Design]] team | ||
* Publication procedure for Fedora Weekly News | * Publication procedure for Fedora Weekly News | ||
=== Phase 2 === | |||
The following additional functionality: | |||
* The ability to select items from configured RSS feeds to be promoted to publication and other tagging | |||
=== Phase 3 === | |||
The following additional functionality: | |||
* The ability to publish and attach podcasts to a story | |||
* Post announcements of podcast publication | |||
== Requirements == | == Requirements == |
Revision as of 14:14, 12 August 2010
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
- Robyn Bergeron (rbergeron) - Marketing team
- Pascal Calarco (pcalarco) - Fedora Weekly News team
- Mairin Duffy (mizmo) - Design team
- Hiemanshu Sharma (gwerra) - Websites team
- Stephen Smoogen (smooge) - Infrastructure team
Others?
Receivers
- Jared Smith - FPL
- Mike McGrath - Infrastructure team lead
Customers
Primary
- Marketing team
- Fedora Weekly News team
- Media (journalists, reporters, bloggers)
- Fedora community members
Secondary
- Documentation team
- Fedora users
- 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
Phase 2
The following additional functionality:
- The ability to select items from configured RSS feeds to be promoted to publication and other tagging
Phase 3
The following additional functionality:
- The ability to publish and attach podcasts to a story
- Post announcements of podcast publication
Requirements
Tasks
- Determine all requirements
- Determine whether platform meets requirements
- Scope requirements into phases
- Deploy test instance
- For each requirement in phase:
- Assign responsible contributor
- Document procedure for fulfillment on wiki
- ...