WordPress Sustainability Team Badges (formal decision)

The WordPress Sustainability Team offers two different team badges:

  1. WordPress Sustainability Team Badge
  2. WordPress Sustainability Contributor Badge

The two Team Badges are common use also applied by other WordPress teams like the Documentation and Hosting teams.

The proposed criteria for obtaining the badges are:

  • In order to obtain a WordPress Sustainability Team Badge you are actively involved as a leading team member by:
    • Having the role of WordPress Sustainability Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.(representative)
    • Having a leading role in creating documentation
    • Having a leading role in developing code for the team
    • Leading a Sustainability table during a WordPress Contributor DayContributor 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/.
    • Having a leading role for the WordPress Sustainability GithubGitHub 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/
  • In order to obtain a WordPress Sustainability Contributor Badge you are actively involved as a performing contributor by:
    • Regularly participating in a meeting
    • Regularly participating in projects
    • Adding some documentation (but not leading it),
    • Contributing to code for the team (but not leading it)
    • Commenting on the Sustainability Github
    • Mentorship Coordinator
    • Team Meeting Coordinator

As the team is still developing itself, the overview above may not be complete yet and can be subject to change. Changes will be communicated at make.wordpress.org/sustainability/. Feel free to leave comments for improvement below.

Badges can be obtained by contacting one of the WP Sustainability Team Reps: Nora Ferreirós, Nahuai Badiola, Csaba or Thijs Buijs. Badges are not distributed automatically yet.

This post is a formal decision based on the lively discussion at Github, the proposal for a formal decision and the comments below that proposal.

Sustainability Chat Agenda, March 1, 2024

The next meeting is scheduled with the following details:

When

01-03-2024 12:00 UTC

Where

At #sustainabilty channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Agenda

In this meeting we will focus on the onboarding experience for (new) contributors. Onboarding is related to all our available tools (Slack, our blog and GitHub) and should explain how we use them. The goal is to create clear guidelines for a smooth onboarding experience.

Other ongoing focuses are:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. Follow up on this project here and the last meeting’s comments here.
  2. WordCamp Handbook with sustainability ideas/guidelines. Learn how to contribute to this here and follow up on this project here.

If you have any updates on issues or projects that we have previously discussed, you are free to bring them up during the meeting.

Ideas or suggestions

Anything else? Please leave a comment if you want some topic to be discussed at the meeting that is not listed above.

Sustainability Chat Summary, February 23, 2024

The WordPress Sustainability Chat meeting took place on 23-02-2024 12:00 UTC on the Sustainability channel of Make WordPress Slack.

Agenda

You can check the initial agenda here.

We have work on the topics contributors prioritized in the last meetings:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. Follow up on this project here and the last meeting’s comments here.
  2. WordCamp Handbook with sustainability ideas/guidelines. Follow up on this project and read some guidelines on how the work is happening here.
  3. Sustainability Team self-approval system. This proposal has been approved and closed.
  4. Sustainability Team Badges. The process goes ahead without objections.
  5. Improving onboarding for new contributors and roadmap for mentors. It’s not currently clear for mentors or newcomers what we are working on, what’s next, how contributors should proceed for contributing (e.g. in the Google Docs documents or GitHubGitHub 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/ projects), the team’s priorities, etc. In order to improve this situation, some suggestions have been dropped:
    • Create a provisional onboarding post for being linked in the Welcome Box. This provisional information should be updated as projects and priorities progress or change. In the meanwhile, a proper and official onboarding guide should be created.
    • Create a clear and understandable roadmap for everyone, including newcomers.
    • Change the date and the time of meetings.
  6. Collaboration between 5ftF and the Sustainability Team. @patricia70 announced her aim to collaborate in the 5ftF project and to be a bridge between it and our team.
  7. Introducing the WordPress Core Trac Sustainability Focus. We celebrate this post the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team has just published.

Attendance

You can find the attendance thread here.

Next meeting

We look forward to seeing you next 23-02-2024 12:00 UTC. If you have any suggestions for the next meeting agenda, please, leave a comment on this post.

Sustainability Chat Agenda, February 23, 2024

The next meeting is scheduled with the following details:

When

23-02-2024 12:00 UTC

Where

At #sustainabilty channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Agenda

We will continue the projects we are currently working on as a priority:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. Follow up on this project here and the last meeting’s comments here.
  2. WordCamp Handbook with sustainability ideas/guidelines. Learn how to contribute to this here and follow up on this project here.

There are other issues that may require our attention right now:

  1. Sustainability Team self-approval system. This meeting marks two weeks since the publication of the proposal. We will review if there are any counterproposals or suggestions and, if none, we will consider the system approved.
  2. Sustainability Team Badges. The guidelines proposal for this have been published, and the final decision will be made at the March 1st meeting. You can share your thoughts on Slack or directly in the post.
  3. Sustainability Team video presentation. Team Reps are going to record a short video to present the team. You can share here your suggestions or thoughts about the content of the video.

If you have any updates on issues or projects that we have previously discussed, you are free to bring them up during the meeting.

Ideas or suggestions

Anything else? Please leave a comment if you want some topic to be discussed at the meeting that is not listed above.

Sustainability Chat Summary, February 16, 2024

The WordPress Sustainability Chat meeting took place on 16-02-2024 12:00 UTC on the Sustainability channel of Make WordPress Slack.

Agenda

You can check the initial agenda here.

We have work on the topics contributors prioritized in the last meetings:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. See progress here. There was a discussion about whether it makes sense to use estimations (actual numbers) of CO2 emissions to compare the impact of web pages. Participants seemed to agree that (at least) spreading awareness is a good reason to do so.
  2. WordCamp Handbook with sustainability ideas/guidelines. Follow up on this project here.
  3. The Welcome Box has been published on the site (see above :-)).
  4. The travel information page of WCEU 2024 has been updated with some contributions of our team.
  5. Sustainability Team self-approval system seems to get support and will be added to the handbook.
  6. Attract new contributors and engage the existing ones. A question was asked for a short introductory video about the sustainability team (as well as for other teams). Feel free to contribute.
  7. A post has been published about the Sustainability Team Badges.
  8. Open Website Alliance. Reflect on the formation of the Open Website Alliance which was the result of the collaboration between the Drupal AssociationOpen Source Matters (Joomla), the TYPO3 Association, and the WordPress Project around an open letter to the European Union. More info here.

Attendance

You can find the attendance thread here.

Next meeting

We look forward to seeing you next 23-02-2024 12:00 UTC. If you have any suggestions for the next meeting agenda, please, leave a comment on this post.

WordPress Sustainability Team Badges

The WordPress Sustainability Team offers two different team badges:

  1. WordPress Sustainability Team Badge
  2. WordPress Sustainability Contributor Badge

The 2 Team Badges are common use also applied by other WordPress teams like the Documentation and Hosting teams.

The proposed criteria for obtaining the badges are:

  • In order to obtain a WordPress Sustainability Team Badge you are actively involved as a leading team member by:
    • Having the role of WordPress Sustainability Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.(representative)
    • Having a leading role in creating documentation
    • Having a leading role in developing code for the team
    • Leading a Sustainability table during a WordPress Contributor DayContributor 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/.
    • Having a leading role for the WordPress Sustainability GithubGitHub 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/
  • In order to obtain a WordPress Sustainability Contributor Badge you are actively involved as a performing contributor by:
    • Participating in a meeting
    • Adding some documentation (but not leading it),
    • Contributing to code for the team (but not leading it)
    • Commenting on the Sustainability Github
    • Mentorship Coordinator
    • Project Manager
    • Team Meeting Coordinator

As the team is still developing itself, the overview above may not be complete yet.

Badges can be obtained by contacting one of the WP Sustainability Team Reps: Nora Ferreirós, Nahuai Badiola, Csaba or Thijs Buijs. Badges are not distributed automatically yet.

This post gives an overview of the lively discussion at Github. It summarizes the discussion. Friday 1st of March 2024 at 12.00 UTC, two weeks after the publication of this post, we consider the content of this post as a formal decision. In the meantime feel free to comment below and to provide us with feedback to confirm the decision.

Sustainability Chat Agenda, February 16, 2024

The next meeting is scheduled with the following details:

When

16-02-2024 12:00 UTC

Where

At #sustainabilty channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Agenda

We will continue the projects we are currently working on as a priority:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. Follow up on this project here and the last meeting’s comments here. There were some questions proposed in the last agenda post to discuss about that didn’t have answer in the last meeting, so we could visit them again:
    • The WordPress Sustainability Plugin is an interesting initiative, but how do you plan to address the objections made to existing tools for estimating CO2eq emissions, especially as there is as yet no consensus? Wouldn’t it be more responsible not to use figures that, while satisfactory, are necessarily misleading and potentially detrimental to the original goal? See: https://www.debugbear.com/blog/website-carbon-emissions
  2. WordCamp Handbook with sustainability ideas/guidelines. Learn how to contribute to this here and follow up on this project here.
  3. Welcome Box. We already have the content of the welcome box, we just need to choose the design the works better (2 or 3 columns). You can follow the evolution on the issue 6 and the text in this Google Doc.

There are other issues that may require our attention right now:

  1. Sustainability Team self-approval system. The proposal for the guidelines were published last week. So far it has been a support to move it forward. If you have something to add/suggest this would be the moment.
  2. Attract new contributors and engage the existing ones. You can follow up the topic and leave your thoughts here.
    In the last week chat there was some consensus to focus our effort, for now, on details like the welcome box, the documentation, the handbook for events, the informative plugin, encouraging people to own a proposal or project and elaborate them. But new ideas are welcome.
    Also related with this, there was a suggestion that we add the weekly meeting date and the GithubGitHub 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/ link on https://make.wordpress.org/ (as some other teams have).
  3. Sustainability Team Badges. Which ones we should have and how they would be obtained. There are already some suggestions, you can join the discussion here.
  4. Open Website Alliance. Reflect on the formation of the Open Website Alliance which was the result of the collaboration between the Drupal AssociationOpen Source Matters (Joomla), the TYPO3 Association, and the WordPress Project around an open letter to the European Union. More info here.

If you have any updates on issues or projects that we have previously discussed, you are free to bring them up during the meeting.

Ideas or suggestions

Anything else? Please leave a comment if you want some topic to be discussed at the meeting that is not listed above.

Sustainability Chat Summary, February 9, 2024

The WordPress Sustainability Chat meeting took place on 09-02-2024 12:00 UTC on the Sustainability channel of Make WordPress Slack.

Agenda

You can check the initial agenda here.

We have work on the topics contributors prioritized in the last meetings:

  1. WordCamp Handbook with sustainability ideas/guidelines. Follow up on this project and read some guidelines on how the work is happening here. We have been discussed about making the handbook also for attendees and not just for organizers.
  2. Welcome Box. We have been working in/discussing about the layout. You can follow up the progress and give your opinion here for helping to wrap up this task.
  3. Sustainability Team self-approval system. After publishing a post with some guidelines on how this protocol may work, some comments were left there.
  4. Attract new contributors and engage the existing ones. There have been some suggestions on what to begin with and how far we as a team should be responsible for.
  5. Sustainability Team Badges. Some thoughts and suggestions had been shared on the GH issue. The intention is to wrap up this at the next meeting by publishing a concept P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. summarizing what has been said so far.
  6. Open Website Alliance. We have shared more information about this topic and discussed about our role on here.
  7. WCEU Website – Traveling to Torino page. There have been some updates about this project from @malgra (WCEU Communications, Marketing & PR Team Lead).

Attendance

You can find the attendance thread here.

Next meeting

We look forward to seeing you next 16-02-2024 12:00 UTC. If you have any suggestions for the next meeting agenda, please, leave a comment on this post.

Sustainability Chat Agenda, February 9, 2024

The next meeting is scheduled with the following details:

When

09-02-2024 12:00 UTC

Where

At #sustainabilty channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Agenda

We will continue the projects we are currently working on as a priority:

  1. WordPress Sustainability PluginPlugin 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 supported by the WP Sustainability Team. Follow up on this project here and the last meeting’s comments here. There’re some questions proposed in the last agenda post to discuss about:
    • The WordPress Sustainability Plugin is an interesting initiative, but how do you plan to address the objections made to existing tools for estimating CO2eq emissions, especially as there is as yet no consensus? Wouldn’t it be more responsible not to use figures that, while satisfactory, are necessarily misleading and potentially detrimental to the original goal? See: https://www.debugbear.com/blog/website-carbon-emissions
  2. WordCamp Handbook with sustainability ideas/guidelines. Learn how to contribute to this here and follow up on this project here.
  3. Welcome Box. Let’s wrap up the content of the welcome box, issue 6, text in this Google Doc.

There are other issues that may require our attention right now:

  1. Sustainability Team self-approval system. Announcement of the post with the guidelines for this suggestion made at the previous meeting.
  2. Attract new contributors and engage the existing ones. You can follow up the topic and leave your thoughts here.
    • We can discuss about onboarding, mentoring, define a common discourse (for events, talks, contribution tables…), documentation, etc.
    • We can also try to answer some of these questions (and any other related suggested):
      • How could we attract and guide the new contributors?
      • What can we do?
      • How can we explain them what we do and how can they help the team?
  3. Sustainability Team Badges. Which ones we should have and how they would be obtained.
  4. Open Website Alliance. Reflect on the formation of the Open Website Alliance which was the result of the collaboration between the Drupal AssociationOpen Source Matters (Joomla), the TYPO3 Association, and the WordPress Project around an open letter to the European Union. More info here.

If you have any updates on issues or projects that we have previously discussed, you are free to bring them up during the meeting.

Ideas or suggestions

Anything else? Please leave a comment if you want some topic to be discussed at the meeting that is not listed above.

Sustainability Team self-approval system

In the previous team meeting, it was suggested to establish a deadline system for approving changes or contributions when it’s not clear who or when move forward with them.

How the system works

As we often get stuck waiting for approval, we can manage a deadline ourselves to accept our own changes as follows:

  1. Make a change or a proposal. It may be minor contributions like a GithubGitHub 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/ Pull Request or the structure of a documents, for example. Check more examples below.
  2. Announce it in the team meeting. It is important to make it easy for everyone to be aware and have the opportunity of leave their opinion. So that purpose, we could:
    • ask for a topic to be included in the next meeting (if not related to an existing one) so that you can announce your contribution, explain it and ask for feedback, and
    • use Github or P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. (ask the Team Reps in this case) to have a place (if there is not already one) for contributors to give feedback in an accessible and lasting way.
  3. Establish a deadline. Ideally, it’d be two weeks from the moment you share your contribution at the team meeting. During this time, contributors will have time to leave their comments and discuss about your contribution.
  4. Move forward. You can go ahead with your contribution in two ways:
    • Flow with the feedback. Depending on the type of proposal you have made, the discussion can lead the thing to a different solution or even to refuse your suggestion, to name a few possible scenarios. Forget or reschedule depending on the case.
    • Self-approve your changes. If no one shares their thoughts, everybody agrees with your proposal or the feedback does not represent a significant change to its nature, you can assume that nobody has any problem with it. So you can approve the thing yourself when the deadline is up, and move on.

When to apply this system

👍 This system is intended for minor contributions or those that have been discussed previously and everyone agrees, but no one has offered to make them a reality. Just some examples:

  • Changing a title or the wording in a document, like the Handbook or any team documentation.
  • Creating a structure for a document that the team already agrees to create.
  • Create new Github issues.
  • Add or update content in the Github repository of an existing project.

👎 The system is not valid for major changes that significantly affect the team and its operation. This changes must have the explicit approval of a significant portion of the contributors.

There is no strict definition of the cases in which not to use this system for now, because we are still trying to test what works best for the proper functioning of the team and because we appeal to individual common sense in favor of the community as a whole. If in doubt, bring up the subject at a meeting or directly ask the Team Reps.

Endorsement of the measure

This proposal has been suggested and supported in this Slack meeting. However, you can share your thoughts about it here. You can also suggest do/don’t examples to help contributors to be more clear about when to use the system.