Community CCB Agenda: July 01 2020

Completed Integration Candidate: 2020-06-17

1. cFE PR #756
2. osal PR #521
3. cFS-GroundSystem PR #107

In-Progress Integration Candidte: 2020-06-24

Combines 7 PRs!

1. https://github.com/nasa/cFS/pull/108
2. https://github.com/nasa/cFE/pull/765
3. https://github.com/nasa/osal/pull/529
4. https://github.com/nasa/PSP/pull/176
5. https://github.com/nasa/elf2cfetbl/pull/47
6. https://github.com/nasa/cFS-GroundSystem/pull/109

Items to Review

@jphickey

PR #528 - Fix #525, ensure POSIX stack size meets requirements

Fixes bug found after IC 2020-06-17. APPROVED

PR #527 Fix #526, scrub OSAL stubs

APPROVED

PR #763 Fix #762, scrub of all CFE UT stub functions

APPROVED

@lbleir-GSFC

PR #108 Enhancement #103, Custom header mechanism

Replace "enhancement" with a valid linking word: Linking a pull request to an issue Are there people using the GroundSystem in other platforms? Do we really need ZMQ? We might want to avoid forcing a user to install more packages. Can we use memorymap for inter-process communication? APPROVED

@CDKnightNASA

PR #764 fix #759 - removes GetLastSenderId()

Remove and replace with a well thought-out API Need to address the true requirements Need to have a design discussion Don't touch the ticket and open a new one for documenting the problem with GetLastSenderId

Fast Track

https://github.com/nasa/to_lab/pull/48

Do we want to use typedefs for all of our types? APPROVED

Discussion topics

cFS 6.7 Aquila release.

The constellation names will be used going forward to indicate compatible bundle elements.

Git Tags

Releases, prereleases, and release candidates.

Version Numbering and Codename

Why?

• We should provide “extreme clarity” to everyone using cFS
• Multiple questions about compatibility
• SemVer helps to accurately communicate API Changes apps use BOTH cFE and osal APIs
• Accurately answers the question "which version are you using"
• Build-based "version" reporting helps supporting bugs and troubleshooting during development.
• Use tags so testers don’t have to worry about a “moving’ target

Constellation Names and Bundle

cFS Bundle

We are exploring CalVer to separate the version number for cFE from cFS. The individual repositories will maintain their versions. Every submodule will have a constellation prefix before their version number.

Individual repositories

• Use constellation name plus build number for development versions and keep SemVer for tags and releases.
• STOP increaseing the PATCH number for development updates.
• Be explicit in version.h showing both the build string and version number INDICATE that it only refers to the last release.

Development process

As stated last week, we will stop increasing the PATCH number each week and instead rely on a new "build number" that will be added to each repository's version.h. This number will be reported in the executable as AppName Development Build CONSTELLATION-NUMBER.

We're still working out the details but the current idea is that this number will be assigned during the merge process.

6.8 Process Update:

• Name tags as 6.8.FIX-rcNUMBER (relase candidate)
• Use the prerelease GitHub marker
• All 6.8 developments get added onto the 6.8.x branch as long as they pass the bundle CI
• Create 6.8.x branch on 7/7/2020 (assuming clean CI) and tag with 6.8.0-rc1, use github’s prerelase feature.

Renaming master branches to main

GitHub recently shone a spotlight on this though it has been discussed for a while. This shows solidarity with our Black, Indigenous, and People of Color (BIOPOC) developers, users, and community members. This will not solve racism. It is however, important to consider the unconscious and conscious effects that our technological nomenclature can have. I hope this change will drive conversation and I encourage everyone to reach out to me (@astrogeco), your management team, or your diversity and inclusion contacts to learn more about the different ways we can make tech more approachable for everyone. This will make some of us uncomfortable and that's ok.

Resources

1. dev.to - Replacing master with main in Github
2. Internet Engineering Task Force (ietf.org) - Terminology, Power and Oppressive Language
3. ZDNet - GitHub to Replace Master with Alternative Term to Avoid Slavery References

Invite list

GSFC

[P] = Present today

• Jacob Hageman (cFS Framework Lead)
• Jonathan Wilmot (cFS Program Manager)
• Alan Cudmore (cFS Architect)
• Gerardo Cruz-Ortiz (cFS Management)
• Dan Knutsen (cFS Developer)
• Jay Czarnecki (Software Process Imp
• Beth Timmons (GSFC Apps)
• Dwaine Molock (Project Developer)
• Anhelina Yurkova (cFS Test Automation)
• Leor Bleier (cFS Developer)
• Olanrewaju Amoo
• Jandlyn Bentley
• Yasir Khan
• Eric Pollack
• Jandlyn Bentley

JSC

• Steve Duran (PSP, OSAL Developer)
• Ron Maglothin (Lunar CATALYST Developer)
• Allen Brown (AES Developer)
• Thomas Brain (AES Integration)
• Tam Ngo AES Lead
• Carrejo, Daniel Systems
• Schlesinger, Adam Avionics and Software
• Thad Flemming

ARC

• Chris Knight (SBN Developer & Research)
• Joseph (Pat) Castle
• Michael Scott
• Craig Pires

LaRC

• Chris Thames (Lead/FSW Management)
• Noah Ryan (Software Developer)

MSFC

• Deanna Whitehead
• Stefanie Justice
• Lisa Vanderaar (Software lead)

GRC

• Joe Hickey (cFS Developer)

IV&V

• Matt Grubb (SmallSat baseline, build testing)

JHU/APL

• Chris Monaco

Guests

• Dave McComas (GSFC)