Initial Import

Author: mikehaller

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Community Code of Conduct
+
+**Version 1.2  
+August 19, 2020**
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as community members, contributors, committers, and project leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+*   Using welcoming and inclusive language
+*   Being respectful of differing viewpoints and experiences
+*   Gracefully accepting constructive criticism
+*   Focusing on what is best for the community
+*   Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+*   The use of sexualized language or imagery and unwelcome sexual attention or advances
+*   Trolling, insulting/derogatory comments, and personal or political attacks
+*   Public or private harassment
+*   Publishing others' private information, such as a physical or electronic address, without explicit permission
+*   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+With the support of the Eclipse Foundation staff (the “Staff”), project committers and leaders are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project committers and leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the Eclipse Foundation project or its community in public spaces. Examples of representing a project or community include posting via an official social media account, or acting as a project representative at an online or offline event. Representation of a project may be further defined and clarified by project committers, leaders, or the EMO.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Staff at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Staff is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project committers or leaders who do not follow the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the Staff.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org) , version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)

CONTRIBUTING.md

@@ -0,0 +1,130 @@
+# 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: 
+
+1. being the crystalization point for functionally integrating
+diverse SDV-scope projects into a working whole 
+2. 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:
+
+1. be the crystalization point for functionally integrating diverse SDV-scope projects into a working whole
+2. deliver a continually available, always working starting image for developers interested in getting going with the SDV tech stack
+
+### Why Eclipse?
+
+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.
+
+* 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
+