From Fedora Project Wiki
Briangribble (talk | contribs) No edit summary |
(Removed redirect to SIGs/Join) Tag: Removed redirect |
||
| (18 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{admon/caution|Draft documents|Draft documents may be incomplete or contain errors. Click on REDIRECT to view the latest one.}} | |||
#REDIRECT [[SIGs/Join]] | |||
== Fedora Join Special Interest Group == | == Fedora Join Special Interest Group == | ||
The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors engage with the community. The idea here is to enable people looking to join the Fedora community to converse with existing members, make friends, find mentors, and get a feeling of what and how the community does in general, with a view to reduce the learning gradient that joining a new community entails - and make it more enjoyable! | The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors engage with the community. The idea here is to enable people looking to join the Fedora community to converse with existing members, make friends, find mentors, and get a feeling of what and how the community does in general, with a view to reduce the learning gradient that joining a new community entails - and make it more enjoyable! | ||
=== Mission === | ==== Mission ==== | ||
Different teams already have different, mostly well documented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet people who are unsure of how their skills fit into the community. We want to provide these people a channel where they can speak to existing members of the community, learn about what they do and use this information to find the right team to get started with. We help new members form relationships with members; we point them to the right resources - wiki or otherwise; and we expect that this should greatly improve the joining experience. | Different teams already have different, mostly well documented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet people who are unsure of how their skills fit into the community. We want to provide these people a channel where they can speak to existing members of the community, learn about what they do and use this information to find the right team to get started with. We help new members form relationships with members; we point them to the right resources - wiki or otherwise; and we expect that this should greatly improve the joining experience. | ||
| Line 9: | Line 13: | ||
==== Goals ==== | ==== Goals ==== | ||
# | # Set up a communication channel between the existing contributors and prospective contributors. Speaking to current team members is always encouraging. We could even set up a system to send "easyfix" tasks to this mailing list giving folks a chance to work on them and learn in the process. | ||
# | # Guide/aid prospective contributors to turn into solid contributors. Rather than just pointing them to join.fp.o, talk to them, see what issues they face, help them decide where they want to get started. | ||
# | # To form better mentor-mentee relationships. Here, I mean "mentor" in the real sense of the word. | ||
# | # Give prospective contributors a communication channel to converse amongst themselves. This is very important. Take the Google Summer of Code mailing list for instance. It is set up specifically so that the candidates can talk to each other. Since they're all in the same boat, they feel more comfortable discussing certain issues amongst themselves. They'll also be aware of what different people are up to which will give them a better idea of what they can do. It would be great if they could discuss and share the cool stuff they've begun to do. It would surely be encouraging. | ||
Basically, look for '''potential''', not '''polish'''. We can help them gain the polish that established contributors have. | Basically, look for '''potential''', not '''polish'''. We can help them gain the polish that established contributors have. | ||
| Line 19: | Line 23: | ||
* '''Mailing list:''' {{fplist|fedora-join}} | * '''Mailing list:''' {{fplist|fedora-join}} | ||
* '''IRC:''' #fedora-join freenode | * '''IRC:''' [irc://irc.freenode.net/fedora-join #fedora-join] on irc.freenode.net | ||
* '''Webchat:''' {{fpchat|#fedora-join}} | * '''Webchat:''' {{fpchat|#fedora-join}} | ||
=== | === Meetings === | ||
The Fedora Join team hosts bi-weekly meetings. The next scheduled meeting can be found [[Fedora_Join_SIG/Next_Meeting|here]]. All meetings use the [[Template:Fedora_Join_Meeting|Fedora Join meeting template]]. Everyone is welcome to attend. | |||
Meeting minutes are logged at [https://meetbot.fedoraproject.org/teams/fedora-join/ Meetbot] with links to past meeting minutes below. | |||
* [[Fedora_Join_SIG/Past_Meetings/2015|Meetings 2015]] | |||
* [[Fedora_Join_SIG/Past_Meetings/2016|Meetings 2016]] | |||
* [[Fedora_Join_SIG/Past_Meetings/2017|Meetings 2017]] | |||
=== Tasking === | |||
We use [https://pagure.io Pagure] to manage tasks we are working on and issues we need help with. Submit a [https://pagure.io/fedora-join/Fedora-Join/new_issue ticket] if you need help from Fedora Join or help us with existing tickets by visiting our [https://pagure.io/fedora-join/Fedora-Join repository]. | |||
== | == Ways to help == | ||
* | * Blogging about Fedora | ||
* Teach classes | * [[Classroom|Teach classes]] | ||
* | * Help people new to Fedora | ||
* Mentor | |||
* Help with [https://pagure.io/fedora-join/Fedora-Join/issues issues] | |||
* Share ideas to make this SIG, and Fedora, better | |||
== Members == | == Members == | ||
* [[User:amsharma|amsharma]] | * [[User:amsharma|amsharma]] | ||
* [[User:ankursinha|ankursinha]] | * [[User:ankursinha|ankursinha]] | ||
* [[User:briangribble|briangribble]] | |||
* [[User:immanetize|immanetize]] | * [[User:immanetize|immanetize]] | ||
* [[User:jflory7|jflory7]] | * [[User:jflory7|jflory7]] | ||
| Line 49: | Line 60: | ||
== User Contributions == | == User Contributions == | ||
Check out some of our [[Fedora_Join_SIG/User_Contributions|user contributions]]. Got something to share? Let us know. | |||
[[ | |||
[[Category:SIGs]] | [[Category:SIGs]] | ||
Latest revision as of 09:33, 18 November 2019
.png){kind=small}
Draft documents
Draft documents may be incomplete or contain errors. Click on REDIRECT to view the latest one.
Draft documents may be incomplete or contain errors. Click on REDIRECT to view the latest one.
- REDIRECT SIGs/Join
Fedora Join Special Interest Group
The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors engage with the community. The idea here is to enable people looking to join the Fedora community to converse with existing members, make friends, find mentors, and get a feeling of what and how the community does in general, with a view to reduce the learning gradient that joining a new community entails - and make it more enjoyable!
Mission
Different teams already have different, mostly well documented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet people who are unsure of how their skills fit into the community. We want to provide these people a channel where they can speak to existing members of the community, learn about what they do and use this information to find the right team to get started with. We help new members form relationships with members; we point them to the right resources - wiki or otherwise; and we expect that this should greatly improve the joining experience.
Goals
- Set up a communication channel between the existing contributors and prospective contributors. Speaking to current team members is always encouraging. We could even set up a system to send "easyfix" tasks to this mailing list giving folks a chance to work on them and learn in the process.
- Guide/aid prospective contributors to turn into solid contributors. Rather than just pointing them to join.fp.o, talk to them, see what issues they face, help them decide where they want to get started.
- To form better mentor-mentee relationships. Here, I mean "mentor" in the real sense of the word.
- Give prospective contributors a communication channel to converse amongst themselves. This is very important. Take the Google Summer of Code mailing list for instance. It is set up specifically so that the candidates can talk to each other. Since they're all in the same boat, they feel more comfortable discussing certain issues amongst themselves. They'll also be aware of what different people are up to which will give them a better idea of what they can do. It would be great if they could discuss and share the cool stuff they've begun to do. It would surely be encouraging.
Basically, look for potential, not polish. We can help them gain the polish that established contributors have.
Communication
- Mailing list: fedora-join
- IRC: #fedora-join on irc.freenode.net
- Webchat: #fedora-join[?]
Meetings
The Fedora Join team hosts bi-weekly meetings. The next scheduled meeting can be found here. All meetings use the Fedora Join meeting template. Everyone is welcome to attend.
Meeting minutes are logged at Meetbot with links to past meeting minutes below.
Tasking
We use Pagure to manage tasks we are working on and issues we need help with. Submit a ticket if you need help from Fedora Join or help us with existing tickets by visiting our repository.
Ways to help
- Blogging about Fedora
- Teach classes
- Help people new to Fedora
- Mentor
- Help with issues
- Share ideas to make this SIG, and Fedora, better
Members
User Contributions
Check out some of our user contributions. Got something to share? Let us know.