Title: Software Quality Standards comparison for OSS best practices
Proposal: The Lighthouse-SIG started with 3 (now 4) pillars of their work. One pending element is to identify existing standards which deal with software quality and development and see how they differ or fit to what the SIG wants to write down for OSS best practices. In this work packages students will start looking into standards, write the purpose and possible fit for extensions to have a base to either extend or argue for an additional standard. As a work package result we as ELISA will be able to demonstrate a systematic review on quality standards and their potential application to open source development as an entry point argument for safety-critical software development.
How it supports ELISA: The initiative directly benefits the work of the Lighthouse-SIG and indirectly also the OSEP WG. It is a planned work package of the Lighthouse-SIG which has not been executed for some time. The nice thing about this work package is that it can be handed over to a student and a monitoring of 1h per week can be sufficient to drive it forward properly. As the lighthouse-SIG misses enough time from the existing contributors, this can significantly accelerate the achievement of the lighthouse-SIG goals and also help students progressing their thesis or PhD.
Tangible Deliverables: A report will be available eventually as scientific paper or thesis which provides insights into existing standards and their fit to Open Source development plus the potential to improve them in their next revision. The Lighthouse-SIG can provide clear arguments where standards help and where they lagging behind what became open source best practices.
What's preventing progress: Lack of contributors, Lack of funding
Being worked on by other project/community: This may have touch points to other communities, but we are not aware of a specific community already taken it up or having it on their roadmap. The closest may be the Automotive Process group within Eclipse SDV, but this was recently paused/discontinued due to missing contributions and clear vision of participants.
Funding: 10k maybe?
If not pursued, what opportunities/benefits/capabilities will be lost: The opportunity delayed by this would be that the ELISA footprint as the go-to place for safety critical open source development is improved. We would be able to work on it over time and will ask for excuse that things take much longer whenever we are asked by attendees at conferences or workshop. The risk is that our reputation is lower that ELISA is able to deliver results.
Title: Software Quality Standards comparison for OSS best practices
Proposal: The Lighthouse-SIG started with 3 (now 4) pillars of their work. One pending element is to identify existing standards which deal with software quality and development and see how they differ or fit to what the SIG wants to write down for OSS best practices. In this work packages students will start looking into standards, write the purpose and possible fit for extensions to have a base to either extend or argue for an additional standard. As a work package result we as ELISA will be able to demonstrate a systematic review on quality standards and their potential application to open source development as an entry point argument for safety-critical software development.
How it supports ELISA: The initiative directly benefits the work of the Lighthouse-SIG and indirectly also the OSEP WG. It is a planned work package of the Lighthouse-SIG which has not been executed for some time. The nice thing about this work package is that it can be handed over to a student and a monitoring of 1h per week can be sufficient to drive it forward properly. As the lighthouse-SIG misses enough time from the existing contributors, this can significantly accelerate the achievement of the lighthouse-SIG goals and also help students progressing their thesis or PhD.
Tangible Deliverables: A report will be available eventually as scientific paper or thesis which provides insights into existing standards and their fit to Open Source development plus the potential to improve them in their next revision. The Lighthouse-SIG can provide clear arguments where standards help and where they lagging behind what became open source best practices.
What's preventing progress: Lack of contributors, Lack of funding
Being worked on by other project/community: This may have touch points to other communities, but we are not aware of a specific community already taken it up or having it on their roadmap. The closest may be the Automotive Process group within Eclipse SDV, but this was recently paused/discontinued due to missing contributions and clear vision of participants.
Funding: 10k maybe?
If not pursued, what opportunities/benefits/capabilities will be lost: The opportunity delayed by this would be that the ELISA footprint as the go-to place for safety critical open source development is improved. We would be able to work on it over time and will ask for excuse that things take much longer whenever we are asked by attendees at conferences or workshop. The risk is that our reputation is lower that ELISA is able to deliver results.