Archive deprecated Cordova repos

[brody4hire]

As discussed in: [1]

INFRA should be able to do this if we can reach sufficient agreement.

@jcesarmobile reminded me that we discussed this in the past. I recall there were some objections, quick search on my inbox did not give me any results.

I am hopeful we can give it another try and address any objections that may come up moving forwards.

Pointers to some important discussions before they get lost:

• [1] https://lists.apache.org/thread.html/57c30b14df0dadaac1e9e99b2ff41ebdc1f6a118ff7142d24c6629e3@%3Cdev.cordova.apache.org%3E - recent discussion in [email protected]

• [2] https://lists.apache.org/thread.html/34369ada22f8a616e90471d38c8fd7def2eb17ff3ddbf4ba0b47987f@%3Cdev.cordova.apache.org%3E - discussion in [email protected] from last August (2018)

• [3] https://github.com/apache/cordova-docs/pull/878 - "New deprecating & archiving" docs PR from last August (2018)

• [4] https://github.com/apache/cordova-contribute/pull/2 - another "deprecating & archiving" PR from last August (2018)

[janpio]

-1 on archiving without further preparation. Just archiving all the deprecated repos would hurt lots of users.

There is a PR open that did preparational work for this, but was not merged yet: https://github.com/apache/cordova-contribute/pull/2 The work this suggest was of course also not done.

[jcesarmobile]

I think the topic is about archiving or not archiving, not about how to do it. We first vote about archiving or not archiving. If we all agree on archiving, then we can discuss on the steps to follow before telling infra to archive. Your proposal sounds good, but if we don’t plan on archiving then it makes no sense to have such plan.

I’m +1 on archiving. I don’t see the point on deprecating if we keep them open and people keep creating issues that we won’t fix

El jueves, 29 de noviembre de 2018, Jan Piotrowski [email protected] escribió:

-1 on archiving without further preparation. Just archiving all the deprecated repos would hurt lots of users.

There is a PR open that did preparational work for this, but was not merged yet: apache/cordova-contribute#2 https://github.com/apache/cordova-contribute/pull/2 The work this suggest was of course also not done.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/apache/cordova/issues/60#issuecomment-442641234, or mute the thread https://github.com/notifications/unsubscribe-auth/ABj-BO4lw4F1efphp01UUCuCNw5ogJ-hks5uzxf5gaJpZM4Y4i84 .

[brody4hire]

Thanks guys for the feedback.

I raised this issue in order to help get the ball rolling and avoid losing track of this task or any information related to it.

I do think we should be careful not to do it the wrong way, though. I think @janpio has a valid point that we should finalize or at least answer the open questions in the proposal PRs https://github.com/apache/cordova-contribute/pull/2 & https://github.com/apache/cordova-docs/pull/878 before actually freezing (archiving) the deprecated repos. (Apologies to @janpio if I paraphrased or explained your point wrong.)

I think it was @jcesarmobile that had a valid point that we can always unfreeze archived repos if needed for any reason.

I updated the description with what I think are important pointers to the related discussions & PRs to avoid losing them.

I personally do not have much extra time to deal with this task right now, just wanted to raise it before it gets forgotten.

[janpio]

+1 on archiving some of the deprecated repos, some I think should stay un-archived for the benefit or current users. Will be able to provide a list later.

Feedback on 2 PRs @brodybits linked to is very welcome, I will try to make some time later to go over the current feedback once more to get it closer to merge ready.