As I said in the PR I really do not see what this has to do with a project or repo called "contribute".
On Wed, Aug 22, 2018 at 6:02 PM Jan Piotrowski <[email protected]> wrote: > And Part #2: > Contributor documentation on the process "Deprecation and Archiving" > of repositories: > https://github.com/apache/cordova-contribute/pull/2 > > J > Am Mi., 22. Aug. 2018 um 21:07 Uhr schrieb Jan Piotrowski > <[email protected]>: > > > > Part #1: > > A public deprecation policy on the Cordova website: > > https://github.com/apache/cordova-docs/pull/878 > > Please keep discussion on the PR and text in the GitHub Pull Request. > > > > Part #2 will be the contributor documentation that will include the > > steps and notice template required to deprecate a repository - and > > will follow later (and build on the actual policy of course). > > Am Mi., 8. Aug. 2018 um 13:07 Uhr schrieb Jan Piotrowski < > [email protected]>: > > > > > > +1 > > > > > > cordova.apache.org/contribute/deprecation_policy.html maybe? > > > Should include summary of what was discussed here, and best also the > deprecation notice template in markdown for copy paste. > > > > > > -J > > > > > > 2018-08-08 12:55 GMT+02:00 Shazron <[email protected]>: > > >> > > >> Formal as in this is our policy. From what Julio Cesar Sanchez said > earlier: > > >> "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." > > >> > > >> As to where, we just make a new page, say deprecationpolicy.html or > > >> something, and link it from the Contribute page (as a suggestion). If > > >> we run into this again, we point to the policy. > > >> On Wed, Aug 8, 2018 at 6:33 PM Chris Brody <[email protected]> > wrote: > > >> > > > >> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <[email protected]> wrote: > > >> > > > > >> > > Let's make it formal with what we had in the repo > > >> > > > >> > Does this mean make the archiving process formal or make something > else formal? > > >> > > > >> > What kind of repo? > > >> > > > >> > > or section in the docs somewhere. > > >> > > > >> > The question is always where? > > >> > > > >> > On Wed, Aug 8, 2018 at 6:24 AM julio cesar sanchez > > >> > <[email protected]> wrote: > > >> > > > > >> > > I wouldn't point to a fork, because that will mean we have to > search for > > >> > > the forks and decide which one is better. > > >> > > > >> > +1 > > >> > > > >> > > If a better fork appears after archiving > > >> > > we won't be able to change. > > >> > > > >> > I think someone else made the point that we can always unarchive in > > >> > case of need. I suspect (and hope) we should be able to unarchive > on a > > >> > temporary basis then re-archive. > > >> > > > >> > > I think best option is to point to network tab of github (in case > people is > > >> > > > >> > +1 > > >> > > > >> > > --------------------------------------------------------------------- > > >> > To unsubscribe, e-mail: [email protected] > > >> > For additional commands, e-mail: [email protected] > > >> > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
