The discussion centers around the recent addition of core plugins during a Discourse site update. patrickemin discovered several core plugins were added and disabled, and inquired about deleting them, expressing surprise and initial panic. pfaffman explained that the plan is to add more plugins to core and suggests removing them via app.yml. patrickemin admits to missing the announcement about this change and questions the definition of a plugin if core functionality is added this way. Heliosurge shares a personal experience of a similar issue with the chat plugin, stressing the importance of reading release notes. Moin points out that the announcement about bundling plugins wasn’(t) included in the release notes, linking to the relevant Meta Discourse post. Heliosurge hopes this was a minor oversight. The overall sentiment is one of surprise and adjustment to the change.
Hi, when updating my site today, several core plugins have been added to my plugin list, those plugins are disabled because I do not used them I guess, such as this one framed in red:
Questions:
From what I understand, the plan is to add more plugins to core.
You could add lines to your app.yml to remove them, just like the git clone lines add them now.
It’s hard to know if there’s interest. I’m a little surprised that the apple plugin made it to core, but Google has been in core forever, so maybe that’s fair.
Ok, I was a little surprised I must say, and to be frank in panic for few minutes, when updating, until I realized I had to remove from my app.yml all plugins that are now in core. May be I missed that change was going to take place ?
Surprised as you are that some core plugins that I am not going to use are in my install now (that redefines what a plugin should be no? 
), but the main point if it does not impair my site’s performance… why not…
I can appreciate that. Long ago I missed the update if chat being neeg e into core. It didn’t like me trying to install it. Took me a few minutes to track why th site wouldn’t rebuild. Once I removed th chat plugin line and checked site. Found chat was already in plugin list.
Purely my fault, but was an annoyance at the time.
My lesson learned was to take a bit more time and read over release notes
I think this announcement was not in the release notes
Ah then that is a gap. Hopefully just a minor oversight
