Re: Dealing with deprecated repos

Again you split the discussion in 2 places by repeating here what you already commented on the PR. Please stop doing so and complaining how complicated and scattered everything is in other threads. This is part of the reason. I responded to your PR comment. Am Do., 23. Aug. 2018 um 00:59 Uhr schr

Re: Dealing with deprecated repos

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 wrote: > And Part #2: > Contributor documentation on the process "Deprecation and Archiving" > of repositories: > https://github.com/apache/cordo

Re: Dealing with deprecated repos

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 : > > Part #1: > A public deprecation policy on the Cordova website: > https://github.c

Re: Dealing with deprecated repos

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 r

Re: Dealing with deprecated repos

+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 : > Fo

Re: Dealing with deprecated repos

> 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 n

Re: Dealing with deprecated repos

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

Re: Dealing with deprecated repos

We can probably unarchive and re-archive, but as long as we need to ask infra to do it, I don't find it reasonable to do it to just edit the README to point to a new repo. I would only do it in case there are some security fix we have to land. Anyway, even for security fixes I think we have a 6 mo

Re: Dealing with deprecated repos

On Wed, Aug 8, 2018 at 6:15 AM Shazron 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

Re: Dealing with deprecated repos

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

Re: Dealing with deprecated repos

+1 for archiving repos and documenting them. On Wednesday, August 8, 2018, Shazron wrote: > 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 > wrote: > > > > Please note that this part of th

Re: Dealing with deprecated repos

> Is there any way users can find out about new forks of deprecated > repos? Fork network view on Github maybe? I just forked https://github.com/nodejs/wiki-archive which they archived. My fork show up in: https://github.com/nodejs/wiki-archive/network/member My fork has PRs enabled by default. I

Re: Dealing with deprecated repos

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 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 th

Re: Dealing with deprecated repos

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

Re: Dealing with deprecated repos

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

Re: Dealing with deprecated repos

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 : > No,

Re: Dealing with deprecated repos

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 offici

Re: Dealing with deprecated repos

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 : > +1 on archiving deprecated repo

Re: Dealing with deprecated repos

+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 > wrote: > > > > Archived repos are read only. > > > > People can still clone and/o

Re: Dealing with deprecated repos

+1 On Tue, Aug 7, 2018 at 11:32 AM julio cesar sanchez 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, escribió: > > > I suggest archiving

Re: Dealing with deprecated repos

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, escribió: > I suggest archiving them all and deal with any issues as they appear. After > all, repos can be unarch

Re: Dealing with deprecated repos

I suggest archiving them all and deal with any issues as they appear. After all, repos can be unarchived if necessary. Chris Brody schrieb am Di., 7. Aug. 2018, 17:16: > Continuation of discussion from > > https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e185cc98b946d260184847fdf

Re: Dealing with deprecated repos

What is the current (probably unwritten) rule regarding deprecation and archival of Cordova repositories? -J 2018-08-07 17:16 GMT+02:00 Chris Brody : > Continuation of discussion from > https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e185cc98b946d260184847fdf191@%3Cdev.cordova.ap

Dealing with deprecated repos

Continuation of discussion from https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e185cc98b946d260184847fdf191@%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