This ticket is a stub for working out the artwork, concept, and steps involved for awarding a Fedora badge for contributors who would like to officially join the Design team.
Like with some of these previous tickets I've been flipping through, I don't have a whole lot of info or brainstorming thought out right now. But I know the Design Team is top of things when it comes to Badges. I also know there's a lot of discussion going on about on-boarding "pathways" in Tahrir, to be used in Hubs.
Maybe @duffy, @riecatnor, @mleonova, or other Design Team members have some thoughts or ideas about their own on-boarding series and how we can more effectively bring new contributors into the Design Team.
Metadata Update from @bee2502: - Issue priority set to: critical (next week) (was: minor (3-4 weeks))
@jflory7 will discuss this further with the Design team so that we know what next steps to take about this or close it for now.
Metadata Update from @bee2502: - Issue assigned to bee2502
Metadata Update from @bee2502: - Assignee reset
Metadata Update from @bee2502: - Issue assigned to jflory7
Metadata Update from @jflory7: - Assignee reset
It was decided in CommOps meeting on 2017-09-13, that CommOps would work towards an integrated document to guide different teams on how-to create effective onboarding guidelines and provide them with examples.
More Info here - https://meetbot.fedoraproject.org/fedora-meeting/2017-09-13/commops.2017-09-13-17.05.log.html
Ticket for how-to document to guide different teams on creating and implementing effective onboarding guidelines is here - https://pagure.io/fedora-commops/issue/117
Accordingly, I am closing the onboarding tickets for individual teams.
Metadata Update from @bee2502: - Issue set to the milestone: None (was: Fedora 26)
Metadata Update from @bee2502: - Issue close_status updated to: Moved
Metadata Update from @bee2502: - Issue close_status updated to: None (was: Moved)
Login to comment on this ticket.