Comments

rcross’s picture

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

Wrong queue. Please don't eat us.

xjm’s picture

Project: Drupal.org customizations » Core office hours tasks
Version: 7.x-3.x-dev »
YesCT’s picture

YesCT’s picture

xjm’s picture

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

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

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

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

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

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’s picture

YesCT’s picture

xjm’s picture

valthebald’s picture

Issue summary: View changes
alimac’s picture

Project: Core office hours tasks » Mentoring