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.

#5ftf, #five-for-the-future

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. 

#5ftf, #discussion, #five-for-the-future

Suggested iterations for the Five for the Future program and tool

The Five for the Future site and tools launched at the end of 2019, and then the pandemic hit. It’s been difficult to make time to iterate on the program, but eventually the window of opportunity for changes will open, and I wanted to collect my suggestions here, in case they will be helpful in the future.

The program has a few major challenges that have kept it from reaching its full potential. Here’s my take on those problems, and how they might be resolved:

Spam or dormant pledges

The program runs on the honor system, and it wasn’t clear how much of a risk that would be, at launch. Two years later, there have certainly been more “spam” pledges than anyone would want, and surprisingly (to me) few reports of fake or spam pledges. What that tells me = either people don’t go surfing around in the pledge lists, checking for accuracy, the Report feature is too hard to find (unlikely), or people don’t really care whether pledges are accurate or not.

I do think that a substantial number of false/fake/spam pledges are a problem, because they depreciate the value of the sincere/active/real pledges. If we never intend to clean up the rolls, then we should probably consider shutting down the program or putting more disclaimers on the site. 🙂

I don’t think it’s time to get that drastic, though. Here’s what I think could work, to increase the signal to noise ratio in pledges, in no particular order:

  • Share the list of pledges with leaders on each contributor team, asking them to mark the contributors they’ve never worked with or seen participate on the team.
  • Send the “absent” contributors a friendly email, letting them know that we’re cleaning spam pledges from the site, and asking them to confirm that their pledge is not-spam. Share the names of those who confirm not-spam back to contributor teams and encourage them to reach out to that list with opportunities to help work on things.
  • (This will depend on each team being able to provide a list of ways to contribute. Worse comes to worst, I suppose we can send pledgers to each team’s handbook page that talks about how they can help.)
  • For those who do not confirm within a reasonable time period, remove their pledges from the site, and email them with a friendly message that we have been removing apparent spam pledges. Let them know how they can re-pledge if they simply missed our previous message asking for confirmation. It would be interesting to know if people who only come back once we’ve removed their pledge, actually become active or not. I’m not sure what will happen there.
  • Institute a biannual 5ftF spam-check, following the above process. Maybe that’s too often — maybe only once every year?

Disconnect between contributor teams and pledged contributors

For whatever reason, the outreach that I imagined would happen, between contributor teams looking for help and the list of pledged contributors that was added to every sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. on the Make network…. never really came to pass. I’m not sure if that’s because contributor teams don’t feel comfortable pinging someone out of the blue and asking for help (it’s very likely that I have less shame than most, in my recruitment work), or if that *has* been happening, but just hasn’t been productive.

I was talking to Courtney Engle Robertson about this a little, this week, and she mentioned the idea of a tagging system on Make blog posts, that could automagically alert pledged contributors of posts that included opportunities to help out. I think we’d need to add some opt-in steps there, for privacy reasons of course, but I think this idea has merit.

When contributors re-confirm their pledges, they could be asked to click a box on their Profile page if they want to be emailed posts from Make blogs with a #5ftF tag or something, and maybe even specify which blogs they’d like to hear from in that way.

Another idea in this vein = inviting people to mark what kind of work they’re interested in doing for WordPress, when they make their pledge. I’m envisioning options like:

  • administrative (answer emails in a queue, take meeting notes, etc)
  • feedback (review and comment on blog posts,
  • testing (CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. betaBeta 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. testing, contributor tool beta testing, pre-beta testing for new features, etc)
  • writing (write new or update old documentation, revise contributor team handbooks)
  • and the like.

Then contributor teams could get a regular report that (for example) 24 people have pledged 2 hours per week to their team, and 10 of them are willing to write or edit documentation. This could aid in the outreach/recruitment that contributor teams do, when they need to find people to work on a new or dormant project.

Train the pledgers, train the recruiters/onboarders

Another thought I had, about how we don’t seem to see a strong connection between pledged contributors and the teams they’re pledged to, is that not everyone knows how to effectively recruit people to contribute — even if they’re “qualified leads” (which is what I’d consider pledged contributors).

And not all people making pledges, necessarily know how to *find* the pages that tell them how to get involved.

So I think a two-pronged approach could help here. We write some docs or a training on how to recruit (and onboard?) contributors, and then we alter the email that pledged contributors get when they pledge, to include links to the onboarding docs for the teams they indicated. That’s work, y’all! But I think it would have a positive effect even beyond this program.

Discuss!

What do you think of these ideas? What ideas do YOU have for making the Five for the Future program more reliable and useful? Share your ideas/feedback and discuss in the comments, below!

#five-for-the-future

The Metrics of Contributions

When the Five for the Future (5ftF) program was proposed, one of the big questions I found myself considering was how to reconcile participating in a team with specific outcomes and expectations for work when that team contributes to a larger organization that has impact as one of its coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. values. It can feel like impact should be the primary consideration, but for those who are employed, there is always the pressure to quantify contributions over time.

The following notes are from a two part session with current sponsored contributors, to discuss how this tension appears in their day-to-day and how it balances over time.

General Thoughts

  • High impact contributor work in the project usually gets defined and clarified over time (e.g. the reiteration of priorities, the WordPress North Star, posts that outline goals).
    • Is it OK to have aimless or agenda-free contributions?
    • What is the difference between aimless and agenda-free? Or agenda-free and agenda-aligned?
    • If a contributor’s agenda is too clear, that doesn’t feel right—it is in direct conflict with “agenda-free contribution.”
  • Early contributions can be tricky for sponsored contributors as there are expectations from employers, project leadership, and casual contributors.
    • Goal alignment can be a struggle. What is valuable to the company may not be impactful for the project. 
    • How do you balance and align those expectations and responsibilities?
    • How do you reset expectations with casual contributors who become sponsored?
    • Should we have a different or more explicit onboarding process for company-sponsored contributors vs. self-sponsored contributors?
  • Sponsored contributors ensure that someone will track and execute the operations and administrative side of the project.
    • Does anyone even know about this type of work in the project?
    • Do we need a way to identify those who can do less desirable tasks?
    • Should sponsored contributors have an 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. mission statement that makes the project’s internal goals visible to impactful work
  • WordPress project onboarding necessarily has friction, which is a good thing.
    • A clarifying example is that you don’t hand over the keys to the first person who walks into the Red Cross and claims to have the solutions to all the problems.
    • The friction is going to exist if there is growth and transfer of knowledge. 
  • Being a sponsored contributor tends to come with a change in how volunteer contributors perceive you and your work.
    • The weight of your vote can change as goals align more/less over time.
    • Invisible work becomes your responsibility, but is rarely easy to point to let alone quantify.

Question to Contributors:
What are the things that changed when you shifted from a contributor to a sponsored contributor? Answers anonymized. 

  • I am now more willing to take on the less glamorous (administrative) tasks.
  • I am now expected to take on dropped tasks that are important to goals.
  • As a contributor, adding to the project made me feel empowered, and I think even more so now as a sponsored contributor. I felt like I was mainly guessing, whereas now I have familiarity and context. 
  • Sponsored contributors have more direct interaction with project leads, and extra vision and foresight setting than regular contributors have access to. 
  • When you can work full time on the project without the distraction of other work, you can see the patterns and projects more clearly. That exposure comes when you have a lot of time.
  • I started on the fringes, but saw that the onboarding to the space was steep and I didn’t have the time to invest in that. Having a buddy/guide helped.
  • Once you show up more frequently, people are more willing to offer help and guidance.  

Final Thoughts

It comes down to balance:

  • Aimless contribution vs agenda-free contribution (& if working toward goals works against that)
  • WordPress goals vs Company goals (& when they don’t match)
  • WordPress needs vs Company value (& when they don’t match)
  • Project work vs admin work (& setting expectations w/ contributors)

Resolving these conflicts is multi-tiered. We need to get better at welcoming organizations into a Five for the Future arrangement where the stakeholders, impactful work, and responsibilities are made clear at the start. We need the information to be clearly received by 5ftF contributors, while also making sure the same information is readily available to any contributor.

Five Proposed Solutions (+ pros and cons)

  • TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. sponsored contributors.
    • We have this tag but it’s unverified (honor-system and self-selected).
    • Can it be reframed to the lens of a contributing vs staff writer.
    • At what point should there be a closed selection component to contribution? 
    • Cons
      • It would be easy for that to carry too much weight/power.
      • We can’t opt-out of certain contributions.
  • Clarify the difference in the expectations. 
    • What are the differences and how do we keep people accountable?
    • When you are clear about what you are doing, it’s easier for people to work alongside you.
    • It can bring stability to sponsored contributors and level set their own expectations.
    • Cons
      • Could alienate other contributors.
      • That level of clarity could feel antithetical to OS methodologies for all contributors. 
  • Clarify the steep learning curve and trust-building for this type of team
    • The work of building trust, context, and rapport should be explicit to support personal and organizational expectations (6-12 mos).
    • Being sponsored does not immediately mean we are trusted with a decision.
    • Cons
      • No cons found.
  • Dedicated 5ftF onboarding process
    • What does that look like?
    • Do we change the metric from hours to perhaps contribution or event participation? 
    • Automated greenhorn system for 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/.?
    • Cons
      • Could alienate other contributors.
      • That level of clarity could feel antithetical to OS methodologies for all contributors. 
  • Should we have a specific 5ftF mission statement?
    • Having one could clarify the expectations for sponsored contributors.
    • Does a mission statement make it clear who can work on what, or is it divisive?
    • Current 5ftF White Paper

But there are so many questions

You might have noticed that there are twice as many unanswered questions as there are answered thoughts in this discussion. And these aren’t even all the questions I have!

Yet, the most important thing to me is how the project can support sponsored teams (and how those sponsored teams can support the project) transparently and with as much care as possible.

#5ftf