search

SoftDev4Research / 4OSS-lesson

The overall aim of these 4OSS in the shape of training materials will contribute to make research software FAIR.
https://SoftDev4Research.github.io/4OSS-lesson
Other
23 stars 22 forks source link

Lesson 5 -- contributing #24

Closed fmichonneau closed 6 years ago

fmichonneau commented 6 years ago

@mkuzak please review (or assign someone to do it).

c-martinez commented 6 years ago

Discussion: Why allow others to contribute to your project?

Perhaps before "Why allow others to contribute to your project" I would add "How a to contribute" or rather "What is a contribution". I think it is good to clarify very early that a contribution is not necessarily a patch to your code which will suddenly fix all bugs, but that issues, suggestions and discussion are also valid and valuable forms of contribution.

Challenge: Part II

Is there any reason to select this list of packages? It seems very R-heavy. Also, wouldn't it make sense to have the contributing guidelines for this lesson listed in there?

"You can acknowledge all contributors and reward contributions as co-authors if the contribution is substantial" -- co-authors of the software? Of future papers? Maybe it is appealing to researchers to know they can gain something by being contributors.

Governance

Does it make sense to provide some guideline on what size of project may require what level of governance? I think @tobyhodges mentioned there was some research done on this direction (up to 150 people don't need any formal governance).

orchid00 commented 6 years ago

This is a first milestone for the Contributions episode Authors @fmichonneau @Pfern @malvikasharan @orchid00 :) and thanks to comments from @c-martinez @JenHarrow Please review @mkuzak @fpsom

fpsom commented 6 years ago

There are a few outstanding issues and typos in the PR. As soon as they are addressed, we can merge.