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.
As a sister to the "Current Company or Organization(s)" field, this would allow tracking of customers for use in #2288727: [meta] Provide credit to organizations / customers who contribute to Drupal issues.
Comments
Comment #1
drummI wonder if there is a good way to integrate with (draft, since the project won't be done) case studies. It would be good to reduce duplicate-ish data, and encourage writing case studies.
Comment #2
webchickOooh, that's a great idea.
Comment #3
Bojhan CreditAttribution: Bojhan commentedWhat would this link to? We don't have customer profiles or something do we?
Comment #4
webchickThey would just be organization nodes like Drupal companies are. Probably with a field to differentiate.
Comment #5
mgiffordThis would really help begin to populate the map of end users that Dries talks about here in his Amsterdam keynote:
http://youtu.be/4NN5EM4CYVE?t=34m37s
Not that all the current folks here don't already fully get that. Just trying to link together ideas related to the keynote.
Comment #6
joshuamiComment #7
drummIf needed, this directly helps #2340363: Add issue comment attribution.
I think the way to do this should match the organizations-related UI. Treating customers the same in technical implementation will save work and provide some consistency.
It does introduce a bit of a barrier, someone/something needs to create an organization page for each customer. I think the best first pass would be ensuring the organization creation is friendly enough for a customer to reasonably do. In the future, we can do things like a UI "this customer isn't known on Drupal.org, confirm & it will be created when you comment on this issue, and let us know who should be responsible for it."
We could do a name like organizations is done today, and not require an organization page; but Drupal developers tend to not like non-numbers, #2323705: Add user's organization computed reference field.
Comment #8
joshuami@drumm and I were chatting about this a bit. I think it makes sense to track customers at the organization profile level rather than at the user profile level. Most individual users will have less motivation to maintain their profile customer list than vendors.
Comment #9
webchickSorry, don't quite follow that... so DrupalShopInc would put the ZapBangBoom customer in their organization profile's multivalue "customer" field? But since DrupalShopInc is probably working on 20+ customers at once, between 20+ employees, how does ContributorFoo document that this patch was paid for by ZapBangBoom? Or are you thinking it's a single-select for organization, then a "states API" style second step that lets you select from current customers of DrupalShopInc?
Comment #10
drummWe might be able to skip new fields for customers.
User profiles are already getting heavy, we should limit paperwork to what is necessary.
Comment #11
drummCurrently, #2340363: Add issue comment attribution suggests customers which you have been used in an issue comment in the last 6 months. This saves a step editing your user profile.
Thinking about this more, including case studies doesn't make sense. The reverse, using issue comments to populate the case study defaults, might be interesting.