# Meeting notes 2/23/2022

### Agenda:
1. First draft updates/comments (all)
- how do we deal with big picture changes/redundancies?
- Probably will need 1-3 people to do full read through and identify those redundancies/paragraph merges etc.
- can we comment onto the FULL rendered HTML output?
- Volunteers for full read through??
3. How are we going to provide general edits/suggestions (Dylan)
- What if you notice a typo?
- Maybe better to catch these in PR reviews, but could also be something to fix later in a full read-through
- Can view source on github (with <> button), then click a line, and start a new discussion with the ... button. Might be useful for discussing across multiple .md files
5. Workflow for editing someone elses paragraph (Rob / All)
a. Person B makes edit's to person A's paragraph (on a branch)
b. Person B submits a PR mentioning changes that were made.
c. Person B, in the PR interface, indicates they want Person A to review changes
d. Person A reviews changes, approves, merges into main.
4. Creating figures in R (Eric)
- Eric is creating R folder in our repo.
- If you are making a figure in R, add you code to it.
- Hopefully Eric/Pedro can figure out the github actions to update manubot.
6. Revisiting timelines (pasted below)
7. Contacting attendees we haven't heard from
8. Next meeting TBD, focus on writing for now

## Timeline
- Paragraph/Topic first drafts by Feb 16(?)
- Expectation: gather citations, high-level overview of why this component is important
- Complete first drafts by 3/2
- Any paragraphs that don't have a first draft complete by 3/9
- Volunteers: Brandon, Vivienne
- Everyone does read through for general edits by 3/23
- Figures and tables ____
- A few authors do a final read through by ____
- Sign up for this: Emma, Eric, Brandon (if three is not a crowd), Matt
- Do we want to draft a letter to Nature EcoEvo editor?
- Rob and Matt

**For group writing up tips*
https://www.atlassian.com/git/tutorials
https://swcarpentry.github.io/git-novice/
https://git-scm.com/book/en/v2