WordPress.org

Making WordPress.org

Opened 6 weeks ago

Closed 3 weeks ago

#5863 closed task (fixed)

Create new Documentation repo on WordPress GitHub organisation

Reported by: Kenshino Owned by:
Milestone: Priority: high
Component: General Keywords:
Cc:

Description

Hello.

As the result of our discussions trying to bring all of our different projects under one "doorway" so to say, we decided to adopt GitHub and use it for our issue tracking needs.

We'll start off with very vanilla GitHub issue tracker but might consider ZenHub or the soon to be further upgraded GitHub projects.

There's a decent possibility we will use it for it's versioning capabilities as well but that will be a later phase.

FOr those interested in details -> https://make.wordpress.org/docs/2021/08/02/summary-for-docs-team-meeting-july-27-2021/

I'm also aware that we have 2 other Documentation related repos but they serve their own purpose for now - while we might look at consolidating them in the future (again later phase, we don't have the bandwidth and would want to do away with the distraction for now)

Can we please get a repo called Documentation created under the WordPress Org team?

Please also add me as the team admin so that I can give others the appropriate repo access too.

Thank you so much.

Change History (9)

This ticket was mentioned in Slack in #docs by kenshino. View the logs.


6 weeks ago

#2 @dd32
6 weeks ago

Can we please get a repo called Documentation created under the WordPress Org team?

I'm unsure if WordPress/Documentation would be appropriate here, it feels like it'll be seen by some as "WordPress Documentation" and could possibly rank well for that search term.

As no documentation would be living there, maybe something less generic and more specific to the purpose would fit better? Something like WordPress/docs-team-triage or something?

#3 @Kenshino
5 weeks ago

Yeah that makes sense.

Could we do WordPress/Documentation-Issue-Tracker @dd32

Thanks!

#4 @dd32
5 weeks ago

  • Resolution set to fixed
  • Status changed from new to closed

@Kenshino Created https://github.com/WordPress/Documentation-Issue-Tracker

I've assigned the Team WordPress/documentation Maintain on the repo, please add members as needed to that team. https://github.com/orgs/WordPress/teams/documentation/members

Note: You'll probably need a GitHub owner to invite users to the team who do not have an existing role on the WordPress org, please ping #meta or post on this ticket.

#5 follow-up: @milana_cap
5 weeks ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Hello @dd32 ,

If GitHub team gets maintaining rights over their repos, can we get people from this list added to Documentation team - https://github.com/orgs/WordPress/teams/documentation (these are GitHub usernames):

Thanks

#6 in reply to: ↑ 5 ; follow-up: @dd32
5 weeks ago

  • Resolution set to fixed
  • Status changed from reopened to closed

Replying to milana_cap:

can we get people from this list added to Documentation team

Done.
You can also add/remove members from the team now too. Please note the previous note, 7 of the users did not have an existing role, so I (or someone else) would've had to add them:

Note: You'll probably need a GitHub owner to invite users to the team who do not have an existing role on the WordPress org, please ping #meta or post on this ticket.

#7 in reply to: ↑ 6 @milana_cap
4 weeks ago

Replying to dd32:

Done.

Thank you so much <3

#8 @milana_cap
3 weeks ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Hello @dd32 ,

Can we have this GitHub repo connected to #docs slack channel so that we get notification on new issues and changed statuses? Thank you

#9 @dd32
3 weeks ago

  • Resolution set to fixed
  • Status changed from reopened to closed

I've connected it using the /github flow:

https://wordpress.slack.com/archives/C02RP4WU5/p1630894125102400

GitHubAPP 12:08 PM
:white_check_mark: Subscribed to WordPress/Documentation-Issue-Tracker. This channel will receive notifications for
issues, pulls, commits, releases, deployments

Swing by #meta if you can't edit/update it yourself using /github (I'm not sure who can/can't do that)

Note: See TracTickets for help on using tickets.