Changes between Version 1 and Version 2 of GCI/Documentation/ClassicAPIRequirements
- Timestamp:
- 09/12/18 19:29:15 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GCI/Documentation/ClassicAPIRequirements
v1 v2 2 2 3 3 [[TOC(GCI/Documentation/ClassicAPIRequirements , depth=2)]] 4 5 Tasks related to creating/editing documents and helping others learn more6 7 We expect approximately 30 tasks in this category for the first round. There can be followup tasks sets to further refine them.8 4 9 5 This task is part of the RTEMS project's effort to reduce certification costs by easing requirements traceability. As we want our developers to spend more time on adding technical value (instead of updating duplicate documentation), we will want to merge as much of this documentation as possible. … … 11 7 We have several existing classic API documents and converting each into chapter into reStructuredText will provide a baseline which is easier for further automated processing and updates. The focus will be on the final versions of the RTEID and ORKID specifications. 12 8 13 == Classic API Requirements Document (Phase I Deliverables) == 9 We expect approximately 30 tasks in this category for the first round. There can be followup tasks sets to further refine them. 10 11 12 == Directions for Students == 13 14 === Classic API Requirements Document (Phase I Deliverables) === 14 15 15 16 The deliverable is a .rst 17 16 18 === Classic API Requirements Document (Phase I Method) === 17 19 … … 29 31 1. use ```` on items that are supposed to be code 30 32 1. Upload to melange, ask the mentor to review the .rst 33 31 34 === Classic API Requirements Document (Phase I Example) === 32 35 … … 98 101 TBD: identify unified textual format 99 102 100 == = Note to Mentors ===103 == Directions for Mentors == 101 104 102 105 1. Verify the .rst renders in the [http://rst.ninjs.org/ RST editor]