# Oct 27 2021 Meeting Notes

## Agenda
- Discussion and brainstorming on authorship guidelines
- providing/confirming affiliation prior to submission within given timeframe (~2 weeks)
- Endorsing final content of manuscript within given timeframe (~2 weeks)
- Providing written content/figures or substantial edits to manuscript.
- Authorship order? For middle authors that contributed equally, I am a fan of random number generators (Dylan).
- Also, this: CRediT – Contributor Roles Taxonomy (https://casrai.org/credit/) and Defining the Role of Authors and Contributors (http://www.icmje.org/recommendations/browse/roles-and-responsibilities/defining-the-role-of-authors-and-contributors.html) (Pedro)
- Figure ideas: https://docs.google.com/presentation/d/1SnAwK4XLlKf-XqGCqianW3-cGp3SlQYnCZ6ASJDKn_c/edit?usp=sharing
- Consider ways of converting table 1 to figure? (Ali Guncan)
- Example of (commercially used) table to compare product features: https://media.nngroup.com/media/editor/2017/02/24/smugmug-plans-detailed-3.png (Pedro)
- Lots of information being conveyed in Table 1 (or maybe 3 tables) Yes, no, qualifying statement. Table just for that.
- Can be hard to follow table w/ x's and checks, can be tough to get something out of a table like this. Maybe switch into multiple tables, related to subtopic. Something that could make it.
- Slides 7 and 9 much more clearly call out the user groups. Rather than 8 and 10 which
- Slide 9: presents all the ways of using github, even though we want to make it non-hierarchical. Sorting from individual to collab is useful. Could sort by difficulty, could sort by purpose. Maybe getting rid of arrows would help with hierarchy. Could color code boxes going down.
- Maybe change slide 9 to more like a scatter plot (difficulty X degree of collaboration)
- How did we come up with the difficulty scale? Collaborative aspect makes things harder
- Do we even need difficulty ranking? Becuase collaborative coding (for example) is just harder to begin with.
- GitHub has free and paid plans.
- Discussion of free vs. paid plans. When projects get highly collaborative may have to add / pay for accounts. At this point, little difference between paid and free.
- Eric - diff collaborator personas, who might be involved in projects that are hosted on github, which features of github might be most useful for them. Outlining what main host can do. Rstudio "Learner personas"
- 24: Here's how different collaborators/stakeholders could contribute to a repo.
- Funding
- Adding journal to consider: Data Science Journal
- Next steps
- Begin writing the manuscript
- Proposition
- Setup a collaborative system (make an effort to implement and use Github for the *entire* writing process)
- 1. [Manubot](https://manubot.github.io/rootstock/), [Hypothesis.is](https://web.hypothes.is/), and our own Slack or Gitter?
- 2. *?*
- Begin with the titles of the main topics, the first sentences of each paragraph of the introduction and the general objectives of the manuscript (*?*)
- Defining each headings/sections roughly and subheadings of the manuscript and choosing leads per each section/sections to communicate with other members.
- How about the title of MS? Thinking of the submission window?
- Maybe we can think of a clean document with the sections and pieces of text and use it to add in our text/outline for each section (google doc). Notes and comments can be added to the original document. So that we would have two files, one for ideas and new comments and one for the more finalized text.
- Outline
- Next meeting December 8th (review draft of outline)
- Then resume last Weds of the month meetings
- Jan 26th 2022 (review first draft)