Making WordPress.org

Opened 9 months ago

Closed 6 months ago

Last modified 6 months ago

#4850 closed defect (fixed)

Component Pages missing Administration component

Reported by: garrett-eclipse Owned by:
Milestone: Priority: normal
Component: Make (Get Involved) / P2 Keywords:



While looking at core#46418 being assigned to the Administration component I went to see whom the maintainer(s) might be and found it's not listed on the Component Pages.

Comparing the Trac component dropdown to the Component Pages list I also found Security, Text Changes, and WordPress.org site were missing from the Component Pages so wanted to flag but understand it's likely these others aren't real components (aside from Security).


Change History (6)

#1 @SergeyBiryukov
9 months ago

Administration is likely missing because it was proposed for removal during the last Trac component reorganization, but then ended up being left as is. Since it's not going anywhere anytime soon, I have no objections to adding it to the Components page.

#2 @SergeyBiryukov
9 months ago

Text Changes can probably be retired in favor of the ui-copy focus, as proposed in the same reorganization post:

Here are the components removed:
Text Changes (this will become a focus, for wordsmiths — needs a name)

Last edited 9 months ago by SergeyBiryukov (previous) (diff)

#3 @garrett-eclipse
9 months ago

Thanks for the reference and background @SergeyBiryukov

With >350 tickets in Administration, I'd second it's probably sticking around for a while so a page makes sense.

And that's interesting about Text Changes, I wasn't really aware of it so nice to see it naturally evolved to a focus on it's own. I guess those tickets just need to be triaged if it's to be deprecated.

#4 @dd32
6 months ago

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

I've re-added the Administration and Security components, since they've got actual tickets in there.

The security component page could do with a blurb about how to properly report security issues, and that the tickets in the component are not security issues per-se, but rather security-related hardening tickets (hopefully).

Text Changes seems like it should just be replaced with the ui-copy keyword as above, and the WordPress.org Site component shouldn't really be used, ever, and only has 2 tickets in it (One of which should be considered fixed, and the other should exist on Meta trac).

#5 @garrett-eclipse
6 months ago

Thanks @dd32 as a start on the Security Component blurb I just carried over the text and links from core.trac landing page. Please review and add anything further you feel useful.

I went through WordPress.org component and agree the one there should be marked fixed and the other I moved to the Upgrade/Install component.

I also went through Text Changes and found new homes for all the tickets and ensuring they all got the ui-copy label.

So we can pretty safely deprecate those two unneeded components (WordPress.org & Text Changes).

This ticket was mentioned in Slack in #core by sergey. View the logs.

6 months ago

Note: See TracTickets for help on using tickets.