RTEMS Software Engineering Handbook

[Shashvat Jain]

Scott has done a awesome job , would love to do the task  : )



On Thu, Nov 29, 2018 at 6:22 AM Joel Sherrill <joel at rtems.org> wrote:

> Hi
>
> Scott Zemerick of NASA IV&V did a review of NASA's quality standard and
> DO-178B and tried to find a way for open source projects to provide
> documents meeting the spirit and intent of those standards in a way that is
> palatable and not soul crushing for an open source project. He presented
> about this at the Flight Software Workshop last year. The title was
> "Open-Source RTOS Space Qualification: an RTEMS Case Study"
>
> Presentation:
> http://flightsoftware.jhuapl.edu/files/2017/Day-3/06-Zemerick-RTOS-Qualification.pptx
> Video of presentation: https://youtu.be/UYJqABg2Mzk
>
> Scott suggested an outline which takes existing content and puts it into a
> structure that an IV&V person would recognize. It also moves content from
> the Wiki into Rest which is much better for long-term controlled
> maintenance and organization. Plus prettier. Scott's outline and info is at
> https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/.
>
> For example, the Coding Style, Licensing Requirements, git instructions,
> project policies, etc. should be in here. Other topics are up for
> discussion.
>
> I took his outline with URLs and converted it to Rest. I left TBDs for the
> wiki pages to convert and insert. I also left TBDs for things to write.  I
> am going to write Google Code-In tasks for the conversion.  The current
> Rest code is in my rtems-docs git repo git://
> git.rtems.org/joel/rtems-docs.git on the sw_eng_hb branch. The current
> formatted version (as is) is at
> https://ftp.rtems.org/pub/rtems/people/joel/docs-eng/
>
> This is a solid starting point to having some of the documentation
> required by high integrity processes. We can grow it.
>
> Obviously this is a starting point and I am hoping that in the remaining
> two weeks of GCI we can get the wiki pages converted. At some point in the
> near future, I hope to submit it for inclusion in the main rtems
> documentation set.
>
> Please pitch in and let's make this happen. Improving our processes and
> supporting documentation is important.
>
> Thanks
>
> --joel
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181129/bc3ac78b/attachment-0002.html>