Document Applications in trac wiki

[skliper]

It would be helpful to construct a small Wiki page corresponding to each Application in cFE giving a quick overview of each.

I suggest including hotlinks on each such page back into the doc
subtree of the specific App for extended documentation -- as clones
will obtain the content of the project sources but do not clone
the Trac wiki.

[skliper]

Imported from trac issue 3. Created by glimes on 2014-12-22T11:19:51, last modified: 2019-03-05T15:20:25

[skliper]

Trac comment by jphickey on 2014-12-22 12:58:31:

Just a thought: Would this documentation be more accessible in the NSCKN wiki or the trac wiki? Wherever it lives, this could also serve as a catalog of available apps (i.e. poor man's app store)

[skliper]

Trac comment by glimes on 2015-06-11 12:05:48:

It just occurred to me that this ticket might be misread
as duplicating [cfs_apps:2], which talks about documenting
the library of CFS Applications.

This ticket is intended to be much more narrow, documenting
the very small and specific set of applications that are
considered to be within the Core Flight Executive and are
maintained within this repository.

The other thing that occurred to me -- and I need to poke
the other related tickets that this idea might apply to -- is
that a Card Catalog or Application Index or whatever it
turns into, kept in a Wiki separate from the source tree,
is quite likely to go stale. In any case, it is also going
to need to carry notations about "this is in the development
branch but not in master" and so on.

Perhaps such Catalogs should be instead maintained within the project
itself, so that acquiring a copy of the project, IN THEORY,
acquires a copy of the catalog that is up to date with respect
to that version of the project.

This would also make it more likely that the Babelfish version
of the catalog and the IPAS-LIB version of the catalog would
match each other.

Even if we get a formal fancy Application Store, having this
internal catalog is still nice for collectinos other than
the main "collection of cool CFS applications" -- it applies
equally to the OSAL OS list, OSAL BSP list, the PSP list, and
probably other collections of mostly independent but related
bits of code.

Something to think about.