Document usage of github projects

[pahmann]

OSEP, Systems and Automotive WG start using github projects to track tasks and distribute work. The structure of the projects should have a common look and feel and need to be properly documented. Also the process in using it need to be written down.

This issue is there to have documentation (most likely in the workgroups repo of elisa-tech) how to work with github projects The issue may be moved based on discussion within OSEP and TSC meeting

[reiterative]

One of the things that we discussed at the ELISA Workshop was establishing a common way of working with regard to change management for material that working groups produce and publish (share in public), to include some level of review and scrutiny appropriate for functional safety.

This topic is related to this issue. To start addressing it, someone in this working group could:

1. Review the Automotive WG's Contribution Workflow, to consider whether this is a good starting point:

https://github.com/elisa-tech/wg-automotive/tree/master#contribution-workflow

2. Review the notes from the workshop discussion and document some proposed actions / requirements in the issue

https://docs.google.com/document/d/1HUX2wQSpVDN77zDPxG_Ju6TtlPih-s6Tj5sIMCMpm4c/edit#bookmark=id.5kqnnirqg37h

The results of these can be documented in the issue, and we can discuss them at a future weekly meeting.