Consider a chapter on how "average" (typical) users can contribute

[MikeKSmith-Pfizer]

Following PhUSE EU Connect discussion about "Lack of feedback", can we include a chapter on how a typical user could contribute to Open Source projects?

#43

Could include:

• contributing to test case definitions (don't need to actually write test cases, but contributing scenarios for testing would be good)
• contributing to user documentation. "Average" users are more likely to have sensible contributions to make to improve documentation (maybe better than the original developer)
• contributing to vignettes. Not just how to use functions, but how to use combinations of these to achieve realistic workflows.
• contributing Issues. Not just reporting bugs but suggesting new features. Perhaps typical users don't think it's their place to comment on tool / package functionality (as the software is free).

[MikeKSmith-Pfizer]

May also want to discuss barriers to contribution:

• Am I allowed to contribute? (perhaps due to company policy, IP, etc.)
• Is it fair to point out problems with the software when it's provided free?
• I don't know how Git / Github works
• I'm overwhelmed with the process of contributing / technology aspects