Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
To give organizations more-formal credit for their support of projects, and formalize the pattern of project descriptions mentioning their sponsors, we can:
- Add an entity reference field on each project content type to organizations.
- Make sure the display of this looks good on project pages.
- Add an embedded View on organization pages to show what projects the support.
An open question is whether this should be a simple "Supported by" field, or come with a text field to describe what each sponsor has contributed.
Comments
Comment #1
drummI think "supporting" is a more accurate word than "sponsoring". To me, sponsoring implies a more-formal transaction.
Comment #2
drummComment #3
joshuamiSounds good. This gives us a way forward that will not require a complete restructure of organizations and users and gets to the heart of the desire to show how an organization is helping contribute code. This method will also put the emphasis on maintainers to highlight fiscal support (through funds or time) that was sponsored by a company or organization.
Make it so.
Comment #4
Bojhan CreditAttribution: Bojhan commentedShould I add this to the project work I am doing? What are we exposing a title, logo?
Comment #5
drummLogo, if available, and fallback to title. For now, I'll add it where everyone puts it now, after the body text.
Comment #7
drummComment #8
drummNow deployed on Drupal.org. For example, https://www.drupal.org/project/drupalorg has Drupal Association listed under Supporting organizations.
Comment #10
mgiffordOk, wasn't aware this was an issue.
It's been a month now, how many projects have listed supporting organizations? I just added it to:
https://www.drupal.org/project/troll
Have DA members been informed that this is available?
In a list of links, a logo would stand out a lot more. It would also be useful to have that logo on more than the project page.
Why not also have this in related issue queue pages like https://www.drupal.org/node/2164687
Are there any metrics to track clicks on these links so we can measure how many folks are hitting those links? Having a regular report from the DA about traffic from D.o to https://www.drupal.org/marketplace/openconcept would be useful for me as a business owner.
I can track how many links come to my site from an individual d.o page, but if projects I'm contributing to are having the links automatically go to our marketplace page it makes it much harder to track value for the contributions on any given project.
Comment #11
mgiffordBased on #5 setting this back to needs work as our logo is available, but only the title is showing.
Comment #12
mgiffordComment #13
drummSorry, I should have mentioned this in the issue - Josh and I, I don't remember who all we talked to, decided to not show logos for a couple reasons. First, the goal is to "pave the cowpath" of how people were using project descriptions, almost always text. Second, the purpose of a project page is primarily to help people decide if they want to use a module or not, organization support shouldn't be a primary factor in that.
The field has been used to record 565 project/organization relationships. As always, you can pull this data from a dev site.
Yes. https://www.drupal.org/news/supporting-organizations-credit-on-profiles and https://assoc.drupal.org/blog/tvn/drupal.org-team-week-notes-29
Because that is not relevant to communicating around an issue.
No. That has nothing to do with this issue.
I'm re-closing this old issue. Followups, like #2329049: Allow (some) HTML in "Supporting organizations" » "How they helped" field can be opened when needed.
Comment #14
mgiffordGood to hear the rationale for not including the images. You're thinking as a developer, working to evaluate a module. That's an important group. It adds a semantic relationship to the Marketplace pages too. Making it easier for developers is a great thing, but it's only one of the audiences.
Thanks for your detailed feedback.
If we want to demonstrate to Drupal shops that investing in contrib modules/themes is beneficial for them, we have to start thinking about how managers & marketers are also seeing these pages (not just developers). How is their brand represented on Drupal.org? The logo is a basic component of any companies identity. If we want to highlight the companies that contribute, it really should stand out and not look like all of the other links on the page.
There is a reference, but the bigger goal is about changing participation of Drupal shops. Finding new incentives for shops to invest limited time & resources to producing high quality modules that are available for free. That's why I opened #2177459: Highlight Supporting Organizations in the Issue Queue - which you closed.
issue queue pages
If you want it to be a priority for Drupal shops to contribute, you need to look for places to highlight their contribution. Individual issue queues are a great location. There is a lot more traffic on the issue pages than on the central page. Even if it were just for anonymous users, it's an opportunity lost to highlight companies that are contributing. Getting individual issues resolved faster should be the goal.
Metrics to track clicks
You chose to link to the marketplace page, not to the companies URL. Because of that choice, it's harder to measure the results. It is directly related to choices made in this issue.
Comment #15
mgiffordNow that the semantic relationship is established, we need to look for more ways to expose it so that it can be visible in the community. I'm attaching an approach that would make it more visible on the Weekly Drop.
Comment #16
joachim CreditAttribution: joachim commentedThe commit for this issue, 0e725f1515b7dd6d807d38abe3621a2a9c2928ea, appears to have added a dependency on node_reference module, which I presume is part of https://www.drupal.org/project/references.
Does that mean that d.org is now running both references module AND entityreference module? Umm...?
Comment #17
drummYes, we do have both. Especially in migration from D6, one was more convenient than the other at the time. We should standardize before we try to get to D8.