New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

wording suggestions for guidance #48

Open

NicciPotts opened this issue Jun 20, 2023 · 0 comments

Assignees

Milestone

Draft -> v1.0.0

Contributor

NicciPotts commented Jun 20, 2023 •

edited

Loading

Feedback from survey

The following sentence may be unnecessary duplication of the paragraph above it: "There are many sources which explain these benefits in detail [3]–[6], [8]–[11], and they all argue strongly as to why this guidance advocates for open source development. "

I particularly love the mention of skills and experience as a reason not to publish, there are less technical people around and I forget that sometimes.

The text in the box "Supports the Whole Community" could potentially be expanded to: "Other analysts and developers can benefit from work already developed by re-using code directly and by having many more examples available of code that handles public datasets."

NicciPotts assigned ethan-moss

r-leyshon added this to the Draft -> v1.0.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment