Abstract
The mission of the project currently is to 'develop a "reference design" and "industrial grade" open source real-time platform'. In practice, this would make alignment of other Linux distributions to SEAPATH impossible unless they follow the reference design to the letter. To open SEAPATH to a wider audience, the project would have to provide a specification that details what a SEAPATH conformant implementation needs to look like. We thus propose to widen the mission of SEAPATH to include such a specification.
Current status
Subsection 1(a) of the project charter reads:
The mission of the Project is to develop a “reference design” and “industrial grade” open source real-time platform that can run virtualized automation and protection applications.
Detailed Description
Change subsection 1(a) of the project charter to:
The mission of the Project is to develop a reference design and industrial-grade open-source real-time platform that can run virtualized automation and protection applications, and to derive a specification to allow similar implementations on other Linux distributions using similar components natively included therein.
Benefits to SEAPATH
This would open the project to many more distributions than Debian and Yocto, as many distributions support other components than those two. It would be unreasonable to expect every distribution to support exactly the components SEAPATH prescribes. In particular, commercial distributions with 24/7 service contracts for utilities (a model that is crucial for many utilities) cannot provide this service for all possible components. To allow alignment of those distributions to SEAPATH, a specification is indispensable.
Work to be done
Trivial.
Abstract
The mission of the project currently is to 'develop a "reference design" and "industrial grade" open source real-time platform'. In practice, this would make alignment of other Linux distributions to SEAPATH impossible unless they follow the reference design to the letter. To open SEAPATH to a wider audience, the project would have to provide a specification that details what a SEAPATH conformant implementation needs to look like. We thus propose to widen the mission of SEAPATH to include such a specification.
Current status
Subsection 1(a) of the project charter reads:
Detailed Description
Change subsection 1(a) of the project charter to:
Benefits to SEAPATH
This would open the project to many more distributions than Debian and Yocto, as many distributions support other components than those two. It would be unreasonable to expect every distribution to support exactly the components SEAPATH prescribes. In particular, commercial distributions with 24/7 service contracts for utilities (a model that is crucial for many utilities) cannot provide this service for all possible components. To allow alignment of those distributions to SEAPATH, a specification is indispensable.
Work to be done
Trivial.