[META] Random Things To Do

From #2173425: [META] Merge DrupalMentoring.org features into Drupal.org:

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.).

I need a way to broadcast updates in mentoring recommendations to mentors. :) E.g.: https://www.drupal.org/node/2274113/revisions/view/7322671/7618655

From @Michelle:

I'm trying to follow the reroll page but it's so full of complex stuff for fixing conflicts and hard to pick the basics out

It might be worthwhile to clean up the reroll doc so we put the simplest case above the fold, adn then go into explanation about conflict resolution.

• Schedule monthly mentoring meetings?
• Find @YesCT and @Bojhan's work from Austin about d.o IA (Getting Involved Guide etc.) and get it into the queue properly and shareably.
• Refine/polish contributor task doc for beta phase evaluation. Done

https://www.drupal.org/core/issue-category should also be updated to directly link and be more consistent with https://www.drupal.org/core/issue-priority.

#8 2. #2332789: Reduce Novice Contribution differences and consolidate landing pages, content, blocks is the issue which has a link to the google doc.

http://doodle.com/z2bnv8u347sucyfa is a doodle for scheduling a monthly meeting for mentors.

We've gotten feedback before that "rerolling" is a different task than "rerolling with change X" (i.e. updating an existing patch), and it's also different than creating a new patch. Thus: https://www.drupal.org/node/2272209/revisions/view/7823397/7919241

To do: need a different contributor task document?

@xjm I feel that rerolling should not introduce changes.

thanks, for doing that. I had been copying that line to do something similar. makes sense to have it in the template.

maybe I'll add something there directly linking to / mentioning interdiff.

https://www.drupal.org/node/2272209/revisions/view/7919241/7920043

https://www.drupal.org/documentation/git/blame is no longer very useful; it doesn't explain how you would want to navigate back through the history of multiple commits that changed a line, or how you would use it to find issues on d.o, or why you would even want to do it in the first place.

https://www.drupal.org/issue-tags/special is out of date. Among other things, the old "Needs change notification" tag is listed instead of "Needs change record" and "Needs change record updates", and "D8 upgrade path" and things from https://groups.drupal.org/node/424518 are missing.

Belated thanks @stpaultim.

Another task: We need a contributor task doc for checking for updates for existing change records that will also be listed as a sub-step or related task for https://www.drupal.org/contributor-tasks/draft-change-record. This would be for issues that have either the "needs change record" or "needs change record updates" tags (because people don't always know to use the latter).

First step is searching existing change records for related strings and keywords. There are two options: for small changes, add language like "Previously... Following [#foo], ..." and add a reference to the new issue as well as the previous ones, or for extensive changes, draft a completely new CR to replace the old one, again with references to all the applicable issues.

I'm closing this issue as as part of issue queue clean-up meta: #2960983: [meta] Plan for Mentoring Project/Issue Queue. This does not mean topics in this issue is or was not important or completed.

Issue was mainly used for organising other issues and as a collector one for @xjm and @YesCT - if you feel reopening it makes sense, do so, otherwise i think closing it after almost 3 years of being untouched could be sufficient as outdated.