Make contribution document visible and update repo list

Author: erikbosch

config/_default/config.toml

@@ -26,27 +26,32 @@ paginate = 10
 
 [[menu.main]]
     name = "Vision"
-    url  = "/about/"
+    url  = "/about"
     weight = 15
 
 [[menu.main]]
     name = "Quickstart"
     url = "/quickstart"
     weight = 16
 
+[[menu.main]]
+    name = "Contributing"
+    url = "/contributing"
+    weight = 18
+
 [[menu.main]]
     name = "Blog"
-    url  = "/blog/"
+    url  = "/blog"
     weight = 20
 
 [[menu.main]]
     name = "Videos & Publications"
-    url  = "/publications/"
+    url  = "/publications"
     weight = 30
 
 [[menu.main]]
     name = "Resources"
-    url  = "/resources/"
+    url  = "/resources"
     weight = 40
 
 

config/staging/config.toml

@@ -12,4 +12,4 @@ Eclipse Kuksa and its latest development activities will be presented along with
 
 ## Embedded Software Engineering Kongress 2018
 
-In addition to the EclipseCon Europe event, you can join us at the **ESE Kongress** in Sindelfingen, Germany, on December, 6th. The talk [Überwindung der Silos – Revolution für vernetzte Fahrzeuge](https://www.ese-kongress.de/paper/presentation/id/78), that means 'Overcoming the Silos - Revolution for Connected Vehicles',  will be held at 16:45 o'clock (4:45pm) and will cover both a generic as well as detailed descriptions of the three Eclipse Kuksa platforms (a) In-Vehicle, (b) IDE, and ( c) Cloud. 
+In addition to the EclipseCon Europe event, you can join us at the **ESE Kongress** in Sindelfingen, Germany, on December, 6th. The talk "Überwindung der Silos – Revolution für vernetzte Fahrzeuge", that means 'Overcoming the Silos - Revolution for Connected Vehicles',  will be held at 16:45 o'clock (4:45pm) and will cover both a generic as well as detailed descriptions of the three Eclipse Kuksa platforms (a) In-Vehicle, (b) IDE, and ( c) Cloud. 

content/blog/2018-10-22-ece1018ese1218.md

@@ -4,15 +4,7 @@ date: 2019-01-29T09:46:31+02:00
 draft: false
 ---
 
-**Get in touch** ! There is the 
-### [kuksa-dev mailing list](https://accounts.eclipse.org/mailing-list/kuksa-dev) and a 
-### **bi-weekly** [Zoom meeting](https://eclipse.zoom.us/j/537310990) every Thursday on even calendar weeks from 1-2pm (CET/CEST).
-
------------
------------
-
-
-# HowTo contribute to Eclipse Kuksa
+# How to contribute to Eclipse Kuksa
 Great that you are interested in contributing to Eclipse Kuksa. 
 We really looking forward to receive your contribution!
 
@@ -24,13 +16,11 @@ In the project we agreed upon the following approach to add contributions to the
 4. Clearly outline third party dependencies
 
 ## Definition of Done
+
 First, we have DoD for solved issues. Please check if you met all the items in the following list:
 
 * File headers in file OK (see section [License Headers](#licensing-and-file-header) for details)
 
-* Each new feature is developed in a separate branch
-  * Development branches should be named like`<github-nickname>/<issue>/<description>`, e.g. bs-jokri/#2/fix-connection-handling
-
 * Coding style
   * Clean code is encouraged (see ‘Clean Code’ by Robert C. Martin or the 
     [Clean Code Cheatsheet](https://www.bbv.ch/images/bbv/pdf/downloads/V2_Clean_Code_V3.pdf).
@@ -42,15 +32,13 @@ First, we have DoD for solved issues. Please check if you met all the items in t
 
 * All tests pass
   * Unit testing as it is already present
-  * You have more - use them!
+  * If you have more - contribute them!
 
 * Documentation
   * Provide the necessary technical documentation of your feature in the respective 
     Github repository that you contribute to. Documentation is in markdown and it either 
     included in the top-level README.md file of the Github repository, or linked from 
     there. 
-  * Update the high-level overview of Kuksa in the [kuksa.integration Wiki at Github](https://github.com/eclipse/kuksa.integration/wiki).
-    From the wiki, provide links to relevant technical documentation in the Github repositories.
 
 * Commit style
   * Please write brief and useful commit messages: Separate the subject from body with a blank line because the subject line
@@ -70,7 +58,7 @@ First, we have DoD for solved issues. Please check if you met all the items in t
 If you checked your code according to the DoD and you feel it can be merged to master, please create a PR to master. 
 Each PR that is merged to master has to pass all tests and needs a code review of some other person of the project that looks onto your contribution from another angle, 
 i.e. didn't work with you on the new feature. Probably a good idea is to have someone from another organization doing the review.
-Maybe you already have someone in mind doing the review, then request a review from this person via the github review functionallity.
+Eclipse Kuksa Committers regularly scan the repositories for new Pull Requests.
 
 ## Review
 If you conduct a code review, please look at the following issues:
@@ -81,60 +69,36 @@ If you conduct a code review, please look at the following issues:
   * Does the new feature fit the overall project goal, is it suitable for the community
 
 ## Manual Test
-If applicable the new  feature should at least be deployed and tested by someone before actually merged to master.
-This could be done by the same person that is doing the review but could be performed  by another person.
-
+If applicable the new feature should at least be deployed and tested by someone before actually merged to master.
+This could be done by the same person that is doing the review but could be performed by another person.
 
 After review and tests are finished it should be documented who actually did the review and the test.
-Do this with the following lines in the comments of the PR.
-```
-review-by:[email protected]
-```
-and
-```
-tested-by:[email protected]
-```
-
-## Third party dependencies
-
-If you use third party content (import / include ...), you are required to list each third party content explicitly with its version number in the documentation or your pull-request comment.
-Please note that GPL software cannot be approved for Eclipse Kuksa.
+Use the GitHub review mechanism and give comment stating what you have done.
 
 ## Licensing and file header
 
 All files contributed require headers - this will ensure the license and copyright clearing at the end.
 Also, all contributions must have the same license as the original source.
 
-If a file has relevant functionality add the official EPL-2.0 header as described here
-https://www.eclipse.org/legal/epl-2.0/faq.php#h.q72cnghf29k0
-
-We recommend to use the releng copyright tool at:
-https://wiki.eclipse.org/Development_Resources/How_to_Use_Eclipse_Copyright_Tool
+Most Eclipse KUKSA repositories use the [Apache-2.0 ](https://www.apache.org/licenses/LICENSE-2.0) license.
+A header like the one below shall be used.
 
 ```
-/*********************************************************************
-* Copyright (c) {date} {owner} [and others]
+/********************************************************************************
+* Copyright (c) {year} Contributors to the Eclipse Foundation
+*
+* See the NOTICE file(s) distributed with this work for additional
+* information regarding copyright ownership.
 *
-* This program and the accompanying materials are made
-* available under the terms of the Eclipse Public License 2.0
-* which is available at https://www.eclipse.org/legal/epl-2.0/
+* This program and the accompanying materials are made available under the
+* terms of the Apache License 2.0 which is available at
+* http://www.apache.org/licenses/LICENSE-2.0
 *
-* SPDX-License-Identifier: EPL-2.0
-**********************************************************************/
+* SPDX-License-Identifier: Apache-2.0
+********************************************************************************/
 ```
 (please adapt comment characters usage)
 
-For small files such as property files, configuration files or standard XML files:
-
-```
-# Copyright <COPYRIGHT_HOLDER>, <YEAR>. Part of the Eclipse Kuksa Project.
-#
-# All rights reserved. This configuration file is provided to you under the
-# terms and conditions of the Eclipse Distribution License v1.0 which
-# accompanies this distribution, and is available at
-# http://www.eclipse.org/org/documents/edl-v10.php
-```
-
 ## Eclipse Contributor Agreement
 
 Before your contribution can be accepted by the project team contributors must

content/contributing.md

@@ -20,36 +20,8 @@ You can reach us on the [kuksa-dev mailing list](https://accounts.eclipse.org/ma
 
 # Get the code
 
-The code for the various subprojects is provided in the following Github repositories. Please note that
+The code for the various subprojects is provided in  Github repositories. Please note that
 issues are tracked and discussed in the repository of the respective sub-project.
 
-## Active projects 
-{{<table "table table-striped table-bordered">}}
-| Component                | Source                                    | Description |
-|--------------------------|-------------------------------------------|----------|
-| Eclipse KUKSA.val        |https://github.com/eclipse/kuksa.val       | KUKSA Vehicle Abstraction Layer, this is a an implementation of a VSS server provding access to in-vehicle signals using VISS or GRPC interfaces  |
-| Eclipse KUKSA.val.feeders        |https://github.com/eclipse/kuksa.val.feeders       | Multiple data and actuation providers, gathering vehicle data and transforming it to VSS suitable for KUKSA.val  |
-| Eclipse KUKSA.val.services        | https://github.com/eclipse/kuksa.val.services       | Set of example vehicle services  |
-| Eclipse KUKSA Android SDK        | https://github.com/eclipse-kuksa/kuksa-android-sdk  | SDK to develop KUKSA clients on Android using Kotlin or Java  |
-| Eclipse KUKSA Android Companion        | https://github.com/eclipse-kuksa/kuksa-android-companion  | Example App using the Android SDK to check and control temperature, tire pressure, doors etc. from your phone  |
-| Eclipse KUKSA Python SDK        | https://github.com/eclipse-kuksa/kuksa-python-sdk  | SDK to develop KUKSA applications and providers using Python. Also includes a versatile CLI client for testing/debugging  |
-| Eclipse KUKSA.hardware   | https://github.com/eclipse-kuksa/kuksa-hardware |Hardware schematics and manufacturing files for the KUKSA SDV prototpying platform. This is a PI-compatible hardware providing access to CAN, OBD and cellular connectivity  |
-| KUKSA-website            | https://github.com/eclipse-kuksa/kuksa-website  | The sources for the website you are reading now |
-{{< /table >}}
-
-## Dormant projects
-This repositories contain components that have been developed in the past, but are currently not actively maintained or whose functionality has been integrated into active components.
-
-
- 
-{{<table "table table-striped table-bordered">}}
-
-| Component                | Source                                     | Description |
-|--------------------------|--------------------------------------------|----------|
-| Eclipse KUKSA.ide        |  https://github.com/eclipse/kuksa.ide      |  Browser-based IDE used by developers to create applications for the Eclipse Kuksa in-vehicle. If you are searching for an integrated way to build applications based on vehicle data provided by KUKSA.val, you may want to check the [Velocitas framework](https://eclipse-velocitas.github.io/velocitas-docs/). As first step you can have a look at the playground from [digital auto](https://digitalauto.netlify.app/). | 
-| KUKSA.Apps               | https://github.com/eclipse/kuksa.apps      | Contains applications to showcase use-cases of Eclipse KUKSA. Demos regarding vehicle signal access have been moved over to [KUKSA.val](https://github.com/eclipse/kuksa.val) |
-| KUKSA.In-Vehicle         | https://github.com/eclipse/kuksa.invehicle | The in-vehicle platform of Eclipse Kuksa. The KUKSA hardware has been moved to [KUKSA.hardware](https://github.com/eclipse/kuksa.hardware), the VISS dataserver for accessing in-vehicle data is further developed in [KUKSA.val](https://github.com/eclipse/kuksa.val ). For a modern integrated SDV distribution check [Eclipse LEDA](https://eclipse-leda.github.io/leda/) | 
-| Eclipse KUKSA.cloud      | https://github.com/eclipse/kuksa.cloud    | The cloud-backend of Eclipse KUKSA, including the App Store. Provides helmcharts for easy deployment of the KUKSA.cloud. For deploying software in a vehicle check [Eclipse Kanto](https://github.com/eclipse-kanto) or other pojects in [Eclipse SDV](https://sdv.eclipse.org/). For updated versions of the components utilized in KUKSA.cloud check [Eclipse IoT packages](https://github.com/eclipse/packages)  |
-{{< /table >}}
-
+Please visit [Eclipse Kuksa](https://github.com/eclipse-kuksa) on Github to explore all repositories!
 

content/resources.md

@@ -1,3 +1,3 @@
 name: "Eclipse Velocitas"
 image: "img/clients/velocitas-h180.png"
-url: "https://websites.eclipseprojects.io/velocitas/"
+url: "https://projects.eclipse.org/projects/automotive.velocitas"