Title of Session: Improving maintenance of older default themes
Notetaker 1: @mikachan
Notetaker 2: @zoonini
From the session schedule:
Recently, there was a proposal to retire some old default themes. In response concerns were raised around how to do so. This discussion aims to explore how to maintain older default themes in more sustainable, streamlined methods.
- Concerns raised around breaking the promise of supporting all default themes forever, just like we do for Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- Can we write an underlying framework to help support all themes?
- They’re all so different so may be difficult to build a framework to support all of them. It could be a lot of work.
- Older themes are an educational resource for theme developers. By maintaining older themes we are educating developers on how to update their own themes.
- The burden falls on the Core team to maintain themes. Original theme authors often get re-assigned or leave the project.
- How can we help spread the workload?
- Can we onboard more people to maintain themes?
- We have already tried having a default theme maintenance team. This has previously been a burden; 20xx themes are a burden to maintain.
- Why is there only a default theme lead for the last version of the year?
- Why not each release so updates can be bundled in each release?
- Used to have a Theme Wrangler for each release but this dropped off.
- More docs needed for default themes.
- Using the default theme to showcase new features makes it difficult for backwards compatibility.
- Does it have the same impact if we make all default themes block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes?
- Is there a world where we could make all default themes as light as possible?
- Default themes can be updated outside of the release cycle. Could we introduce a regular cycle of updating default themes? Theme cycle vs release cycle
- What about designing a method of testing older themes for each release?
Action Items/Next Steps:
- Explore moving default themes to Github GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ (with sync to SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/.)
- Pick the most critical issues from trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. to move over
- Consider having a Theme Wrangler for every release
- Explore creating style variations and patterns based on past default themes, as a way to blockify the older themes
- Explore setting up visual regression testing for default themes
- How do we improve the feedback loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. from people building themes in GB?
- Improve default theme docs
From the session page:
The WordPress project both generates and processes a lot of information on a regular basis. Even for tenured contributors, it can be challenging to know where or who to go for much needed information. On each team and across the project, who should be responsible for disseminating information, and how can communication practices be streamlined to make collaboration more seamless for everyone building WordPress? This discussion will explore current friction points and possible ways to address communication and collaboration in the WordPress ecosystem.
Facilitator: Kevin Cristiano (@kcristiano)
Notetaker: Jessica Frick (@jessibelle)
- Explore current problems we face when communicating across teams
- Explore possible solutions to address the identified friction points
The Community faces a number of different challenges where communication and collaboration are concerned. Whether it manifests as duplicated work across teams due to a lack of communication or simply dead zones where discussions are purposely kept behind closed doors, these friction points cause real issues on all teams. While most agree we need cross-team communication, many don’t know where to go or what information is missing.
Action Items / Next Steps
- Members from different Make teams need to work together to develop a proposed process for more public communication and coordination.
- An ethical standard and code of conduct should be established to determine what information can be kept private and what we have an ethical duty to keep public.
- We should update our definition of the community to reflect what it is today, including the roles and power therein, as this informs the communication internally and externally from reps, members, and beyond.
Full Session Notes
From the session schedule:
Historically, the WordPress project has avoided taking clear public stances on legislation as it appeared across the world, instead relying on our sustaining/underwriting corporations to advocate for the best positions. Increasingly, WP is being asked to weigh in or participate in taking a collective stand with other FOSS projects in our field. Are our current methods sustainable? Do we have the community backing to make this sort of broad claim?
Facilitator: Angela Jin (@angelasjin)
Notetaker: david wolfpaw (@wolfpaw)
Notetaker: Erica Varlese (@evarlese)
- As we’ve learned from Spider-Man: with great power comes great responsibility.
- Some questions to address:
- What questions do we have on the topic and what context would be helpful to start the conversation?
- What kind of government regulation/legislation are we discussing? Global, such as EU, GDPR, etc.
- While a lot of legislation is starting in Europe, such as GDPR, it is going to evolve and spread to other parts of the world, as that already has.
- What do we currently do, how we can improve it, and is it sustainable when it involves participating in legislation.
- How reactive versus proactive should we be in the project for legislation: just reacting to legislation as it comes up, or making suggestions for future legislation.
- We need to find an official home within the structure of the project (Make Teams) to have legislation related discussions. The Sustainability Team has been brought up as a suggestion. Without this anchor of a team, transparency becomes untenable. We need to set some sort of framework for a process when it comes to thinking about these issues.
- Russia is considering a law to make it illegal to work with a foreign non-profit. What does that mean when it comes to volunteering with the WordPress project? We have to be proactive since we can see it coming. It’s not just high level discussions on code and security, but on who can participate in the community.
- When we respond to requests, how do we ensure that we are capturing the community.
- We might want to measure how likely legislation is to pass before determining if we should get involved.
- We should not only be discussing legislation, but how else we can or should be involved with other governmental activities. For instance, should the WordPress project respond with amicus briefs on cases being brought before courts, such as what some technology projects have done.
- This in part goes to the idea of, “decisions, not options”. Are we an opinionated project or not? Should we put out these amicus briefs, or just respond if something affects us. We can say that we have talked about things as a community, and generally agree on some action/idea and publish that to Make.
- WordPress could say, “this could affect these sites, this source code, etc”, and the greater community could take this information and act on it. Not making the statement so much advocacy, but opinions that could facilitate action that the community would not have to take explicitly.
- As a community we need to lobby a little to be reactive to things that exist like GDPR, and to make changes in WordPress. For instance how we need to be more open about security in the project because we will need to due to upcoming legislation.
- We need a space to explain what is happening with specific laws when it relates to our community.
- As a 501(c)3 we cannot be seen as doing any sort of lobbying.
- What would a proactive response from WordPress look like? – The most important thing to be proactive about is deciding about what is important to address. Legislation that we are looking at is very broad, and could be globally reaching, or even more locally, such as Montana banning TikTok. Deciding upfront which things that we care about, and then looking for how we can get involved. We should not feel intimated or that there is a barrier, but work on conversations where we can participate in with our domain knowledge, such as on open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., contributors, security, etc.
- We don’t want our contributors, especially self-sponsored contributors who make smaller contributions, to be responsible for legislation. We have a majority of contributors in the EU, and we want them to be able to contribute for as long as they would like, as safely as possible.
- Would it be beneficial for WordPress to explore consultative status at the United Nations, with the office of NGOs
- There was a position taken concerning contributors and the EU, and there will need to be other positions taken in the future. If someone takes a position on behalf of the community, it needs to have the support of the community. Perhaps we could create a structure where discussions happen, for when positions will or won’t be taken.
- There are so many times when individuals or sponsored contributors take positions, and the rest of the community can feel left out and that their discussion and feedback does not matter.
- There are so many issues that the community could comment on: Black Lives Matter and George Floyd, gender, sexuality, war. How can these translate into advocacy? We can have a conversation of how far we go. Human Rights are important, but how far do we go as a community?
- There is an assumption that Make teams are representative of what we call the Community. The challenges of representing the community is that people are represented, but that is not representative. That could be an issue with whether representation is ever possible. We are asking some big block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. of people but it won’t represent everyone.
- How do we flag things for WordPress to review. How do we see what things that we should be concerned about, what should be the structure to do this advocacy work, and how do we keep it sustainable.
- We cannot be representative of the entire community, and decisions have to be made, otherwise not making a decision is a decision. There will be some subset of people who make opinions that are representative of the WordPress community. Majority cannot make opinions that cover the Minority.
- Right now, someone says, “hey, has someone looked at this?” and shares it to Matt or Josepha, and we react.
- What could a process look like: Someone raises a question to Josepha or Matt, but maybe there is a group that could have a process.
- Is the process broken enough that we need to make a system? We need specific people to agree to make positions. Perhaps it is not a process worth iterating on right now.
- Leaning on the fact that the community is global would be nearly impossible to track things in countries where we don’t have as many contributors or do not speak the same language. Even putting out, “this is what the process is” without adding structure could be helpful to ensure that people know how to be heard.
- Our motto is “democratize publishing”. But we are not going to be a direct democracy in the project. A representative democracy would better serve us by having community members who represent parts of their community. The only thing that is missing right now is garnering topics from the community. One on one conversations are valuable, but can be negative because it excludes people by its nature.
- As an example there are regular town halls in some communities that people can bring issues up to that are not specifically about one problem, so that people can bring up any of the issues that they have to be addressed. The conversation component as a community is what is missing.
- If something comes out of a discussion that the community cares about, it will become a big thing regardless.
- Looking at how we can improve the process: what we need is a space for people to share in one space, and where people can comment on things that are happening in various parts of the world, with various legislation, etc.
- Voting would be tricky, but we do have tools available, such as polling.
- One issue is that the more things that we take positions on, there are more things that we have to take positions on. For instance we take positions on human rights issues in some places, but not in others. We could look to where we have the most contextual authority as a group of contributors to comment on positions.
- When you ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” someone about a problem asking for position, keeping in mind whether we have domain experience. The recent issues of open source contributors being legally responsible for projects is something that is important to this community, but maybe something like agricultural bills is not important in the same way for our skills. The bigger your grasp gets, the further that people want you to reach.
- We want to ensure that what we are adding is impactful, like having teams and representatives on squads for a purpose, not just because everyone should have a voice. Having people have to reach out to whole teams takes time that could be used for other pressing projects.
- When we lead through example, it is powerful, and that’s something that we can control.
- We don’t think that the community would not understand wanting to keep a narrow focus on things that directly impact the project, and we can define that. Things that matter as an open source project.
- Some people will want us to talk about everything, but we can filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. that out and just focus on a clear scope of things that will directly impact the efficacy of the project. Open source things, infrastructure things, security things that directly impact Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- It is clear that there is a distinction between, “Stuff that WordPress supports”, and “Stuff that WordPress makes a statement about”. Statements about some law that affects someone doesn’t change things, but ensuring that the community is supported matters more.
- Following this conversation, what are the things that we care about to make a statement on:
- Four Freedoms of Open Source
- Things that affect the openness of the internet/web that affect our users
- Things that affect the ability to participate/use open source software
- Security, personal security, encryption
- AI Ethics
- Legislation that might affect the content that we have on our various platforms, like on OpenVerse, Learn, Photos
- WordPress tries to have human-centric approaches to dealing with modern technology and projects. Working your way through the project can teach you a lot about this. We look at open source as you can take it into the world, not just with WordPress itself.
- It can be valuable to share how things are done when it comes to taking a position on behalf of the project. That way even if we don’t address something as the community, we have guideposts on how to respond on an individual level to take action.
- If we don’t have a discussion as a community, then it will be seen as just Automattic’s position when a statement is made. Even from a perception standpoint, this is an issue.
- If conversations are being had but people don’t know where they are or how to get involved, it can seem as if they were not able to have an opinion.
- Some mechanism for Make teams to be notified of legal decisions coming down that would need to adjust what the teams are doing would be helpful to have.
- A barrier to get involved in discussions is being able to parse all of the details, length of research and statements, etc. The summaries can be placed somewhere that more people can see.
- Possible next steps:
- Designate a place for these conversations to happen.
- Draft a “Here are the topics WordPress would address” document.
- We had a lot of discussion, so it may not already be apparent.
- A method of communicating to the Make teams when there is something with legal ramifications or something we’ll need to deal with.
- Summaries of what’s happening to allow people to get involved in the discussion.
From the schedule session:
WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ currently have different release schedules and velocities, and are managed in two different locations (Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. and GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/). This complicates merging Gutenberg code into Core. For example, it is unclear where modificatons should occur, resulting in version control issues. This discussion hopes to bring clarity to these issues and explore possible processes and solutions.
Perspectives needed: Current and interested Core and Gutenberg contributors, project managers, and team members following the release process.
Facilitator: Jonathan Desrosiers (@desrosj)
Notetaker 1: Daniel Bachhuber (@danielbachhuber)
Notetaker 2: Rebekah Markowitz
Notetaker 3: Sarah Norris (@mikachan)
From the session schedule:
This discussion will focus on how the WordPress project can welcome and sustain a diverse pool of contributors to all Make Teams. What are teams currently doing, and what practices can be brought to the whole project? What new practices, resources, support should be introduced?
Perspectives needed: Current and aspiring Make Teams members interested in DEIB.
Facilitator: Birgit Olzem (@coachbirgit)
Notetaker: david wolfpaw (@wolfpaw)
Notetaker: Bigul Malayi (@mbigul)
Notetaker: Taco Verdonschot (@tacoverdo)
- What is DEIB? Diversity, Equity, Inclusion, and Belonging.
- Current state of DEIB in the WordPress project
- Potential Improvement
- Collaboration and Support
- Scope of a DEIB Team?
- The project today: how the WordPress project can welcome and include a diverse team of makers across all teams.
- Equity is to ensure that we have the opportunity to give underrepresented groups the same opportunities that already represented groups have.
- How do we honor the very best of this community? How do we bring people in and feel as welcome and included in our spaces as possible? What can we do to address things that prevent that from happening?
- We would like members of this community to reflect how diversity in the world exists in the many local communities within our global community.
- We want to have a diverse mindset
- Belonging is a new word as part of the acronym. It makes me think of the premise of this discussion: sustain. It is great to have belonging because while we can make this community open, how do we ensure that their needs are continued to be met while as part of this community. I believe that Belonging is representative of that goal. Not only surface things but being able to sustain your presence there.
- A group of four of us outside noted that we were all from four separate continents. The WordPress community can be an example of making the world more open and peaceful, and bringing the dream of open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. to things like politics. I fell in love with the WP community years ago because of that.
- When we talk about DEIB we have to talk about what the barriers of access for different people. Some of us do not have as much ability to easily access spaces for different reasons. The access for everybody is not the same, and e have to look at that and consider how we individually provide accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility). We also acknowledge that it is not free to do this, for instance adding ramps. We have to invest resources, not just human, but financial, to ensure that events are accessible to everyone, through things like sponsorships and financial support and reaching out to underrepresented groups.
- Diversity is special to us. India is a land of languages. Different languages, culture, food. The WordPress community is an ecosystem that has allowed many people to come and contribute. There is a communication issue but discussing this will help the community to learn and improve.
- Seconding that Belonging is important. It is one thing to have DEI, but Belonging brings it full circle.
- This community is very open. Some people do not know if they will have a place in the WP community and it is great to show that everyone can belong here. I can do what I do here without being judged by my background or what I look like.
- I want to acknowledge that we have come a long way in this community. Sometimes it is easy to say, “we’ve done it, we’ve created a space”, but as a community what we haven’t quite done yet is have some of the invisible inclusions. We need to be honest about where we are and aren’t inclusive yet. We don’t want people to have to share their invisible inclusion, but be able to show up and already have space for them. Whatever person you see in front of you, you should not judge their ability or situation.
- I grew up in India and lived my adult life in the US. I worked in the corporate world before WP, and sometimes I was the only female among white, male developers. It was hard to get that sense of belonging there. I am generally a quiet person, and for folks who are quieter and introverts you don’t feel as left out in the WordPress community. People welcome you and it is very different between this community and the corporate world.
- We have a variety of diversity, inclduing people from many countries coming here, and finding it enjoyable. It gives me hope because I have been in other technology communities as the lone woman and designer in a room of developers who are men. WordPress has many things to be improved, as any other community. But this community gives me the feeling that things can be changed. I asked a question and it became a team. WordPress has the ability to evolve and improve, and there is an opportunity to make changes that can be little or make great, big things.
- I love to hear the positive stories about where we are, but for me the diversity and inclusion part is about who is not in this room, and who is not at a WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.. Someone posted yesterday that they do not feel welcome or safe at WordCamps. We should not ignore this and despite how far we’ve come and how diverse the group is, we cannot stop realizing that there is so much more work to do before everyone feels welcome.
- What is our status in diversity, not only on events, but within Make team collaborations. Where are the differences between the global and local Make teams, and do you see any interference or points.
- Local communities are disconnected from Make itself. It is a challenge to introduce a local community to what we do as the WordPress project. A lot of people at local Meetups are seeking help, and a majority of the time it is walking them through a problem, not introducing them to what the WordPress volunteer project does. It creates a sgnificant challenge in introducing more people to the WordPress project.
- If we are talking about Diversity and Inclusion, we have to talk about it in the Meetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. community. How do leaders include you, how safe do you feel, and how do they ensure that you return because you feel welcome and safe enough. If you return over time you will learn about the Community and Make teams.
- How do we handle bad actors in and outside of the community?
- One of the significant barriers of having people involved is the language barrier. A lot of the Make pages are only in English, and a lot of people cannot read English. Polyglots cannot increase participation in the project because of the language barrier. Many people who don’t speak English do not feel comfortable reaching out about getting involved. How do we get the non-English community feel more welcome to get involved.
- Translation tools have been very helpful for me to get involved as a non-English speaker
- WordPress is very open to join, but it is hard to stay for some people. The belonging is not there for everybody. WordPress a toxic positivity problem. We try to make narratives to change minds to get people who are prejudiced to be involved. There are people who cannot be here because their abusers are here. I do not feel safe at conferences where I have spoken out about racism, sexism, and homophobia. It got bad enough that if some people have not stood up for me I would not still be here. How do we do that for everybody? I am one person who stayed, but there are people leaving and losing diversity because people are scared. When people do things and make mistakes we should do something, and we cannot let bad actors blossom in the community. They are not even the best of the community. We have to be strong and speak up but it should not be on us to do so. People don’t want to be calling out their friends, but you should be the one doing so, as you have a better chance of changing them than a stranger. We are a global community. When it is positive it should be global, and when it is negative we should be global.
- Where does the Code of Conduct apply, and where doesn’t it? Where can we apply things and where can we not? As a community, people can come out and do things, but where as WordPress can we come out and regulate and mandate, and where do we have influence? We have a lot of issues because of this.
- I am new to WordPress and I am more of an observer. It is a hard place to get more diverse. Unfortunately the people who run the events can take over the conversation sometimes. As an educator I want to make sure that you are included and will try to call you to come into the conversation to ensure that you are heard. It is ok if you come and are lurking but we have people who tend to take over conversations and ensuring that we introduce ourselves to people to get them involved.
- I have tried getting involved in some teams but onboarding is hard, and it took time to build my confidence to speak up a bit more. Everything is a learning moment. We should be learning every day to be better and support people around us.
- Instead of organizing a Meetup sometimes we will do things like have a coffee chat or at a sponsor office. Sometimes instead of having a session we will just have talks so that people can be part of a group and we try to bring in newcomers. Most of the people coming to Meetups are coming for their own personal goals. We will try to accommodate them so that they return for the next Meetup and next event. We tell people that if you are attending a Meetup you are a part of the community. We tell people that you do not have to think that you have to be a programmer to be a contributor to an open source project. We tell people to come, write documentation, translate a few strings, post a video. We want people to feel safe to be part of the community. We also have events like parties, and organize in a WhatsApp group. This is going good. We want to have different contributor days, for specific groups and types of contributions, like core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. one day, and documentation another.
- How do we deal with something that happens when someone is being intolerant? Should we ask them not to come
- I have held events where we have threatened to be sued. We have to take someone’s free speech into consideration, and there is a fine line that you have to draw. You don’t want to position yourself where you lose everything when someone pushes the right buttons. You can speak up and say that you don’t feel comfortable, but to tell someone “leave” is a very slippery slope. It is hard to keep ourselves in a way that we do not have to deal with legal issues.
- We have had issues with someone at our events who had made physical threats to members of our team, in part because of our marginalized status. We already had issues with this person and WordCamp Central Website for all WordCamp activities globally. https://central.wordcamp.org includes a list of upcoming and past camp with links to each. was aware of them. But it took too many meetings, one-on-ones and finally having threats made in a written format that could be shared before something was done.
- There is a lot of talk about regulation of social media right now for how it influences children. It is hard to see when it is something that you were not born into to see how that works. The current political climate is how we have had a presidency that for four years folks emboldened to say whatever they wanted to say. Before what was unacceptable to say, or only said behind an avatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name., is no longer unacceptable to say. It now becomes legally ok to say things. There are other parts of the world where there are other similar political issues.
- Some people engage and organize online, and some people do so via their local communities.
- The world has a variety of different laws, but we have to tailor based on what some parts of the world define for ourselves, such as GDPR in the EU, and their position making us shift accordingly. Depending on where you are in the world you may not have those checks and balances. There are a lot of things that I see about where you are breaking the law. We don’t just have to deal with various cultures, but also with various legalities around the world.
- There was a member in our community who wanted sign language interpreters and it had to be with a specific company. This person was very vocally threatening with me about it. I had to have conversations with Central about how to handle it, because they can handle the legality but myself as an individual I cannot handle that.
- When we look at someone we cannot tell if they are all seeing the same things to consider as we are.
- The biggest thing that I wanted to bring into the conversation was the idea of community responsibility. Not just what the Community team does about bad actors, but what we as community members do. There’s a level of respect, curiosity, and response that I think is a default in WordPress community interactions. One of the strengths that we have as part of a diverse community is that we can continually learn from people who have different backgrounds and experiences. If we are not growing and adjusting we are not learning. The community has grown tremendously in accepting others, but we are going to see those bad actors. What can we do as a community but also individually in doing something about those bad actors.
- If you want to make people feel like they belonging, what do we as a community do about bad actors? We cannot just let it go. Personally I would not feel that I belong and feel relaxed in an environment where I do not feel like a human being. We need to do things to protect the community in our Code of Conduct.
- We could come up with a digital policy for the Code of Conduct for how people interact digitally around the community.
- Your freedom does not allow you to interfere with other people’s freedoms.
- Punishment could be applied for specific infractions, and what people can do, for instance being banned from events for a specific timeframe.
- We had an incident a few years ago where someone had to be banned for a year and is not going to be an organizer when brought back.
- Respect others. It is not ok to attack other people online.
- We do have a community-wide Code of Conduct that does address both in-person community spaces, and online community spaces as well. It is a specific scope. Conversations on social media can become hostile and they are outside of what we consider the core of where we participate. It is challenging to consider where we can have influence from a community support perspective.
- We have been building out this Code of Conduct as well as an Incident Response team. There is a lot that goes into reaching out to people and supporting community members as best we can. If there are edits that we want to make, we can improve it.
- Toxic Positivity It is already big that we are talking about it, but some people have to realize that a conversation about diversity an a willingness to improve is important and not making it look like it is a fairy tale.
- I see someone with an opinion that I absolutely do not appreciate, and is hurtful and wrong, and I see them being scolded at and attacked online by people trying to defend inclusion. It was very much counterproductive, while responses from someone saying that they want to help and educate was taken positively and agreed upon. If there is a chance to educate someone and there is a chance to do something about that and specific people don’t always have to be defending, there are ways to keep people involved and try first to have conversations with someone to show why their position is wrong and hurtful.
- There was an incident of racism in the community and I had to talk to people that I considered friends and I thought that we’d had an understanding. But they flipped and called the reporters liars, and the incident response team stepped in and helped, but not a lot of people know about them. We found out that the person had multiple violations already. Luckily we had evidence of what these people did.
- People can be educated and people make mistakes. But you have to be willing in good faith and honesty to take that help. The Incident Response team will step in and help, but why did it have to get to that? How can we stop it from getting to that point where people are on their fourth or fifth chances.
- We don’t always know the right action if it is not your exclusion. Lots of instances that we are seeing time and time again where people who are marginalized have to stand up for themselves and be the ones to educate, and that is wrong. The people who are being attacked should not have to do the work, and those of us who are privileged should be stepping up, going on a quest for education, learning what support is needed, and offering it.
- Exclusions impact greatly in a range of spaces outside of just Meetups and WordPress. Tokenism does not help in those spaces. This has happened because of a scarcity in the community spaces and I do not want that to happen.
- Doing incident reports is one of the hardest jobs. If you love the community and have to see the not so great aspects of the community, it is hard to see. We nee
- The amount of support that we can directly provide is limited legally, but as people we still care and want to help. Where we can help is collaborating with incident responders for knowledge share to offer support.
- What can we do in our work to make active contributors feel seen, heard, and belonging?
- One thing that has been done for regional conferences of a different open source project is having people specifically available both online and in person at smaller events to help with incident response. There are more people present who are not just organizers to respond to attendees in that space. We tried getting people with varied experiences. We have a response playbook that is public for events that we use when an incident occurs at the events. After the event we summarize and anonymize all of the incidents that occurred and what was done about them and publish it for transparency.
- What would it take to proactively make events and other contributions safe for people? There are different barriers for different people and we can only know about what challenges we are facing ourselves. As much as some of us may want to contribute to events, we cannot take on certain roles. We could ask community members to fill a form to proactively address issues that they may have, to ensure that we are proactively being welcoming to those people.
- Letting people know how they can feel going to an event, such as a tech event as an older woman who is not a developer.
- Amplifying incident response teams. A lot of people don’t know who to go to when there are problems, with mediating, helping with people who made mistakes and want to learn, etc
- Is there a way that we can start learning laws from different parts of the world to solve some of our challenges with a response team and education. The Incident Response team has some access to the legal team for Automattic pro-bono
- An idea is to create advocacy and ally workshops to educate the rest of the community as to what that entails.
- We have a Code of Conduct, but if we create a DEIB statement that says something along the lines of if you are part of a marginalized group, whether visible or invisible, you are welcome. If you
- Three suggestions: making the language more inviting on bringing forth accessibility needs for events. Currently the form for WordCamp tickets asks you to list accessibility needs, but does not invite people who may not feel emboldened to share that those needs will be heard and a good faith effort will be made to address them. Second, trying to be transparent where possible what the limitations of a Code of Conduct would be, for things like legal reasons. Third suggestion, ensuring that a transparency report is published after events to address issues that came up, to avoid toxic positivity and ensuring that there is a bit less second and third hand reporting.
- There is an organization called CHAOSS (chaoss.community) to help with open source groups, including a knowledge base with metrics around public health and safety. They have a badging system that linux events are required to go through to organize.
- We asked people with experience organizing events to put some of that experience and ideas on things that went right and wrong in a document for others to review. Having that documentation will help others to get ideas and practical knowledge on how to improve events. My idea is to create a group around having this institutional knowledge available as a resource.
- The pandemic gave accessibility to Meetups in an interesting ways. There are no Meetups near me, and it is hardly the most remote place. We need to create an online experience as much as possible. If you have a Meetup and can stream it and share it, please do that.
- We have an aging contributor pool and we need to think about how to expand it to include younger contributors.
- We need to address other things beyond just community events, such as having onboarding available in multiple accessible formats, and they are not yet. If something is available in only one format, we need to make sure that they are available in other formats to ensure that we have different contributors eventually.
- We could publish a menu guide at WordCamps to ensure that people can attend an event and ensure that everyone has some form of food that is protein for them. We cannot expect all organizers to know what fits for a vegan or gluten free diet as an example. We could include a template for adding menus on WordCamp sites.
- I think that we can start with something simple and concrete for how individuals can contribute.
- One thing that we talked about is what happens when people cause bad situations but we haven’t talked about what happens when team leads are the ones that are causing problems. When someone in leadership makes disparaging comments I have to decide to ignore it or tell people to try to talk about people in different power dynamics.
- There should be a separate process for project leadership to address power dynamics. It’s a whole different way to be held accountable. It shouldn’t just be holding them accountable, but requiring that they go through extra education, to ensure that they know a bit more.
- We can look to other organizations that have had to deal with things done by higher ups, and see what they have published and how they have solved problems. For instance, in the Drupal project.
- The WordPress project intentionally keeps ticket prices as low as possible to make events accessble, and we don’t cut things like captioning when the budgets don’t work. We need to share the intention about how we spend our funds to ensure that sponsors see that and
- Future community summits could have captioning to help when people cannot as easily hear speakers. We need people to speak slowly and project and not cross-talk. Can these be part of the guidelines of events, and add specificity.
- As a teacher, a suggestion is that we can incorporate language like, “ouch” to say when people say something harmful and stopping to address it. Or “elmo” to indicate “everybody, let’s move on” when someone is going on for too long.
- One thing that I’ve heard over and over is that, “they should already know” for things that things that we assume that people should know, but not everyone knows. I would rather that more is put in the handbook even if we think that people should know them, so that we aren’t put in the position of having to ask uncomfortable questions.
- Sometimes it is hard to be the person to step up and say something even as an organizer. If you are an organizer, try to recognize when people are having issues or seeing an issue and stepping up on their behalf.
- There is a dedicated slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, #deib-working-group on the Making WordPress Slack
- How do we honor the very best of our community? What can we do to address the things that prevent that from happening.
- Belonging is a new word to this acronym. It’s great to have belonging here. Because once we invited people in, how do we sustain their presence. How do we make them want to be here?
- The WP community can be an example for the world, as we are ahead of the curve in bringing people together.
- The WP community has never made me feel uncomfortable or unwelcome, which is a first given many communities I’ve been part of. However, DEIB is a never-ending project, because there’s always more to improve.
- When talking about DEIB we also have to think about barriers. Access for everyone isn’t the same. And we need to acknowledge that people can be in the majority in one aspect, but in a minority in another way.
- India is a land of variety. Different cultures, different languages, different foods. The WP community is a kind of ecosystem. It’s adopted many people. Everyone can come in and contribute.
- This community is a very open community. There’s a place for everyone in our community. I feel I can do what I do, and be who I am in this community.
- What we haven’t quite done yet in this community is pay attention to invisible disabilities or needs.
- We need everybody here.
- We should think beyond these flagship events. Where do we see the state of our online community? What’s the state of our local communities?
- Local communities are disconnected from Make itself. As a meetup organizer, I see that many attendees are beginners in WP. They’re not even aware there’s a global WP community. Not everyone organizing events is aware they’re then part of a team.
- If we’re touching about D&I, we have to talk about meetups and how we’re supporting meetup organizers integrate people into those local communities.
- Part of DEIB means making the WP community slightly less welcome to those who are not open to DEIB. So how we deal with bad actors?
- I want to echo the disconnect between local communities and the Make project. One of the challenges there is the language. Not everyone can speak English. This language barrier brings up the next barrier.
- WordPress is very open to join, but it’s hard to stay for some. The belonging is not there. If something happens, we try to out-positive it. But we seem to think that with a Disney-movie ending, it will all be fine. But in reality, it’s up to the same people over and over again to fight this fight.
- When there’s a bad actor, yes we need to educate them, but maybe we also need. People are afraid to call out their friends, but that is what’s needed to make things better.
- Where does the COC apply, and where does it not? Where can regulate, and where can we only influence?
- Everything is a learning moment. We should be working every day to improve ourselves.
- Most people who come to our meetups are mainly looking for help. Most of them are in a learning curve. So oftentimes we organize meetups that a basically a chit-chat, instead of doing a session. We also continue to tell people they don’t have to be a programmer.
- When someone is crossing a border about inclusivity, is telling them not to come to an event non-inclusive?
- [General response] No.
- As an organizer, there was a prior attendee who made me and other feel physically unsafe. That made organizing very difficult. It was challenging at the time to get the support we felt we needed. It was disheartening that it came to the point where it needed to escalate to a physical threat via email before action was taken.
- We have generations that didn’t spend the majority of their life on social media. It’s important to recognize that there is a generation that is completely influenced by social media.
- We are in a situation where things that in the past were only said from behind an anonymous avatar online are now said in-person, due to changes in the cultural and political climate.
- We’re a world-wide community, but we’re not dealing with the same laws everywhere. So beyond different cultures, we’re also facing different legal structures.
- If you want to make the community more diverse, we have to respond to bad actors. We can’t let it go. We need to protect the people we want to keep in the community.
- We do have a community code of conduct, that addresses both online and offline parts of our community. Sometimes it’s outside of the scope of what we (WP) can regulate. WP does have an Incident Response Team that’s handling COC violations within WordPress. make.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//community/handbook/code-of-conduct/
- Create more awareness for the IRT.
- Create list of things that make people feel unsafe/unwelcome.
- Create an inclusivity statement that we publish in our community to help people understand expected behavior.
- Create a (non-exhaustive) overview of the spaces where we can interact.
- Have a transparency report from the event’s IRT in the post-event wrap up.
- Learn from https://chaoss.community/.
- Create resources to do better. For example an example vegan menu to help local organizers get that right.
- Share the list of names of people who are on the IRT, to make clear to the community that it’s not just Automatticians. People from around the world are included and they’ve had “formal” training.
In the first half of the session we have mainly discussed the following.
- What is DEIB
- Current state of DEIB
- Potential improvement
- Collaboration & Support
- Scope of a DEIB Team
Key Points came out in the discussions are
- WordPress’s growth continues. We are a very big team now.
- WordPress is a never ending project
- The WordPress ecosystem accommodates thousands of people from different backgrounds(like nationalities, languages, religion, cultures, politics, beliefs etc..)
- The Make WordPress project is also vast and has multiple tracks.
- We are a very diversified community.
- Because of diversity our each local team will be different & has many barriers
- Diversity will be different for each local team
- Our community represents multiple interests
- WordPress is very open to join, we have to maintain that
- Therefore we need a team to take care of both
- The biggest challenge is we have to make sure the community accessible to all
- The next generation is coming to the stage now. So we have to make sure a smooth generation change
- We have to welcome & open new people & ideas always
- The biggest challenge is accommodating new people & transforming them as contributors
- So the Sustainability of contributors matters
- Transparency in all actions are must for it
- We have to consider the feelings of new & existing people
- The community should be open to all and there should be any judgement based on their background
- We have work on the documentations to keep the resource live & easy accessible
- Because of language barriers we can consider of translating documentations
- Each one should be considered equally(not matter of gender & race)
- The local community should be connected with global community
- Meetup Organiser should make sure everyone’s voice is heard
- Document the meetups if possible
- Everything is a learning moment. So support the people & their ideas around with kindness and tolerance
- We are living in a era of extremism so we have to consider the people with equality
- It will be great if we can consider digital code of conduct. It will be more helpful for the people
- We can also regulate the code of conduct often
- We are from different continents & countries. So may have to consider the localization of the code of conduct with extra attributes/terms
- We should start to train the people about the code of conduct
- Clear & easy guidelines for the newcomers specially
- Global & local team to monitor and take actions if any incident happens
Actionable Items to improve DEIB
- All should feel as more welcomed
- Events should be more aligned to DEIB
- Looking for make our work(contribution) more sustainable
- Raise more awareness & committee/team for code of conduct
- We have to take care of disabled people, their requirements will be different. Encourage participation & contribution from them
- Keeping an ongoing list for people from all backgrounds(Organiser, Volunteers & participants). It will welcome & encourage more people
- Local communities face different legal issues. A legal handbook to refer for the working group
- Create advocacy and allyship. Classes for organisers
- Educate, meetup members & conduct workshops.
- Transparency & inclusivity statement
- Have a form people can fill our(even anonymously)
- Ageing(balance between ageing contributor & new one)
- Incorporate wording that lets people to know that it is okay to ask for accommodation on form
- Transparency around what can & cannot be done
- Transparency reports around issues to clarify and avoid rumours
- Publish official responses
- Checkout documents the other organisations have already created and adjust accordingly. Example for those documents are Drupal & https://chaoss.community/
- Create online experience as much as possible
- Make information/meetups available through more than one format
- A menu guide for WordCamps
- We can be friendlier & more open as a community. Proactive with other community members also
- A separate process for the higher leadership
- Training for the leadership
- An open forum to speak, report regardless of the level of leadership
- Setup as an organiser
- A WordPress Language
- Add as much info as needed more to the handbook
- WordPress events are budget events. We have to keep the sponsor aware about this
- Budget Transparency
- Text capture in next community summit
The 2023 WordPress Community Summit has come to a close, marking another milestone in our journey to shape the future of the WordPress open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. While the event itself was a whirlwind of ideas, discussions, and collaborations, the real work — building upon these insights and translating them into action — has only just begun.
Notes from each Summit session are now available at make.wordpress.org/summit. For your convenience, you can view a complete list of Summit sessions along with their corresponding notes here.
We don’t want this to be a one-way conversation. We urge everyone in the WordPress ecosystem to delve into these notes, share your comments, and encourage others in your network to do the same. Your feedback is not just welcome – it’s essential. By sharing and discussing these notes with your teams and fellow WordPress enthusiasts, you’re ensuring that our collective vision for the future of WordPress is inclusive and well-informed.
Let’s continue to shape the future of WordPress together. Your voice, insights, and passion are what drive this project forward.
From the session schedule:
One important way to welcome new users, builders, and extenders of all ages is to create excellent curriculum or educational experiences around WordPress. To address this gap, the WordPress community has held KidsCamps and launched Learn WordPress. This discussion will focus on the future of WordPress education, from topics to teach, to levels of experience, to curriculum for specific age groups.
Facilitator: Benjamin Evans (@bsanevans)
Notetaker 1: Courtney Robertson (@courane01)
Notetaker 2: Kim Coleman (@kimannwall)
Title of Session: Refreshing the contributor pipeline
Notetaker 1: @mikachan
Notetaker 2: @evarlese
From the session schedule:
A healthy contributor pipeline requires new contributors! Prior to the pandemic, our in-person events were key to welcoming and engaging new contributors. With events slower to return, how can we continue to connect with and bring in new contributors? This discussion will explore where Make Teams are currently seeing new contributors from, and brainstorm what kind of outreach the WordPress project could do to refresh the contributor pipeline. An additional focus for this discussion will be around how to continually retain new contributors.
- Community Team spent 2022 re-activating the community.
- The Docs team is an inspirational team, both in how they attract new contributors and how they support people longer-term 🍪
- The pandemic immensely impacted the community; there is a lot of work done at in-person events and we lost that.
- There is a new Contribute page on Make WP.
- Ideally, we’d also have a “getting set up” page that includes how to set up Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., find your team meetings etc.
- There are no longer enough people to help organise in-person events as the momentum has been lost post-pandemic.
- The need to go to the larger WordCamps because the local ones no longer happen.
- People tend to be more passionate at local events.
- Personal connections are important.
- Recent mentorship program has been extremely successful.
- What is the reward? What are people getting from contributing?
- Reframing why we contribute – what open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. is on a broader scale. You’re helping the wider community, keeping the software free.
- Badges are an under-utilised component, and WP profiles could be improved.
- Lack of contributor data.
- Reframe “office hours” to AMAs – everyone can help everyone, eases the pressure on the usual few people.
- Big challenge is that there is a completely different repo for every single team. Overwhelming. GH and trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. are very overwhelming for new contributions. Do we need some consistency across the different repos?
- We should recruit more contributors from external projects.
Action Items/Next Steps:
- Create a “getting set up” page alongside the new Contribute page, for each Make team.
- Create a contributor tool CTA that takes people to the Contributor page.
- We also need a clear pathway for people who get stuck or need help – add a direct link to the public-mentoring channel to ask for help on anything from the contributor team handbook pages.
- Recruit more organisers for in-person events.
- What can other teams learn from the Docs team?
- Revisit Google Summer of Code as a way to recruit new contributors. Look for other ways to recruit externally to the WP community.
- Set up support for existing contributors to become mentors to new contributors.
- Be consistent with what’s included on each Make team handbook, how can people ask for help? Add link to mentoring channel.
- Explore introducing a more immediate attribution system – get the “feel good” factor early on in the contributor journey.
- Are there more online workshops that the Make teams can create?
- Break down the large YouTube tutorial videos into shorter videos.
- Can we look into how we can improve the badge system for each Make team? And the WP profile page in general.
- Explore creating events to attract specific types of contributors – e.g. a design event
- Make incentives more transparent, make it easy to find out what people did.
- How can we handle data better? Data can help with the incentives, especially for contributor day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., similar to a release squad.
From the session schedule:
The Five for the Future (“5ftF”) program can help ensure the long term health of WordPress’ contributor pipeline. To make 5ftF as effective as possible, strong participation from 5ftF companies and project-wide understanding of Make Team needs and priorities is required. As such, this discussion will focus on two related topics:
- How we can more readily identify priority needs and opportunities and match them to 5ftF contributors.
- How to incentivize and facilitate further participation to the 5ftF program.
Facilitator: Jeff Paul (@jeffpaul)
Notetaker: Kim Coleman (@kimannwall)
From the session schedule:
WordPress contributors are incredible. How can we better acknowledge and celebrate the important contributions made, and recognize the impact they have for the WordPress open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project? This discussion will explore where we currently are not recognizing contributions, and how we can more appropriately and readily show appreciation for contributions and contributors.
Facilitator: Julia Golomb
Notetaker 1: Jonathan Desrosiers (@desrosj)
Notetaker 2: Bigul Malayi (@mbigul)
- Current state of props across project
- Props are not uniformly tracked across various teams.
- Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does the best job, but only on the SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. side with “Props x, y, z.” in commit messages.
- All contributions boil down to 1 prop, regardless of the amount of effort invested or overall impact.
- Props are collected during beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RC A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. of each release cycle. Some of it is automated, but a good amount of manual work involved.
- Inevitably there are always contributors unintentionally left out.
- Different teams have different ways to recognize contributors.
- Original purpose of props in a core release: to recognize lots of work that is not apparent by just looking at a commit (design, testing, code review, etc.).
- The goal was to incentivize behaviors we want to see from contributors.
- Why are there invisible contributions at all?
- Other open source projects were discussed:
- Drupal: Attributions are discussed a lot.
- Drupal.org pages can be used as a resume. Not as true for wp.org.
- They’re highly automated.
- There are different ways of breaking down one issue into multiple phases instead of one epic.
- Credit can be received multiple times for each ticket (testing, coding, designing, etc.).
- can create sub tasks for the Drupal Conference. Like Logo creation, financing, writing articles on event sites etc.. Once the task is finished the credit will be shown in Profile.
- The Drupal profile has many type of credits & attributes
- More easy access to the statistics of the contributions
- It also has a dashboard for contributors
- Credit is weighted.
- Some attribution farming occurs.
- Different contributions based on experience. There is a structured phase out of credit to try and encourage positive progression to more advanced contributions.
- Drupal embraces company and organization involvement, giving recognition to corporate entities that contribute.
- Drupal allows enterprises to create profile pages like this – https://www.drupal.org/agileana. Their contribution is also listed like an individual. Like Sponsorship, Supporting Contributors etc..
- The profile page also have section to list the mentors of a user
- Corporate citizenship is weighted by the last 90 days, affecting how they’re displayed on drupal.org in a few ways.
- Is this what Five for the Future is meant to do? Different discussion, but does there need to be more incentivization for companies to participate?
- Drupal uses a “novice” tag instead of “good-first-bug”
- Linux Foundation has a badge system used to give attribution.
- Why are credits not grouped by team or separated out on the Credits page for a release?
- That page was meant to reflect everyone who contributed positively to that specific release. Who pushes that release forward?
- Drupal has team recognition unrelated to a release.
- Other teams have been left to send credits to release squads or figure out their own methods to give credit.
- Where do we currently give credit outside of a release?
- wp.org profile Badges
- #props channel in Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
- Translators receive credit in a separate section on the credits page when a non-default locale is being used (though this is tied to contributing to a specific version number
- Openverse does not have a formal way to recognize contributions besides badges.
- This Week in Core posts on make.wordpres.org/core
- Commits are not always the right way to recognize contributions or quantify effort.
- Badges are a form of credit/props
- Each team is on their own to come up with the qualifications to receive a badge.
- There is a good amount of badge hunting that occurs.
- Badges are one thing that makes wp.org profiles more like a resume.
- Majority of badges are currently assigned by role.
- Training team has a great outline of how to receive a badge with task and count requirements outlined. They were praised multiple times for their related processes and documentation.
- Some teams are less structured.
- Photo team gives out badges as soon as someone shares a single photo in the directory.
- There are gaps in badges that can be given out.
- All flagship contributor days have virtual contributor days. Could add a virtual contributor day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. badge for those folks unable to travel.
- Could explore tiered or “super user” badges to encourage contributors to advance and contribute more.
- Teams should decide what is appropriate for them for issuing badges, but having documented best practices, or guidelines would be helpful for this.
- Badges are binary in nature. How can we add nuance, leveling, etc..
- Some teams have multiple badges. Openverse, for example, has team and contributor badges. But most contributors are sponsored. There is a higher threshold to cross for unsponsored folks. There is a disadvantage.
- Badges could have an expiration period
- This would discourage badge hunting.
- Incentivize the actual behavior we want.
- They shouldn’t disappear entirely, though. They were important and valid for a point in time, and that history should be preserved.
- Badges could also be active or inactive.
- Expectations and removal criteria must be clear to avoid mix ups and hurt feelings.
- It’s important to recognize contribution where it matters to the person investing the time and effort.
- There are times when both external and internal recognition are important
- Where else can contributors be recognized that may be more impactful?
- Releases are not the event to recognize for all teams within the entire project.
- Some teams work on different timelines. Have different deadlines, etc..
- Props chasing does occur.
- How do we nudge people to make more substantive contributions as they learn and grow?
- Sometimes this will be an indication of the limits of their skills.
- Contributions are accepted in all forms from everyone, regardless of size, perceived impact, or team/component.
- It’s totally fine for someone to find a comfort zone where they are happy and live forever.
- The Lead Developer title currently does not really mean anything. Especially to new contributors.
- Previously, this may have incentivized some folks to work harder. But it’s currently unattainable.
- What else can we offer along these lines and at what levels to hopefully incentivize better?
- There are considerations to be had around sponsored vs. unsponsored contributions.
- The number of hours is not a great way of quantifying contributions either (see 5FTF).
- It’s difficult for contributors to meetups, WordCamps, etc. to quantify a regular amount.
- This creates a perceived disadvantage to self sponsored folks vs. sponsored ones.
- Being sponsored by a corporation to contribute is recognition in itself. That is meaningful to many in the community but not all.
- Visibility and transparency into contribution should be a goal.
- It creates a cross team understanding and excitement for collaboration
- Quantifying contribution is difficult and not uniform.
- Writing make posts can be a big deal that can require days of work.
- Creating well worded and detailed issues can also be time intensive.
- See above about it being difficult for contributors to meetups, WordCamps, etc. to quantify a regular amount.
- Design team does a ton of work that’s not represented in the final deliverable. Wireframes and design iterations, for example.
- For Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, it’s difficult to juggle GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ vs. Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/./SVN.
- Code commits are easiest but a very small piece of the puzzle.
- Docs commits are gamified the most with typo fixes, etc.
- Hard to decide who should receive attribution for changes.
- Discussions, triage, etc. all deserve credit.
- Gutenberg recognizes contributors for all public plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party version releases.
- Could the People of WordPress series be used to recognize contribution efforts as well as unique contributor journeys?
- Can the release page be expanded to recognize different groups?
- Legacy people are important to all aspects of what we do. How do those contributions get properly recognized?
- Having strong clear automation helps avoid bias. Anytime a human gives credit it opens the door for some bias, whether intentional or not.
- WordPress has a bad habit of being internally facing and not interacting with other communities. What can we learn from mistakes and triumphs for other projects and communities?
- Who is the audience for the recognition types being discussed?
- Be very clear about problems being solved.
- How do people find out who to talk to about what?
- Titles represent recognition to peers.
- Badges represent recognition for self or prospective employers.
- How to recognize work in siloed communities
- Travel funds could be a form of recognition to enable travel.
- Emeritus committers is a potential example of how to have an “archived” or “inactive” contributor state.
- Fair and accurate recognition is a key to a thriving open source project. Contributors must feel valued.
- All forms of contribution should be recognized.
- Behaviors that the project wants to see should be incentivized by any credits system.
- Contributions need to be recognized where it matters most to the contributor.
- There are different audiences for different types of recognition.
- There are many different types of contributors (unsponsored, sponsored) with many different backgrounds (design, development, translations, testing, etc.).
- Releases may not be the right event to celebrate recognition for all teams.
- Event organizing (WordCamps & Meetups) takes lots of time and effort, but receive less recognition.
- Any credit system adopted must stand on its own, independent of the tools being used.
- There should be as little invisible contribution as possible.
- Strong automation helps avoid any potential bias.
- Contributions are not weighted by level of effort or difficulty.