Next step after Start Onboarding button
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Multiple contributors in our FY25 user study have shared their confusion about the next step after clicking the Start onboarding button on contributors.gitlab.com.
- Users don't know what they are supposed to do after receiving a message that their access is pending
- The automatically generated onboarding issue takes a couple minutes and in the meantime users aren't even aware it is being created
- Users don't know what the community forks really are unless they come across the GitLab Community README.md but the button does not guide to this page
- Users have highlighted how helpful and informative the README.md is once they do discover it
- Users have highlighted the onboarding issue checklist once they find it
See user study diary snippets on this topic collected here: https://docs.google.com/document/d/1DBzjiTX7y3REAovYy9cg7XYrWYhAnxvK_aQ3gL09M0M/edit?usp=sharing
Possible options
- Require Login on the platform to determine status when user clicks Start onboarding
- Guide to the community forks README instead of group level page without README
- Pop up on the platform explaining what is happening (onboarding issue being generated and where to find it, access request to community forks started)
- Open the GitLab page in a separate tab from platform to not leave the platform page
- Skip sending to GitLab and keep the actual onboarding steps, checklist, progression all on the platform, but engagement with community maintainer in issue is helpful
Edited by 🤖 GitLab Bot 🤖