Project NanoMQ

We would adopt the LF Edge Code of Conduct

Required Information

Responses (Please list N/A if not applicable)

Name of Project

NanoMQ

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

An Ultra-lightweight and Blazing-fast MQTT Broker for IoT Edge

Statement on alignment with Foundation Mission Statement

NanoMQ contributors share the same vision as LF Edge. We are committed to build a powerful, user-friendly, and open-source message broker on edge devices.

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. 

EdgeX Foundry

Open Horizon

Home Edge (archived)

Fledge

Link to current Code of Conduct

We would adopt the LF Edge Code of Conduct

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

Joe Pearson, Jim White 

Project license

MIT License

Source control (GitHub by default)

https://github.com/emqx/nanomq

Issue tracker (GitHub by default)

https://github.com/emqx/nanomq/issues

External dependencies (including licenses)

No dependencies for Core functionality (MQTT Broker)

https://github.com/nanomq/NanoNNG (A self maintained for of NNG)

MIT License

Add-on dependencies:

https://github.com/GlitchedPolygons/l8w8jwt (If JWT Token is enabled for HTTP authorization)

Apache-2.0

https://github.com/microsoft/msquic (If MQTT over QUIC is enabled)

MIT License

(only source code dependencies are counted)

Release methodology and mechanics

Github

Names of initial committers, if different from those submitting proposal

Jaylin Yu

Current number of code contributors to proposed project

23

Current number of organizations contributing to proposed project

2

Briefly describe the project's leadership team and decision-making process

Jaylin Yu as the project leader, whom is also responsible for communicating with community to collect feature request and issue report. 

New feature/architecture plan is decided among EMQ' governing board.

List of project's official communication channels (slack, irc, mailing lists)

Slack 
Discord

Github Discussion

Link to project's website

https://nanomq.io/

Links to social media accounts

N/A

Existing financial sponsorship

EMQ Technologies

Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...)

N/A

Currently Supported Architecture

Windows + Linux/Yocto/Build-root/OpenWRT/QNX/Any POSIX compatible Operating System

X86/64, ARM/MIPS/RISC-V

Planned Architecture Support

Android

Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines)

Trademark status

EMQ‘ intellectual property

Does the project have a Core Infrastructure Initiative security best practices badge? (See: https://bestpractices.coreinfrastructure.org)

NO

Any additional information the TAC and Board should take into consideration when reviewing your proposal?

N/A

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

APIs

Cloud Connectivity

Container Runtime & Orchestration

Data Governance

Data Models

Device Connectivity

Filters/Pre-processing

Logging

Management UI

Messaging & Events

Notifications & Alerts

Security

Storage

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

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)

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.

APIs

Applications

Firmware

Hardware

Orchestration

OS

VM/Containers

Applications

Configuration (drive)

Content (management system)

IaaS

PaaS

Physical Infrastructure

SaaS