Met with Jonathan and Eric. Notes are recorded on google doc, the equivalent of what I have on this google doc will eventually be recorded onto a GitHub repo that outlines how a developer is to go about documenting their code.
https://docs.google.com/document/d/1DwsnjtWn6TIG7WaZXrC6qctSjKEumbZovyyB0zVdfTQ/edit
An important fact I learned is that as long as whatever tool we use to do our source code documentation produces static HTML, Jonathan can take care of the rest via Travis. My real only concern going into this was requiring a C++ developer need python to do whatever uploading of HTML generation but this will not be the case.
The next step in this effort is to create the template, Eric agreed to take on the template for Python. I will create the template for Java and C++, getting ts_sal done and a how to guide going over building sal I think will be a good place to start with this.
Met with Jonathan and Eric. Notes are recorded on google doc, the equivalent of what I have on this google doc will eventually be recorded onto a GitHub repo that outlines how a developer is to go about documenting their code.
https://docs.google.com/document/d/1DwsnjtWn6TIG7WaZXrC6qctSjKEumbZovyyB0zVdfTQ/edit
An important fact I learned is that as long as whatever tool we use to do our source code documentation produces static HTML, Jonathan can take care of the rest via Travis. My real only concern going into this was requiring a C++ developer need python to do whatever uploading of HTML generation but this will not be the case.
The next step in this effort is to create the template, Eric agreed to take on the template for Python. I will create the template for Java and C++, getting ts_sal done and a how to guide going over building sal I think will be a good place to start with this.