Hi,

These days Drupal is being increasingly adopted in commercial circles, be it government, charities, NGOs, private enterprise, etc. It occurs to me, as a maintainer of a few modest modules, that often these modules are commissioned by somebody or some organisation that pays for the initial development and, in some cases, even ongoing maintenance. It might be an idea to provide a field on the Project content type to allow maintainers to name and link to project sponsors. It would also be nice to offer organisations a little Drupal badge they can use on their site (like the Association badge) saying "I sponsor a Drupal module" or somesuch.

Just a thought...

Comments

gerhard killesreiter’s picture

gerhard killesreiter commented

You can put any such links directly into the body of the project node.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

I know, and I do... Just thought it might be nice to have a "Project sponsor" link or "Project sponsors" fieldgroup containing links, a bit like the documentation site links, etc. - for visual consistency.

What's nice about other things, like documentation links, demo pages, etc. is they have a proper place and everyone knows where they sit on the project page. Project sponsors do not. If it were me, I'd want them to.

But if you think it's overkill, fair enough. =)

killes@www.drop.org’s picture

killes@www.drop.org commented
Component: Other » Redesign

Yeah, I think it is overkill, however, I'll ask the redesign people to look at it.

dww’s picture

dww
we/he/they
commented

A nice thing about having it as separate fields is it becomes possible to do faceted searches on this info. There's really no good way right now to say "Show me all the modules sponsored by Foo Co. Inc."

killes@www.drop.org’s picture

killes@www.drop.org commented

I don't think this rather exotic use case warrants the added complexity.

kbahey’s picture

kbahey commented

Actually, it gets more complex. There are module that have more than one sponsor. Do we provide several of those fields then? How will that be faceted?

The original use case was for visual consistency more than queries and such, and I agree with that point. The redesign folk have to evaluate that.

Anything beyond that needs to be really evaluated/discussed more before a decision is made.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

A CCK link field set to allow unlimited values with an optional title would do it. ;-)

kbahey’s picture

kbahey commented

Yeah, but that would entail performance overhead on d.o if we do it via CCK. And upgrading cck is no fun. Have you see the 5.x to 6.x upgrade instructions? I am doing that now for a client, and having nightmares.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

Hence the "winking smiley" ... indeed - I wasn't really suggesting you'd implement CCK on an enterprise site like Drupal.org - merely trying to point out that the feature I initially had in mind is actually a very simple use case ... =)

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Closed (works as designed)

Just use HTML links in the existing places.

greg.harvey’s picture

greg.harvey
Primary language English
Location Occitanie, France
commented

That's fine, but it doesn't introduce design consistency, which was the point. See #2. But anyway, it doesn't matter.