Problem
- Not enough Drupal core contributors.
- Too many tasks to do.
- Many existing contributors who would love to train/mentor newbies.
- But they don't do it.
Goal
- Make onboarding new Drupal contributors fun and a positive game.
Details
Proposed solution
-
Add a My mentors field to d.o user profiles: Allows to specify (multiple) people that you want to credit for "pulling" you into Drupal [core?] contributions.
-
Expose a "People mentored by xyz" view for each d.o user. (native, built-in Profile module feature, no work required)
Notes
-
This applies to all kinds of Drupal mentoring (core, contrib, documentation, leadership, community building, etc.).
-
This leads to an actual exposure of the prolific community interactions. Pulling more people into contributing to Drupal [core] is a constant need and action. No one can reasonably disagree with that.
The amount of possible faking/abuse is close to zero, as we easily notice unusual numbers very quickly.
Mentoring also works in all fields and on all levels — it is not limited to code, reviews, or commits. It's an universal measure that also works for UX/design contributions, and even for Community building contributions.
-
It's a way to give "kudos" to someone else, but in a very particular way.
Allowing everyone of us to learn about whom we have positively 'infected' to contribute to Drupal [core] is a major incentive for doing more of that. (Next to the positive feeling of "distributing workload" ;))
It also works r.e.c.u.r.s.i.v.e.l.y. as soon as the process is started.
Screenies
-
Profile edit form:
-
Profile view:
-
Profile listing:
Instructions
- Label:
Mentored by
- Field name:
profile_mentored_by
- Type: List
- Description:
Give credit to community members who have significantly influenced your contributions to Drupal. For example, people who mentored you in the issue queue, IRC, user groups, code sprints, <a href="/core-mentoring">Core contribution mentoring hours</a>, etc.<br /> <br /> Learn more about <a href="/mentoring">mentoring</a> other contributors.<br />
- Page title:
People mentored by %value
Related Issues
Comment | File | Size | Author |
---|---|---|---|
#17 | who-mentored-the mentor-2012-09-08_0737.png | 110.72 KB | YesCT |
#9 | mentors-profile-edit.png | 12.23 KB | sun |
#9 | mentors-profile-view.png | 16.8 KB | sun |
#9 | mentors-profile-listing.png | 4.36 KB | sun |
Comments
Comment #1
sunComment #1.0
sunUpdated issue summary.
Comment #1.1
sun.
Comment #1.2
xjmUpdated issue summary.
Comment #2
xjmI really, really like this idea, because:
I can't wait to fill in this field with the names of the people who mentored me. :)
Comment #3
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedI don't want to spoil the party, but can we postpone that to after the D7 upgrade? You could get a d.o d7 dev site and start developing there.
Comment #4
webchickI think as long as we de-scope this to only a standard "freeform list" Profile module field on user profiles, it should both only take 3 seconds to implement AND cause no additional burden on the D6 -> D7 upgrade.
So can I? Pretty please? :)
I can only second everything that xjm just said, and right now would be an ideal time to do this, given D8 feature freeze is coming up fast. I fear that by the time the d.o D7 upgrade is done, it'll be too late.
Comment #4.0
webchickSmall tweak.
Comment #5
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedIf that works for you, I see no reason not to do it. The upgrade path should be straightforward.
Comment #6
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedCan we ensure that no external links can be added?
Comment #7
webchickWell, not really. It's a free-form text field. If external links were added they would go to a link like:
http://drupal.org/profile/mentored_by/http%3A/%252Fspamorama.com
, rather than spamorama.com.I'm not really down with blocking this feature on that, though, given that at this very moment I can do this http://drupal.org/profile/profile_interest/http%3A/%252Fspamorama.com :)
Comment #8
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedthat is good enough for me (for now, can be improved later).
Comment #9
sunComment #9.0
sunKilled confusing stuff for later.
Comment #9.1
sunUpdated issue summary.
Comment #10
chx CreditAttribution: chx commentedThat sounds sheer awesome! Thanks sun for the awesome idea. Implemented and tested at http://drupal.org/user/9446 http://drupal.org/profile/profile_my_mentors/Gabor%20Hojtsy
Comment #11
Dries CreditAttribution: Dries commentedI like it.
We should try to capture the data in such a way that is can be sliced and diced later.
Comment #12
webchickYeah, this is unfortunately the best we can do for now, but the plan is once Drupal.org is on D7, to move to something like actual user reference fields, back-references, listing overview pages, and the like. :)
Comment #13
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedCalls for an opt-out option. :p
Comment #13.0
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedUpdated issue summary.
Comment #14
TransitionKojo CreditAttribution: TransitionKojo commentedAre we using this for CORE mentors only, or ANYONE who's mentored us in Drupal?
Just checking...I don't want to 'pollute the namespace'.
I probably said that wrong...
Comment #15
chx CreditAttribution: chx commentedAnyone I'd say.
Comment #15.0
chx CreditAttribution: chx commentedUpdated issue summary.
Comment #16
xjmUpdated the summary to reflect that we decided any sort of Drupal mentoring should go in the field. The fact that all my mentors happen to be core developers probably reflects my interests and involvement! :)
Comment #16.0
xjmUpdated issue summary to reflect the scope of the mentoring field.
Comment #16.1
xjmUpdated issue summary.
Comment #17
YesCT CreditAttribution: YesCT commentedOne fun thing to do is to go to someone's page, like sun's and click on someone who mentored sun, like webchick, and see who mentored webchick. From a list of people "mentored by" whoever, I want to see who mentored whoever. Make that a link. These are tags, right (or something not really references...). But we could guess they are d.o user names and use something like dgo.to/@whoever to guess a link to link to their profile and see who mentored them.
Comment #18
YesCT CreditAttribution: YesCT commentedhmm. spaces and special chars make linking interesting. http://drupal.org/profile/profile_my_mentors/Gabor%20Hojtsy is the same as http://drupal.org/profile/profile_my_mentors/G%C3%A1bor%20Hojtsy but dgo.to/@Gabor Hojtsy doesn't go to the place people probably want to go to: dgo.to/@Gábor Hojtsy
Is that why the user search box is on the people mentored by page? Because typing Gabor Hojtsy will give search results better than guessing at a link? ... Nope: http://drupal.org/search/user_search/Gabor%20Hojtsy
Since the search doesn't work any better, maybe guessing at a link for whoever in "People mentored by whoever" is ok?
Comment #19
YesCT CreditAttribution: YesCT commentedI made #1778766: Add a "People I Mentored" link to drupal.org user accounts (follow-up to "My Mentors") for adding a different field to the profile.
Comment #20
frazras CreditAttribution: frazras commentedIt would be nice to have a mentee count, to say frazras has mentored 33 mentees. Another nice ranking system for the Drupal eco-system :-)
Comment #21
vlad.dancerOh my God! It's really cool feature! I love it! And i completely agree with xjm #2 comment!
Comment #23
YesCT CreditAttribution: YesCT commentedfollow-up: #2024317: Add a link from https://drupal.org/profile/profile_my_mentors/webchick to the user account.
Comment #23.0
YesCT CreditAttribution: YesCT commentedFixed a typo.
Comment #23.1
YesCT CreditAttribution: YesCT commentedwith related issues
Comment #24
mgiffordI think we need to reflect a bit about this issue, so I am re-opening it.
5 people including @sun touched this idea before it was implemented. This is telling, considering the number of people who were very active in the same time period looking at issues regarding the Prairie Initiative.
All of the real discussion happened on either September 7th or 8th, 2012.
YesCT: opened a follow-up issue here linking to a related issue that I added. Nobody on this list follow-ed up on it.
I've added an issue where we could leverage this information a bit more in order to better highlight users. YesCT is the only one who responded.
So now the mentor role has been implemented on d.o for over a year, has there been any evaluation? I've just added another issue to #2193959: [meta] Add more metrics to try to see if we can't start looking at this.
Going back to the stated problems. Has adding the mentor field:
Has this option made "onboarding new Drupal contributors fun and a positive game"?
I don't think that it has. Perhaps because it wasn't taken far enough. Perhaps because it was only really interesting for 2 days.
I think these kinds of changes need to be put into a broader plan. We need to have a process for onboarding new people.
Also adding link back to the Prairie Initiative discussion on this:
https://groups.drupal.org/node/136154
Comment #25
tim.plunkettThis was closed (fixed) as of October 2, 2012.
Feel free to open a follow-up issue.
Comment #26
mgiffordIt needs to be evaluated. Follow-up issues have been ignored.
If drumm or others want to permanently close this thread, fine. I think it's worth discussing though.
Did the implementation of the mentor field fix @sun's perceived problems?
Comment #27
tim.plunkett@mgifford please familiarize yourself with https://drupal.org/node/156119, which explains that issues marked
closed (fixed)
should "not be reopened, but instead a new issue should be opened, providing a link to the closed issue"Comment #28
sunAs @tim.plunkett mentioned, I also think this issue should be closed again.
There are possibilities to further improve these contributor-to-contributor relationships in the future (and it certainly doesn't help that the "mentored-by" listing pages are disabled due to high traffic on d.o currently), but in terms of overall goals, we don't want to revert this improvement; we only want to advance on status quo.
Comment #29
mgiffordThanks for your input @sun. Always appreciated.
1) Certainly, there are a lot of folks who are busy to get D8 out. Lots of big issues. Thanks! Most of the changes that need to be made now are outside of my skill set. As you know, I'm looking to help push that along too.
I do think it is bigger than that though. The Prairie Initiative had lots of good ideas back in 2011 & 2012, and it's totally understandable that they couldn't all be implemented, however, it's now 2014. We were focused on D7 in 2011, we were focused on upgrades to Drupal modules in 2012, we were focused on upgrading Drupal.org in 2013, now we're focused on the D8 release, but this cycle will begin again after the release of D8.
Maybe the same people pushing Core can't be the same people pushing improvements to d.o?
Maybe there is too much focused in the hands of too few. Would seem that way if 5 folks can implement a change like this in 48hrs.
2) Absolutely, the data is useful. Good to hear that it is being used by active members. It wasn't a mistake to add this field. I do think it's a good idea.
3) Totally mentor-ship is an important concept. It's did help to establish the idea. We can probably do more to explain the why/how it matters as part of onboarding new users.
4) Great to hear that this, and the other efforts have helped to bring on more contributors to D8.
Having evaluative comments like this is really useful. We do need to be able to reflect as to whether the changes we've made have had the desired results. Doing that in a new issue seems a bit ridiculous.
I'm all for advancing on the work that's already been done. Definitely am not interested in reverting it.
The upgrade to D7 certainly has not been smooth. Hopefully the remaining wrinkles get sorted out soon.
But we have to be able to innovate, evaluate & improve Drupal.org on a faster time scale. It has to be be given a priority which is as important as Core work.
We are a community that collaboratively develops software. If we don't nurture that community, we won't be able to effectively develop the software together.