+1 The deprecation notice needs to be prominent, I missed it myself on a quick scroll. Some of that readme is in a specific format to support appearance in docs.cordova.io ( similar to https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-file/index.html ) This is no longer a requirement, so we can go prominent. We should also ask INFRA to put the text [DEPRECATED] in the description, and possibly even archive the repo.
On Wed, Jun 3, 2020 at 12:02 PM Norman Breau <nor...@normanbreau.com> wrote: > I'm sure you're not the only one who misses it, considering the repo is > still pretty active in terms of new issues being reported. > > On 2020-06-03 3:59 p.m., Darryl Pogue wrote: > > Correction: There is in fact a deprecation notice, part-way down the > > README, but it's not especially attention grabbing and I missed it the > > first 2 times I skimmed the file. > > > > On Wed, Jun 3, 2020 at 11:55 AM Darryl Pogue <dar...@dpogue.ca> wrote: > > > >> Hey folks, > >> > >> The File Transfer plugin has been officially deprecated since 2017: > >> > https://cordova.apache.org/blog/2017/10/18/from-filetransfer-to-xhr2.html > >> > >> However, the repo and npm have no link to that page or any sort of > >> indication that it is not maintained. > >> > >> With the release of cordova-ios 6, the FileTransfer plugin no longer > >> compiles on iOS: > >> https://github.com/apache/cordova-plugin-file-transfer/issues/258 > >> > >> I want to reply to that issue saying that it's deprecated and not > >> maintained, but I feel like we haven't made that very clear. > >> > >> I would like to propose that we update the README for File Transfer > with a > >> clear deprecation notice which links to the blog post from 2017, and > that > >> we ask ASF Infra to mark the repo as archived. > >> > >> Any objections? > >> > >> ~Darryl > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
