...
Required Information | Responses (Please list N/A if not applicable) |
Name of Project | OpenIDX - Open Instant Data eXchange |
Project Description (what it does, why it is valuable, origin and history) | OpenIDX is a cloud and edge cloud platform to exchange and distribute data in real-time between users in a certain geography. One use case is V2X (Vehicle to anything communication), where data between road users (like cars) and between road infrastructure (e.g. traffic lights) and road users is anonymously exchanged with each other |
Statement on alignment with Foundation Mission Statement | We agree with the foundation's 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. | OpenIDX will investigate synergies with other LF Edge projects, like Akraino for leveraging infrastructure and application blueprints. Beside, projects like Fedge, ... |
Link to current Code of Conduct | We will adopt LF Edge's Code of Conduct. |
2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations | Tina Tsou |
Project license | |
Source control (GitHub by default) | https://github.com/OpenIDX |
Issue tracker (GitHub by default) | https://github.com/OpenIDX/[component]/issues |
External dependencies (including licenses) | Apache 2.0 EPL 1.0, 2.0 MIT, ... full list with dependencies will be updated based on final source code |
Release methodology and mechanics | GitHub Releases |
Names of initial committers, if different from those submitting proposal | |
| Current number of code contributors to proposed project | 56 |
| Current number of organizations contributing to proposed project | 4-6 tbc. |
| Briefly describe the project's leadership team and decision-making process | |
| List of project's official communication channels (slack, irc, mailing lists) | Slack and mailing list (tbd. after name has been finalized) |
| Link to project's website | https://step.vodafone.com |
Links to social media accounts | N/A |
| Existing financial sponsorship | Vodafone Business |
| Infrastructure needs or requests (to include GitHub/Gerrit, CI/CD, Jenkins, Nexus, JIRA, other ...) | SCM (Gitlab), CI/CD (Jenkins), Artifact Repo (Nexus), Code Scanning (Sonarqube), Jira |
| Currently Supported Architecture | Cloud, Kubernetes, OpenShift |
| Planned Architecture Support | Cloud, Kubernetes, OpenShift |
| Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines) | tbd. after name is fixed |
| Trademark status | Trademark will need to be pursed by the Linux Foundation upon project proposal acceptance |
| 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? |
...