# Suggestions for better plugin maintenance

**URL:** <https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337>\
**Category:** Development\
**Created:** [31 أكتوبر 2016، 4:41م UTC](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337 "2016-10-31T16:41:51Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [4 نوفمبر 2016، 12:36م UTC](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337/9 "2016-11-04T12:36:14Z")

</div>

What could help here is if changes to libraries, i.e. functions in `discourse/lib` and `discourse-common/lib`, are treated with a bit more caution and notice than other changes. Typically it is a change to a commonly used library that catches one of my plugins, the most [recent example](https://meta.discourse.org/t/topic-list-previews/41630/453) being the change to buffered rendering that also effected @cpradio.

Generally speaking, I am confident that things are moving in the right direction in this respect. Just a few tweaks to how more systemic changes are notified are needed perhaps.

---

_[View the full topic](https://meta.discourse.org/t/suggestions-for-better-plugin-maintenance/52337)._