- Timestamp:
-
10/20/18 17:46:04 (6 years ago)
- Author:
-
Gedare Bloom
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v22
|
v23
|
|
21 | 21 | * Write a new example-v2 program derived from other examples/tests to demonstrate some aspect of RTEMS. |
22 | 22 | |
23 | | * (Repeatable) Fix a bug based on a ticket and Coverity Scan report. ([[GCI/Coding/CoverityIssues]]) |
| 23 | * ~~(Repeatable) Fix a bug based on a ticket and Coverity Scan report. ([[GCI/Coding/CoverityIssues]])~~ |
24 | 24 | |
25 | | * (13) Address the remaining BSPs which do not have per-function section compilation and linking. See ticket #2577 and this query for the remaining tickets (https://devel.rtems.org/query?status=!closed&keywords=~KEEP). The generation script needs to be updated to match the list of BSPs and tickets once reviewed. |
| 25 | * ~~(13) Address the remaining BSPs which do not have per-function section compilation and linking. See ticket #2577 and this query for the remaining tickets (https://devel.rtems.org/query?status=!closed&keywords=~KEEP). The generation script needs to be updated to match the list of BSPs and tickets once reviewed.~~ |
26 | 26 | |
27 | 27 | == !Documentation/Training == |
… |
… |
|
55 | 55 | * (Repeatable) We have trouble knowing when a specific NASA or ESA mission using RTEMS launches or has interesting news. How could we know that? How could we get this information to the RTEMS Community? A few example missions are NASA Parker Solar Probe, NASA ICESAT-2, ESA ExoMars, and ESA BepiColumbo. |
56 | 56 | |
57 | | * (~25 unique) Convert project pages ([[Developer/OpenProjects]]) to tickets or make obsolete. |
| 57 | * ~~(~25 unique) Convert project pages ([[Developer/OpenProjects]]) to tickets or make obsolete.~~ |
58 | 58 | |
59 | 59 | * (~3-10 unique) Interview a previous RTEMS GSoC Student. Need to confirm availability of the GSoC alum. |
… |
… |
|
61 | 61 | * (Repeatable) Write a tutorial for how to contribute to RTEMS. |
62 | 62 | |
63 | | * (~30 unique) Updates Citations for recent years (2015, 2016, 2017). New component of this task is to add bibtex entries/links. Might be able to do bibtex links on prior years ([[GCI/Outreach/Citations]]). |
| 63 | * ~~(~30 unique) Updates Citations for recent years (2015, 2016, 2017). New component of this task is to add bibtex entries/links. Might be able to do bibtex links on prior years ([[GCI/Outreach/Citations]]).~~ |
64 | 64 | |
65 | 65 | == Quality Assurance == |
… |
… |
|
67 | 67 | * (~35 unique) Fix 3 warnings in RTEMS. Generate 3 separate patches. |
68 | 68 | |
69 | | * (~125 unique) Investigate a Coverity Scan CID and file or update a ticket accordingly. |
| 69 | * ~~(~125 unique) Investigate a Coverity Scan CID and file or update a ticket accordingly.~~ |
70 | 70 | |
71 | 71 | * (~34 unique) Investigate an open ticket on a released version of RTEMS. |
… |
… |
|
81 | 81 | == Design == |
82 | 82 | |
83 | | * (multiple times) Design a new organization logo. We could use a nice square logo. |
| 83 | * ~~(multiple times) Design a new organization logo. We could use a nice square logo.~~ |
84 | 84 | |
85 | 85 | * Create a new set of templates for web pages to upgrade www.rtems.org. We would like to migrate to an easier to maintain platform. It might also be desirable to use a static site generator to create the pages. |