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 Ambassadors team.
In the CommOps workshop @ Flock 2016, we received a lot of helpful and valuable feedback from members of the community, and the Ambassadors were one of the most discussed items at Flock. After #84, I would like to bring focus over to this ticket. For now, reviewing the video isn't a bad idea.
Discussed in the (informal) 2016-09-10 post-Flock hack session.
There's so added detailed added to the section for that date, pasted below for convenience:
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 close_status updated to: Moved
Metadata Update from @bee2502: - Issue close_status updated to: None (was: Moved)
Metadata Update from @jflory7: - Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Future releases)
Log in to comment on this ticket.