There is some desire/discussion to have the features from http://drupalmentoring.org merged into http://drupal.org so that there is not a separate site required.

This issue is for discussing the pros/cons of that approach, and coordinating any actions plans for making it happen.

From YesCT

Long term, we are hoping to improve d.o so we dont need drupalmentoring.org anymore. See d.o issues tagged "Core mentoring on d.o" for ways to help make d.o better and drupalmentoring obsolete.

issues that are part of this include:
#2151041: Add a "draft" status for change records
#2143083: "Assigned" field is confusing and not appropriate in all circumstances
#2279441: Update the dashboard contributor links Novice link to be a better view
#1621714: Allow to bookmark/favorite issues without abusing the Assigned field or issue tags
#2466139: Add a handbook page about how to get involved with porting contrib modules that Core mentors can refer people to

Closed:
#1710850: Deploy RestWS for D7 project issue JSON
#493074: Back-link to the commit as a comment on the related issue.
#1465924: Add explicit field/section for steps to reproduce
#1393226: Encourage use of issue summary template
#2013222: Add "Issue tasks" to project issues and correlate tasks with handbook documentation
#2282517: Update/Redo Contributor Links block for Dashboard page

Comments

rcross’s picture

rcross commented

I think there is actually some real merit to having a separate site for handling the mentoring outside of the main d.o issue queues. Some initial reasons:

  • It is potentially less frightening for newbies. Smaller/simpler issue queue, plus all the extra helper text/features
  • Having many of these extra hand holding features in the main issue queue could make it harder for the ones doing lots of heavy lifting in the queues
  • It could also make the UX of our issue queue unnecessarily complex
  • There are benefits to having a concept of "sprints" as an organising principle that I'm not sure translates well to day-to-day working in the queue
  • The ability to have a mentor + mentee assigned to tasks (where tasks are parts/steps in an issue) seems somewhat out of place
  • Lots of nesting of issues to support the concept of tasks (and their statuses) underneath an issue seems burdensome for those that don't need to use them.

I'm not saying that i'm against this in principle, but just not fully convinced. For example, a big positive is it would be nice to not have to have a separate user account for the two sites. I'm sure there are also some elements of the site that could be incorporated into d.o, just not all of them.

xjm’s picture

xjm
she/her
Primary language English
commented

Wrong queue. Please don't eat us.

xjm’s picture

xjm
she/her
Primary language English
commented
Project: Drupal.org customizations » Core office hours tasks
Version: 7.x-3.x-dev »
yesct’s picture

yesct commented
Related issues: +#2173425: [META] Merge DrupalMentoring.org features into Drupal.org
yesct’s picture

yesct commented
Related issues: -#2173425: [META] Merge DrupalMentoring.org features into Drupal.org +#2232047: [META] Get ready for DrupalCon

:)

yesct’s picture

yesct commented
Issue summary: View changes
Related issues: +#1621714: Allow to bookmark/favorite issues without abusing the Assigned field or issue tags

adding #1621714: Allow to bookmark/favorite issues without abusing the Assigned field or issue tags

xjm’s picture

xjm
she/her
Primary language English
commented

Added to the template:
https://www.drupal.org/node/1424502/revisions/view/1930408/7476505

Most specific task documents probably need to be updated to add the "and mentors".

Also to do: A handbook page explaining issue scope and scope management (what scope is, why it's important, how to manage followups for out-of-scope issues, etc.).

xjm’s picture

xjm
she/her
Primary language English
commented

Also we really should do something a bit more awesome with the main core mentoring page that describes the core mentoring program as it is today rather than the office hours of 2011. :)

xjm’s picture

xjm
she/her
Primary language English
commented

And we should come up with a process for tracking issues touched at specific sprints (Dries has asked for metrics about each sprint's effectiveness). Smaller sprints use tags sometimes, but what about DrupalCon? Would tagging add too much noise? Would activity be under-reported because of people not remembering to tag? (Or I wonder if we could adminstratively query by IP range to identify activity at a particular physical sprint location?)

yesct’s picture

yesct commented

I think administrative query by IP range would be our closest thing to accurate info on what is worked on at a sprint (an in-person sprint)

yesct’s picture

yesct commented

Re #8

I updated https://www.drupal.org/core-office-hours to try and reflect the current purpose and state of office hours.
https://www.drupal.org/core-office-hours
further improvements welcome.

xjm’s picture

xjm
she/her
Primary language English
commented

Did we have an issue to make the novice link on the dashboard more useful (e.g. not too old, not too new, not too long, etc.) and maybe with meta information? We discussed it at Austin and someone took notes and was going to file an issue but I can't find it. :)

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

Ah it's #2282517: Update/Redo Contributor Links block for Dashboard page. Adding to summary. :)

xjm’s picture

xjm
she/her
Primary language English
commented
Issue summary: View changes

Or #2279441: Update the dashboard contributor links Novice link to be a better view...

yesct’s picture

yesct commented
Related issues: +#2396859: [Meta] finding issues is difficult
xjm’s picture

xjm
she/her
Primary language English
commented
Related issues: +#2462101: [policy, no patch] Update backport policy to account for 8.x minor versions and 7.x divergence

 

valthebald’s picture

valthebald
Location Sofia
commented
Issue summary: View changes
alimac’s picture

alimac commented
Project: Core office hours tasks » Mentoring
shardulagg’s picture

shardulagg commented

From my point of view we shouldn't be merging two different things into one as it always increases the complexity and UI which in result will be little frighten for newbie contributors

quietone’s picture

quietone commented
Issue summary: View changes
kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Issue tags: +Needs issue summary update

Got here from:

https://www.drupal.org/community/contributor-guide/contribution-areas/me...

so read the issue summary which points to:

http://drupalmentoring.org/

but, if I go to that link, it redirects to:

https://www.drupal.org/community/contributor-guide/contribution-areas/me...

:)

So, IMO this needs an issue summary update.