Canonical Plugins

[chipbennett]

"Core" is just a bad idea altogether as the plugins are definitely not a part of the core code. I don't like the other names based on arguments already given in this thread.

So far, "canonical" seems to be the best to me (if we need a label at all for these plugins).

+1

Please let the powers-that-be hear the voice of reason.

[andrea_r]

If verified had been an option, I woudl have preferred it.

[JohnM]

To me, the canonical plugin idea, seems to be an attempt to do what Drupal community does:

http://drupal.org/node/23789
http://groups.drupal.org/contributed-module-ideas

I think its a good idea, but it will only be successful if enough plugin devs want to collaborate

I dont think canonical is a bad term at all: http://en.wikipedia.org/wiki/Canonical

[chipbennett]

So, I've been reading what wp-hackers have had to say about canonical plugins.

I have to admit, I can see one valid use case for "core plugins": plugins that are part of the default download package, are disabled by default, and address popular-yet-niche functionality (such as podcasting, Twitter, lifestreaming).

In this case, the "core" plugin would be the best-of-breed plugin to address the specified functionality, but, if enabled by default, would still represent "bloat" for the majority of users.

(I suppose bbPress, if made into a plugin, would also fall into this category - as could MU or buddyPress.)

And in this case, calling these "core" plugins makes sense: they are core functionality, but can be enabled/disabled, just like a plugin.

Otherwise, I think the name should be "canonical" or "recommended" or some-such.

[Jeffro]

Well, from what I saw during the dev meeting yesterday, the people voted overwhelmingly for these plugins to be called Core Plugins. That's all we need is more confusion. I understand the relationship between these plugins and the core development of WordPress but having both things called core I feel is a bad idea anyway you look at it.

I've never wrapped my head around canonical but now, it's ingrained into my head on what it means and references in terms of plugins.

I know that the entire core team discussed the canonical plugin idea and purpose at great lengths which will be interesting to read once that conversation summary has been published online but I'm going to have to sit back and see how it plays out.

I think one of the best things about canonical plugins is that it gives WordPress a chance to lighten the load even more by taking a chunk of functionality and turning it into a canonical plugin. A great example I harp on that would be a good test for canonical stuff is the Code editors in WordPress. Take CodePress and turn it into a canonical plugin and then rip out the editors from the core of WordPress.

However, until things are implemented and rolling along, I and many others have a 100 questions with no answers yet. For instance, when and how does a plugin become canonical and when does that plugin be removed from that classification?

[chipbennett]

Well, from what I saw during the dev meeting yesterday, the people voted overwhelmingly for these plugins to be called Core Plugins. That's all we need is more confusion. I understand the relationship between these plugins and the core development of WordPress but having both things called core I feel is a bad idea anyway you look at it.

I've never wrapped my head around canonical but now, it's ingrained into my head on what it means and references in terms of plugins.

I know that the entire core team discussed the canonical plugin idea and purpose at great lengths which will be interesting to read once that conversation summary has been published online but I'm going to have to sit back and see how it plays out.

I think one of the best things about canonical plugins is that it gives WordPress a chance to lighten the load even more by taking a chunk of functionality and turning it into a canonical plugin. A great example I harp on that would be a good test for canonical stuff is the Code editors in WordPress. Take CodePress and turn it into a canonical plugin and then rip out the editors from the core of WordPress.

However, until things are implemented and rolling along, I and many others have a 100 questions with no answers yet. For instance, when and how does a plugin become canonical and when does that plugin be removed from that classification?

In my opinion, the only way a Plugin could be called a Core Plugin would be if it were installed (even if inactive) by default. Even then, such plugins would really only be Default Plugins.

So, a further requirement for a Core Plugin would be a high level of testing, polish, finish, and seamlessness with core - including a separate UI from the general plugins UI.

Further, Core Plugins should be limited to those plugins that extend the core functionality of WordPress, such as PodCasting, forums (bbPress), social networking (buddyPress), multi-blogging (MU) - functionality that is higly useful and that needs rock-solid integration, yet that is still mostly niche.

I don't know if Akismet (or, its successor, "Anti-Spam") rises to this standard. Maybe "Anti-Spam" can be considered highly useful yet niche functionality? Personally, I think anti-spam is important enough to be built into core, such that (regular) plugins could be used to choose the provider (Akismet, etc.).

So, to summarize, a Core Plugin:

1. Addresses highly useful, yet niche functionality that extends WP core functionality
2. Is installed, though may be active or inactive by default, in the core download
3. Has a high degree of testing, polish, finish, and integration with WP core
4. Has a separate UI from the regular plugin UI

So, those are my thoughts at this point. We'll see where the devs go with the idea.

[Jeffro]

I watched Janes keynote from WordCamp Atlanta today and she refers to Canonical plugins as Core Plugins. Ughh. Majority of people voted for it though.

[andreasnrb]

Canonical is a bad name but core plugin is even worse.

[dancole]

I'd be willing to be a contributor to a core plugin (If that's the name we're going by). There are just some many advantages to doing it. In a lot of cases you'd be working with a least one person more skilled than you and it allows you to create a great product without spending all of your free time.

Jeffro, you should keep us updated on core plugins. I only know of Health Check plugin, which is likely the only one so far.

[Jeffro]

Jeffro, you should keep us updated on core plugins. I only know of Health Check plugin, which is likely the only one so far.

Keep an eye on Peter Westwood as it seems he has an idea to rip out Post By Email from the core and turn it into a 'Core Plugin' which could be the second plugin. I wonder if each one of these plugins will at least have the Core tag attached to them or some other unique tag. Would be easier to keep track.

Also, I think I heard this correctly but there might be a new widget in for the dashboard that will highlight these core plugins.