Latex reports folder

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
latex
Domain
documentation

Research direction

Start by reviewing the latex_reports folder and the mixer change documentation, especially how the mixer report is referenced. Clarify whether the reports should be published as PDFs or remain as LaTeX sources, then define the destination and visibility. Done means the reports have an agreed presentation and the documentation reflects it.

Written by the indexing model from the issue text.

Description

There is a folder named "latex_reports" that has some useful information.

Should we generate the pdf version of the latex reports and put them somewhere, or just leave them as latex reports? Some of them contain useful information (somewhat outdated), and I reference the mixer report in the mixer change documentation.

I don't think they are super useful just staying there since they have low visibility. We should change how we do it if we want the reports to be useful.

@iandareid @bsutherland333 @gabesnow99

Dominant language
TeX
Stars
1
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rosflight/rosflight_docs

All issues in rosflight/rosflight_docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.