Meeting - Contributor Guide Update - 28 July 2020

This meeting is on 28 July 2020 at 16:00 UTC** (9 AM US/Pacific, 12 noon US/Eastern) in the #documentation channel on Drupal Slack. This meeting is text-only, no audio or video, and is asynchronous so everyone can join in as they're available for about 24 hours. After that we'll capture notes from the threads.

Agenda - please feel free to edit this to add items!

Hello and welcome to the Contributor Guide Update meeting!

This meeting:
➤ Usually happens on alternate Tuesdays at 16:00 UTC
➤ is text only!
➤ happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ has a public agenda issue anyone can add to.
➤ :star: Meeting transcripts are still a work in progress, but please comment on the meeting agenda issue so we can grant you credit for attending/contributing!

:zero: *Roll Call!*
Who’s here today? Comment in the thread below if you’d like to introduce yourself and share something that will make us smile.

:one: Updates to the content types and views
- We have been using the new content types for a few weeks, and have come up with some updates that may be needed
- Suggestions to be discussed at the meeting are on: https://www.drupal.org/project/drupalorg/issues/3151462

:two: Content migration/creation: We need to figure out how to organize this
- We have a lot of existing content in the old Getting Involved Guide https://www.drupal.org/getting-involved-guide and our goal is to create a great Contributor Guide at https://www.drupal.org/community/contributor-guide
- Some of the old content is good and needs to be migrated. Some of the content is outdated and needs to be revised or deleted. It is very difficult for someone new to contributing to Drupal to understand which is which. We have at least one willing contributor who has time, is great at tech writing, but is new to contributing to Drupal, and we need to organize the effort so that people like that can contribute.
- Would a good approach be to inventory the old Guide and have people familiar with contributing decide on what to do with each page?
- If not, how should we organize the effort to create a great Contributor Guide, so that people less familiar with contributing can contribute? See also the meta issue listing all the Areas that need to be worked on: https://www.drupal.org/project/drupal_org_community/issues/3137918

:three: *Anything Else?*: What else do we need to talk about?

That’s all for now!

The discussions continue in the threads! Please feel free to chime in within the next 24 hours to be captured in the meeting notes. Thank you very much to everyone for attending, learning, and contributing!

Meeting Transcript

jhodgdon (she/her) Jul 28th at 9:01 AM
Hello and welcome to the Contributor Guide Update meeting!This meeting:
➤ Usually happens on alternate Tuesdays at 16:00 UTC
➤ is text only!
➤ happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ has a public agenda issue anyone can add to.
➤ :star: Meeting transcripts are still a work in progress, but please comment on the meeting agenda issue so we can grant you credit for attending/contributing!:zero: *Roll Call!*
Who’s here today? Comment in the thread below if you’d like to introduce yourself and share something that will make us smile.
11 replies
jhodgdon (she/her) 5 days ago
Jennifer here. We have a lot of businesses that put silly things on signs. One recent one: What do you call a fake noodle? An impasta.
jhodgdon (she/her) 5 days ago
@rachel_norfolk we didn't discuss who is leading the meeting today, but I'm happy to do it. :)
rachel_norfolk 5 days ago
Hi!!! Rachel, UK, trying to recover from DrupalCon Global, still!!! Also, got out across the north coast of Scotland last week. So, obligatory picture of the Duke of Wellington in Glasgow:
rachel_norfolk 5 days ago
True!! If you do it, I’ll do that transcript
Carolyn Shannon 5 days ago
Carolyn from Chicagolandia, with her foster-pup Moose, who likes to sit in the wood box.
moose4.jpg
moose4.jpg
rachel_norfolk 5 days ago
Image from iOS
Image from iOS
kay_v 5 days ago
Kay here from Boston. still not back from what appears to have been the Drupal flu in the leadup to drupalcon (among the impressive features of virtual conference sites?)
valthebald 5 days ago
Val from Bulgaria here
brittany.huntzberry / britt (she/her) 5 days ago
Hi all, Brittany / Britt here from Arizona, US! My rats make me smile, especially when they're awake and super excited for food. :slightly_smiling_face:
Webbeh (he/him) 5 days ago
Hello world! Eric here from Atlanta, GA!
jhodgdon (she/her) 5 days ago
Everyone, welcome again! Please add a comment on the meeting issue so that we can give you credit for attending today. https://www.drupal.org/project/drupal_org_community/issues/3161290
Drupal.org
Meeting - Contributor Guide Update - 28 July 2020
This meeting is on 28 July 2020 at 16:00 UTC** (9 AM US/Pacific, 12 noon US/Eastern) in the #documentation channel on Drupal Slack. This meeting is text-only, no audio or video, and is asynchronous so everyone can join in as they're available for about 24 hours. After that we'll capture notes from the threads. Agenda - please feel free to edit this to add items! Hello and welcome to the Contributor Guide Update meeting! This meeting: ➤ Usually happens on alternate Tuesdays at 16:00 UTC ➤ is text only!
Jul 24th

---

jhodgdon (she/her) Jul 28th at 9:06 AM
:one: Updates to the content types and views
- We have been using the new content types for a few weeks, and have come up with some updates that may be needed
- Suggestions to be discussed at the meeting are on: https://www.drupal.org/project/drupalorg/issues/3151462
Drupal.org
Improve the content types/views for the Contributor Guide
On #3089403: Create content types for a new Getting Involved section, we created content types and views for the new Contributor Guide. As we create content and begin to use the Contributor Guide to help new contributors figure out how to contribute to the project, we will find things we could improve in the content types and views. This issue will collect ideas and implement the best ones. List of ideas Skills pages could use a field for "Related Skills". For instance, someone who finds "Drupal Theming" might also want to see HTML, CSS, and Twig skills (and vice versa).
Jun 13th
53 replies
jhodgdon (she/her) 5 days ago
This thread of the meeting is about improvements we can make to the content types and the views that make up the Contributor Guide
jhodgdon (she/her) 5 days ago
One suggestion I had: Skills pages could use a field for "Related Skills". For instance, someone who finds "Drupal Theming" might also want to see HTML, CSS, and Twig skills (and vice versa).
jhodgdon (she/her) 5 days ago
As a note, we already have a field on Tasks that says "This task might lead to...", which is kind of a "related" field, and also a similar field on Roles.
jhodgdon (she/her) 5 days ago
But we don't have currently an easy way to relate skills to each other.
jhodgdon (she/her) 5 days ago
Second suggestion: Skills learned/improved field on Tasks -- change label on this field (and on the blocks that display this relationship on Task and Skill pages) to convey "Skills that aren't absolutely required, but that you could use while doing this task", which is pretty much how we've been using it anyway. If we do this, go back to existing Task pages and see if the list of skills in this field is still correct (may need to add/remove some). See comment 12 for more ideas/reasoning on this item.
jhodgdon (she/her) 5 days ago
So the idea here is that we currently have a "Skills required" field on Tasks, and another one that says "Skills learned/improved". But I think we need a field for "Skills that you might use in some cases"
jhodgdon (she/her) 5 days ago
Example: Someone might not choose a task if it says you need the skill of "Setting up a development environment", when it's kind of optional because you could be testing a patch and you could use simplytest.me instead.
jhodgdon (she/her) 5 days ago
But someone who has some skill in testing software might be browsing skills, find the Testing Software skill, and we would want them to find the "Test a patch" task.
jhodgdon (she/her) 5 days ago
We have that field for "skills learned/improved", and I think we could repurpose it to "skilsl that you might optionally use"
jhodgdon (she/her) 5 days ago
The field would need a more snappy name... Any thoughts?
Carolyn Shannon 5 days ago
A skill (eg “Drupal site building”) could potentially have a “related skills” reference, or maybe even a “prerequisite skills” reference.
jhodgdon (she/her) 5 days ago
The third suggestion on the "improve content types" issue is to move the "Background information" field display to a better location on Task pages. Right now it is in the sidebar, and people who need that information might not see it. My proposal is to put it before the Steps, and to style it so people have the page title and summary.
jhodgdon (she/her) 5 days ago
Prerequisite skills is a possibility... We can handle that somewhat now by putting links in the other fields.
rachel_norfolk 5 days ago
good questions!

I like the idea of a related skills field (and adding a field is less daunting than changing one on live!)
I’m inclined to say that the “core skills” is right but the “optional skills” you mention probably are indeed skills you may learn on the job. We probably just need to make it more clear that skills used occasionally are ones to learn on job

jhodgdon (she/her) 5 days ago
But yes I think we should have related skills.
jhodgdon (she/her) 5 days ago
We only have a few tasks on the site right now, so I am not all that worried about making a change to the existing field (just changing the displayed name of the field).
jhodgdon (she/her) 5 days ago
Optional skills is a good name.
Carolyn Shannon 5 days ago
For tasks, “skills that you might optionally use” could be “related skills”? I like the pairing of “what skills you need going into the task” and “what skills you get out of the task”.
jhodgdon (she/her) 5 days ago
The field right now I think conveys "what you get out of the task", but ... pretty much people have been duplicating the "skills you need" in the existing "skills you learn" field, which makes it kind of worthless.
rachel_norfolk 5 days ago
yeah - @Carolyn Shannon has it
jhodgdon (she/her) 5 days ago
I mean, any task that requires a given skill, you would probably also improve that skill. (edited)
jhodgdon (she/her) 5 days ago
What I'm proposing is to change the "skills you learn/improve" to say "optional skills", because these are the skills that you might use, or might not, depending.
jhodgdon (she/her) 5 days ago
so they are not prerequisites, but if you have the skill, you can use it.
rachel_norfolk 5 days ago
yeah
jhodgdon (she/her) 5 days ago
This way we would have two fields for skills related to tasks, but we would be less inclined to duplicate skills between the two fields.
Carolyn Shannon 5 days ago
sounds good
jhodgdon (she/her) 5 days ago
We would document the essentials and the maybes
jhodgdon (she/her) 5 days ago
so someone would know if they have the skills to do the task, but still be drawn in from a variety of skills to find a task that could use that skill.
jhodgdon (she/her) 5 days ago
So... looks like we can adopt (a) Add a Related skills field to Skills and (b) Change the skills learned/improved field on Tasks to be called Optional skills?
rachel_norfolk 5 days ago
a) yes
b) do we need to change the name of the field or just the description? I think the latter
Carolyn Shannon 5 days ago
yep
Carolyn Shannon 5 days ago
just the description I think
jhodgdon (she/her) 5 days ago
For (b) I tihnk the name, because the description is only shown on Edit pages, but the name is shown on Task output pages.
jhodgdon (she/her) 5 days ago
Also we need to (IMO) change the labels on the views that show the relationships on Skill pages.
jhodgdon (she/her) 5 days ago
So, one more quick one: Take a look at https://www.drupal.org/community/contributor-guide/task/identify-duplica...
jhodgdon (she/her) 5 days ago
That task has some background information that someone might not notice, because it's up in the sidebar.
rachel_norfolk 5 days ago
hmm - I wonder if we could expose the description on the view?
rachel_norfolk 5 days ago
to give context to the reader
jhodgdon (she/her) 5 days ago
My proposal is to move the background info field to between skills required and detailed steps
rachel_norfolk 5 days ago
okay
Carolyn Shannon 5 days ago
ok sounds good
jhodgdon (she/her) 5 days ago
Back to (b) -- to me, both the required skills and the optional skills are skills you can learn/improve, so I don't actually like the idea of having one field called "skills learned/improved" and I prefer the name "optional skills" for that?
jhodgdon (she/her) 5 days ago
(meanwhile, we still have something else to discuss so I'll start another thread, while we continue to think here)
jhodgdon (she/her) 5 days ago
And by the way, I will be available this week to work on the decided-on changes.
rachel_norfolk 5 days ago
Can you checkin with Neil before getting stuck in? He might have thoughts
Carolyn Shannon 5 days ago
Was the idea behind “learned/improved” to be able to give credit? Or to help give people tasks that would help them acquire a specific skill?
jhodgdon (she/her) 5 days ago
Will do (check with Neil)
rachel_norfolk 5 days ago
I think the latter Carolyn
jhodgdon (she/her) 5 days ago
agreed.
jhodgdon (she/her) 5 days ago
Also to help make links between Skill pages and Tasks (if you're browsing skills, to find tasks you could do with that skill).
jhodgdon (she/her) 5 days ago
But it's not helpful if we have 2 fields with exactly (in practice) the same information in them.
jhodgdon (she/her) 4 days ago
I made a patch for these proposed improvements -- links to check it out at https://www.drupal.org/project/drupalorg/issues/3151462#comment-13768346
Drupal.org
Improve the content types/views for the Contributor Guide
On #3089403: Create content types for a new Getting Involved section, we created content types and views for the new Contributor Guide. As we create content and begin to use the Contributor Guide to help new contributors figure out how to contribute to the project, we will find things we could improve in the content types and views. This issue will collect ideas and implement the best ones. List of ideas Skills pages could use a field for "Related Skills". For instance, someone who finds "Drupal Theming" might also want to see HTML, CSS, and Twig skills (and vice versa).
Jun 13th
jhodgdon (she/her) 4 days ago
I'll be away from Slack for the next few days, but please take a look if you have time, thanks!

[Postscript: The changes were committed by @drumm!!]

---

jhodgdon (she/her) Jul 28th at 9:28 AM
:two: Content migration/creation: We need to figure out how to organize this
- We have a lot of existing content in the old Getting Involved Guide https://www.drupal.org/getting-involved-guide and our goal is to create a great Contributor Guide at https://www.drupal.org/community/contributor-guide
- Some of the old content is good and needs to be migrated. Some of the content is outdated and needs to be revised or deleted. It is very difficult for someone new to contributing to Drupal to understand which is which. We have at least one willing contributor who has time, is great at tech writing, but is new to contributing to Drupal, and we need to organize the effort so that people like that can contribute.
- Would a good approach be to inventory the old Guide and have people familiar with contributing decide on what to do with each page?
- If not, how should we organize the effort to create a great Contributor Guide, so that people less familiar with contributing can contribute? See also the meta issue listing all the Areas that need to be worked on: https://www.drupal.org/project/drupal_org_community/issues/3137918
Drupal.org
Getting Involved Guide
Note: We are working on replacing this Getting Involved Guide section with a new Contributor Guide -- with new content in a new organizational structure. Some content in this section has already been moved there.Learn more about this project, and find out how to help, on the Getting Involved Refresh project overview page. It’s really the Drupal community and not so much the software that makes the Drupal project what it is. So fostering the Drupal community is actually more important than just managing the codebase. - Dries Buytaert As an open-source project, we don’t have employees to provide Drupal improvements and support. We depend on our diverse community of passionate volunteers to mov…
Jul 12th, 2008
Drupal.org
Contributor guide
Note: This is a work in progress! We are working on replacing the Getting Involved Guide with new content in a new organizational structure. Learn more about this project, and find out how to help, on the Getting Involved Refresh project overview page.
Jan 28th
Drupal.org
[Meta] Create content for Contributor Area sections
We need to create content for all of the Contribution Areas. Here are the guidelines for how/when/why to create a contribution area page: Guidelines for contribution areas. For each Contribution Area page, we need to create a child issue with the following summary: Develop/edit content for Contribute to WHATEVER IT IS Area Page of the Contributor Guide.
May 19th
138 replies
jhodgdon (she/her) 5 days ago
We made a bunch of progress at DrupalCon, and we've gained a regular contributor @MargyLY,who has been working on this. But she's running into obstacles of not knowing what content in the old Getting Involved Guide is worth keeping, and what content is incorrect/outdated.
MargyLY 5 days ago
I hope I represent other writers would contribute if it were easier to get started.
jhodgdon (she/her) 5 days ago
MargyLY suggested we inventory the existing content in the Getting Involved Guide, and for each page, have leaders of various areas decide on its disposition. Then someone like her (a writer with less experience as a Drupal project contributor) can come through and actually do the work of migrating the content.
jhodgdon (she/her) 5 days ago
Yes, I agree we need to make it easier for others like you to contribute!
rachel_norfolk 5 days ago
Would recording a video help?
Carolyn Shannon 5 days ago
Content inventory with a disposition field would help.
rachel_norfolk 5 days ago
Like with @jhodgdon (she/her) talking us all through the process
jhodgdon (she/her) 5 days ago
The problem isn't that people don't understand the process, so I don't think a video would help... I think the problem is that people who, for example, haven't been lately contributing code patches to Core don't know if the pages about doing so are current or outdated, useful or stupid, etc.
jhodgdon (she/her) 5 days ago
Do you concur with that @MargyLY?It seems like you understand the mechanics of creating/editing content on drupal.org for the Guide, but are stuck with "is this page worth migrating?"
brittany.huntzberry / britt (she/her) 5 days ago
Is there any bandwidth available for mentoring? There is definitely a lot of background to contributing that can be hard to parse through for someone unfamiliar with the content and expectations. Or at least somewhere that questions can be dropped and answered in a relatively comfortable environment and help from community members that have more experience?
MargyLY 5 days ago
A video isn't the point. I know how to edit a page. I can follow numbered steps. (LOVE numbered steps!). It's the starting point that's missing.
Carolyn Shannon 5 days ago
Questions can come to this channel.
jhodgdon (she/her) 5 days ago
t seems like we need subject matter experts rather than process experts?
brittany.huntzberry / britt (she/her) 5 days ago
And filtering out what are the guidelines and best practices that are currently expected in contributing. We can move pages and content, but is the content actually worthwhile and still relevant? I wouldn't know personally as a new contributor.
jhodgdon (she/her) 5 days ago
So I like MargyLY's thought of making an inventory and asking the subject matter Area leaders to decide on whether the pages are good or not?
Carolyn Shannon 5 days ago
For some, definitely. Merging/migrating/curation is different from writing new.
jhodgdon (she/her) 5 days ago
Right, filtering is the problem exactly.
MargyLY 5 days ago
It would be great to retire pages that suggest tasks that aren't actually wanted.
jhodgdon (she/her) 5 days ago
Yes.
Carolyn Shannon 5 days ago
And there is overlap.
jhodgdon (she/her) 5 days ago
Yes, there is overlap.
Carolyn Shannon 5 days ago
It’d be great to combine/merge/cull.
MargyLY 5 days ago
Like this page and all its children are about editing the "Getting Involved Guide" AFAIK. You don't want any of that to happen, right?
jhodgdon (she/her) 5 days ago
Which page?
rachel_norfolk 5 days ago
If we were to ask subject matter experts to “tag” pages in the old guide that were worth migrating, would that help?
MargyLY 5 days ago
Oops, sorry - https://www.drupal.org/contributor-tasks/writers
Drupal.org
New contributor tasks: Writers
Here are some tasks for technical writers who are new to contributing to the Drupal project. Dive in! You might also check the Tasks for anyone section for more ideas on how to contribute. Many of the tasks in that section are also related to Drupal documentation. Adding new tasks If you know a task that would be appropriate for a new contributor to do, read the Adding New Tasks page to find out how to add it (there's a template).
Feb 1st, 2012
jhodgdon (she/her) 5 days ago
I think we need a more systematic approach.
jhodgdon (she/her) 5 days ago
MargyLY just suggested on another thread (outside the meeting) that we make a spreadsheet of all the Getting Involved pages and decide there about disposition. I also like spreadsheets. :)
rachel_norfolk 5 days ago
some sort of regular “office hours” where we invite each subject matter expert in turn?
Carolyn Shannon 5 days ago
That’s my standard approach for content strategy for migrations, yeah.
jhodgdon (she/her) 5 days ago
I can recruit people to help decide on things... I think office hours are difficult, but getting people to fill in parts of a spreadsheet is not so hard maybe?
jhodgdon (she/her) 5 days ago
OK, spreadsheet it is!
rachel_norfolk 5 days ago
true - spreadsheet is probably easier to work
jhodgdon (she/her) 5 days ago
I will ask Neil if there is a way to dump out the hierarchy.
Carolyn Shannon 5 days ago
yeeeeessssss!
rachel_norfolk 5 days ago
:thumbsup:
jhodgdon (she/her) 5 days ago
(would not enjoy making that list by hand)
MargyLY 5 days ago
Re the spreadsheet: Anyone with drush access to the site can run a SQL command that would list all the published pages that don't have redirects and that have aliases that start with /community. I can take that output and put it into a spreadsheet.
jhodgdon (she/her) 5 days ago
The aliases are not universal. We need the book hierarchy.
rachel_norfolk 5 days ago
yeah - I fell foul of that before
brittany.huntzberry / britt (she/her) 5 days ago
Haha, I do enjoy spreadsheets myself. There could be some informal process to review with some experts on something like patches, code standards tho (if they want to). That seems more down the line when things are in their home and content needs editing on them.
MargyLY 5 days ago
Can you say more about the structure of the various documentation sections we are working on?
jhodgdon (she/her) 5 days ago
All of those aliases were put in by hand, so they are inconsistent, and not all pages have aliases.
jhodgdon (she/her) 5 days ago
I'm talking about just the existing Getting Involved Guide. The hierarchy is a Drupal 7 "Book" structure.
jhodgdon (she/her) 5 days ago
Which is similar to a hierarchical menu. Any content type can (technically) be put into a book outline.
MargyLY 5 days ago
Okay, the SQL can select for all pages that are in that book.
MargyLY 5 days ago
(I know all about D7 books.)
jhodgdon (she/her) 5 days ago
I can run drush commands on a dev site...
MargyLY 5 days ago
NICE!
jhodgdon (she/her) 5 days ago
I will look into the exact SQL to select that, good idea.
jhodgdon (she/her) 5 days ago
When I get Neil to spin up or refresh a dev site to work on the content types, I can log in there and do that and make a spreadsheet.
MargyLY 5 days ago
Without being able to see the structure I can't write the SQL but sounds like you guys are on it.
MargyLY 5 days ago
What do we want to know about each node? Alias, title, ...
jhodgdon (she/her) 5 days ago
I'll make it a Google Doc and post it on https://www.drupal.org/project/drupal_org_community/issues/3138007 and we can start working on it. Does that sound like a good plan for a next step?
Drupal.org
Create content for the identified roles, skills, and tasks
On #3089403: Create content types for a new Getting Involved section, we deployed content types and views for a new Contributor Guide. So, now we need to use the new content types to create content for roles, tasks, and skills, and migrate content from the old Getting Involved Guide into the new content types. Related effort: #3137918: [Meta] Create content for Contributor Area sections Some of the content may also be written/migrated in conjunction with Contribution Area pages, on child issues of #3137918: [Meta] Create content for Contributor Area sections We'll use this issue for generic content that isn't specifically associated with any particular area, or crosses multiple areas. Migrating existing content
May 19th
jhodgdon (she/her) 5 days ago
Alias, title, parent/hierarchy
jhodgdon (she/her) 5 days ago
URL
jhodgdon (she/her) 5 days ago
(node ID)
Carolyn Shannon 5 days ago
book depth
Carolyn Shannon 5 days ago
nid, last updated?
eojthebrave 5 days ago
last updated date
eojthebrave 5 days ago
:slightly_smiling_face:
jhodgdon (she/her) 5 days ago
ok
MargyLY 5 days ago
Alias and URL are redundant. Node ID and last update are great ideas.
jhodgdon (she/her) 5 days ago
Then the spreadsheet should probably have an Area designation, and some fields for "what should we do with it"
rachel_norfolk 5 days ago
last updated date will tell us a lot
MargyLY 5 days ago
You'll need our Google IDs so you can grant write access to the spreadsheet?
jhodgdon (she/her) 5 days ago
Yes, please PM me if you'd like write access to the spreadsheet.
rachel_norfolk 5 days ago
post the link and we can request access
MargyLY 5 days ago
In the "what should we do with it" column, what should the options be?
jhodgdon (she/her) 5 days ago
that too.
jhodgdon (she/her) 5 days ago
Good question... options:
jhodgdon (she/her) 5 days ago

Delete

jhodgdon (she/her) 5 days ago

Migrate as is

jhodgdon (she/her) 5 days ago

Split into ....

Carolyn Shannon 5 days ago

Migrate needs work

(edited)
jhodgdon (she/her) 5 days ago
Then we should have a big Notes field probably for more details?
Carolyn Shannon 5 days ago

Merge into (w/field for destination)

MargyLY 5 days ago
And a Status field for "In progress" and "Done"?
jhodgdon (she/her) 5 days ago
OK, I will try to get to that today. Meanwhile, perhaps hold off on migrating more content and concentrate on editing existing Skills pages (which always needs to be done)?
MargyLY 5 days ago
Or maybe just add "Done to the "Plan" column.
jhodgdon (she/her) 5 days ago
Yes, Status!!
jhodgdon (she/her) 5 days ago
I think a separate field is easier to scan for status.
rachel_norfolk 5 days ago
yeah
MargyLY 5 days ago
A column for a link to the replacement page?
jhodgdon (she/her) 5 days ago
k
MargyLY 5 days ago
So you can make the redirects?
rachel_norfolk 5 days ago
good point
jhodgdon (she/her) 5 days ago
yes.
MargyLY 5 days ago
Dumb question -- are these pages already all updated for D8/9?
Carolyn Shannon 5 days ago
No

---

:three: *Anything Else?*: What else do we need to talk about?

MargyLY Jul 28th at 9:54 AM
Back to this question: https://www.drupal.org/contributor-tasks/writers purports to provide tasks that writers can jump in and do. But they actually can't do some of them. Fix that?
37 replies
MargyLY 5 days ago
Also, can we combine https://www.drupal.org/contributor-tasks/writers and https://www.drupal.org/contribute/documentation?
Drupal.org
Contribute to documentation
What is Drupal Documentation? Members of the Drupal community can write and edit all sorts of Drupal documentation: Community Documentation pages on Drupal.org Programming API reference on api.drupal.org Guide to the Drupal community and getting involved Drupal.org content moderation Help pages within the core Drupal software
Jun 8th, 2005
MargyLY 5 days ago
Maybe point them to https://www.drupal.org/community/about/getting-involved-guide-becoming-c...
Drupal.org
Getting Involved Guide becoming Contributor Guide
The Getting Involved Guide is intended to provide everything a member of the Drupal Community, old and new, needs to know to "get involved" in working with others to improve Drupal and, indeed, their own careers. We are working on transforming this into a new Contributor Guide. We will be rebuilding the guide, from the bottom up, to better meet this goal and to involve the right subject matter experts in each subsection.
Aug 15th, 2019
jhodgdon (she/her) 5 days ago
Everything under Getting Involved is currently suspected of being wrong.
jhodgdon (she/her) 5 days ago
I do not really want to go down the rabbit hole of trying to edit particular pages in Getting Involved to redirect people to more appropriate locations.
MargyLY 5 days ago
So that's the place to start, so it makes sense to start with that inventory. Can we take down the pages that suggest working on the Getting Involved pages? (How would I know not to waste my time, if I were just showing up today?)
MargyLY 5 days ago
I'm suggesting retiring one or both of https://www.drupal.org/contributor-tasks/writers and https://www.drupal.org/contribute/documentation, and redirecting them to https://www.drupal.org/community/about/getting-involved-guide-becoming-c...
jhodgdon (she/her) 5 days ago
OK, we can start with that but again, there are a ton of pages in Getting Involved that need taking down or deleting or redirecting, and I don't really think that any one is all that more important than any other to fix RIGHT NOW.
jhodgdon (she/her) 5 days ago
I would rather spend my time organizing the effort to fix all the pages?
MargyLY 5 days ago
Okay, I'll give up on that idea.
rachel_norfolk 5 days ago
not sure i understand what is being asked here.
jhodgdon (she/her) 5 days ago
Those pages are about a lot more than just the Getting Involved Guide. They are related to editing everything under drupal.org/documentation and are not completely outdated or wrong.
rachel_norfolk 5 days ago
ah!
MargyLY 5 days ago
There are pages that say, "Help us with documentation" and suggest tasks that you don't actually want done. I did one and only afterward found out that it was a waste of my time.
rachel_norfolk 5 days ago
ah right
jhodgdon (she/her) 5 days ago
Agreed. Some are outdated. Some are good. We need to get that spreadsheet made and filled in so people like you can migrate the pages that are still useful, and we can delete/redirect pages that aren't.
MargyLY 5 days ago
https://www.drupal.org/contributor-tasks/writers should have a paragraph at the top saying, "Deprecated! See https://www.drupal.org/community/about/getting-involved-guide-becoming-c... instead!"
jhodgdon (she/her) 5 days ago
I disagree. Many of the pages in there are about editing documentation pages, not Contributor Guide pages.
MargyLY 5 days ago
Agreed that the spreadsheet is more urgent -- go with that!