I wouldn't point to a fork, because that will mean we have to search for the forks and decide which one is better. Also in case we want to do that, we should do it before archiving. If a better fork appears after archiving we won't be able to change.
I think best option is to point to network tab of github (in case people is not aware of it). There you can see all forks available and easily spot extra commits people has done in an easy and visually way. Example for contacts plugin https://github.com/apache/cordova-plugin-contacts/network You can see there is a fork from timholbrook that added 22 commits from latest release, and then this fork has a few other forks itself with some other extra commits. El mié., 8 ago. 2018 a las 12:15, Shazron (<shaz...@gmail.com>) escribió: > Let's make it formal with what we had in the repo, perhaps a new page > or section in the docs somewhere. > On Wed, Aug 8, 2018 at 6:09 PM Jan Piotrowski <piotrow...@gmail.com> > wrote: > > > > Please note that this part of the discussion with me playing devil's > > advocate - I pretty much agree with what you are saying. > > > > Is there any way users can find out about new forks of deprecated > > repos? Fork network view on Github maybe? Then adding a link to that > > in the deprecation notice would be a nice move. > > > > Any other comments regarding a possible "Cordova Deprecation Policy" > > than what Julio already wrote? > > > > -J > > > > > > 2018-08-08 11:52 GMT+02:00 julio cesar sanchez <jcesarmob...@gmail.com>: > > > This is the deprecation policy from cordova-plugin-contacts > > > > > > Deprecation Notice > > > This plugin is being deprecated. No more work will be done on this > plugin > > > by the Cordova development community. You can continue to use this > plugin > > > and it should work as-is in the future but any more arising issues > will not > > > be fixed by the Cordova community. > > > > > > All the deprecated repos have a similar deprecation notice. > > > > > > Other than that, I don't think we have something more official. Also, I > > > don't know were/if that message was discussed. > > > > > > What I said on my previous message is my interpretation of "work", for > me > > > what I said is work, not sure if everybody agrees on that, and it's not > > > official, just my opinion. Also my opinion of Cordova Community is > > > everybody who wants to contribute, not just the committers. > > > > > > We have dozens of repos and hundreds of open PRs that we aren't able to > > > manage, so keeping the deprecated repos open for issues/PRs in case > > > somebody want to fix something will just bring frustration to those > people > > > as their PRs won't be reviewed/merged. And if we plan on continuing > > > reviewing/merging on deprecated repos, why did we deprecate them on the > > > first place? > > > > > > El mié., 8 ago. 2018 a las 11:26, Jan Piotrowski (< > piotrow...@gmail.com>) > > > escribió: > > > > > >> Great, then this seems to be Cordova's deprecation policy. Write it > > >> down, publish it, link to it from the deprecated projects so users > > >> know about it - problem solved. > > >> > > >> Just to be on the safe side: Was this previously discussed and > decided? > > >> > > >> -J > > >> > > >> 2018-08-08 10:49 GMT+02:00 julio cesar sanchez < > jcesarmob...@gmail.com>: > > >> > No, when we deprecate something it means no more work will be done > on it. > > >> > > > >> > Triaging issues, reviewing and merging other people prs and > continuing > > >> > doing releases it’s work. We aren’t supposed to do anything else > when we > > >> > deprecate. > > >> > > > >> > People can freely create and maintain a fork, but it won’t be > official > > >> and > > >> > won’t live in the Apache repo. > > >> > > > >> > > > >> > El miércoles, 8 de agosto de 2018, Jan Piotrowski < > piotrow...@gmail.com> > > >> > escribió: > > >> > > > >> >> Let me play devil's advocate: > > >> >> > > >> >> Archiving means disabling everything - issues, PRs, etc. > > >> >> Don't we want to let people create PRs with bug fixes or changes > (we > > >> >> may or may not choose to merge) for other people to benefit from? > > >> >> > > >> >> -J > > >> >> > > >> >> 2018-08-08 3:40 GMT+02:00 Gearóid M <d...@gearoid.me>: > > >> >> > +1 on archiving deprecated repos, it's an easy way to make it > very > > >> clear > > >> >> that it is no longer maintained > > >> >> > > > >> >> > On Wed, 8 Aug 2018, at 01:37, Chris Brody wrote: > > >> >> >> +1 > > >> >> >> On Tue, Aug 7, 2018 at 11:32 AM julio cesar sanchez > > >> >> >> <jcesarmob...@gmail.com> wrote: > > >> >> >> > > > >> >> >> > Archived repos are read only. > > >> >> >> > > > >> >> >> > People can still clone and/or fork them, they just can't send > PRs > > >> or > > >> >> create > > >> >> >> > new issues. > > >> >> >> > > > >> >> >> > I'm +1 on archiving them. > > >> >> >> > > > >> >> >> > > > >> >> >> > > > >> >> >> > El mar., 7 ago. 2018 a las 17:25, <raphine...@gmail.com> > escribió: > > >> >> >> > > > >> >> >> > > I suggest archiving them all and deal with any issues as > they > > >> >> appear. After > > >> >> >> > > all, repos can be unarchived if necessary. > > >> >> >> > > > > >> >> >> > > Chris Brody <chris.br...@gmail.com> schrieb am Di., 7. Aug. > > >> 2018, > > >> >> 17:16: > > >> >> >> > > > > >> >> >> > > > Continuation of discussion from > > >> >> >> > > > > > >> >> >> > > > > > >> >> >> > > > > >> https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e1 > > >> >> 85cc98b946d260184847fdf191@%3Cdev.cordova.apache.org%3E > > >> >> >> > > > > > >> >> >> > > > I think it is not desired to actively support deprecated > > >> repos. I > > >> >> >> > > > think the easiest solution is to simply make those repos > > >> archived. > > >> >> >> > > > > > >> >> >> > > > But what if there are people still using the deprecated > repos > > >> who > > >> >> are > > >> >> >> > > > motivated to take them over? > > >> >> >> > > > > > >> >> >> > > > > ------------------------------------------------------------ > > >> >> --------- > > >> >> >> > > > To unsubscribe, e-mail: > dev-unsubscr...@cordova.apache.org > > >> >> >> > > > For additional commands, e-mail: > dev-h...@cordova.apache.org > > >> >> >> > > > > > >> >> >> > > > > > >> >> >> > > > > >> >> >> > > >> >> >> > --------------------------------------------------------------------- > > >> >> >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > >> >> >> For additional commands, e-mail: dev-h...@cordova.apache.org > > >> >> >> > > >> >> > > > >> >> > > --------------------------------------------------------------------- > > >> >> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > >> >> > For additional commands, e-mail: dev-h...@cordova.apache.org > > >> >> > > > >> >> > > >> >> > --------------------------------------------------------------------- > > >> >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > >> >> For additional commands, e-mail: dev-h...@cordova.apache.org > > >> >> > > >> >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > >> For additional commands, e-mail: dev-h...@cordova.apache.org > > >> > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
