Provide feedback on the issue credit attribution user interface

March 3rd, 2015

With the help of a few key community members, we have been hard at work creating an interface for users to attribute their work in the issue queues to a customer or employer. (#2288727: [meta] Provide credit to organizations / customers who contribute to Drupal issues)

This is an important step in beginning to collect information about the contributions that organizations make in the Drupal ecosystem. Dries has talked about this need in detail in his blog post A method for giving credit to organizations that contribute code to Open Source. Since the original vision laid out in that post, which focused on commit credits, we have expanded the scope to include any contribution in the issue queues.

There will be three parts to the release of this feature on

Comment Attribution

First, we needed a way that contributors could attribute their work to an organization—either their employer, their customer or both. (#2340363: Add issue comment attribution) We would like to have feedback through the comment on the issue. Here is an animated example of the comment attribution user interface:

This new field on every issue comment lets the user attribute their work to organizations per comment. Our team is also very excited to introduce a new interface framework for inline editing of entity fields on There are so many great ways we could use this for easier in place editing of metadata.

Once this comment attribution user interface is deployed, we’ll see how it is used, helping us build the next step.

Interface for Maintainers to Award Issue Credits

The next step will be a method for maintainers to award credit for the intended attribution. (#2369159: Extend crediting UI to include organizations & customers) Allowing maintainers to commit or award the credit for the issue accomplishes two important goals: we incentivise completion and we reduce gaming of the credit system.

By placing credits on issues—rather than commit mentions—we opened up the ability to recognize contributions outside of code. Patch reviews, comments on architectural decisions, wireframes and mockups, and general design feedback are all valuable contributions to the issue queues. Maintainers will now be able to reward those helpful behaviors.

Highlighting Organizations that Contribute

After a couple of months of collecting issue credit data, we will be able to begin using that data to highlight contributing organizations—giving them “trust currency” as Dries put it so well.

Issue credits are not the only contribution we will be tracking. We are already tracking how organizations give back financially through our supporting partner and membership programs. We track organizations that sponsor DrupalCons—and we’d like to start tracking how organizations help build camps.

Next Steps

If feedback goes well, our engineering team is planning to release the comment attribution feature on March 12th.

The user interface for maintainers to award credit should be available for comment in the coming week. Work on that issue has already started at #2369159: Extend crediting UI to include organizations & customers.

Let us know what you think!