DRAFT- LFN Candidate Project Data Template

DRAFT- LFN Candidate Project Data Template

Placeholder page to create candidate project checklist, documentation and TAC presentation slide template.

Instructions

This page is intended to give provide detailed information on how to prepare and present a new project as an LFN Candidate project. A candidate project is described as Projects looking to integrate with the LFN umbrella of projects may be inducted at any lifecycle state, provided it meets The Linux Foundation's proven best practices for success.

Use the checklist below to prepare and present the project presentation, also below, to the LFN TAC for induction as an LFN Candidate project.

Other useful links are at the bottom of the page.

Need Help? Contact: support@lfnetworking.org

Candidate Project Presentation Template

Candidate Induction Checklist

Category

Task

Who?

Requires input from

Mandatory

Comments

Status

Category

Task

Who?

Requires input from

Mandatory

Comments

Status

LFX & LF formation/onboarding

PCC Onboarding & Become an adopted LF Project

LF PM

The community to provide

  • Project name- Note- if project name is net-new the trademark and other registrations need to be checked

  • Project description. This can include

  • Mission statement

  • Final Technical Charter

  • Signed Contributor Agreement

  • A list of initial technical contacts for the project

  • An LFN positioning statement

Y

Work with the LF PM and the LF Formation team to become an LF Project.

The LF Formation team will provide Project Formation Instructions via a Google Doc. The Project Formation Instructions will include a Technical harter Draft, Contributor Agreement Draft, and Series Agreement Draft, as well as explanation of each document. Requirements are:

  1. Have a final Technical Charter, with an Adoption Date, approved by the initial community, and the LF Formation team. A PDF version of the Final Technical Charter must be documented in a public space; for example; Wiki, GitHub, etc.

  2. Transfer of Transfer of project assets to The Linux Foundation (domains, repos, logo, …), where applicable. This culminates into a signed and adopted Contributor Agreement

LF PM May not have the right access rights to create new LF level projects.

Project name
Project description. This can include
Mission statement
Final Technical Charter
Signed Contributor Agreement
A list of initial technical contacts for the project
An LFN positioning statement

Infrastructure

Wiki

LF PM

Project name

 

Y

The LF PM will setup a project Space under wiki.lfnetworking.org to be used as the projects' wiki

Wiki space created

Register project domain(s)

LF PM

Project name

Y

The LF PM will register available domains in PCC, and a primary domain is set.

Domains are registered, and a primary domain is set.

LF ID for project members

Community

None

Y

All project contributors are highly encouraged to create an LF ID. This is needed to be able to edit wiki spaces and to use LFX. Create an LF ID here: https://openprofile.dev/

LF IDs created

 

Communication channel

LF PM

Project name

Y

A project mailing list / slack / zulip channel may be established before Candidate announcement to make it easier to contact community members and to document parties interested in joining the project.

Project mailing list is established
Zulip
Slack

Candidate onboarding

Preparing, presenting, and annoucing the Candidate project

LF PM and Community

Complete all the tasks above

Y

  1. The PM makes a copy of this page and adds it as a new project proposal here: https://lf-networking.atlassian.net/wiki/x/mp-u

  2. The community completes the LFN Candidate project presentation template on the new project proposal page.

  3. Working with the LF PM the community sends an email to the LFN TAC <lfn-tac@lists.lfnetworking.org> with a proposed date to present the project. The date and time must align with a regularly scheduled bi-weekly TAC meeting per the LFN TAC wiki. You must include a copy of the competed Candidate Project Presentation.

  4. Prior to the LFN TAC meeting the community must decide who will present the project. No more then 2 persons. Other techical project experts may attend to help with technical questions.

LFN Candidate presentation is complete
Email sent to the LFN TAC with the proposed presentation date. Attach a copy of the completed Candidate presentation.
Community spokeperson(s) who will present the project have been decided.

Other Helpful Links