X-comment from +make.wordpress.org/updates: Comment on Announcement: Incident Response Training
Monthly Archives: May 2022
Request for feedback: Recording Five for the Future contributions
Have you kept up on the latest updates to the Five for the Future (5ftF) program? In addition to addressing spam and dormant pledges, @josepha has proposed a definition for 5ftF pledges and contributions. Most notably:
Participation in Five for the Future means consistent effort by an individual or a company via a Make WordPress team to directly support the WordPress open sourceOpen 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 and the project’s current big ideas, rather than the sole benefit of a company or individual.
Another important iteration to the 5ftF program is identifying and recording contributions made; this will help Make Teams follow activity and progress (dashboards, anyone?!) and support all WordPress contributors to recognize all the great work achieved.
Upcoming improvements for the 5ftF program are tracked in GitHub. There are a number of suggested contributions to record that apply across Make Teams, such as props, HelpScout activity, or attending a Make Team meeting. There are also suggestions for Team-specific contributions to record, thanks to input from the Training, Documentation, and Community teams.
Of course, there is much, much more activity to celebrate. This is where I would like your input. Based on the definition we now have of 5ftF contributions, what other activity, specific to a Make Team or across multiple teams, should be recognized and recorded? Share your thoughts in the comments below.
Discussion: Contrib Handbook, Part 3
It’s time for the next round of discussions (check out the #handbook tag if you’ve missed the others)! Today we’re opening comments on a code of conduct. Please share your thoughts on what works, what could be improved, and what needs correction.
In coming weeks, I’ll also share a Conflict of Interest Policy and Code of Ethics for your input.
Please share your feedback in the comments of the documents!
Defining Five for the Future Pledges & Contributions
After reading through some of this post’s comments, I think it might be useful to re-articulate the hopes behind the discussion.
The end goal is to find ways to automate contribution props, so that no one has to either spend huge amounts of time before their contributions are noted or find ways to contribute to the most time intensive props opportunities, major releases and major WordCamps. The end goal is to distribute props more equitably and more consistently by taking out the subjectivity of human review, not to make individual contributions somehow less valuable.
The first step for automation is, of course, documenting what you have and what you mean, hence my use of the word “define.” ~Josepha
In recent months, the Five for the Future (5ftF) program has improved to make it more reliable and useful when it comes to tracking impact and success. An example of this is the work being done to reduce the number of spam and dormant Five for the Future pledges and give more credit to non-code contributions.
To support such efforts, it’s also important to build a shared understanding for how the Five for the Future program works.
The WordPress project thrives because of the generous contributions in time and resources from people and companies across the globe. A portion of contributions are made in the form of Five for the Future pledges from individuals and organizations. They commit to giving back to the WordPress project by contributing a goal of at least five-percent of their time (or resources) consistently via the Make WordPress teams. By joining together in giving, we make WordPress stronger.
Participation in Five for the Future means consistent effort by an individual or a company via a Make WordPress team to directly support the WordPress open sourceOpen 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 and the project’s current big ideas, rather than the sole benefit of a company or individual. Simply put, Five for the Future exists to collaboratively invest in the health of the WordPress project, ensuring its long-term sustainability and success.
What makes a contribution a 5ftF contribution?
Some contributions are easy to sort through and agree on; we see them happening, props are given with them already, and we understand how they help make WordPress better. Contributions of code to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or the apps, translations through Polyglots, forum management with Support, organizing WordPress-centric events, and many other main focuses of Make WordPress teams.
But other contributions are in a grey area. For those, it’s important to look at not only whether they move WordPress forward, but also whether it helps the community of contributors work in a sustainable way and whether the contributions can be done consistently over time.
Some examples of grey area contributions that do fit the 5ftF definition include: maintaining WordPress.orgWordPress.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/, WordCamp.org, or Rosetta networks; adding or editing official WordPress documentation, training, or communications; speaking at WordPress Meetups and WordCamps; and maintaining or moderating official repos (plugins, themes, photos, WPTV, et al).
Examples of grey area contributions that do not fit the 5ftF definition include: creating WordPress websites, creating WordPress themes, plugins, or blocks (including those that are listed in WordPress.org), and providing support solely to third-party WordPress themes or plugins. These activities are critical to extending the reach and utility of the WordPress project, but they are not considered part of making Five for the Future commitments.
There are many important efforts and lots of incredible work performed outside of WordPress.org and Make Teams. While these are indispensable activities that further the WordPress ecosystem, Five for the Future is about ensuring that the WordPress project continues to be a fertile foundation for WordPress extenders and users.
What do you think of this definition? Share your feedback in the comments below.