Canonical Plugins

[aaroncampbell]

Again, you'd have to read the (already lengthy) thread. I've proposed something different from the current Core Plugins idea. Core Components != Core Plugins, exactly.

...

In fact, you might even consider tagging the Core Plugins identically to WordPress core.

Sorry if I misunderstood, this is the second long thread that I read when I was trying to catch up on what was being discussed here. It's your proposal, and you can write it however you want. However, "core plugins" has already been decided as the name (again, this was both by popular vote in a poll as well as being the consensus of the developer meeting, both of which were completely open for anyone to vote/participate).

The basic idea is that core plugins are things that shouldn't be in core. That's why they're in plugins to begin with. As such, they may have different release cycles (more or less often than core), etc.

[Otto]

But that's what I'm suggesting: not that they are enabled by default, but that they are included. In my proposal, "component" essentially equals "plugin", insofar as how it it is integrated into core. It is still just an extension of core that can be enabled/disabled. It's just presented differently.

I realize that, and I'm against it.

bbPress and BuddyPress code should absolutely NOT be included with WordPress. They should be plugins. Additional code, downloaded separately.

Again, that's what I'm suggesting, in a somewhat modified proposal from Jane's original definition of "Canonical Plugin".

I realize that, and I'm against it. :)

Including code that most people do not need with the core download is a BIG mistake. Make them plugins. Download them separately. Activate them separately. Do not bundle them in the core download. Do not include major bits of code in the core that most people will not be using. Minor stuff, fine. Forums and social networking features are not minor, and should not be in the base system.

[chipbennett]

I realize that, and I'm against it.

bbPress and BuddyPress code should absolutely NOT be included with WordPress. They should be plugins. Additional code, downloaded separately.



I realize that, and I'm against it. :)

Including code that most people do not need with the core download is a BIG mistake. Make them plugins. Download them separately. Activate them separately. Do not bundle them in the core download. Do not include major bits of code in the core that most people will not be using. Minor stuff, fine. Forums and social networking features are not minor, and should not be in the base system.

And that is now the current state of the proposal - Core Components are installed inline from the Manage Components screen, instead of being bundled by default.