In recent days Leslie Hawthorn published a challenge that we should All Build a Hat Rack on which to hang the hats of the people in our community who do the work that needs to be done behind the scenes, and get little professional recognition for it. She tagged it #LABHR (Let's All Build a Hat Rack)

This is close to my heart. So close, I cried when I read her post. Thanks Lesley, you truly are a champion.

Please read this now, you need to understand what she's saying, before you'll understand the suggestion that we should add LinkedIn style recommendations to our Drupal.org profiles. A simple mechanism for posting a recommendation, reviewing it and then choosing to display it one's profile or not.

A Place to Hang Your Hat

We should discuss the idea itself, before making a concrete request to the Drupal.org and Profile improvement initiative that would need to work to make this happen. Once we have a sense of whether or not this is something we want, then we post a follow up feature request to the D.O queue.

The CWG queue seems to be the right place to have the initial conversation. If anyone thinks otherwise, we can always move it straight to D.O.

Comments

kattekrab’s picture

Issue summary: View changes
kattekrab’s picture

Issue tags: +LABHR
kattekrab’s picture

Issue summary: View changes
kattekrab’s picture

Issue summary: View changes

oops. fixed spelling errors

webchick’s picture

There are some implementation challenges with this idea:

1) Drupal.org doesn't have the notion of "friends/contacts" and AFAIK, LinkedIn doesn't let some random weirdo send you a recommendation; it's only people you've already approved because you know them. You might say, "Who cares? Lots of people don't know people in our community, and they should still be able to recommend them." Which I agree with. Except that...

2) Drupal.org has a horrible spam problem, which DA staff spend a non-trivial time trying to cut down. This would open up a new avenue for this. We could lock it down to only "confirmed" users, which would help, except then you have the situation of...

3) Just turning on commenting for users (which is actually super easy to do in D7+) without some sort of safeguard could just end up being used as a place to publicly shame people ("This guy was a total d*ckhead in the issue queue"), rather than build them up. So we'd need to implement some kind of approval process like LinkedIn has to avoid this.

That is starting to sound like a fair bit of work, which doesn't mean we shouldn't necessarily do it (it's actually a great time to discuss it given that the DA is in the throes of modifying user profiles over at https://www.drupal.org/roadmap/profiles).

But I guess I'm wondering why this is better than just doing what the blog post proposes and writing actual LinkedIn recommendations. Is LinkedIn sub-optimal because it's North American-centric? Or I guess what's the guiding reason for wanting to do this on a homegrown system?

I know there are those of us who are community-savvy and look at Drupal.org profiles first when hiring someone, but I would say that almost exclusively "the rest of the world" looks at hiring Drupal people the same way they look at hiring any other role: resume, LinkedIn profile, portfolio, etc. So it seems like a LinkedIn recommendation would actually be *way* more helpful to people than a Drupal.org recommendation, esp. since I worry that a lot of people in non-technical roles, as Leslie's post proposes we all take an extra effort to honour, often don't even have Drupal.org profiles, or log into the site infrequently.

pdjohnson’s picture

Hi,

I am not convinced developing the Drupal.org profiles to support recognition or endorsements is the most valuable way to invest development time. There is a tendency to assume the solution always resides with Drupal / Drupal.org.

Angie - I would say that LinkedIn has a much broader audience than just North America. It is certainly highly adopted in Europe.

I wonder if the best approach is to somehow promote the notion of LinkedIn endorsements. After all there are over 10K people who list Drupal Project in their professional experience (https://www.linkedin.com/company/2197069?trk=tyah&trkInfo=idx%3A2-1-2%2C...). This is clear evidence that Drupal people use it.

Using LinkedIn gets the message outside our echo chamber. An endorsement on LinkedIn not only achieves broader reach for the individual but also the Drupal project. So many people discover Drupal by accident, having many many endorsements on LinkedIn would increase the likelihood of these happy accidents. Organisations use LinkedIn, it could contribute in the path to increased adoption.

There must be thousands of Drupalists deserve a pat on the back. In the past I have blogged to say thanks e.g. http://www.pauldjohnson.co.uk/blog/alex but arguable this has more value to them on LinkedIn. It's their career passport and if these kinds of credits are curated in one place it is better. This is another argument against using Drupal.org. It is entirely likely that many Drupalists use other systems, have accolades outside Drupal. LinkedIn serves as a better place to promote this.

A simple solution could be to have a block on a user profile linking to a page which suggests ways to high five someone. This page could contain links to LinkedIn explaining how and why to write an endorsement, perhaps Twitter - a simple tweet can mean a lot, suggesting people write a blog even. It would not take much time to do but it might stimulate a wave of positive sentiment in the community.

Whilst this issue might not attract lots of comments I think it is really important. It is not OK that people having volunteered so much are not recognised. Some of the most generous people go unnoticed and that eats me up.

Paul

kattekrab’s picture

Status: Active » Closed (works as designed)

I agree with @webchick and @pdjohnson - Let's just use LinkedIn.