Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
M
manifesto
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • rostools
  • manifesto
  • Merge Requests
  • !7

Merged
Opened Aug 13, 2019 by Joel Ostblom@joelostblomMaintainer

Manifesto suggestions for discussion

  • Overview 15
  • Commits 6
  • Changes 4

Intro

  1. I think the introduction document looks good. I read through it on a high level and there are no topic gaps that stand out and interrupt the flow. I did not look much as language yet.
  2. We should add refs for the factual claims.

Recommendations

  1. Maybe having a clearer tone that the reason there is not more open science is not because people are doing the wrong thing using proprietary software, but instead emphasize how much better things could be if they use it.
  2. Should we make recommendation for how to collaborate with people not using these tools? A common situation for many peole might be that they are grad students and then need to be able to communicate with their prof. For exammple track changes vs git
  3. Git for writing is not perfect, should we talk about hard wrapping code? Is there any easy way to do this outside vim bindings?
  4. Cover installation of R/Python and how to set things up?
  5. Should we work through a single project in detail from creating dirs to publication? All the commands, edge cases, etc.
  6. What line width do you use for hard wrap, 80? I can set the same in vim so that I don't change entire paragraphs instead of just one word.
Edited Jan 14, 2020 by Luke Johnston
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: rostools/manifesto!7
Source branch: manifesto-suggestions

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.