# Survey Question Ideas

Post here potential questions or things you want to learn from the users and developers of the nf-core community from future 'state of the nextflow/nf-core community' surveys

## Question/Topic Ideas to get info from

1. What are current barriers to using nf-core pipelines
- What is the most difficult to understand conceptually?
- What do you struggle to find documentation wise
2. What would motivate you as a periodic developer to come back more often or contribute more

## Or keep it simple?

1. Are you User/developer/both?
2. What Country are you based in?
3. Level of experience of nf-core as user or developer
- Not sure how to measure this
4. What things have you liked most about nf-core
5. What have been you biggest pain points with nf-core
6. Any other wishes/nice to haves?

---

# nf-core DX and UX Survey Brainstorm
Maybe just leave them open-ended to see what people say
## Onboarding
1. [Multiple choice] How did you discover nf-core?
1. Twitter
2. Google
3. BioStars
4. Word of mouth
5. Training event
6. University course
7. Mastodon
8. BlueSky
9. [... others - more suggestions?]
10. Don't remember
11. [Text] Other
2. [Text] What were your first impressions of nf-core?
3. [Scale] How clear was it about how to get started contributing code to nf-core?
4. [Text] What would be your top priority for improving contributor onboarding?
## DX
1. [Scale] How often do you contribute to nf-core?
2. [Text] What would help you in contributing more to nf-core?~What holds you back from contributing more to nf-core?~
3. [Yes / No] Does your workplace maintain a fork of an nf-core pipeline?
4. [Text, Conditional] If so why? Which pipelines?
5. How do you feel about the nf-core release cycle?
6. How do you feel about the nf-core template updates?
7. How easy is it to get involved in nf-core?
8. [Scale] How easy is it to keep up with the design decisions being made with nf-core?
9. [Yes / No] Are you satisfied how changes are communicated?
10. [Text] If not, how would you prefer changes to be announced/described
11. [Matrix Rating] How much do you think the following ideas could help?
1. TLDRs
2. More blog posts
3. ADRs
4. Some equivalent of Python PEPs?
5. [Text] Other
12. [Yes/No] Have you contributed to nf-core/modules?
13. [Text] How was the experience?
14. [Yes/No] Have you contributed to the development of an nf-core pipeline?
15. [Text] How was the experience?
16. [Scale] How do you feel about the community read/write access to repos?
1. Too strict <-> Too permissive
17. [Text] Is contributing too structured, or too loose and bugs get in too often.
18. [Text] If there is one thing that would improve your 'Quality of Life' in regards to nf-core pipeline development, what would it be
19. [Scale]how difficult do you find it to get reviews?
20. [Scale] fhow many people in the dev team?
## UX
1. General: How many nf-core pipelines do you/have you used?
2. General: How regularly do you use nf-core pipelines
3. General: What would help you use nf-core pipelines more often?
4. Documentation: How's the user documentation? Too much boilerplate and duplication?
5. Documentation: please provide a link to what you think is the most useful nf-core user documentation
6. Documentation: why do you find this the most useful nf-core user documentation
7. Documentation: what is the hardest bit of user documentation to find or understand?
8. Documentation: why do you find this the most hardest bit of nf-core user documentation to use or understand?
9. Documenation: What type of currently missing user documentation would give you the biggest 'Quality of Life' improvement?
10. Launch: How do you execute nf-core pipelines
1. CLI
2. nf-core launch
3. Seqera Platform
4. Other platform (specify)
12. Launch: If nf-core launch: What do you like about nf-core launch?
13. Launch: If nf-core launch: What would you improve nf-core launch?
14. Config: have you ever had to create a nf-core specific Nextflow config file?
15. Config: did you have any issues creating such a pipeline?
16. Download: Do you use `nf-core download`?

# What's complicated about the current release system?

Too many steps, makes it difficult for new people to understand the "why"

Let's say there's a bug

## Current release cycle

1. Write a PR for the bug fix
2. Get one person to review the PR(Preferably someone who understands the bug, the science, and nf-core)
3. PR gets merged(if the reviewer doesn't ask for tests, updating the changelog, or any other changes)
4. Create another PR
5. Bump the release version bumping
6. Update the changelog
7. Update the test snapshots
8. Get someone to review the pre-release PR
9. Open a PR for dev -> master
10. Find 2 people to review the release PR
11. Make any fixes that they want in the release PR(which normal contributors can't push to dev on they have to open another PR to dev)
12. Merge the PR into master
13. Create a release, writing up the release notes
13b. Think you're done
14. Create a version bump PR to dev

## Nextflow

1. Write a PR for the bug fix
2. Get one person to review the PR(Preferably someone who understands the bug, the science, and nf-core)
3. PR gets merged(if the reviewer doesn't ask for tests, updating the changelog, or any other changes)
4. Create another PR
5. Bump the release version bumping
6. Update the changelog
7. Update the test snapshots
8. Get someone to review the pre-release PR
9. Merge the PR
9. Create a release, writing up the release notes
10. Think you're done
11. Create a version bump PR