Making WordPress.org

Opened 5 weeks ago

Closed 4 weeks ago

#7563 closed enhancement (fixed)

Create repo @WordPress/contributor-handbook

Reported by: leogopal's profile leogopal Owned by:
Milestone: Priority: normal
Component: Version Control Keywords:
Cc:

Description

The WordPress.org Community Team on Github has sub-teams for larger projects/co-horts/working groups.

The DEIB and Contributor Mentorship Working Group's are 2 project wide, Community focused sub-teams.

→ @WordPress/Make-Community-Team
https://github.com/orgs/WordPress/teams/make-community-team

→ DEIB Working Group
https://github.com/orgs/WordPress/teams/deib-working-group

I am working to assist the DEIB team migrate their Contributor Handbook repo project (with history) to live under their official WordPress Github team.

Required

I require a blank repo named contributor-handbook to be created in the WordPress Github ORG, as part of the Community Team and under the DEIB sub-team.

I require full permissions to this repo mirroring my abilities on these 2 repos, so that I may migrate their Code and Commit history:

cc @dd32 assisted with the initial setup here #7209, @leogopal Community Team Github PoC and DEIB project lead @coachbirgit

Please assist as we hope to move forward this week with this.
The repo I am working to migrate into WordPress' Github is:
https://github.com/os-deib/contributor-handbook

Attachments (1)

Xnapper-2024-04-10-14.12.11.jpg (311.8 KB) - added by leogopal 5 weeks ago.
Needs permissions to transfer repo to @WordPress github ORG

Download all attachments as: .zip

Change History (8)

@leogopal
5 weeks ago

Needs permissions to transfer repo to @WordPress github ORG

#1 @leogopal
5 weeks ago

Ideal Preference

If possible, our first preference would be to get assistance with transferring the repo by someone with the right permissions into the WordPress Github ORG and the mentioned sub-teams from:

https://github.com/os-deib/contributor-handbook

Note: Creating the blank repo as defined above is our alternate work-around but would require lots more manual migration with some data (issues, etc) loss a long the way - we'd appreciate having transferring being an option, but appreciate and understand if this is not possible.

#2 follow-up: @dd32
5 weeks ago

  • Component changed from Make (Get Involved) / P2 to Version Control
  • Keywords changes-requested removed
  • Priority changed from high to normal

To transfer a repo, you need to first transfer it to an Admin of the organisation, have them as an owner of the source repo, or, DM a github admin and let them enable the transfer permission for a few minutes.

Generally; please just request a repo in the official GitHub org for community things rather than creating team-specific organisations that then end up without WordPress ownership, as it means it's much harder to apply the code-of-conduct and security monitoring.

#3 in reply to: ↑ 2 @leogopal
5 weeks ago

Replying to dd32:

Generally; please just request a repo in the official GitHub org for community things rather than creating team-specific organisations that then end up without WordPress ownership, as it means it's much harder to apply the code-of-conduct and security monitoring.

Thank you @dd32 -- this is definitely how we will be doing things; the repo to transfer in question was an initiative that we took over and recommended having it transferred to the official Github ORG and team before further contributions are made to it.

To transfer a repo, you need to first transfer it to an Admin of the organisation, have them as an owner of the source repo, or, DM a github admin and let them enable the transfer permission for a few minutes.

RE: Transferring the Original Repo

I can (a) add an Admin to the repo with the ability to transfer, what would be the best way to make this request to an Admin?
https://github.com/orgs/WordPress/people?query=role%3Aowner

Alternatively, I am quite adept and comfortable using Github, so if (b) I got in contact with an Admin to get the permissions to temporarily perform the transfer; that would work as well.

I would think option (a) is most preferred though.

What would be my best next steps for me?

This ticket was mentioned in Slack in #meta by courtneyengle. View the logs.


4 weeks ago

This ticket was mentioned in Slack in #meta by leo. View the logs.


4 weeks ago

#7 @dd32
4 weeks ago

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.