Introduction
Enter a detailed project description. Include the scope of the project (Goal, purpose, business needs/requirements)
Documentation & Training
Link here to any project documentation & training available for your project
Release Planning & Release Notes
Link here to release notes & release plans. This information is likely stored in the TF community Jira. Information should include Release deliverables (per release), Release Milestones (per release), externally consumable APIs, expected incompatibilities w/ other Projects, compatibility w/ previous releases, themes and priorities, requests from other projects, and any test tool requirements.
Project Facts
Project Creation Date: Use // to set date
Project Lead: Prabhjot Singh Sethi
Committers: This field will need to be maintained by the PTL. LF is currently working on automating this in the future
Mailing List: Indicate a 'hashtag' #*** to use on the mailing list to help with filtering
Meetings: See Community Meetings
If your project has a regularly scheduled community meeting, please make sure it is listed on the community calendar and the Community Meetings page.
Repository: Link to the TF community code repository
Jenkins: Link to Jenkins silo
Open Bugs: Link to Jira filter with tagged bugs
Emeritus Committers:
List of former committers for the project.
Project Working Documents
Task Report
All project pages should be tagged with a label 'projectname-project' example 'TF Operator Framework' is labeled 'operator-project'
This is a necessary step so that action items can be assigned between the PTL and the Committers of the project. Edit the "Task Report" confluence macro below and change the label field to match your project tag.
Project Files
Project files can be uploaded here. Please also follow the same steps for assigning a project label. Update the below macro field with your project label (tag) and remember to that when uploading files they should also be labeled with the same tag so they are easily filtered.
