| |
@@ -1,46 +1,44 @@
|
| |
- include::{partialsdir}/attributes.adoc[]
|
| |
+ include::ROOT:partial$attributes.adoc[]
|
| |
|
| |
- = Get involved with Fedora Diversity, Equity, & Inclusion Team
|
| |
+ = Get involved with {team_name}
|
| |
|
| |
- Diversity, Equity, & Inclusion Team always welcomes new contributors.
|
| |
+ The {team_name} always welcomes new contributors.
|
| |
Whether you are a newcomer or an old-timer, whether you can contribute frequently or sporadically, there are ways to get involved.
|
| |
- As a Diversity, Equity, & Inclusion team member, you can:
|
| |
+ As a {team_name} member, you can:
|
| |
|
| |
* Work closely with Fedora leadership to build initiatives from the ground-up which shape Diversity, Equity, & Inclusion in Fedora community.
|
| |
- * Organize global events like Fedora Women's Day to support people from diverse backgrounds in taking their first steps in Fedora community.
|
| |
+ * Organize global events like Fedora Week of Diversity to support people from diverse backgrounds in taking their first steps in Fedora community.
|
| |
* Cross-collaborate with different teams like Localization to enable Fedora community members from diverse backgrounds to contribute effectively.
|
| |
* Organize community-building workshops and activities to foster inclusion in Fedora community.
|
| |
* Create outreach content like videos, infographics and blog posts to improve the visibility of underrepresented community members in Fedora community.
|
| |
* Research about Diversity, Equity, & Inclusion initiatives in other open source communities and how they can be applied to Fedora community.
|
| |
|
| |
- Interested in helping the Fedora Diversity, Equity, & Inclusion Team?
|
| |
+ Interested in helping the {team_name}?
|
| |
This page explains the typical process for getting involved with our team.
|
| |
|
| |
|
| |
[[create-fas-account]]
|
| |
== Create Fedora Account System (FAS) account
|
| |
|
| |
- All contributors to Fedora need to register in the https://accounts.fedoraproject.org/[Fedora Account System].
|
| |
- New contributors are asked to sign the {FWIKI}/Legal:Fedora_Project_Contributor_Agreement[Fedora Project Contributor Agreement] (FPCA).
|
| |
+ All contributors to Fedora need to register in the link:https://accounts.fedoraproject.org/[Fedora Account System].
|
| |
+ New contributors are asked to sign the xref:legal::fpca.adoc[Fedora Project Contributor Agreement] (FPCA).
|
| |
This is not a copyright assignment agreement, but ensures your contributions to Fedora have acceptable licensing terms.
|
| |
- If you need help with this, contact the https://docs.fedoraproject.org/en-US/infra/day_to_day_fedora/[Fedora Infrastructure Team].
|
| |
+ If you need help with this, contact the xref:infra::day_to_day_fedora.adoc[Fedora Infrastructure Team].
|
| |
|
| |
|
| |
- [[discourse-forum]]
|
| |
+ [[forum]]
|
| |
== Discourse forum
|
| |
|
| |
- We have a tag on https://discussion.fedoraproject.org/tag/dei[Fedora Discussion](our community's forum) where DEI topics can be discussed.
|
| |
+ We have a tag on link:{team_asynch_communication}[Fedora Discussion] (the Fedora community forum) where team topics are discussed.
|
| |
|
| |
-
|
| |
- [[self-introduction]]
|
| |
- == Send a self-introduction
|
| |
+ [[forum-introduction]]
|
| |
+ === Introduce yourself
|
| |
|
| |
If you want to get involved, we want to get to know you!
|
| |
- So don't be shy, open up a https://discussion.fedoraproject.org/tag/dei[Fedora Discussion thread with #dei tag].
|
| |
- This is a helpful step for other folks on the team to get to know you.
|
| |
+ *Post a self-introduction on the link:{team_asynch_communication}[#dei-team tag on Fedora Discussion]*.
|
| |
+ This is a helpful step for other folks on the {team_name} to get to know you.
|
| |
|
| |
Not sure what to say?
|
| |
- Does writing an introduction feel awkward?
|
| |
Consider these questions when introducing yourself:
|
| |
|
| |
* Are you new to the Fedora community?
|
| |
@@ -51,65 +49,41 @@
|
| |
Let us know what parts of Fedora you are involved in.
|
| |
* Are you an organizer of local events or programs?
|
| |
If you run any kind of event in your local community, let us know what you do.
|
| |
- * What is interesting to you about the Fedora Diversity, Equity, & Inclusion Team?
|
| |
+ * What is interesting to you about the {team_name}?
|
| |
Our team is a collection of people with different interests and niches.
|
| |
Knowing each others' interests and what we like lets us connect each other to things we want to help out with.
|
| |
|
| |
|
| |
- [[join-irc-telegram]]
|
| |
- == Join IRC/Telegram/Matrix group chat
|
| |
-
|
| |
- The Fedora Diversity, Equity, & Inclusion Team has a real-time group chat.
|
| |
- We use this group chat for quick updates, friendly chatter, and running meetings.
|
| |
- We use both an IRC channel on the https://libera.chat[Libera.chat IRC network] and a Telegram chat group.
|
| |
- Both are bridged to each other, so folks in IRC will see Telegram messages and vice versa.
|
| |
-
|
| |
- Here are the easiest ways to join:
|
| |
- This document explains how to efficiently work with the Fedora Infrastructure team. Your close attention to this document will help both you and us do the work you are asking us to do.
|
| |
-
|
| |
- * https://app.element.io/#/room/#fedora-diversity:matrix.org[Element/Matrix]
|
| |
-
|
| |
- * https://web.libera.chat/?channels=#fedora-diversity[IRC Web chat]
|
| |
-
|
| |
- * https://t.me/fedoradiversity[Telegram]
|
| |
-
|
| |
+ [[chat]]
|
| |
+ == Join Matrix chat room
|
| |
|
| |
+ The {team_name} has a real-time chat room on Matrix.
|
| |
+ We use the chat room for quick updates, friendly chatter, and running meetings.
|
| |
+ Use link:{team_synch_communication}[this link] to join from your preferred Matrix client.
|
| |
Don't forget to say hi when you join!
|
| |
|
| |
|
| |
- [[first-steps]]
|
| |
- == Make your first steps
|
| |
-
|
| |
- See xref:commops::contribute/first-steps.adoc[Make your first steps in Fedora] for more info.
|
| |
-
|
| |
-
|
| |
[[attend-meeting]]
|
| |
== Attend a meeting
|
| |
|
| |
- https://apps.fedoraproject.org/calendar/diversity-team/[**Find our next meeting on our calendar!**]
|
| |
+ link:{team_meetings}[**Find our next meeting on our calendar!**]
|
| |
|
| |
- The team usually holds a bi-weekly meeting over a Jitsi call to review on-going work and determine next steps on current work.
|
| |
- The meeting format is intended to be quick updates **and** long discussion.
|
| |
- It is a good opportunity to say hello and meet other members of the team in real-time while seeing how we work.
|
| |
+ The {team_name} usually holds a fortnightly meeting over Jitsi Meet to review ongoing work and plan new work.
|
| |
+ It is a good opportunity to say hello and meet other team members in real-time while seeing how we work.
|
| |
+ See the xref:meetings.adoc[team meeting guide] for how our meetings work, including the xref:meetings.adoc#social-agreement[social agreement] and xref:meetings.adoc#format[meeting format].
|
| |
|
| |
|
| |
[[tickets]]
|
| |
- == Check out Pagure tickets
|
| |
-
|
| |
- The next step to get involved is to review our ticket tracker and look for something interesting to you.
|
| |
- All of our open tickets are in our https://pagure.io/fedora-diversity/issues[Pagure repository].
|
| |
- New tasks are added as "issues" into the Pagure repository.
|
| |
-
|
| |
- Here is a quick index of different types of tickets:
|
| |
+ == Ticket-based task management
|
| |
|
| |
- * https://pagure.io/fedora-diversity/issues?status=Open&priority=20[Meeting tickets]
|
| |
- * https://pagure.io/fedora-diversity/issues?status=Open&tags=good+first+issue[Good first tickets for newcomers]
|
| |
- * https://pagure.io/fedora-diversity/roadmap[Roadmap] (collection of tickets around specific objectives or goals)
|
| |
+ The next step to get involved is to review our ticket tracker and look for a task that is interesting to you.
|
| |
+ Our open tickets are in our link:{team_issue_tracker}[GitLab repository].
|
| |
+ New tasks are added as "issues" into GitLab.
|
| |
|
| |
See a ticket that looks interesting?
|
| |
If someone is not already assigned, leave a comment and ask how you can help.
|
| |
- Another member of the team will get back to you with some feedback on how you get help.
|
| |
- This is one opportunity to get mentorship and help with getting started on a task.
|
| |
+ Another member of the team will get back to you with feedback.
|
| |
+ This is an opportunity to get casual mentoring on a task.
|
| |
|
| |
Alternatively, do you think something is missing or could be improved in the Fedora community?
|
| |
Open a new ticket with your idea or suggestion.
|
| |
@@ -118,30 +92,35 @@
|
| |
Open a new ticket and we can discuss more about your idea or suggestion.
|
| |
|
| |
|
| |
- [[joining]]
|
| |
- == Officially Joining the Team
|
| |
+ [[sponsorship]]
|
| |
+ == Team sponsorship
|
| |
|
| |
- If after some time contributing to and hanging out with the Fedora DEI Team you would like to join the team in an official capacity, you can do so. The process is as follows:
|
| |
+ When someone is considered a full voting member of the {team_name}, we call this person a *sponsored member*.
|
| |
+ After spending time contributing with the {team_name}, you can join the team in a formal capacity as a full voting member.
|
| |
+ The process to become sponsored is as follows:
|
| |
|
| |
- * Talk to a member(s) of the DEI team to find a sponsor
|
| |
- * Sponsor will open a "New Team Member" ticket on the DEI team pagure
|
| |
- * Ticket will be open for two weeks for others members to vote and/or give commentary about your team membership.
|
| |
- * If we do not reach consensus in the two week period, it can be extended for another two weeks.
|
| |
- * A negative vote halts the process and requires discussion.
|
| |
- * Full consensus is required for you to join the team. This means 3 +1's and no 0's or -1's.
|
| |
- * If consensus is met, you will then be added to the Fedora Account System group.
|
| |
+ . Talk to a member(s) of the {team_name} to find a sponsor.
|
| |
+ You can see a list of sponsored team members in the https://accounts.fedoraproject.org/group/diversity-team/[`diversity-team` Fedora Account System group].
|
| |
+ . Sponsor will open a "New Team Member" ticket on the {team_name} ticket tracker.
|
| |
+ . Ticket will be open for two weeks for others members to vote and/or give commentary about your team membership.
|
| |
+ .. If we do not reach consensus in the two-week period, it can be extended for another two weeks.
|
| |
+ .. A negative vote halts the process and requires discussion.
|
| |
+ . Full consensus is required for you to join the {team_name}.
|
| |
+ This means at least three +1 votes and no -1 votes.
|
| |
+ . If consensus is met, you will then be added to the Fedora Account System (FAS) group.
|
| |
|
| |
Sponsors will evaluate your membership in a couple of ways:
|
| |
|
| |
- * Ability to work cooperatively with peers
|
| |
- * By the interactions potential members have in meetings and in channel.
|
| |
- * By how potential members respond to criticism.
|
| |
- * By how potential members participate on Discussion and Pagure.
|
| |
- * Community involvement beyond the DEI Team
|
| |
- * By the interactions potential members have in the Fedora community.
|
| |
- * Does the potential member help to answer questions raised on Discussion and Pagure; do they show a helpful attitude and respect for other people’s ideas?
|
| |
- * Commitment and follow through
|
| |
- * By time already given to the DEI Team.
|
| |
- * By how well potential members stick with the process through tough issues.
|
| |
- * By how potential members engage on difficult topics in a constructive way.
|
| |
- * By regularly showing up in meetings or in chat.
|
| |
+ * *Ability to work cooperatively with peers*.
|
| |
+ ** By the interactions potential members have in meetings and in channel.
|
| |
+ ** By how potential members respond to criticism.
|
| |
+ ** By how potential members participate on the forum, chat room, and ticket trackers.
|
| |
+ * *Community involvement beyond the {team_name}*.
|
| |
+ ** By the interactions potential members have in the Fedora community.
|
| |
+ ** Does the potential member engage on the forum, chat room, and ticket trackers?
|
| |
+ Do they show a helpful attitude and respect for other ideas of others?
|
| |
+ * *Commitment and follow-through*.
|
| |
+ ** By time already given to the {team_name}.
|
| |
+ ** By how well potential members stick with the process through tough issues.
|
| |
+ ** By how potential members engage on difficult topics in a constructive way.
|
| |
+ ** By regularly showing up in meetings or the chat rooms.
|
| |
jflory7
commented a year ago
This commit is a significant refresh of the Fedora DEI Team docs based
on our current best practices and team workflows, as described below:
Update attributes
This was the largest change made to the docs. Our attributes file was
updated, in response to feedback that the links to our Fedora Discussion
pages were broken after the recent change from
#deito#dei-team.There was not advance notice made to the team about this change, so the
links are now broken and need to be updated so people are directed to
the correct place for our discussions.
While doing that, I pulled the template file from the Engineering and
Mindshare docs maintained in the Council docs repository to use as a
model. I updated our platforms from the template and then used the
attributes as much as possible throughout our docs. There is more work
to do, but in the future, this will make metadata updates easier. There
will only be one place to update URLs should they ever change in the
future.
Refresh index page
Matrix; we should try to funnel people to the places where the team is
most active and connected to the rest of the Fedora community.
"asynchronous" instead of using platform names.
Refresh getting involved and meeting guide pages
xref's to external team documentation where applicable(e.g. Fedora Legal and Fedora Infrastructure).
list or Telegram group as primary ways to engage with the team.
become a sponsored member of the DEI Team.
Miscellaneous changes
Discussion, stop using punctuation marks to distinguish acronyms. This
was originally done for the benefit of screen reader users, but this
guidance is now out-of-date with how most screen readers work, based
on community feedback.
not already changed.
:toc:attribute in pages, since the Fedora Docs theme nowincludes a table-of-contents in the sidebar by default.