#287 final update landing page
Merged 7 months ago by sumantrom. Opened 7 months ago by sumantrom.
Unknown source main  into  main

final update landing page
sumantrom • 7 months ago  
file modified
+1
@@ -17,4 +17,5 @@

    - modules/teams/nav.adoc

    - modules/outreach-badges/nav.adoc

    - modules/design-assets/nav.adoc

+   - modules/misc-docs/nav.adoc

    

@@ -1,4 +0,0 @@

- * How to contribute

- ** xref:contribute/join.adoc[Join CommOps]

- ** xref:contribute/successful-contributor.adoc[How to be a successful contributor]

- * xref:community-blog.adoc[Community Blog]

empty or binary file added
empty or binary file added
The added file is too large to be shown here, see it at: docs/modules/teams/assets/images/infographic-2020.svg
file modified
+11 -4
@@ -1,4 +1,4 @@

- * *Teams*

+ * Teams

  ** Ambassador

  *** xref:ambassadors.adoc[Team Overview]

  *** xref:ambassador-role.adoc[Roles]
@@ -11,16 +11,20 @@

  *** xref:ambassador-mentor.adoc[Ambassador Mentor]

  **** xref:ambassador-mentor-role.adoc[Roles]

  ** Advocate

- *** xref:advocate-team-overview.adoc[Team Overview]

+ *** https://docs.fedoraproject.org/en-US/mindshare-committee/advocate/[Team Overview]

  *** xref:advocate-role.adoc[Roles]

  *** xref:advocate-logo.adoc[Logos]

  *** xref:advocate-badges.adoc[Badges]

  ** CommOps

- *** https://docs.fedoraproject.org/en-US/commops/index1.adoc[Team Overview]

+ *** xref:commops.adoc[Team Overview]

  *** xref:commops-role.adoc[Member Roles]

  *** xref:mindshare-reps.adoc[Rep Roles]

  *** xref:commlogo.adoc[Logos]

  *** xref:commbadges.adoc[Badges]

+ *** xref:community-blog.adoc[Community Blog]

+ *** How to contribute

+ **** xref:contribute/join.adoc[Join CommOps]

+ **** xref:contribute/successful-contributor.adoc[How to be a successful contributor]

  ** Join

  *** https://docs.fedoraproject.org/en-US/fedora-join/[Team Overview]

  *** https://docs.fedoraproject.org/en-US/fedora-join/welcome/welcome/[Role]
@@ -28,6 +32,9 @@

  *** xref:join-badges.adoc[Badges]

  ** Marketing

  *** xref:marketing.adoc[Team Overview]

- *** xref:marketing-role.adoc[Roles]

  *** xref:marketing-logo.adoc[Logos]

  *** xref:marketing-badges.adoc[Badges]

+ ** Misc Documentation

+ *** xref:irc-group-contact.adoc[IRC/Libera Group Contacts]

+ 

+ 

@@ -0,0 +1,91 @@

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Fedora Appreciation Week

+ 

+ Fedora Appreciation Week is an annual event organized by the Fedora xref:index.adoc[Community Operations] (CommOps) team.

+ Fedora Appreciation Week, abbreviated as FAW, is a week-long event to celebrate efforts of Fedora Project contributors and to say "thank you" to each other.

+ FAW is normally held on the week of November 6th to coincide with the https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html[anniversary] of the Fedora Project.

+ 

+ 

+ == What is it?

+ 

+ The https://wiki.ubuntu.com/UCADay[Ubuntu Community Appreciation Day] inspired CommOps to organize a similar event of appreciation for contributors who make the Fedora community what it is.

+ This includes all types of contributors: development, design, infrastructure, marketing, engineering, and more.

+ During the week, anyone is encouraged to select an individual or a group of contributors to thank for their efforts in Fedora.

+ Appreciation can be given as an IRC karma cookie, a short note of thanks on a mailing list, or a longer form of appreciation (e.g. a https://happinesspackets.fedorainfracloud.org/[Fedora Happiness Packet]),

+ 

+ 

+ == Why do it?

+ 

+ Most Fedora contributors do not get to work together in the same building or office.

+ Our daily interactions are usually in text form (e.g. IRC, emails, wikis, etc.).

+ Even though these work well and we accomplish our goals, we lose touch with the human side of contributing.

+ Fedora contributors aren’t robots, but real people!

+ Fedora Appreciation Week is a chance to remember the Fedora community is a community of people, and to thank our colleagues and friends who might be halfway across the room or halfway across the planet.

+ 

+ 

+ == How to participate

+ 

+ Different ways to participate in Fedora Appreciation Week are explained below.

+ Consider using one or many of the methods below to participate.

+ 

+ === Write a Contributor Story

+ 

+ https://pagure.io/fedora-commops/contributor-stories[Contributor Stories] are just that: the record of our best moments with our Fedora friends.

+ The story can be about our work in Fedora or something personal or unique which you would like to share with the community.

+ Selected stories will be shared on the Community Blog every day during Fedora Appreciation Week.

+ 

+ See some https://pagure.io/fedora-commops/contributor-stories/issues?status=all[examples] and consider https://pagure.io/fedora-commops/contributor-stories/new_issue[writing one of your own].

+ 

+ === Submit and vote on your favorite community pictures

+ 

+ More coming soon (see https://pagure.io/fedora-commops/issue/110#comment-531973[discussion]).

+ 

+ === Send a Fedora Happiness Packet

+ 

+ Happiness Packets are public or private notes of thanks you can send as emails to other contributors.

+ The Fedora Happiness Packets (*FHP*) project launched as part of {COMMBLOG}/happiness-packets-fedora-gsoc-2018/[Fedora Summer Coding 2018].

+ It is a fork of https://www.happinesspackets.io/[happinesspackets.io].

+ FHP supports FAS account login and account search.

+ You can earn a Fedora Badge by sending a message of gratitude or thanks to another contributor.

+ 

+ https://happinesspackets.fedorainfracloud.org/[**Send one now!**]

+ 

+ === Write your appreciation ===

+ 

+ You can also consider other ways of sharing and writing your appreciation for someone else and what they bring to our community.

+ If you are not sure of a specific person, you can also tweet general appreciation of Fedora, as operating city or as community.

+ Consider these ideas:

+ 

+ * Write a blog post

+ * Tweet a "thank you" that mentions https://twitter.com/fedora[@fedora]

+ * Tweet a hat tip / thanks to another Fedora contributor with hashtag *#_WeAreFedora_*

+ 

+ 

+ == Press

+ 

+ This section is a running list of press coverage of Fedora Appreciation Week:

+ 

+ === 2018

+ 

+ * *2018-05-01*: {COMMBLOG}/contributor-stories/[Introducing Contributor Stories] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-08-09*: https://www.youtube.com/watch?v=wV8j2xt8pmw[Flock 2018 - Thank the Fedora Community! Launching Fedora Appreciation Week] - https://youtube.com[_youtube.com_]

+ * *2018-09-18*: {COMMBLOG}/fedora-appreciation-week-2018/[Say thank you this November during Fedora Appreciation Week 2018] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-10-29*: https://fedoramagazine.org/say-thanks-appreciation-week-2018/[Say thanks during Fedora Appreciation Week (Nov. 5-11)] - https://fedoramagazine.org[_fedoramagazine.org_]

+ * *2018-10-29*: https://www.linuxjournal.com/content/fedora-appreciation-week-qt-announces-deprecation-qbs-d-language-front-end-merged-gcc[Fedora Appreciation Week, Qt Announces the Deprecation of Qbs…] - https://www.linuxjournal.com[_linuxjournal.com_]

+ * *2018-11-09*: https://fedoramagazine.org/appreciate-fedora-2018/[How Do You Appreciate Fedora?] - https://fedoramagazine.org[_fedoramagazine.org_]

+ 

+ ==== Appreciation Week highlights

+ 

+ * *2018-11-05*: {COMMBLOG}/faw-2018-day-1-community-makes-the-difference/[FAW 2018 Day 1: “Community makes the difference”] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-11-06*: {COMMBLOG}/faw-2018-day-2-change-the-world-through-open-source/[FAW 2018 Day 2: “Change the world through Open Source. He said.”] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-11-07*: {COMMBLOG}/faw-2018-day-3-becoming-part-of-fedora-family-because-of-her/[FAW 2018 Day 3: “Becoming part of Fedora family because of her!”] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-11-08*: {COMMBLOG}/faw-2018-day-4-you-know-you-can-do-it/[FAW 2018 Day 4: “You know you can do it”] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ * *2018-11-09*: {COMMBLOG}/faw-2018-day-5-encouraging-crazy-ideas/[FAW 2018 Day 5: “Encouraging crazy ideas”] - {COMMBLOG}[_communityblog.fedoraproject.org_]

+ 

+ ==== Community appreciation

+ 

+ * *2018-11-06*: https://blog.justinwflory.com/2018/11/fedora-appreciation-week-tribute-to-a-legacy/[Fedora Appreciation Week: Tribute to a legacy] - https://blog.justinwflory.com/[_blog.justinwflory.com_]

+ * *2018-11-06*: https://blog.hildenco.com/2018/11/thank-you-fedora.html[Thank You, Fedora] - https://blog.hildenco.com/[_blog.hildenco.com_]

+ * *2018-11-10*: https://forums.fedoraforum.org/showthread.php?319858-Fedora-appreciation-week[Fedora appreciation week] - https://forums.fedoraforum.org/[_forums.fedoraforum.org_]

+ * *2018-11-10*: https://lushka.al/thank-you-fedora/[Thank you, Fedora] - https://lushka.al/[_lushka.al_]

@@ -0,0 +1,112 @@

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Community Blog

+ 

+ The {COMMBLOG}[Fedora Community Blog] (CommBlog) is a WordPress-based site that delivers news, updates, and calls for help from contributors across Fedora.

+ 

+ image::https://fedoraproject.org/w/uploads/0/09/Community_Blog_screenshot.png[Community Blog screenshot,90%,90%]

+ 

+ 

+ [[content]]

+ == Content

+ 

+ The Community Blog focuses on updates and information about the Fedora Project community.

+ Topics vary, but mostly include…

+ 

+ * News from specific sub-projects

+ * Updates on new features or changes in Fedora

+ * Calls for help from other contributors

+ * Official {FWIKI}/Elections[Fedora Elections] coverage

+ * Anything related to Fedora _contributor_ community

+ 

+ 

+ [[magazine-vs-community-blog]]

+ == Fedora Magazine vs. Community Blog

+ 

+ What is the difference between the https://fedoramagazine.org[Fedora Magazine] and the Community Blog?

+ They focus on two different audiences (or types of readers).

+ 

+ The Fedora Magazine targets everyday Fedora users, Linux enthusiasts, and technology hobbyists.

+ Fedora contributors are included in these audiences, but they are not the main focus.

+ The Community Blog is the news hub for Fedora contributors and people working inside of the Fedora community.

+ The Community Blog specifically focuses on our contributors.

+ 

+ For example, an article on how to use a new package in Fedora is better for the Magazine.

+ Any Fedora user may be interested in using the package.

+ An article that announces a new feature to a Fedora Infrastructure service or an Ambassador event report is better for the Community Blog.

+ A Fedora user may not be interested, but our contributors have a stronger interest.

+ 

+ Sometimes there is some overlap between the two.

+ Think hard about who you are writing for and who you want to read your article.

+ This should answer the question of where to write your article.

+ The CommOps and Fedora Magazine teams are happy to answer any doubts or questions if you are unsure.

+ 

+ 

+ [[write-article]]

+ == Write an article

+ 

+ The Community Blog is managed by the CommOps team.

+ The system administration is managed by {FWIKI}/Infrastructure[Fedora Infrastructure].

+ However, we need _your help_ to share the awesome things you and your area of Fedora are working on.

+ 

+ Articles don't need to be long.

+ Short snippets are useful too.

+ If you're not sure how much to write, 300 words is a good target.

+ If needed, you can always write more.

+ 

+ See the {COMMBLOG}/writing-community-blog-article/[Writing an article] guide to get started.

+ This page explains the process for writing and how to get your post published.

+ 

+ 

+ [[community-blog-theme]]

+ == Community Blog theme

+ 

+ The Community Blog WordPress theme is open source.

+ Find the source code https://pagure.io/communityblog-theme[on Pagure].

+ Open a ticket if you find a bug, problem, or something to improve.

+ Pull requests are also welcome!

+ Before submitting a pull request, post to the {DISCOURSE}[CommOps Discourse forum] first and ask for feedback on your planned contribution.

+ 

+ 

+ [[editors]]

+ == Editors

+ 

+ Community Blog editors review article drafts and schedule new posts.

+ Editors are reachable on the {DISCOURSE}[CommOps Discourse forum].

+ The Discourse forum is the best way to reach an editor.

+ 

+ Below, you can find a current list of editors:

+ 

+ .Community Blog editors

+ |===

+ |Name |FAS account |IRC nickname

+ 

+ |Ben Cotton (_editor-in-chief_)

+ |{FWIKI}/User:Bcotton[bcotton]

+ |bcotton

+ 

+ |Brian Exelbierd

+ |{FWIKI}/User:Bex[bex]

+ |bexelbie

+ 

+ |Brian Proffitt

+ |{FWIKI}/User:Bproffit[bproffit]

+ |bkp

+ 

+ |Jona Azizaj

+ |{FWIKI}/User:Jonatoni[jonatoni]

+ |jonatoni

+ 

+ |Matthew Miller

+ |{FWIKI}/User:Mattdm[mattdm]

+ |mattdm

+ 

+ |Nick Bebout

+ |{FWIKI}/User:Nb[nb]

+ |nb

+ 

+ |Sumantro Mukherjee

+ |{FWIKI}/User:Sumantrom[sumantrom]

+ |sumantrom

+ 

+ |===

@@ -0,0 +1,104 @@

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = Join Community Operations

+ 

+ Become a member of Fedora Community Operations (CommOps) by following these steps.

+ 

+ 

+ [[fas]]

+ == Create a FAS account

+ 

+ Create a {FWIKI}/Account_System[Fedora Account System account] and sign the {FWIKI}/Legal:Fedora_Project_Contributor_Agreement[Fedora Project Contributor Agreement].

+ Do this through the https://admin.fedoraproject.org/accounts/[Fedora Account System].

+ 

+ 

+ [[discourse]]

+ == Log into Fedora Discourse

+ 

+ Log into the {DISCOURSE}[Fedora Discourse forum] using your FAS account credentials.

+ News, updates, and discussion are shared through on the forum.

+ It is a *key part* to how we communicate.

+ It receives low to medium traffic.

+ 

+ 

+ [[introduction]]

+ == Post a self-introduction

+ 

+ Say hello and introduce yourself to the team!

+ {DISCOURSE}[Post a self-introduction] to the Discourse forum and tell us a little about yourself.

+ 

+ Not sure what to say?

+ Answer these questions to start:

+ 

+ * Why are you interested in contributing to Fedora?

+ * Why are you interested in contributing to CommOps?

+ * If you're involved with other things in Fedora, what are/were you working on?

+ * Do you have any experience in open source or online communities? If so, what?

+ * What parts of CommOps were interesting to you?

+ * Do you have any questions for us? How can we help _you_ get started?

+ 

+ 

+ [[community-blog]]

+ == Register on Community Blog

+ 

+ The Fedora {COMMBLOG}[Community Blog] is a key component to CommOps.

+ An account gives permissions to view article drafts and previews before they are published.

+ If you ever write an article, you will need an account.

+ To register, log in at the {COMMBLOG}/wp-login.php[login page] with your Fedora Account System (FAS) credentials.

+ 

+ Need more help logging in?

+ Read the {COMMBLOG}/how-to-log-in/[help page] for more detailed instructions.

+ 

+ 

+ [[irc]]

+ == Join our IRC channel

+ 

+ Fedora uses the https://libera.chat/[Libera.chat IRC network] for instant messaging and communication.

+ Short discussions and planning happen in our IRC channel #fedora-commops.

+ Our monthly team meetings also take place on IRC.

+ 

+ Never used IRC before?

+ See the https://fedoramagazine.org/beginners-guide-irc/[Beginner's Guide to IRC] on the Fedora Magazine.

+ Additionally, you can connect temporarily in a chat session in your browser via https://web.libera.chat/[Libera.chat web chat].

+ However, if you want to stay connected even when you are not online, consider https://opensource.com/article/17/5/introducing-riot-IRC[using Riot] as your IRC client.

+ 

+ For convenience, the IRC channel is bridged to a Telegram group, https://t.me/fedoracommops[@fedoracommops].

+ You may also participate via the Telegram group, but you are unable to use or interact with IRC bots (e.g. in meetings).

+ Join the group at https://t.me/fedoracommops[t.me/fedoracommops].

+ 

+ 

+ [[first-steps]]

+ == Make your first steps

+ 

+ See xref:contribute/first-steps.adoc[Make your first steps in Fedora] for more info.

+ 

+ 

+ [[start-task]]

+ == Start on a task

+ 

+ CommOps uses https://pagure.io/fedora-commops[this Pagure repository] to track our tasks and what we're working on.

+ Tasks, problems, and goals are filed as tickets in the https://pagure.io/fedora-commops/issues[issue tracker].

+ There are a lot of tickets, but we're not working on everything at once.

+ Scrolling through the issue tracker gives a good idea of what CommOps helps with.

+ 

+ Look for the https://pagure.io/fedora-commops/issues?status=Open&tags=good+first+issue[good first issue] tag on tickets to find good tasks for beginners.

+ 

+ Does something look interesting?

+ Leave a comment if you have a question or want to work on something.

+ Also check and see if the ticket is assigned to someone.

+ If it is unassigned, you can start working on it now.

+ If there is an assignee, ask them if they need help or if they are still working on the ticket.

+ 

+ This provides an opportunity to receive mentorship and get help to start a new task.

+ 

+ 

+ [[meetings]]

+ == Join our meetings

+ 

+ CommOps has an IRC team meeting each week.

+ In our meeting, the team discusses items on our agenda and checks in on any progress of current tasks.

+ Tickets selected for meetings are updated after the meeting with new information.

+ 

+ The meetings are open to the public and anyone can join.

+ See when our meetings are in your time zone on the https://apps.fedoraproject.org/calendar/commops/[CommOps meeting calendar].

+ Feel free to attend and introduce yourself during roll call!

@@ -0,0 +1,88 @@

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = How to be a successful contributor

+ 

+ Audience for this document

+ --------------------------

+ This document is targeted at people interested in contributing to the Fedora Project.  In the Fedora Project, students, professionals and hobbyists all come together to produce software, marketing materials, art, documentation, etc.  We all started as new volunteers at some point.  The items below are designed to help you through the process of joining a team.  It helps you know what we expect of you and what you can expect of us.

+ 

+ Things to know before you join

+ ------------------------------

+ So you think that you would enjoy being a successful contributor to Fedora. Great!! You are most welcome. Here are some thoughts to consider.  Everyone who joins a free software project does so with the best intentions of staying. A few stay to become regular contributors, and fewer still become leaders within the project, and others lose interest.  The biggest difference between those that stay and those that leave is "commitment and time".

+ 

+ Time commitment

+ ---------------

+ A commitment requires reserving some time. If you strongly believe you will enjoy what you are doing, consider your dedication of time. Time commitment is as little as 4 hours per week. Some volunteers may spend 15-30 hours per week contributing.  Doing that level of commitment while holding down a proper day job is a difficult time management skill.  As a volunteer, you should ask yourself whether you can devote 2-4 hours per week, even though it's less than an hour per day.  Four hours a week for most people is an entire afternoon one day.  That's a significant chunk of time.

+ 

+ Get permission from work and family

+ -----------------------------------

+ Volunteering has great rewards in many ways. The two most prominent ones are your success at introducing a person to Fedora, another is your own ego. A third benefit is with your job.

+ 

+ There is a mutually beneficial relationship between working for a living and volunteering.  Many contributors will find their skill sets at work increase dramatically just by having access to and learning from another environment.  This volunteering benefits employer and worker.  It is completely worthwhile to sit down with your employer and ask for permission to contribute during work hours, even if it's only a couple of hours on a Friday afternoon. If you are married, make sure your family agrees to your being busy for this time commitment. Your volunteering must be a win-win-win for the company, your family and you. Explain the benefits to you, to the business, and your family. Family is the important people in your social life. (spouse, friends, parents, others).

+ 

+ If work says no, then you will have to volunteer in your own time. Your family may be enthusiastic to help you. Volunteering is very rewarding.

+ 

+ Joining

+ -------

+ 

+ The single biggest mistake most new contributors make is showing up "just wanting to contribute."  It's important to take the time to observe the team (refer to the section below) and see how their work aligns with your own skills and personality.  Know that getting work to do on day one is very rare, and those who are highly skilled in a specific technology  will still have to take the time to get to know an environment before access is granted.

+ 

+ For example, if you're a database expert it is very unlikely you'll be given access to databases (where personal info, passwords, etc are stored) within your first several weeks of volunteering.  If you're looking to become an ambassador, it is unlikely you'll get marketing materials shipped to you in your first week.  This may seem unfortunate, but it's necessary to keep the project members working well together.  The same can be said about any major changes, like a complete redesign of a system or a new look and feel for a website.  Don't get discouraged.  Show up as often as you can, and get to know the team.

+ 

+ Observation

+ -----------

+ 

+ It is important to get to know the organization and teams you are looking to work with before you try to join them.  Learn what they do and how they do it, and try to get to know the people involved.  It is extremely unlikely you will be able to actually contribute from day one.  In organizations with hundreds or thousands of people working together, understanding how things work is critical.

+ 

+ Don't be shy about asking questions and getting to know people.  Plan to spend several days or even weeks attending meetings, emailing on mailing lists and hanging out on IRC before you get to do any actual work.  Offer suggestions on topics being discussed, and share any experiences (good or bad) you've had that is relevant to the discussion.

+ 

+ Part of observing and making constructive suggestions may require withholding judgment.  When making suggestions, don't assume you come with all of the answers or that the Fedora Project is ''doing it all wrong.''  There is a good chance we can improve the way we are doing things, however most of our current practices were developed over long periods of time after lengthy discussion.  Your criticism may be better received once you have established yourself in the community and are perceived as understanding our culture.

+ 

+ Pick what you want to work on

+ -----------------------------

+ 

+ It's your job to decide what you want to work on.  Pick something that's important to you and something you have passion for.  You'll see this advice repeated several times in this document:  Don't just show up looking to have work assigned to you.  Get to know the teams and procedures they have in place.  Ask questions and really get to know what you're going to be working on _before_ trying to work on it.

+ 

+ Don't jump into the deep end

+ ----------------------------

+ 

+ When picking something to work on, don't be the sole person to take on a huge task as your first contribution.  Picking a task that's too large significantly raises the chances of failure.  Also don't pick several things on several teams to work on.  Start small, picking at most one or two things, and grow from there.  The key is slow, steady, and sustainable growth.  Don't join with the immediate goal of becoming the next leader of the project.  Start small.

+ 

+ First contact

+ -------------

+ After you've decided what you're looking to do and what team you are looking to do it with, it's time to send an introduction to the list.  When sending an introduction (usually by mail list), include the following information:

+ 

+ * Name

+ * Time Zone / Country

+ * Basic skills and experiences

+ * Why you're joining

+ * What you're looking to do (be specific)

+ * How much time you can contribute (usually hours per week)

+ 

+ If any of the above questions are not clearly answered, don't send the email yet.  You're not ready.  Remember, be specific about what type of work you're looking to do.  Saying "Whatever needs to get done" isn't helping anyone.  Saying "I'd like to help document system A," "I'd like to translate software for my native language," or "I noticed this webapp is particularly slow sometimes and I'd like to help fix that" is perfect.

+ 

+ Find a mentor or sponsor

+ ------------------------

+ This step is both incredibly difficult and important.  Finding a proper sponsor will increase your chances of being a successful contributor significantly.  Sometimes it's absolutely required.  A sponsor will help with training, introductions and teaching new contributors how a team works.

+ 

+ Most teams have mailing lists.  Email the list, say you're looking for a sponsor, and explain what you are wanting to do.  If you haven't heard back in a few days, reply saying that you are still looking.  ''Keep doing this.''  Most sponsors are people that have been in the project for a long time, and are often very busy.

+ 

+ They don't mean to be rude and don't want to send the impression they don't want new contributors.  It's just that at the moment, some people will assume other people will take care of you and so for the moment, no one does.  This is a common problem -- in real life as well as in online communities -- and a difficult one to fix.  But sticking to it and continuing to ask for help without being annoying will show that you are serious and ready to contribute.  Don't send this kind of message more than once every couple of days, but be positive, and persistent if needed.

+ 

+ Contributing

+ ------------

+ Once you've got something to work on, it's time to actually do work.  The first several tasks you will work on will likely be small or maybe mundane.  Do them consistently, conscientiously and well.  This will raise the level of trust you have from the other team members.

+ 

+ As with other volunteer organizations, there are high turnover rates in the free software universe.  Training volunteers is time consuming, especially for more complex tasks, and requires a commitment from currently busy volunteers.  Spending days or weeks training someone only for them to vanish can be disheartening for mentors and sponsors.  By giving out small tasks that have been hanging around, a sponsor can help you take small but vital steps, and learn whether or not the work you're going to be doing is really for you.

+ 

+ Look for work

+ -------------

+ If you have access to a repository, system, or content, consider yourself a partial owner.  This doesn't mean you should immediately re-design everything.  Remember that other owners have time and effort invested in the current material as well.  It does mean, though, that you should take pride in the work you are doing.  If you see something not quite right, do research on it and notify the list.  Seek work out, keep yourself busy and help others.

+ 

+ Quitting

+ --------

+ If you've found you've over-committed or decide volunteering isn't for you, that's OK.  You don't need to be embarrassed that you can't contribute further.  Contributors will not make you feel bad about it either.  Realize that lots of contributors come and go every day.  Being busy with your day job or not having enough free time is a perfectly valid reason for not being able to contribute.  It's even possible that you might not feel a good fit with the team or organization.  You're entitled to offer help as a volunteer how you want and when you want.

+ 

+ First and foremost, though, don't just vanish.  When a contributor or potential contributor agrees to do work, can't follow through for a valid reason, and vanishes, the team may not know the work can be reassigned.  In some cases, people in the team may even worry about the contributor's health or well being.

+ 

+ When you've decided it's time for you to go or take a break, let your sponsor or the list know and let them know what you were working on.  Having people think you are working on something when you aren't slows the team down, and ultimately doesn't benefit you or the team.

docs/modules/teams/pages/index12.adoc docs/modules/ROOT/pages/index1.adoc
file renamed
file was moved with no change to the file
@@ -0,0 +1,37 @@

+ include::ROOT:partial$attributes.adoc[]

+ 

+ = IRC / Libera Chat Group Contacts

+ 

+ libera.chat IRC network has a concept of ‘Groups’ for various projects. Group contacts for each of those groups are granted special powers on the network over their groups channels. Additionally, requests from Group contacts can be taken as ‘official’ requests from the group. Fedora group contacts represent Fedora to libera.chat.

+ 

+ The primary functions of group contacts are:

+ 

+ * Check/process ‘cloak’ requests and request them from libera.chat admins to process. (Cloaks are a hostmask with the project name in them instead of hostname or ip address. It’s a way to note your affiliation with a group)

+ * To (re)gain and configure control of irc channels in the group namespace “#fedora*”

+ 

+ 

+ == How to join the team / step down

+ 

+ 

+ Group contacts are added from very trusted project members and kept to a small number. Council should appove changes in libera.chat group members. Changes will then be made by libera admins to joining / leaving accounts.

+ 

+ == Responsibilities

+ 

+ * Process the ‘cloaks’ requests: https://fedoraproject.org/wiki/LiberaCloaks as time permits.

+ * Process requests in the https://pagure.io/irc tracker for matrix bridges or regaining control of a channel in the #fedora* namespace as requested.

+ * Idle in the #libera-communities channel to make requests to libera admins as needed.

+ 

+ == Teams you will be working closely with

+ 

+ * libera.chat admins in #libera.communities

+ * Any fedora groups needing irc work

+ 

+ == Current members

+ 

+ ** Tom Calloway / spot

+ ** Nick Bebout / nb

+ ** Kevin Fenzi / nirik

+ 

+ == Contact information

+ 

+ Link : https://pagure.io/irc