Make WordPress Core

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#9326 closed defect (bug) (wontfix)

Remove what really should be plugins from core functionality

Reported by: jidanni Owned by:
Milestone: Priority: lowest
Severity: trivial Version:
Component: Optimization Keywords:
Focuses: Cc:


If you step back and take a look at it, things like RSS readers being bundled right in the core to help the administrator keep abreast of WordPress development, should be at most optional plugins.

I know this must seem unbelievable, but do step back and take a look at things from a distance.

Sure, you can have them checked by default on a list of items to install by default -- but if the user does not press "install optional plugins?" then that should be the closest he need encounter them.

Maybe it also serves an aggregator role, but then still aggregators should be just aggregators, not at the same time content providers, to keep things simple. (However that is all over my head. All I know is you are risking your core functionalities by gluing too much mess into it that should really be plugins.)

Change History (2)

#1 @jidanni
9 years ago

  • Cc jidanni@… added

#2 @DD32
9 years ago

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version 2.7.1 deleted

There was a lot on the wp-hackers about "Optional Modules", In the end, No.

Popular plugins are merged with core to allow continued development of the features in line with WordPress. Developers are not interested in keeping extra plugins up to date when they can simply keep core updated. Akismet/Stats/other Automattic project plugins are a different kettle of fish though, They're kept up to date, but are kept externally for other reasons which wouldnt fit the majority of plugins, or the current core-functionality.

Note: See TracTickets for help on using tickets.