Make WordPress Core

Opened 9 years ago

Last modified 3 weeks ago

#33993 new enhancement

Add Links for additional props on about.php after updating.

Reported by: scotthack's profile scotthack Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Help/About Keywords:
Focuses: administration Cc:


Upon updating WordPress, a user is presented with the "Welcome to WordPress X.X" or the about.php page that has tabs that also link to the credits.php page and the freedoms.php page. I recently started following development in Slack. Reading new tickets, watching committed tickets and I've been really amazed by all of the hard work that goes into the project. I've been sucked into reading trac tickets and comments and looking at the various patches etc and I'm NOT a coder. I do however run the monthly meetup in my city and I do my best to teach from the middle and share what I learn and what features developers need to be made aware of. That said, the average person isn't following along in Slack and they have no idea how many tickets have been impacted in a release, how many lines of code were added, how many were deleted, how many new files were created for organization...

I propose that the about.php add an addition tab that has a "Project Progress" tab that will then link to the showing how many tickets were recently closed and how many are still outstanding. How many lines of code were actually impacted by being added and deleted, etc. A lot of times I tell my Meetup attendees that there was "a ton of things done under the hood" that made the code base better/faster/etc. But having numbers I think would help people really get a feel for the progress that is made during a release.

I'd also think it would be neat if trac can give up the info on the ticket that was oldest that was closed during the release. Just today I saw something that was 6 years old that was closed. That is pretty cool to see, and a few days ago I saw something that was submitted and then committed all within 2 hours it seemed like. What is the fastest ticket closed. Some of those stats would be nice to see ESPECIALLY on releases that don't have a whizbang feature plugin being merged into them.

PS - Thanks to everyone who works tirelessly to make the project better.

Change History (9)

#1 follow-up: @johnbillion
9 years ago

  • Component changed from General to Help/About
  • Version 4.3.1 deleted

There's certainly lots of things we could do with the About screen. Stats for the release could be a good idea, but we also need to bear in mind that this is an end-user facing page and we wouldn't want to add too much technical information.

On the Credits page, there's a small link at the bottom which says "Get involved with WordPress". Maybe making this more prominent could be a good idea. The site is pretty much the gateway to all things relating to getting involved with WordPress.

#2 in reply to: ↑ 1 @scotthack
9 years ago

I think stats are really easy for someone non-technical to start to wrap their head around the amount of work that goes into a release and the man power that gets donated.

This release had 264 people who contributed code.
There were 894 tickets closed as a result of this release.
There were 4000 lines added to the code base.
There were 1000 lines deleted.
There were 18 new files created.
The oldest ticket closed was opened on September 14, 2007.

There are currently 3200 tickets that still need to be addressed. ( Get Involved )

This release represents 6000 man hours of work by the following volunteers :

#3 @desrosj
4 years ago

  • Milestone set to Awaiting Review

#4 follow-up: @marybaum
3 years ago

Just so I don't forget: maybe a callout graphic on the release post?

#5 in reply to: ↑ 4 @desrosj
3 years ago

Replying to marybaum:

maybe a callout graphic on the release post?

I think including any information in a graphic should be avoided whenever possible. It's difficult to make a graphic with lots of information accessible. And once the graphic is released, it cannot easily be changed.

I think I'd much rather see some statistics get added to the response for a release (, but I can't speak to the feasibility of that. This would also make the statistics publicly available for anyone to use.

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

3 years ago

#7 @meher
3 years ago

What the @scotthack has suggested is definitely good for non-tech and tech people.

I feel instead of another tab, it may be better to have it at the end of What's new, so people read the information.

Not sure how many people click on the Credits, Freedoms, and Privacy tabs.

There are a lot of WordPress developers who do not follow trac.

By showing these stats they may get inspired and start contributing back to the software.

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

2 years ago

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

3 weeks ago

Note: See TracTickets for help on using tickets.