-
Notifications
You must be signed in to change notification settings - Fork 8
/
CONTRIBUTING
116 lines (92 loc) · 6.1 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
# Contributing to Eclipse Leda
Thanks for your interest in this project.
## Project description
In the ambition to build a technology ecosystem for software-defined vehicle,
one of the main challengs will be the combination of the diverse components into
a coherent and useful whole: all the software components in the world will not
have the impact needed to transform the automotive industry unless we can make
them play together coherently an form a functional portfolio. As a first step
towards that goal, Eclipse Leda provides an "SDV distribution" that pulls
together individual contributor pieces from SDV and the larger OSS community, to
deliver a functional and always-available Linux-based image/distribution with
two primary goals: being the crystalization point for functionally integrating
diverse SDV-scope projects into a working whole delivering a continuously
available, always working starting image for developers interested in getting
going with the SDV tech stack Background:Â The newly instantiated Eclipse SDV
working group is currently gearing up to receive a first batch of project
proposals for technology building blocks that will begin to populate the
landscape of what will become an SDV ecosystem. The mid-term goal is to form a
technology ecosystem, where a myriad of projects and companies contribute
diverse functional additions around a set of core APIs, extension points and
integration patterns. To enable developers and users of the SDV ecosystem, an
SDV distribution is expected to help integrating several individual components
and various other open-source projects to a ready-to-use development environment
for new and existing components, as well as creating a basis for
automotive-grade, production-ready SDV solutions. Scope: The Eclipse Leda
project will provide system image “recipes†to deliver a functional
Linux-based image/distribution in the context of SDV (Software Defined Vehicle),
by pulling together individual contributons from the SDV and the larger OSS
community. The Eclipse Leda distribution will work with build scripts, package
definitions, image build pipelines, etc, with the goal to pull SDV projects and
dependecies from the larger OSS community into a working Linux system. Such
system images (or other useful forms of delivery, as determined by the project)
will be made available for consumption for anyone who is interested in working
with the SDV tech stack. These deliveries take the form of container (base)
images, installable/flashable image files, etc (again to be evolved by the
project team according to community needs). Also in scope is concise and useful
documentation for consumers of the project's deliverables, plus a method of
delivering that documentation. Description: In the context described above - the
ambition of SDV to build a technology ecosystem for software-defined vehicle
concern - a prime challenge will be the combination of these initially diverse
components into a coherent and useful whole: all the software components in the
world will not have the impact needed to transform the automotive industry
unless we can make them play together coherently an form a functional portfolio.
As a first step towards that goal, this proposal (Eclipse Leda) is for a "SDV
distribution" project that pulls together individual contributor pieces from SDV
and the larger OSS community, to deliver a functional and always-available
Linux-based image/distribution with two primary goals: be the crystalization
point for functionally integrating diverse SDV-scope projects into a working
whole deliver a continually available, always working starting image for
developers interested in getting going with the SDV tech stack Why Here?: The
Eclipse Leda project aims to become the integration point for individual
SDV-related projects, so it only makes sense in the scope of the Eclipse SDV
working group. At the same time, it could be a driving force for showcasing SDV
to the wider communtiy, and for providing a great onboarding experience to
SDV-driven technology. Project Scheduling: Initial contribution expected by Q3
2022 Release cycles are planned every 3-6 months Release planning will be
conducted together with corresponding Eclipse projects Future Work: Be the
integration and collaboration platform for Software defined Vehicle
functionality. include/update [Eclipse kanto] parts include [Eclipse velocitas]
include [Eclipse Backend function Bindings] add Open Telemetry include more
functionality of SDV special interest group
* https://projects.eclipse.org/projects/automotive.leda
## Terms of Use
This repository is subject to the Terms of Use of the Eclipse Foundation
* http://www.eclipse.org/legal/termsofuse.php
## Developer resources
Information regarding source code management, builds, coding standards, and
more.
* https://projects.eclipse.org/projects/automotive.leda/developer
The project maintains the following source code repositories
* https://github.com/eclipse-leda/leda
* https://github.com/eclipse-leda/leda-distro
* https://github.com/eclipse-leda/meta-leda
## Eclipse Development Process
This Eclipse Foundation open project is governed by the Eclipse Foundation
Development Process and operates under the terms of the Eclipse IP Policy.
* https://eclipse.org/projects/dev_process
* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
## Eclipse Contributor Agreement
In order to be able to contribute to Eclipse Foundation projects you must
electronically sign the Eclipse Contributor Agreement (ECA).
* http://www.eclipse.org/legal/ECA.php
The ECA provides the Eclipse Foundation with a permanent record that you agree
that each of your contributions will comply with the commitments documented in
the Developer Certificate of Origin (DCO). Having an ECA on file associated with
the email address matching the "Author" field of your contribution's Git commits
fulfills the DCO's requirement that you sign-off on your contributions.
For more information, please see the Eclipse Committer Handbook:
https://www.eclipse.org/projects/handbook/#resources-commit
## Contact
Contact the project developers via the project's "dev" list.
* https://accounts.eclipse.org/mailing-list/leda-dev