From Fedora Project Wiki
No edit summary
(48 intermediate revisions by 25 users not shown)
Line 1: Line 1:
==Background==
{{admon/note|This document has moved.|Please go to https://docs.fedoraproject.org/en-US/fedora-join/index.html}}
We're looking to reduce the learning gradient that new folks need to hike up when they look to contribute to Fedora. Users looking to give back to the community is amazing. We need to go out and give them as much help as we can. The importance here is that most of them will be new to the work flows, SIGS, teams and processes that Fedora community uses. Quite a few of them will be new to Linux even. For these novices, learning all that is required to become contributors is a daunting task. However, what is important is that all of them have the *potential* to make awesome contributors!


== Fedora Join Special Interest Group ==


===Current workflow===
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 reducing the learning gradient that joining a new community entails - and make it more enjoyable!
At the moment, this is how folks go about it:
# Look at the join-fedora page
# Select what they want to do
# Join the various mailing lists
# Ask how they can help
# Start working, and learn while they work, get sponsored etc.


===Issues===
==== Mission ====
Even though this works, there are a few issues here that we'd like to address:


# Quite a few folks aren't sure what they want to do. The join fedora page is confusing for them at times. They don't know first hand what each role is about, so they aren't sure if they should join up SIG A or SIG B.
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 with 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.  
# The various mailing lists: devel, mktg, infra are work oriented. While we do guide newcomers that ask for help on the lists, these newcomers are usually scared to ask questions. They feel they'll make fools of themselves if they ask simple questions in front of established contributors.  


Basically, the working mailing lists aren't exactly the best environment for new comers. They are task oriented. They aren't dedicated to aiding new comers. We also don't want lots of introductions etc. on the work mailing lists either. We want them to be dedicated to *work*.
==== Goals ====


==IRC==
<nowiki>#fedora-join</nowiki> on Freenode
==Mailing list==
[https://admin.fedoraproject.org/mailman/listinfo/fedora-join https://admin.fedoraproject.org/mailman/listinfo/fedora-join]
==Goal==
# 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.
# 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.
# 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.
# Via these channels, form better mentor-mentee relationships. Here, I mean "mentor" in the real sense of the word.  
# 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.
# 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.


==Members==
== Communication ==
* [[User:Ankursinha|Ankur Sinha "FranciscoD"]]
 
* [[User:shaiton|Kévin Raymond "shaiton"]]
{{admon/tip|Office hours|You can find us in {{fpchat|#fedora-join}} (and on the [https://t.me/joinfedora Telegram channel]) at [[SIGs/Join/OfficeHours|these times]].}}
* [[User:bochecha|Mathieu Bridon "bochecha"]]
 
* [[User:niteshnarayan|Nitesh Narayan Lal "niteshnarayanlal"]]
* '''Mailing list:''' {{fplist|fedora-join}}
* Add your name here!
* '''IRC:''' {{fpchat|#fedora-join}}  on irc.freenode.net
* '''Telegram''': https://t.me/joinfedora (this is bridged to the IRC channel)
* '''Matrix''': https://riot.im/app/#/room/%23freenode_%23fedora-join:matrix.org
* '''Discord''': https://discordapp.com/invite/fedora
 
 
== Membership ==
 
In general, members of the SIG should be contributors experienced enough to be able to help newbies. So, as a guideline (not a strict rule), we suggest that:
* a SIG member should be part of two other groups (CLA+2)
* active for at least the previous release cycle
* must be subscribed to the mailing list
 
While we do not usually need to clean up the membership group, we will periodically do so to remove inactive members. This will be done by gathering data from datagrepper on activity.
 
Please file a ticket on our [https://pagure.io/fedora-join/Fedora-Join/ Pagure instance] to apply for membership. The current membership can be viewed in FAS [https://admin.fedoraproject.org/accounts/group/view/fedora-join here].
 
=== Temporary membership for new community members ===
 
We also provide temporary membership to newbies just getting started in the Fedora community. This is so that they have access to Fedora infrastructure that requires a CLA+1 (membership of at least one SIG), such as the wiki. This is part of the [https://communityblog.fedoraproject.org/fedora-join-is-trying-a-new-people-focused-workflow-for-newcomers/ new workflow for newcomers]. Please get in touch with us, and we can discuss about that.
 
=== Tasking ===
 
We use [https://pagure.io Pagure] to manage tasks we are working on and the 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].
 
=== Meetings ===
 
The Fedora Join team hosts meetings, sometimes. 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]]
* [[SIGs/Join/Past_Meetings/2018|Meetings 2018]]
 
== Ways to help ==
 
* Blogging about Fedora
* [[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
 
== User Contributions ==
 
Check out some of our [[Fedora_Join_SIG/User_Contributions|user contributions]]. Got something to share? Let us know.


==TO DO List==
# File ticket at infra to set up fedora-join mailing list. (Is it possible to set up one where they won't need to register) '''Done! [https://fedorahosted.org/fedora-infrastructure/ticket/3344 https://fedorahosted.org/fedora-infrastructure/ticket/3344]'''
# Set up IRC channel #fedora-join: '''Done! Go hang out there now!'''
# File ticket with websites SIG to make tiny changes to join.fp.o to list Fedora-Join IRC and mailing list channels. '''Done! [https://fedorahosted.org/fedora-websites/ticket/116 https://fedorahosted.org/fedora-websites/ticket/116]'''
# Ask infra if we can set up a system to send "easyfix" notifications to the channel/mailing list.
# Get started!


==IRC Meetings==
[[Category:SIGs]]
Not yet. We need to decide if we really need a regular meeting.
[[Category:Fedora special-interest groups]]

Revision as of 13:46, 20 August 2021

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 reducing 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 with 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

  1. 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.
  2. 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.
  3. To form better mentor-mentee relationships. Here, I mean "mentor" in the real sense of the word.
  4. 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

Idea.png
Office hours
You can find us in #fedora-join[?] (and on the Telegram channel) at these times.


Membership

In general, members of the SIG should be contributors experienced enough to be able to help newbies. So, as a guideline (not a strict rule), we suggest that:

  • a SIG member should be part of two other groups (CLA+2)
  • active for at least the previous release cycle
  • must be subscribed to the mailing list

While we do not usually need to clean up the membership group, we will periodically do so to remove inactive members. This will be done by gathering data from datagrepper on activity.

Please file a ticket on our Pagure instance to apply for membership. The current membership can be viewed in FAS here.

Temporary membership for new community members

We also provide temporary membership to newbies just getting started in the Fedora community. This is so that they have access to Fedora infrastructure that requires a CLA+1 (membership of at least one SIG), such as the wiki. This is part of the new workflow for newcomers. Please get in touch with us, and we can discuss about that.

Tasking

We use Pagure to manage tasks we are working on and the 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.

Meetings

The Fedora Join team hosts meetings, sometimes. 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.

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

User Contributions

Check out some of our user contributions. Got something to share? Let us know.