[wp-hackers] comments should be a plugin

[Scott Kingsley Clark]

Heavily agree with you here, Canonical plugins all the way for these
types of "previously part of core" WP features. And in Installation
process of WP the user should be able to select which "features" they
want enabled / disabled, and these "features" would really be
Canonical plugins - but the user doesn't need to hear "plugin", only
"feature". Thoughts?

-Scott

On Mar 6, 8:26 pm, Mike Schinkel <mikeschin... at newclarity.net> wrote:
> On Mar 6, 2010, at 9:20 PM, Scott Kingsley Clark wrote:
>
> > There's an example of a "won't happen" / "not necessary" attitude. I
> > think many people are tied to the idea of core features being part of
> > core WP. As WP grows up and out of the blogosphere, the community has
> > to accept that people want WP to be an "a la carte" type of system.
> > Yeah, you'll have plenty of discussions as to which features should be
> > core and which should be plugins, but let's not stop the progress by
> > flat out saying "no" to anything that deserves it's proper discussion.
>
> +1.
>
> FWIW, I think the idea of "put it into a plugin" is anathema to many people because the chances of many users ever finding and installing it are slim thus very few themers or other plugin developers will support it.  OTOH, if put into a canonical plugin that is included with the WordPress core download, those concerns diminish greatly. At least for me.  
>
> Said another way, IF it's infrastructure but only used by a segment of users then:
>
> core=good,
> plugin=bad, but
> canonical plugin=bettter.
>
> -Mike
> _______________________________________________
> wp-hackers mailing list
> wp-hack... at lists.automattic.comhttp://lists.automattic.com/mailman/listinfo/wp-hackers