Page tree
Skip to end of metadata
Go to start of metadata

Instructions

  1. Review the Project Proposal Process
  2. Add New Proposals to the Wiki using the template below and detailed instructions here.
  3. If you need help creating your new Project Proposal page - and adding the template below, please email info@lfedge.org



Project Proposal Template


Project Proposal - Project Introduction:

Required Information

Responses (Please list N/A if not applicable)

Name of Project


Project Description (what it does, why it is valuable, origin and history)


Statement on alignment with Foundation Mission Statement


High level assessment of project synergy with existing projects under LF Edge, including how the project compliments/overlaps with existing projects, and potential ways to harmonize over time. Responses may be included both here and/or in accompanying documentation. 

Link to current Code of Conduct


2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations


Project license


Source control (GitHub by default)


Issue tracker (GitHub by default)


External dependencies (including licenses)


Release methodology and mechanics


Names of initial committers, if different from those submitting proposal


Current number of code contributors to proposed project
Current number of organizations contributing to proposed project
Briefly describe the project's leadership team and decision-making process
Preferred maturity level (see stages here)
For Projects applying at the Growth (Phase 2) or Impact Stage (Phase 3), please outline how your project successfully meets/exceeds the requirements as defined under each category. Responses may be included both here and/or in accompanying documentation.
List of project's official communication channels (slack, irc, mailing lists)
Link to project's website

Links to social media accounts


Existing financial sponsorship
Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...)
Currently Supported Architecture
Planned Architecture Support
Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines)
Trademark status
Does the project have a Core Infrastructure Initiative security best practices badge? (See: https://bestpractices.coreinfrastructure.org)
Any additional information the TAC and Board should take into consideration when reviewing your proposal?




Project Proposal - Mapping Criteria and Data:

Stage 1: At Large Projects (formerly 'Sandbox')

CriteriaData

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations


A presentation at an upcoming meeting of the TAC, in accordance with the project proposal requirements


The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board.


Upon acceptance, At Large projects must list their status prominently on website/readme



*** For existing Projects requesting Stage 2 or Stage 3 consideration, please update the above with the Stage 2 or Stage 3 Mapping criteria, available at Project Stages Mapping: Criteria and Data




Project Proposal - Taxonomy Data:

Functions (Provide, Consume, Facilitate, or N/A; Add context as needed)

Functions(Provide, Consume, Facilitate, or N/A; Add context as needed)
APIs
Cloud Connectivity
Container Runtime & Orchestration
Data Governance
Data Models
Device Connectivity
Filters/Pre-processing
Logging
Management UI
Messaging & Events
Notifications & Alerts
Security
Storage

Deployment & Industry Verticals (Support, Possible, N/A; Add context as needed)

Deployment Type(Support, Possible, N/A; Add context as needed)
Customer Devices (Edge Nodes)
Customer Premises (DC and Edge Gateways)
Telco Network Edge (MEC and Far-MEC)
Telco CO & Regional
Cloud Edge & CDNs
Public Cloud
Private Cloud

Deployment & Industry Verticals (✔ or X; Add context as needed)

Directly applicable Industry/Verticals use cases(✔ or X; Add context as needed)
Automotive / Connected Car
Chemicals
Facilities / Building automation
Consumer
Manufacturing
Metal & Mining
Oil & Gas
Pharma
Health Care
Power & Utilities
Pulp & Paper
Telco Operators
Telco/Communications Service Provider (Network Equipment Provider)
Transportation (asset tracking)
Supply Chain
Preventative Maintenance
Water Utilities
Security / Surveillance
Retail / Commerce (physical point of sale with customers)
Other - Please add if not listed above (please notify TAC-subgroup@lists.lfedge.org when you add one)

Deployments (static v dynamic, connectivity, physical placement) - (✔ or X; Add context as needed)

Use Cases(✔ or X; Add context as needed)
Gateways (to Cloud, to other placements)
NFV Infrastructure
Stationary during their entire usable life / Fixed placement edge constellations / Assume you always have connectivity and you don't need to store & forward.
Stationary during active periods, but nomadic between activations (e.g., fixed access) / Not always assumed to have connectivity. Don't expect to store & forward.
Mobile within a constrained and well-defined space (e.g., in a factory) / Expect to have intermittent connectivity and store & forward.
Fully mobile (To include: Wearables and Connected Vehicles) / Bursts of connectivity and always store & forward.

Compute Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Compute Stack Layers(Provide, Require, or N/A; Add context as needed)
APIs
Applications
Firmware
Hardware
Orchestration
OS
VM/Containers

Cloud Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Cloud Stack Layers(Provide, Require, or N/A; Add context as needed)
Applications
Configuration (drive)
Content (management system)
IaaS
PaaS
Physical Infrastructure
SaaS


Attachments (LF Edge PPT template is below, if proposing project would like to leverage):


  • No labels
Write a comment…