Perhaps modernising Quip would be a good first use of the [OpenCollective funds](https://opencollective.com/modx), though I have no idea how much work Quip would need. Probably better to discuss [in the right repository](https://github.com/modxcms/Quip/issues) too.
Originally posted by @Mark-H in modxcms/Articles#152 (comment)
I took this comment from the Articles repository. A few thoughts of mine:
I think making Quip MODX3 compatible does not require many changes. However, the current version has a few bugs and fixing them requires more work. Quip also generates many PHP warnings and may not be compatible with the latest PHP versions.
Even more work is needed if Quip will be changed to ajax-based.
I don't know how widely Quip is being used. I am using it on a website and it is a great extra. However, I have started replacing Quip with Hashover to be able to upgrade to MODX3. I am not sure if there is a real need for a MODX-based commenting component. The OpenCollective funds seem to be quite limited so maybe they should be targeted to something else?
Originally posted by @Mark-H in modxcms/Articles#152 (comment)
I took this comment from the Articles repository. A few thoughts of mine:
I think making Quip MODX3 compatible does not require many changes. However, the current version has a few bugs and fixing them requires more work. Quip also generates many PHP warnings and may not be compatible with the latest PHP versions.
Even more work is needed if Quip will be changed to ajax-based.
I don't know how widely Quip is being used. I am using it on a website and it is a great extra. However, I have started replacing Quip with Hashover to be able to upgrade to MODX3. I am not sure if there is a real need for a MODX-based commenting component. The OpenCollective funds seem to be quite limited so maybe they should be targeted to something else?