Develop pseudo-code for basic FluDAG implementation about dagmc

[gonuke]

We need a plan for developer documentation:

• which parts are in Doxygen
• which parts are in Sphinx
• which parts are in GH issues

Will there be overlap (generally discouraged because of inevitable consistency problems)?

[gonuke]

Some things to track:

• user feature list vs. what is working and what is not
• decisions that will impact future development, e.g. conventions for naming of regions & materials
• build process/decisions

[julamot]

Tasks for public pages that are created via Sphinx:

• Add a FluDAG bullet under 'Single Physics Analysis Tools' on svalinn.github.com (github.com/svalinn/svalinn.github.com). Note: This page is not in the doc-src tree.
• Add sub-bullet linking to repository
• Add sub-bullet linking to userguide (fludag-intro.rst)
• Create fludag-intro.rst with workflow documentation and user feature status table
• Put the user feature status table into Sphinx, link to the FluDAG section created in the previous step,

[julamot]

For for the doxygen/Code Documentation portion

• Fill out Doxygen for the feature list wrapper functions with more detail.
• Add the fludag-calls.rst document containing a table of wrapper calls, descriptions and their status

[gonuke]

See https://github.com/svalinn/DAGMC/blob/fludagwork/FluDAG/README.rst#planning for some project management concepts

[makeclean]

Is this going to be done, it seems like it hasnt been touched in quite some time?

[gonuke]

Under its original title, thi is probably overcome by events and no longer necessary - it was intended as a mechanism to accomplish our goal for developing FluDAG. If we want to turn it into a documentation issue, then we can probably move it to existing issues on documentation or make a new issue.

[gonuke]

overcome by events