Need to Pick an Application File Structure Convention - Githubissues

cubesatlab / cubedos

A flight software framework in SPARK/Ada

48 stars 5 forks source link

Need to Pick an Application File Structure Convention #51

Open Eric-Edlund opened 1 year ago

Eric-Edlund commented 1 year ago

NASA's cFS has a file structure convention for their modules and applications. Standardizing this has implications on the future usability of CubedOS as a platform and for our development. We need to decide on one and put it in the Manual portion of the documentation.

Sevan has pitched a structure in https://teams.microsoft.com/_#/apps/d7958adf-f419-46fa-941b-1b946497ef84/sections/MyNotebook

Some requirements for a structure:

Includes the MXDR files
Makes the API packages available to all modules
There is one name_resolver per application
Not confusing (we need people to want to use this, lets try to avoid stuff like environment variables if we can)
Has one message_manager and main per domain