I've just found cordova-plugin-media was voted to be "sunset", but we didn't do it (https://issues.apache.org/jira/browse/CB-13095), so might be a good start.
I think it's the only one left, and cordova-plugin-dialogs didn't get a definite decision. I wouldn't deprecate more, as biggest struggle cordova users face is the lack of supported/maintained plugins. The ones we deprecated was because of a "native" (pure html/js) alternative that could replace the plugin and wouldn't need maintenance. (Except contacts, it was the only one without alternative). Deprecating without an alternative and hoping users will fork and maintain them is not likely to happen. I think it would be better to try to find more contributors that can work on core plugins and make them committers after a while (easier said than done) El jue., 23 ago. 2018 a las 9:32, Jan Piotrowski (<piotrow...@gmail.com>) escribió: > Which plugins do fall in these two categories in your opinion? > Am Do., 23. Aug. 2018 um 01:27 Uhr schrieb Chris Brody < > chris.br...@gmail.com>: > > > > From some other discussions I started to wonder if we should consider > > deprecating some more Cordova plugins that fall into either of these > > categories: > > * not critical to core need or functionality > > * hard to support > > > > My idea is that people in the user community can start to expand and > > support the plugins they care most about, on the npm ecosystem. This > should > > free us Cordova committers to spend more time on the Cordova libraries > and > > platforms that need more of our care. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
