Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Proposed home page template NOT APPROVED BY TSC. On the agenda for July 12

TEMPLATE NOTES FOR PTLs : Help/HOW-TO instructions are in red - PLEASE READ THEM

  • This template is for Approved projects only

  • Make a copy of this template and move it under your own project page hierarchy.

  • EDIT the copied and moved page accordingly, 

    • do a global replace of "<project-name>" with your project name

    • provide the links and information requested.

  • CLICK on the padlock at the top of the page and set "editing restricted" - Add Kenny Paul, Phil Robb & Gildas Lanilis Gmail as editors

  • REMOVE res text and examples as you go

  • REMOVE this entire section 

    • highlight this section of text 

    • click on the page layout icon (the one with the two dark vertical rectangles in it)

    • click "Remove section" 

  • EDIT your existing project hame page and rename it to "<project-name> Old Home Page"

  • send an email to Kenny Paul & Gildas Lanilis Gmail asking to have your project home page relinked

Official <project-name> Release Documentation 

ink to the readthedocs section for your project: (example: http://onap.readthedocs.io/en/beijing/submodules/sdc.git/docs/

Key Information About <project-name>

Note when filling this out Items marked with a * should mirror, (or point to) the same source as the contents of your INFO.yaml.

Project Approval Date*

  use correct date and provide a link to the approved proposal (example:

Logging Enhancements Project Proposal

Lifecycle Status*


Project Technical Lead (PTL)*

use @ macro to link to your wiki profile

Current Committers*

use @ macro to link to each Committer's wiki profile

Meeting Info*

link to your specific meeting wiki page under the Community Calendar (example:

[onap-tsc] TSC Meeting ONAP1, Thr UTC 14:00 / China 22:00 / Eastern 10:00 / Pacific 07:00

Mailing- List

link to groups.io list (if appropriate) or to the tag.

Repo(s)

link to appropriate gerrit query (example:

https://gerrit.onap.org/r/#/admin/projects/?filter=aaf

JIRA*

link to your project's JIRA board page (example:

https://jira.onap.org/projects/POLICY

Community Statistics

link to appropriate bitergia query (example: https://onap.biterg.io/goto/5257354228247ba8a320d3cbafa01931

IRC (if used)

Listed this if used, otherwise nuke this line. (example:

freenode.net #onap-int

Description:


A few short sentences to describe your project, usually taken from your approved project proposal.


Release Lifecycle Artifacts

Change all bulleted items to links to your docs Old items can probably be cut and pasted from your current project page.

Casablanca

  • M1 Release Planning 
  • M1 Release Planning Checklist 
  • M2 Functionality Freeze
  • M3 API/Data Model Freeze
  • M4 Code Freeze
  • RC0 Checklist
  • RC1 Checklist
  • RC2 Checklist

Beijing

  • M1 Release Planning 
  • M1 Release Planning Checklist 
  • M2 Functionality Freeze
  • M3 API/Data Model Freeze
  • M4 Code Freeze
  • RC0 Checklist
  • RC1 Checklist
  • RC2 Checklist

Amsterdam

  • M1 Release Planning 
  • M1 Release Planning Checklist 
  • M2 Functionality Freeze
  • M3 API/Data Model Freeze
  • M4 Code Freeze
  • RC0 Checklist
  • RC1 Checklist
  • RC2 Checklist

Other Project Material

Meeting Minutes (link)

Architecture Documents

etc.

etc.


High & Highest Priority Open Bugs

Add the JIRA issue/filter widget here for your highest priority bugs. Use the filter: 

project = "<project-name>" AND type = Bug AND resolution = Unresolved AND (priority = High OR priority = Highest) ORDER BY description DESC,updated DESC

Example:

key summary type created updated due assignee reporter priority status resolution
Refresh

  • No labels