DRAFT - UNDER REVIEW
Instructions
- Review the Project Proposal Process
- Add New Proposals to the Wiki using the template below and detailed instructions here.
- 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 |
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 | |
Sponsor from TAC, if identified (a sponsor helps mentor projects) | |
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 | |
Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines) | |
Trademark status | |
Any additional information the TAC and Board should take into consideration when reviewing your proposal? |
Project Proposal - Taxonomy Data:
Functions | Does Proposed Project Currently Address? (Yes, No or Planned/Roadmap) |
---|---|
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 Type | Does Proposed Project Currently Include? (Yes, No or Planned/Roadmap) |
---|---|
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 |
Industry/Verticals | Does Proposed Project Currently Target? (Yes, No or Planned/Roadmap) |
---|---|
Automotive | |
Chemicals | |
Cloud Operators | |
Cloud Service Provider | |
Data Centers & IT | |
Enterprise | |
Facilities | |
Home Edge | |
Manufacturing | |
Metal & Mining | |
Oil & Gas | |
Pharma | |
Power & Utilities | |
Pulp & Paper | |
Telco Operators | |
Telco/Communications Service Provider | |
Transportation | |
Water Utilities |
Use Cases | Does Proposed Project Currently Address? (Yes, No or Planned/Roadmap) |
---|---|
Fixed placement edge constellations | |
Gateways (to Cloud, to other placements) | |
Mobile deployments, static services, intermittent connectivity | |
NFV Infrastructure | |
On-demand events | |
Wearables |
Compute Stack Layers | Does Proposed Project Currently Include (Yes, No or Planned/Roadmap) |
---|---|
APIs | |
Applications | |
Firmware | |
Hardware | |
Orchestration | |
OS | |
VM/Containers |
Cloud Stack Layers | Does Proposed Project Currently Include (Yes, No or Planned/Roadmap) |
---|---|
Applications | |
Configuration | |
Content | |
IaaS | |
PaaS | |
Physical Infrastructure | |
SaaS |
Attachments (LF Edge PPT template is below, if proposing project would like to leverage):