# How plugins moving to core is communicated **URL:** https://meta.discourse.org/t/how-plugins-moving-to-core-is-communicated/374493 **Category:** Site feedback **Created:** [July 15, 2025, 1:31pm UTC](https://meta.discourse.org/t/how-plugins-moving-to-core-is-communicated/374493 "2025-07-15T13:31:09Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin) #### Post date: [July 16, 2025, 6:05am UTC](https://meta.discourse.org/t/how-plugins-moving-to-core-is-communicated/374493/7 "2025-07-16T06:05:09Z")
> [@tobiaseigen](#): > > I was surprised too I also thought the category chosen for the announcement was rather unusual. I don’t think anyone watches it because support questions are often asked there. > [@Bundling more popular plugins with Discourse core](https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574): > > Over the next few weeks, we’ll be moving a number of popular Discourse plugins into the core repository. That means that Discourse will come with a larger number of plugins by default, and it’ll be easier for us to keep them all tested & up-to-date. All these plugins will remain disabled by default, so this won’t have any visible impact on existing communities. If you use a managed hosting service like [discourse.org](http://discourse.org), you don’t need to do anything. Self-hosted communities If you self-host Disco… Maybe subcategories in announcements would be better, then you could inform hosting customers and self-hosters (and devs) separately. Everyone is informed about a release, but you can choose whether you want to be informed about all subcategories. Also, a reply to the topic to bump it after the edit would have been helpful. Otherwise, it’s very easy to miss edits. --- _[View the full topic](https://meta.discourse.org/t/how-plugins-moving-to-core-is-communicated/374493)._