Repurposing the wptrainingteam GH organisation

[jonathanbossenger]

What?

Members of the WordPress community have been looking for a place to house all code examples used for Learn WordPress and the Core Developer Blog. You can read about this request here.

It has been suggested and mostly agreed upon to repurpose the https://github.com/wptrainingteam/ organization for this purpose.

How?

1. Invite specific community team members and project leadership to join this organization as owners. To start with, the following folks could be added: @webtechpooja and @bsanevans ( as team reps of the Training Team), @bph (as the team rep for the core dev blog), and @josephahaden (executive director of the WordPress project). Other owners can be added later as needed.
2. Rename the organization to something other than wptrainingteam. This new name can be discussed amongst the updated organization owners.
3. Review all open code repositories in the organization, with a view to marking them as archived. Marking them as archived will retain the repositories and their history, but make it read-only for all users and indicate that it's no longer actively maintained.
4. Review and update the https://github.com/wptrainingteam/wptrainingteam.github.io repository to match the new organisation name and purpose.
5. Decide on a process for how WordPress contributors will be added to this organisation, in order to upload their example code repositories.

[jonathanbossenger]

Tagging @courtneyr-dev on this conversation, we may need your help inviting new owners.

[jonathanbossenger]

@courtneyr-dev would you be able to start the process by elevating @webtechpooja to owner status?

[jonathanbossenger]

Thank you @courtneyr-dev for upgrading our team reps, @webtechpooja, @bsanevans and @Piyopiyo-Kitsune as owners of this organization.

[jonathanbossenger]

@bsanevans or @webtechpooja a next step, can we please invite @josephahaden and @bph as owners of the organization as well.

At the same time, can we look at renaming the organization from wptrainingteam to learn-wordpress.

[kaitohm]

@josephahaden and @bph have both been invited as owners of this organization 👍

For the moment, I've updated the organization display name to Learn WordPress. I've also changed the billing email from a Gmail address to a WordPress.org address the Training Team has access to in Help Scout.

I can also rename the organization, but would just like a nod from another couple of owners before I do so.

[Piyopiyo-Kitsune]

Access confirmed-- thank you for getting this set up @jonathanbossenger @courtneyr-dev! I think it would be super helpful to start drafting a handbook page on how to engage with this repo/org going forward which we can link in the description.

[jonathanbossenger]

I think it would be super helpful to start drafting a handbook page on how to engage with this repo/org going forward which we can link in the description.

@Piyopiyo-Kitsune agreed, but @bph, @courtneyr-dev, and I also chatted about the fact that this doc shouldn't live with the training team handbook exclusively, as we might want this GH organization to be made available to all make teams/team reps who need to host code examples for educational/training purposes.

So it was suggested that we create a readme.md file in a code repository in this organisation, and then link to it from our respective team handbooks. My plan is to work on this when I get back next week.

[courtneyr-dev]

Agreed @jonathanbossenger on the readme.md approach. Can we also include a contribute.md file that drives people to any teams using this?

Also noting for historical purposes, we want to preserve the content that Training team worked on for many years before we could access LearnWP.

[bph]

Howdy, howdy. Huge thank you to everyone in this thread for moving forward with the discussion on how to admin this organization and accommodate various make teams producing educational content

If that's ok with you, I would like to start a test project with one of the most prolific writers on the WordPress Developer Blog, Justin Tadlock (github handle: @justintadlock) He is working on part 2 of his Beyond Block Styles series and could use a repo to house the example code, which you can view on his personal GitHub account here

Going through onboarding Justin would give us enough process experience to form opinions and focus on what's important for writers, reviewers, and admins on the Developer Blog Editorial group.

What do you think?

[justintadlock]

I'm happy to be the tester for this from the Dev Blog side of things. As @bph said, I'm currently in the middle of a three-part tutorial series that has a lot of code examples, so this would be an ideal time to test. Currently, there is no way for readers to see the code as a whole without me linking to my personal GH account, something we'd rather avoid.

[jonathanbossenger]

I think this is a great idea, and will help us define the process for how we allow access to folks for adding their repos to this Organization.

All I ask is that we document the steps you all take to make this happen so that we could turn this into a handbook document somewhere.

Feel free to ping me if you need any help or have any questions on anything.

[bph]

Fabulous! We'll discuss process and documents along the way on the issue #133 on the Developer Blog Content space.

[justintadlock]

I have transferred ownership of the Beyond Block Styles repo as a first test.

I don't really have any notes at this time since I simply just did a straight transfer from my personal account to this org. I'll still need to go through the process of linking to it within the Dev Blog posts.

[jonathanbossenger]

@bph I feel like the original purpose of this issue has been accomplished now. Do you think we can close this?

[bph]

Yes, this has been completed. Closing now. And activity on this organization now also reflected on contributors' wordpress.org profiles (meta trac 7355)