This meeting is on 6 October 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.
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 tell us your favorite thing about the season that just started in your part of the world.
:one: Content status -- Migrations of old Getting Involved Guide
- We have a Google spreadsheet for the content migrations in the old Getting Involved Guide:
https://docs.google.com/spreadsheets/d/15bLdzwwe9xECfTGM4miAQRzUs3pGqz3z...
- A lot has been done; some still left to do... [will start separate threads]
:one: :a: Community Initiatives -- https://www.drupal.org/community-initiatives
:one: :b: Drupal Core development policies:
- Beta testing https://www.drupal.org/docs/8/minor-release-beta-testing-program
- Other policies https://www.drupal.org/contribute/core
:one: :c: Contribute to Documentation -- https://www.drupal.org/contribute/documentation
- Are these pages at all current?
:one: :d: Contributor Tasks -- https://www.drupal.org/contributor-tasks
- Some are good; some are outdated; I am not sure which are which
:one: :e: Misc pages:
- Guides to how to apply patches on various OS without using Git command line [delete?] https://www.drupal.org/patch/apply
- Most of the other pages I think I know what to do with
:two: Content status -- Other areas:
- I had a meeting with the Event Organizers group mid-September, and they are hopefully going to round up content and get it to us on https://www.drupal.org/project/event_organizers/issues/3165327
- We need to figure out who the area heads are for the Area issues, contact them, and figure out what roles/tasks should be created for those areas. Parent issue: 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!
jhodgdon (she/her) Yesterday at 9:01 AM
:zero: *Roll Call!*
Who’s here today? Comment in the thread below if you’d like to introduce yourself and tell us your favorite thing about the season that just started in your part of the world.
jhodgdon (she/her) 1 day ago
I'm Jennifer, in the inland northwest part of USA. It is autumn here, and I like the cooler weather and pretty leaves.
rachel_norfolk 1 day ago
Hi! Rachel here from the UK. Heading into Autumn and it’s definitely a time for finding pubs with log fires. Mind you, that’s not easy this year!
hestenet (he/him) 1 day ago
Tim from Portland, OR, USA. Normally would be very excited for Halloween but not sure what that will be like this year.
:wave:
1
bircher 1 day ago
Fabian :flag-ch: :flag-cz: it is autumn here too, gray, rainy, cold
:wave:
1
AmyJune (volkswagenchick she/her) 1 day ago
AmyJune coming in a bit late… the leaves falling is always my fav art of the season.
:fallen_leaf:
2
jhodgdon (she/her) Yesterday at 9:05 AM
:one: Content status -- Migrations of old Getting Involved Guide
- We have a Google spreadsheet for the content migrations in the old Getting Involved Guide:
https://docs.google.com/spreadsheets/d/15bLdzwwe9xECfTGM4miAQRzUs3pGqz3z...
- A lot has been done; some still left to do... [will start separate threads about work to be done]
jhodgdon (she/her) 1 day ago
The content that has already been migrated is at:
jhodgdon (she/her) 1 day ago
a) Sub-pages of https://www.drupal.org/community/contributor-guide/reference-information
Drupal.org
Contributor guide reference information
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.
Feb 11th
jhodgdon (she/her) 1 day ago
b) https://www.drupal.org/docs/develop/issues
Drupal.org
Drupal project issues
The Drupal project and community as a whole is composed of many smaller "projects", and each project uses "issues" to keep track of bugs, feature requests, tasks, and in some cases, support requests. Most people who contribute time to the Drupal project will eventually find themselves interacting with issues, so it is important to understand how they work and how the Drupal community uses them.
Jul 1st
jhodgdon (she/her) 1 day ago
c) https://www.drupal.org/docs/develop/git
Drupal.org
Git version control system
The Drupal open-source software project and community organizes itself into projects; most have an associated source code repository. Changes to the source code are tracked using the Git revision control system, and we use GitLab software to provide a web interface to Git and other features. Most changes to the source code are managed using issues on the drupal.org web site.
Sep 14th
jhodgdon (she/her) 1 day ago
and a few pages went under https://www.drupal.org/drupalorg/docs or as tasks/etc. in https://www.drupal.org/community/contributor-guide
Drupal.org
Drupal.org documentation
Various guides and guidelines on using Drupal.org tools and services.
Jul 8th, 2016
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
rachel_norfolk 1 day ago
There has been a huge amount migrated but also a huge, huge, huge amount still to go.
What moves can we make to step up our capacity here?
jhodgdon (she/her) 1 day ago
Let's discuss that in the individual sub-threads because it depends on the content.
rachel_norfolk 1 day ago
ok
hestenet (he/him) 1 day ago
Echoing the same question and will look in the other threads. Wondering if we can put out a call for migration assistants to help you in DA channels.
bircher 1 day ago
is there an estimate of when that will be in a state one can refer new contributors to? ie next virtual drupalcon?
jhodgdon (she/her) 1 day ago
Depends on how much help we get, honestly. I can only do so much... I was hoping to get inexperienced contributors to help, but there are too many decisions about what is relevant/current or not in the migration, and it's too hard for people who don't know the current contribution procedures to write new docs about contributor tasks and stuff like that, so it's pretty difficult to get it done.
:heavy_plus_sign:
2
:100:
1
jhodgdon (she/her) Yesterday at 9:07 AM
:one: :a: [beginning of Work To Be Done threads] Community Initiatives -- https://www.drupal.org/community-initiatives
Drupal.org
Community Initiatives
These are the critical projects that people in the Drupal community are working on. If you'd like to find a place to jump in and start contributing, start here. Drupal Core Drupal core initiatives: Help out on the next release of Drupal!
Jan 20th, 2009
jhodgdon (she/her) 1 day ago
I've been discussing this with @Kristen Pol (she/her) -- I think our plan is to move the Initiatives documentation to a dedicated section under either https://www.drupal.org/docs/ or https://www.drupal.org/docs/develop
Drupal.org
Drupal
Drupal community-maintained documentation.
May 26th, 2016
Drupal.org
Develop
Documentation for developers about tools, processes, and standards that are not specific to a major version of Drupal. For version specific documentation see the Drupal 8, and Drupal 7 documentation.
Sep 20th, 2016
jhodgdon (she/her) 1 day ago
I'm undecided about which one it belongs under... Develop is more oriented towards coding, and many of the initiatives are not coding, so I'm leaning towards the Drupal guide.
jhodgdon (she/her) 1 day ago
Any thoughts?
jhodgdon (she/her) 1 day ago
The migration process for this information is fairly straightforward but somewhat tedious. I can do it, or if someone else has time, they could do it if we get them the proper permissions. Anyone interested and with time, let me know and I can provide information on how to do it.
hestenet (he/him) 1 day ago
Hmm.
jhodgdon (she/her) 1 day ago
@Kristen Pol (she/her) already went through and cleaned up the Initiatives docs by archiving the old initiatives.
hestenet (he/him) 1 day ago
I'm thinking about whether we should find a way to integrate these changes with the /strategic-initiatives section, which is a non-docs area...
jhodgdon (she/her) 1 day ago
Do you have a script that will migrate docs -- the problem is it's a multi-level outline, and the Guide docs on d.o have a hard limit of 1000 characters for the body (which is tiny). So it seems to take a human to make a Guide structure and then migrate the pages under them.
jhodgdon (she/her) 1 day ago
Strategic initiatives are separate.
rachel_norfolk 1 day ago
I would say that the community guide contains the roles, tasks and skills required to create and maintain the inititatives more than the initiatives themselves
jhodgdon (she/her) 1 day ago
These are Community Initiatives.
jhodgdon (she/her) 1 day ago
What I learned from Gabor/Kristin was "Strategic are the initiatives that our Fearless Leader has designated for the Driesnote" basically.
:joy:
1
hestenet (he/him) 1 day ago
Totally, not quite the same as the 'official' ones for sure, but wondering if it should be organized in a similar way. Just thinking out loud though.
hestenet (he/him) 1 day ago
I think you're probably right that they should be migrated into Guides and then even if we make some dedicated landing area for community initiatives in the same way as the strategic ones, we can link them in...
jhodgdon (she/her) 1 day ago
I have a proposed structure for the community initiatives section in the second tab of the Google sheet I linked in the other thread.
hestenet (he/him) 1 day ago
I'll take a look.
jhodgdon (she/her) 1 day ago
We can also make a Related Content link from Community to Strategic initaitives and vice versa (or an in-text link if the Related is the wrong content type).
hestenet (he/him) 1 day ago
(I'm also brainstorming this because it relates to the groups replacement notion - can we provide initiative section features to accomplish what groups used to for these) (edited)
hestenet (he/him) 1 day ago
Yeah the related content linking makes sense.
jhodgdon (she/her) 1 day ago
Kristin already said she thought the structure was OK, I just haven't done the migration yet. Gabor said OK as well on the Iniatiaves proposal.
rachel_norfolk 1 day ago
I like the related content thing
hestenet (he/him) 1 day ago
+1
jhodgdon (she/her) 1 day ago
There was talk at some point in the past of an Initiative content type. Is that happening?
rachel_norfolk 1 day ago
We should definitely not forget to capture the “how” of the initiatives - matters at least as much as the “what”
jhodgdon (she/her) 1 day ago
Yeah what we have now is just pages.
jhodgdon (she/her) 1 day ago
the "what".
jhodgdon (she/her) 1 day ago
describing them.
jhodgdon (she/her) 1 day ago
Not sure we have any docs on "how" at this time... not sure what they would cover?
rachel_norfolk 1 day ago
how the initiatives were determined
rachel_norfolk 1 day ago
that’s the bit I’m really interested in capturing
jhodgdon (she/her) 1 day ago
The Community ones, my understanding is "a group got together and decided to do something and called it an Initiative". The Strategic ones are not determined by the community.
rachel_norfolk 1 day ago
(mainly because, as a community, we are not very good at capturing it)
rachel_norfolk 1 day ago
okay - tell you what - I’m going to bother Dries until we get that…
jhodgdon (she/her) 1 day ago
Good, and that should go into the Strategic section.
rachel_norfolk 1 day ago
ok
jhodgdon (she/her) 1 day ago
Kristin is working on an initiative to get people involved in initiatives. :)
rachel_norfolk 1 day ago
awesome! The strategic ones?
jhodgdon (she/her) 1 day ago
I think all of them.
rachel_norfolk 1 day ago
good good
hestenet (he/him) 1 day ago
Yeah, definitely still interested in something like an initiative content type. The above sounds great as a start :slightly_smiling_face:
jhodgdon (she/her) 1 day ago
OK, well we can move the docs at least into a structure, and then if there is an Initiative content type, at least we'll have a clean starting point.
hestenet (he/him) 1 day ago
Agreed.
jhodgdon (she/her) 1 day ago
OK, I'll add this section to my "ready to migrate, just do it" queue. :)
jhodgdon (she/her) 1 day ago
Which was kind of empty, so this will probably be the next bit.
Kristen Pol (she/her) 1 day ago
Just catching up on all this but jumping on a call. Sounds like this will stay separate from strategic initiatives which is ok. I like the idea of an initiative content type but maybe that's only for strategic initiatives? Anyway, I'll read this again after my call but it sounds like you have a plan
jhodgdon (she/her) 1 day ago
Yeah, my current plan is to basically make a new section using the new content types in a new location under the "Drupal" guide, and migrate the existing Community Initiatives pages into the new section.
jhodgdon (she/her) 1 day ago
The new content type doesn't exist yet, so...
jhodgdon (she/her) Yesterday at 9:18 AM
:one: :b: [second Work To Be Done area] Drupal Core development policies:
- Beta testing https://www.drupal.org/docs/8/minor-release-beta-testing-program
- Other policies https://www.drupal.org/contribute/core
Drupal.org
Major and minor release beta testing
Learn how to become involved in testing new Minor releases of Drupal during the Beta phase
Mar 12th, 2019
Drupal.org
Drupal core
The core of Drupal encompasses all of the files that you get when you download Drupal from the Drupal project page. Generally, there is one version of Drupal in active development at any time, and two past versions that are maintained with bug fixes and security updates. See http://drupal.org/documentation/version-info for more information about versions of Drupal. There are several ways that you can help out with development of the core of Drupal, and all are very valuable. Your help is welcome in any of the following areas. The suggestions below assume that you are familiar with the Drupal issue queue. What you can do
Feb 17th, 2010
jhodgdon (she/her) 1 day ago
This set of documentation I also have a proposed plan for in the second tab of https://docs.google.com/spreadsheets/d/15bLdzwwe9xECfTGM4miAQRzUs3pGqz3zUXJmQi_CbEI/edit?usp=sharing but @xjm and @Gábor Hojtsy (he/him) have not agreed to the plan so ... we need some guidance on what to do.
jhodgdon (she/her) 1 day ago
I don't really have anything else to say on that but I'm hoping Gabor or xjm will chime in on this thread.
rachel_norfolk 1 day ago
not agreed or disagreed? Two quite different things
jhodgdon (she/her) 1 day ago
They expressed some concern but it was non-specific.
jhodgdon (she/her) 1 day ago
or at least I didn't have any clear take-aways.
jhodgdon (she/her) 1 day ago
I'm almost inclined to go ahead and migrate the docs and then we can move things around as needed. If nothing is lost, we should not be worse off than we are now, and we can always move docs to other guides etc. as needed.
rachel_norfolk 1 day ago
and the redirects will work
rachel_norfolk 1 day ago
I’m happy with that approach, tbh
jhodgdon (she/her) 1 day ago
right. If you migrate, the nodes are even the same nodes, and the old aliases just become redirects automagically.
jhodgdon (she/her) 1 day ago
the structure will be slightly different because of the Guide being short rather than having big pages with sub-pages, but pretty much you can maintain the same node IDs and aliases => redirects.
:heavy_plus_sign:
2
jhodgdon (she/her) 1 day ago
(What I mean is, with the old content types, you could have a large body page and it could have sub-pages; with the new content types, large-body pages cannot have sub-pages, so you use Guides with small bodies, and large sub-pages, so the outline changes slightly.)
rachel_norfolk 1 day ago
I get it
xjm 20 hours ago
Relevant to this, apparently core development news is going to live here now: https://www.drupal.org/about/core-dev-and-strategic-initiatives
Drupal.org
Core Development & Strategic Initiatives
The following are the strategic initiatives for Drupal core, in alphabetical order. For more details, and a full list of all high-priority efforts going on in Drupal core, see https://www.drupal.org/core/roadmap. See How are strategic initiatives chosen? for details on the selection process.
May 10th, 2018
xjm 20 hours ago
Seems like core policies etc. should probably live in the same place?
jhodgdon (she/her) 20 hours ago
That would be good. Would you like me to migrate the docs currently under https://www.drupal.org/contribute/core there?
Drupal.org
Drupal core
The core of Drupal encompasses all of the files that you get when you download Drupal from the Drupal project page. Generally, there is one version of Drupal in active development at any time, and two past versions that are maintained with bug fixes and security updates. See http://drupal.org/documentation/version-info for more information about versions of Drupal. There are several ways that you can help out with development of the core of Drupal, and all are very valuable. Your help is welcome in any of the following areas. The suggestions below assume that you are familiar with the Drupal issue queue. What you can do
Feb 17th, 2010
xjm 20 hours ago
@jhodgdon (she/her) I think we could do that. We'll want to work a bit on the top-level landing page (discussing atm linking the release schedule from it) but seems like our decision got made for us. :slightly_smiling_face: Which isn't a bad thing.
jhodgdon (she/her) 20 hours ago
Hm. That top-level page is type "Section" not "Documentation Guide". Can't migrate docs there now. Maybe @hestenet (he/him) can make a child page called "Core Development Policies", make me a maintainer, and I can migrate into that
jhodgdon (she/her) 20 hours ago
There is not a rush. The existing docs aren't going anywhere.
jhodgdon (she/her) 20 hours ago
@hestenet (he/him) @Kristen Pol (she/her) I am currently migrating the Community Initiatives stuff from Getting Involved into a new guide at https://www.drupal.org/docs/community-initiatives -- I think it should be moved under this new section, but it can wait until I'm done with the migration?
Drupal.org
Community Initiatives
People in the Drupal community come together to work on projects, such as Drupal Core and contributed modules, themes, and distributions. Some work within and across projects is organized as initiatives, which are groups of people coming together to work on particular areas of concern. Dries, the official leader of the Drupal project, has identified some initiatives that he feels are particularly important as Strategic Initiatives.
Yesterday at 12:34 PM
jhodgdon (she/her) 20 hours ago
It really would be good to have all of the "initiative" stuff together.
hestenet (he/him) 20 hours ago
@jhodgdon (she/her) made: https://www.drupal.org/node/3175325 for you
jhodgdon (she/her) 20 hours ago
OK, thanks! I'll see about migrating content into there (and organizing it, de-duping, etc.)
Kristen Pol (she/her) 20 hours ago
It would be great to have all initiative content together but unfortunately it sounds like it would be hard to have the community initiatives with the strategic initiatives because of editing permissions and maybe quality control. I assume there is more oversight for the strategic pages. But the strategic workflow initiative page still says "coming soon"... uh... it's been out for some time. :shrug:
When someone brought up the official vs community guides being separate, Amy June mentioned this was due to editorial permissions and workflow so maybe this is a similar issue
jhodgdon (she/her) 20 hours ago
I think we can ask @hestenet (he/him) to move my new Initiatives section https://www.drupal.org/docs/community-initiatives that I just started so that it is under https://www.drupal.org/about/core-dev-and-strategic-initiatives , and then they'll all be together, right?
Drupal.org
Core Development & Strategic Initiatives
Strategic Initiatives The following are the strategic initiatives for Drupal core, in alphabetical order. For more details, and a full list of all high-priority efforts going on in Drupal core, see https://www.drupal.org/core/roadmap. See How are strategic initiatives chosen? for details on the selection process.
May 10th, 2018
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/docs/community-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
Kristen Pol (she/her) 20 hours ago
I don't have access to that new page from @hestenet (he/him) so hard for me to review
jhodgdon (she/her) 20 hours ago
To me it would make more sense to have the Strategic Initiatives part of https://www.drupal.org/about/core-dev-and-strategic-initiatives as a separate child page?
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/about/core-dev-and-strategic-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 20 hours ago
Oh you can't see it? sorry!
hestenet (he/him) 20 hours ago
I think it might, with what we're moving in getting bigger.
jhodgdon (she/her) 20 hours ago
@hestenet (he/him) not sure about the permissions? If they are staying hidden for the time being, I can post a screenshot?
jhodgdon (she/her) 20 hours ago
actually why is that page invisible to Kristen anyway?
Kristen Pol (she/her) 20 hours ago
Ah. The strategic initiatives URL changed
jhodgdon (she/her) 20 hours ago
yes.
jhodgdon (she/her) 20 hours ago
and a blog got added to the section (at the top).
Kristen Pol (she/her) 20 hours ago
I get access denied on new page
jhodgdon (she/her) 20 hours ago
so you can see it?
jhodgdon (she/her) 20 hours ago
oh that's not good.
Kristen Pol (she/her) 20 hours ago
I can see strategic initiatives
Kristen Pol (she/her) 20 hours ago
But not new page above
jhodgdon (she/her) 20 hours ago
which URL can you see and can't you see?
hestenet (he/him) 20 hours ago
I've just published that page now so you can see. Currently empty
Kristen Pol (she/her) 20 hours ago
Now it shows up
Kristen Pol (she/her) 20 hours ago
Says "Core Development Policies" ???
jhodgdon (she/her) 20 hours ago
We have 3 pages:
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/about/core-dev-and-strategic-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 20 hours ago
a) Core & Strategic section https://www.drupal.org/about/core-dev-and-strategic-initiatives [currently has Strategic Initiatives and a blog section, probably needs to be separated out]
jhodgdon (she/her) 20 hours ago
b) Core development polices docs section https://www.drupal.org/node/3175325 {newly created, needs content and a URL alias, currently empty]
jhodgdon (she/her) 20 hours ago
c) Community Initiatives section [currently empty, should be moved under (a)] https://www.drupal.org/docs/community-initiatives
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/docs/community-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 20 hours ago
I plan to migrate the docs that are currently under https://www.drupal.org/community-initiatives into (c), and the docs that are currently under https://www.drupal.org/contribute/core into (b).
Drupal.org
Community Initiatives
These are the critical projects that people in the Drupal community are working on. If you'd like to find a place to jump in and start contributing, start here. Drupal Core Drupal core initiatives: Help out on the next release of Drupal!
Jan 20th, 2009
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/contribute/core because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 20 hours ago
And I'm hoping @hestenet (he/him) can move (c) into the (a) section.
jhodgdon (she/her) 20 hours ago
Also hoping @hestenet (he/him) can move the content on (a) about Strategic Initiatives into a sub-page, because if it's underneath a blog it will be less prominent.
hestenet (he/him) 20 hours ago
I've added it to the menu. We may want to update aliasing (or maybe not)
hestenet (he/him) 20 hours ago
I can do that too - doing now
jhodgdon (she/her) 20 hours ago
Maybe we should also consider moving the blog to a sub-page, so there is a short landing page and 4 sub-pages [two of which are guides]?
jhodgdon (she/her) 20 hours ago
Let me know when you're done... I will also remove Community Initatives from the Drupal landing page menu.
jhodgdon (she/her) 20 hours ago
OK, I think we need to start over on the child pages somewhat...
jhodgdon (she/her) 20 hours ago
(1) https://www.drupal.org/about/core-dev-and-strategic-initiatives/policies is apparently a Documentation Page and we need a Documentation Guide instead.
Drupal.org
Core Development Policies
Yesterday at 1:59 PM (39 kB)
jhodgdon (she/her) 20 hours ago
(2) https://www.drupal.org/docs/community-initiatives should be a new Documentation Guide in that section. The existing page is part of the Drupal OG and it shouldn't be, plus it should be part of the Home / About navigation and not part of Documentation / Drupal. So maybe create a new top-level Guide for that?
Only visible to you
Slackbot 20 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/docs/community-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
hestenet (he/him) 20 hours ago
I can move those guides to be parented by th esection instead of creating new pages
hestenet (he/him) 20 hours ago
Does that make more sense?
hestenet (he/him) 20 hours ago
Let me demonstrate with the community initiatives one real quick..
jhodgdon (she/her) 20 hours ago
(1) is a Page not a Guide though. For (2) yes.
jhodgdon (she/her) 20 hours ago
Yes if you can move Initiatives to be parented properly, great!
jhodgdon (she/her) 20 hours ago
https://www.drupal.org/about/core/policies is a Documentation Page though. It needs to be a Documentation Guide.
Drupal.org
Core Development Policies
Yesterday at 1:59 PM (39 kB)
hestenet (he/him) 20 hours ago
Yup - can do that.
jhodgdon (she/her) 20 hours ago
great!
Kristen Pol (she/her) 20 hours ago
Sorry but it's hard to follow this... I'll wait until the dust settles. Thanks for the cleanup!!! :)
Kristen Pol (she/her) 20 hours ago
As I was clicking around about pages, I found this sad page... https://www.drupal.org/about/awards
Drupal.org
Awards
Don't just take our word for it. Find out for yourself. Drupal is an award-winning choice for creating, managing, and deploying your content.
Nov 11th, 2015 (39 kB)
hestenet (he/him) 19 hours ago
Oh wow, that is an old one.
hestenet (he/him) 19 hours ago
@jhodgdon (she/her) Think I captured your revisions, also updated aliases to be cleaner - can you review? https://www.drupal.org/about/core
Kristen Pol (she/her) 19 hours ago
Yeah... IMO best to unpublish the awards page if it won't be updated
jhodgdon (she/her) 19 hours ago
Community Initiatives page is great. I just updated its alias to community-initiatives and changed the old Initiatives page to be aliased community-initiatives-old. Thanks!
hestenet (he/him) 19 hours ago
I'm seeing if DA Marcomm folks want to try to crowdsource an update. Otherwise unpublish, yah
jhodgdon (she/her) 19 hours ago
Core Policies looks good too, thanks!
jhodgdon (she/her) 19 hours ago
I'm already migrating docs into Initiatives.
hestenet (he/him) 19 hours ago
Sweet.
Kristen Pol (she/her) 18 hours ago
Thanks! I'll try to help clean up the community initiative pages as time permits. If there is anything is particular that needs some love, let me know
jhodgdon (she/her) 18 hours ago
The Initiatives content is all migrated to https://www.drupal.org/community-initiatives ... It seems OK. The Previous/Inactive pages are probably in need of love but not a high enough priority to love them much. :)
Drupal.org
Community Initiatives
People in the Drupal community come together to work on projects, such as Drupal Core and contributed modules, themes, and distributions. Some work within and across projects is organized as initiatives, which are groups of people coming together to work on particular areas of concern. Dries, the official leader of the Drupal project, has identified some initiatives that he feels are particularly important as Strategic Initiatives.
Yesterday at 12:34 PM
:blue_heart:
1
jhodgdon (she/her) 18 hours ago
I just need to delete/redirect the two top-level pages and that will be done.
:blue_heart:
1
Only visible to you
Slackbot 18 hours ago
Pssst! I didn’t unfurl https://www.drupal.org/community-initiatives because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 18 hours ago
@Kristen Pol (she/her) One thing that would be a great addition to this is anything you want to write up on how to get involved with initiatives? I will also add you as a Maintainer of https://www.drupal.org/community-initiatives
:+1:
1
:100:
1
Kristen Pol (she/her) 18 hours ago
Yes. I would like to do that. That was on my list for a blog post and could do something in the docs too
jhodgdon (she/her) 18 hours ago
Those pages were straight migrates, except a few initiatives that had multiple pages (for those I had to create a new Guide page, then migrate the main page and child pages into that Guide). I didn't go back and edit them, for the most part, so they are lacking good Summary lines (default is the first 140 characters or so of the page, which is better than nothing). So... those could be edited. But at least they are there.
Kristen Pol (she/her) 18 hours ago
Thanks!!!
jhodgdon (she/her) 18 hours ago
Ping me if you need to be added as maintainer of any of the sub-groups. You should be able to edit the pages without maintainership, and since you are maintainer of the parent group, you may be able to add yourself... not sure? I put you on as maintainer of both Community Initiatives and the sub-guide for the inactive ones.
Kristen Pol (she/her) 17 hours ago
Will do, thanks for all the hard work:)
jhodgdon (she/her) 17 hours ago
OK, I've migrated I think all of the relevant core policies docs (until I find more hidden elsewhere!) into https://www.drupal.org/about/core/policies -- take a look. We can change the organization if needed... All the pages there are migrated nodes, so have the orginal node IDs and aliases are redirected. (The Guide landing pages were added by me so they are new.)
Drupal.org
Core Development Policies
This documentation guide encompasses all the policies involved in developing Drupal Core.
Yesterday at 2:31 PM
jhodgdon (she/her) 17 hours ago
@hestenet (he/him) how come when I am on https://www.drupal.org/about/core/strategic-initiatives the sidebar menu says "Core development and strategic initiatives", but when I am on the sister page https://www.drupal.org/community-initiatives the menu title is "Drupal Core"? I think the full title is better?
Drupal.org
Strategic Initiatives
The following are the strategic initiatives for Drupal core, in alphabetical order. For more details, and a full list of all high-priority efforts going on in Drupal core, see https://www.drupal.org/core/roadmap. See How are strategic initiatives chosen? for details on the selection process.
Yesterday at 2:12 PM (39 kB)
Drupal.org
Community Initiatives
People in the Drupal community come together to work on projects, such as Drupal Core and contributed modules, themes, and distributions. Some work within and across projects is organized as initiatives, which are groups of people coming together to work on particular areas of concern. Dries, the official leader of the Drupal project, has identified some initiatives that he feels are particularly important as Strategic Initiatives.
Yesterday at 12:34 PM
hestenet (he/him) 16 hours ago
Ah - it can be manually overridden. I thought shorter and less linbreaky was better
hestenet (he/him) 16 hours ago
We can decide and standardize
jhodgdon (she/her) Yesterday at 9:22 AM
:one: :c: Contribute to Documentation -- https://www.drupal.org/contribute/documentation
- Are these pages at all current?
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
jhodgdon (she/her) 1 day ago
For this one, I think we need some input from @eojthebrave or @batigolix or someone else in the Docs Working Group (if that is still a thing).
jhodgdon (she/her) 1 day ago
The next thread is about the Contributor Tasks -- some of them are also about Documentation.
jhodgdon (she/her) 1 day ago
Anyway, I haven't migrated the Contribute to Documentation section mostly (a couple of pages about issues went into the Issues section) because I'm not sure if these pages are relevant or not.
eojthebrave 1 day ago
Is there a place where you're keeping track of these pages and what should/shouldn't migrate and what needs updates? I'm happy to help out with this section.
jhodgdon (she/her) 1 day ago
https://docs.google.com/spreadsheets/d/15bLdzwwe9xECfTGM4miAQRzUs3pGqz3zUXJmQi_CbEI/edit?usp=sharing
jhodgdon (she/her) 1 day ago
If you don't have edit access already, request it or dm me your Google email address and I'll add you.
eojthebrave 1 day ago
Great. I see you assigned those pages to me already. What's the next step?
jhodgdon (she/her) 1 day ago
Decide on what to do with them.
jhodgdon (she/her) 1 day ago
We have https://www.drupal.org/community/contributor-guide/contribution-areas/documentation as an "Area" page.
Drupal.org
Contribute to documentation
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. All of the documentation that makes the Drupal Project is freely contributed by people all around the World, just like you.
Jan 28th (39 kB)
jhodgdon (she/her) 1 day ago
Then we would want to make Task and Role pages as appropriate
jhodgdon (she/her) 1 day ago
And other things can be Background Information.
jhodgdon (she/her) 1 day ago
So the main thing is to decide, for each page, is it Task, Role, Background, or Should Be Deleted (or a combination).
eojthebrave 1 day ago
Okay sounds good. And just edit/update them in-place for now? I should be able to get through them all within the next week.
eojthebrave 1 day ago
Probably sooner, but don't want to make any promises. :stuck_out_tongue:
jhodgdon (she/her) 1 day ago
Yeah... hm.... So if they need to become Tasks/Roles, that is creating new content items.
jhodgdon (she/her) 1 day ago
If they need to be Background, we need to figure out where they should go.
jhodgdon (she/her) 1 day ago
If they need to be deleted, we should figure out if they're just plain old or duplicate other content so they can be redirected.
jhodgdon (she/her) 1 day ago
If you want to edit the pages and put notes right in them about what should happen, that would be one approach. The other approach would be to put notes in the spreadsheet. A third would be to start a thread in Slack and put notes there.
eojthebrave 1 day ago
:thumbsup:
jhodgdon (she/her) 1 day ago
Any of those approaches works for me!
jhodgdon (she/her) 24 hours ago
you have access.
jhodgdon (she/her) Yesterday at 9:30 AM
:one: :d: Contributor Tasks -- https://www.drupal.org/contributor-tasks
- Some are good; some are outdated; I am not sure which are which
Drupal.org
Contributor Tasks
Note: This section is in process of being migrated to the Find a task page in the new Contributor Guide. Try searching there for a task instead of looking in this section -- some tasks have been moved there already. When the migration is complete, we will remove this section.
Feb 1st, 2012
jhodgdon (she/her) 1 day ago
This is one area where I could really use some input.
jhodgdon (she/her) 1 day ago
It would be super helpful if people could go through the existing pages under Contributor Tasks, and edit pages with a small note at the top saying "This page is current" or "We don't do things this way any more" or something of that nature. Especially if people who are current mentors could help.
:heavy_plus_sign:
1
jhodgdon (she/her) 1 day ago
I'm going to post a link in the Mentoring channel to this thread specifically.
:+1:
1
hestenet (he/him) 1 day ago
++ to asking the mentors to help here.
AmyJune (volkswagenchick she/her) 1 day ago
for the new contributor tasks: anyone…
Maybe writing and improving documentation via a README? This is a great task for coders and non-coders alike.
AmyJune (volkswagenchick she/her) 1 day ago
^^ but this would be more for contrubted projects
jhodgdon (she/her) 1 day ago
Good idea for a task.
jhodgdon (she/her) 1 day ago
I'm all for people contributing to both core and contrib.
rachel_norfolk 1 day ago
do we need to differentiate in the contributor guide?
AmyJune (volkswagenchick she/her) 1 day ago
I dont think so
jhodgdon (she/her) 1 day ago
Each Task item can be listed as part of one or more Areas. We have an Area for Core and another for Contrib projects.
jhodgdon (she/her) 1 day ago
The tasks that are under the current Contibutor Tasks section should mostly I hope become Contributor Task content items.
rachel_norfolk 1 day ago
yes
jhodgdon (she/her) Yesterday at 9:34 AM
:one: :e: Misc pages:
- Guides to how to apply patches on various OS without using Git command line [delete?] https://www.drupal.org/patch/apply
- Most of the other pages I think I know what to do with
Drupal.org
Applying patches
This section deals with applying patches. For guiding to create patches, please see the Advanced patch contributor guide. Applying patches, modifying files according to instructions in the patch file, is the domain of patch programs. There are many different programs with this functionality, some stand-alone (patch), some integrated in IDEs (Eclipse, XCode). Warning: Patching is something that should never be done on your production site unless you first have a complete backup of your site, including the codebase and database; and you have tested that backup First. While patching itself is relatively easy, it is important that you fully understand that a patch can possibly lead to the loss o… Show more
Apr 24th, 2006
jhodgdon (she/her) 1 day ago
So that patch/apply section is an interesting question. They're old pages about how to apply patches on MacOS, Windows/Cygwin, etc. My inclination is that they are outdated, because we tell everyone they need Git. These pages don't seem all that useful.
jhodgdon (she/her) 1 day ago
So I kind of want to delete them... But I could be wrong. Any thoughts? I guess I should ping the mentors and the contrib channel on this question.
hestenet (he/him) 1 day ago
I strongly suspect that pre-git docs can go...
:heavy_plus_sign:
1
jhodgdon (she/her) 1 day ago
I am not sure they are pre-git but I think they may be because they don't mention Git.
drumm 1 day ago
I could go either way on those, but I’m far from a regular site builder. Knowing patch in addition to git apply is useful. Even with merge requests coming up, applying a patch will still be useful knowledge, although moving more toward composer-patches. Much easier to apply multiple patches than maintain your own repo with combining merge requests.
jhodgdon (she/her) 1 day ago
We have instructions for using the patch command elsewhere.
jhodgdon (she/her) 1 day ago
But I don't think we need 10 pages on how to use the patch command under various scripting environments.
drumm 1 day ago
If it is mostly git docs, https://git-scm.com/docs/git-apply should be better maintained.
jhodgdon (she/her) 1 day ago
https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch is a pretty comprehensive guide to applying a patch using our preferred workflow, but it also mentions the patch command.
Drupal.org
Applying a patch in a feature branch
This page outlines a workflow for downloading and applying patches to a local workspace, based on local "topic branches". Note: You can also use the drupalorg-cli tool to create an issue branch and apply the patch.
Jan 9th, 2012
drumm 1 day ago
Yeah, a lot of those environments shouldn’t be used now, I hope.
jhodgdon (she/her) 1 day ago
I hope.
AmyJune (volkswagenchick she/her) 1 day ago
I’d like to see git apply -v somewhere on this page maybe… wget and curl may be confusing for novices.
Downloading a patch and using git apply -v looks much easier IMHO
jhodgdon (she/her) 1 day ago
Good idea. So we'd say "Click the link to download the file to your computer, and then use git apply"
jhodgdon (she/her) 1 day ago
I will make that change. Is -v good (more verbose I assume)?
Only visible to you
Slackbot 1 day ago
Pssst! I didn’t unfurl https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch because it was already shared in this channel quite recently (within the last hour) and I didn’t want to clutter things up.
jhodgdon (she/her) 1 day ago
page updated https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/applying-a-patch-in-a-feature-branch
AmyJune (volkswagenchick she/her) 1 day ago
git apply -v [path to file]
jhodgdon (she/her) 1 day ago
Do you think all the git apply command examples should use the -v option?
AmyJune (volkswagenchick she/her) 1 day ago
I dont have the answerto that
jhodgdon (she/her) 1 day ago
OK, I have put in a note about -v in the page. We can always edit it again. :)
:checkbox-yes:
1
jhodgdon (she/her) Yesterday at 9:42 AM
:two: Content status -- Other areas:
- I had a meeting with the Event Organizers group mid-September, and they are hopefully going to round up content and get it to us on https://www.drupal.org/project/event_organizers/issues/3165327
- We need to figure out who the area heads are for the Area issues, contact them, and figure out what roles/tasks should be created for those areas. Parent issue: https://www.drupal.org/project/drupal_org_community/issues/3137918
Drupal.org
Event planning documentation
Documentation location/URL This issue is about these pages in the Contributor Guide on the subject of event planning: Area: https://www.drupal.org/community/contributor-guide/contribution-areas/event-planning Skill: https://www.drupal.org/community/contributor-guide/skill/event-planning Reference info section: https://www.drupal.org/community/contributor-guide/reference-information/event-plan Guidelines for the content types in the new Contributor Guide:
Aug 14th
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
:+1:
1
jhodgdon (she/her) 1 day ago
I've been focused lately on the migration of existing docs, but we still need to round out the Areas to have Tasks and Roles.
rachel_norfolk 1 day ago
yeah
Comments
Comment #2
volkswagenchickAttended - a little late, but made some comments
Comment #8
jhodgdonComment #10
jhodgdonComment #11
jhodgdonThanks again to everyone who participated yesterday! I've added the log to the issue summary.