r5 - 02 Feb 2006 - 11:08:30 - LisaDusseaultYou are here: OSAF >  Journal Web  >  TWikiUsers > LisaDusseault > LisaDusseaultNotes > LisaDusseault20041122

Example of "Project Template" project


Overview: The project template project is a sample project to demonstrate what a project page might look like. This project is being done during the 0.4 development cycle but not tied to that cycle.

We recommend project status pages be named "FooProject" (though renaming existing pages isn't needed. In addition to maintaining status, they should be jumping off points for more information about the project.

(Focus on immediate goals and scope of project, not details)

People

  • Lisa Dusseault (Template author)

Scheduled Tasks

Task name/info Status Milestone
Propose a project page template Done 0.4.3
Move existing project pages to template Not started 0.4.4

  • The milestone target is the most important column -- it's both the plan and the record of what was achieved.
  • Task info should be brief but might point to issue pages
  • No priority column. -- low priority things shouldn't be on the table of scheduled tasks
  • May include Owner column if project has multiple active contributors.
  • Err on the side of simple and short (easy to maintain).
  • Exact consistency with other tables is valuable but not necessary.

References section:

  • AboutThePageInfoBox? -- Used to declare the page as a project page

Unscheduled tasks section

  • Feature ideas, refactoring ideas, issues for the future)
  • may be described here, listed here, or link elsewhere
  • brevity here is fine

Optional sections?

  • News section (like EmailService)
  • History section (like ContentModelProject) - keep brief, mostly pointers to historic pages
  • Up-to-dateness is probably better than completeness -- better not to have the news section than to have it really out-of-date

-- LisaDusseault - 22 Nov 2004


I like this, but I would like to have a brief description of the project right up top, first thing, so that people wandering around lost dazed and confused will know what the page is about.

You mention that there ought to be consistent naming of project pages. I think that means we need guidelines for what a project is. Is Queries a project, or is it some sub-thing of Repository? Is Wiki maintenance a project? Is QA a project or a process? Is Product Management a project or a group?

You seem to imply that all project pages should have a Page Info box. Do you propose that as a policy item?

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.