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 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 asking to have your project home page relinked

<project-name> Documentation

Formal Documentation - End users and implementers

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

Developer Documentation - Builders and contributors

Link to your key developer docs on the wiki
(example: Service Design and Creation (SDC) Portal)

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

Meeting Minutes

link to the location of your meeting minutes

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

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 T Created Updated Due Assignee Reporter P Status Resolution
Refresh

  • No labels

4 Comments

  1. Keong Lim

    Instead of creating "template" pages to be copied into actual pages (one of these has already caused confusion with people editing the template as if it was the actual page), shouldn't these "templates" be added as Confluence "blueprints"? Then they would be available to the "Create from template" button at the top navbar of the wiki.

    PTLs or TSC could be given Confluence admin permissions to maintain the templates.

    If going with the "restricted page" permissions, there should probably be a user group created for "ONAP template admin", so that changes to personnel can be done once in the user group management.


    1. Kenny Paul

      I agree that a blueprint would be a better solution, however on my first attempt to introduce a blueprint last year I was told it was too confusing and doing it this way was better. :-\   Perhaps that has changed now.

      I do have an LDAP group for PTLs and TSC members which I set up earlier in the year, but have not done much with yet. After this round of elections is complete I need to be utilizing that to a much greater extent and moving a number of things I have been doing into the hands of the community.


      1. Thomas Kulik

        Hi Kenny. Is there any update on the status of this proposal?

        1. Kenny Paul

          Hi Thomas Kulik, this has been pushed so far down the stack that it has become fossilized. (wink)  Ressurecting it should be simple enough however.

          This proposal reflkects the general chaos of the time and is overly complex.  There are more things in place now that can simplify it.

          Also, a true click-to-create template is something the community would be more than happy to accept now.