Contributor_NonCodeNeeds

Non coding needs in the SasView Project

There are many tasks in the project that require no coding skills. These constitute at least 50% of the overall project effort and divert what precious coding resource we do have. The following list of tasks should provide an idea of the various needs that members of the community may feel they can contribute to. Most will probably require a bit of context/help in understanding _how _the tasks can be performed in a useful manner, but that should be relatively simple. Anyone using SasView and wishing/willing/able to give back to the community, please contact the leadership team at [email protected]

SPECIFIC

• Full user acceptance testing of SasView release candidates (Mac and PC - also Linux?)
• Checking the math on a Pull Request (PR)
• Functionality review of a PR (Mac and PC - also Linux?)
• Documentation review of a PR (did the functionality change; were the docs updated?)
• Updating the documentation
• Reviewing documentation changes (in a PR)
• Writing tutorials (also see TutorialsTNGForAuthors)
• Reviewing tutorials (in a PR)
• Recording video tutorials (see the SasView YouTube channel)
• Twitter posting
• Maintaining web pages (infrequent but requires knowledge of status of project) & web servers (applying security patches, etc)
• Responding to help requests (and posting to the developers list and/or creating issues as appropriate)

GENERAL

• Checking any and all documentation -> submitting corrections when appropriate
  • Obvious → submit correction
  • Possibly more complex → start discussion item.
• Checking math anywhere and everywhere
  • Obvious → submit correction
  • Obvious but need extra coding skills → submit ticket
  • Possibly more complex → start discussion item.
• Help cleaning/sorting issues: can they be closed (done? obsolete?) - should they be moved to a discussion, should they have different tags?