Contribution ideas

[shiltemann]

Joining one of our collaboration fests and looking for ideas for how to contribute? Below are some ideas to get you started:

Events - Smörgåsbord 2: Tapas Edition help wanted!

• Help us add captions (subtitles) to training videos! This makes this event accessible for everybody!
• Pick one of the videos in this folder
  • watch the video, fix up the autogenerated captions that are in the document
  • e.g. add punctuation, fix mistakes (e.g. technical terms often need fixing)
  • add your name to the top of the document so that we can give you credit on the event webpage!
• Add workflows & workflow tests to tutorials!

GTN Content

1. Look through the tutorial feedback we have received and make the suggested changes or address the comments (click on the tutorial names to see the detailed feedback and suggestions)

   • When they've been resolved, let us know and we can hide those feedback as "resolved"

2. Give some love to one of the tutorials needing it (see https://github.com/galaxyproject/training-material/issues/807)

3. Add or update speaker notes of slides to make them suitable for automatic slide-to-video creation. instructions here

4. Replace screenshots of tool forms with proper hands-on boxes (see https://github.com/galaxyproject/training-material/issues/675)

5. Have a look at any issues labelled "help-wanted", "CoFest", "newcomer-friendly", or "Hacktoberfest" or "paper-cut"

6. Tutorial testing - run through a tutorial of your choice and let us know if:

   • did you run into any issues?
   • spot any typos?
   • did you want more scientific background information anywhere?
   • did you have any other suggestions to improve the tutorial?

Reviewing

1. Help us review open pull requests!
   • Can be on any level, from finding typos to testing the full tutorial and providing your feedback.
   • You do not need to be an expert on the topic! It is also very valuable to have non-experts read or try the tutorial and let us know where things are unclear or more information is needed.
   • Some info on adding your review in the GitHub interface here

Infrastructure (ping @hexylena)

1. Add tool versions to hands-on boxes so that they can be linked directly when using GTN from within Galaxy, instructions here
2. Add workflow testing to tutorial workflows, instructions here

We will try to keep this issue up-to-date over time.

Please comment below if you would like to work on any of these issues, we are happy to help you get started! You can also reach us on our Gitter channel for help with this. Thanks for contributing!

[Chinonyemildred]

I noticed some things and I'll love to make contribution to the tutorial testing

[Ajadi-Abiola]

Hi, I noticed some things in the tutorials and I'll love to contribute to the galaxy 101 for everyone tutorial.

[TheKharleeci]

Hi @shiltemann, I would love to review open pull requests and also contribute to tutorial testing. Please let me know how I can begin. Thank you.

[bebatut]

For tutorial testing, you

• take any tutorial
• run through the tutorial
• open an issue and report
  • did you run into any issues?
  • spot any typos?
  • did you want more scientific background information anywhere?
  • did you have any other suggestions to improve the tutorial?
• if the tutorial do not have a workflow attached, you can add it also

[TheKharleeci]

Awesome. Thank you. I will start working on it

[rahmot]

Hi, @shiltemann! I would like to work on tutorial feedback and tutorial. They are somewhat related. For the tutorial feedback, do I need to fix it myself or I can just open an issue?

[bebatut]

For the tutorial feedback, do I need to fix it myself or I can just open an issue?

It may depend on the changes to do. I would recommend you to start by opening an issue with all comments / things to change and then if you can do them

[rahmot]

@bebatut okay, thanks!

[megaBabe]

I would love to review open pull requests and also contribute to tutorial testing. Please let me know how I can begin. Thank you. And also contribute to content checks for error

[bebatut]

Thanks @megaBabe.

For tutorial testing, you

• take any tutorial
• run through the tutorial
• open an issue and report
  • did you run into any issues?
  • spot any typos?
  • did you want more scientific background information anywhere?
  • did you have any other suggestions to improve the tutorial?
• if the tutorial do not have a workflow attached, you can add it also

[megaBabe]

Please add me as a contributor

[shiltemann]

@megaBabe you don't need to be added in order to make contributions, just go ahead and work on what you find most interesting, and when you make your first PR, you can also add yourself to the CONTRIBUTORS.yaml file :)

Please let us know if you have any questions or get stuck anywhere, thanks for contributing!