You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Chris Brody <ch...@gmail.com> on 2018/08/07 15:16:35 UTC
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 if there are people still using the deprecated repos who are
motivated to take them over?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by gandhi rajan <ga...@gmail.com>.
+1 for archiving repos and documenting them.
On Wednesday, August 8, 2018, Shazron <sh...@gmail.com> 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 <pi...@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 <jc...@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 (<
> piotrowski@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 <
> jcesarmobile@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 <
> piotrowski@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 <de...@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
> > >> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> > >> >> >> > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > >> >> >> > > >
> > >> >> >> > > >
> > >> >> >> > >
> > >> >> >>
> > >> >> >> ------------------------------------------------------------
> ---------
> > >> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >> >>
> > >> >> >
> > >> >> > ------------------------------------------------------------
> ---------
> > >> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >> >
> > >> >>
> > >> >> ------------------------------------------------------------
> ---------
> > >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >>
> > >> >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
--
Regards,
Gandhi
"The best way to find urself is to lose urself in the service of others !!!"
Re: Dealing with deprecated repos
Posted by julio cesar sanchez <jc...@gmail.com>.
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 month policy of
support. I think all repos have been deprecated for more than 6 months.
Unless that 6 month support policy is just for back porting fixes to older
versions and we have a different one for deprecated repos.
El mié., 8 ago. 2018 a las 12:33, Chris Brody (<ch...@gmail.com>)
escribió:
> On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 schrieb Chris Brody <ch...@gmail.com>:
>
> 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 <pi...@gmail.com> 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
> > <pi...@gmail.com>:
> > >
> > > 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 <
> > piotrowski@gmail.com>:
> > > >
> > > > +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 <sh...@gmail.com>:
> > > >>
> > > >> 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 <ch...@gmail.com>
> > wrote:
> > > >> >
> > > >> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> > > >> > <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> > > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >> >
> > > >>
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > > >>
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Chris Brody <ch...@gmail.com>.
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 <pi...@gmail.com> 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
> <pi...@gmail.com>:
> >
> > 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 <
> piotrowski@gmail.com>:
> > >
> > > +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 <sh...@gmail.com>:
> > >>
> > >> 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 <ch...@gmail.com>
> wrote:
> > >> >
> > >> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> > >> > <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> > >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >>
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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
<pi...@gmail.com>:
>
> 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 <pi...@gmail.com>:
> >
> > +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 <sh...@gmail.com>:
> >>
> >> 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 <ch...@gmail.com> wrote:
> >> >
> >> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> >> > <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 <pi...@gmail.com>:
>
> +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 <sh...@gmail.com>:
>>
>> 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 <ch...@gmail.com> wrote:
>> >
>> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
>> > <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
>> > For additional commands, e-mail: dev-help@cordova.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
+1
cordova.apache.org/contribute/deprecation_policy.html
<http://ordova.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 <sh...@gmail.com>:
> 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 <ch...@gmail.com> wrote:
> >
> > On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> > <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Shazron <sh...@gmail.com>.
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 <ch...@gmail.com> wrote:
>
> On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
> <jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Chris Brody <ch...@gmail.com>.
On Wed, Aug 8, 2018 at 6:15 AM Shazron <sh...@gmail.com> 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
<jc...@gmail.com> 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: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
> 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.
Sorry if that was not clear, this is exactly what I meant. The standard
deprecation notice text should include a general link to /network of the
repo with some appropriate language and explanation how to look for forks.
2018-08-08 12:23 GMT+02:00 julio cesar sanchez <jc...@gmail.com>:
> 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 (<sh...@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 <pi...@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 <jcesarmobile@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 (<
> > piotrowski@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 <
> > jcesarmobile@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 <
> > piotrowski@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 <de...@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
> > > >> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> > > >> >> >> > > > For additional commands, e-mail:
> > dev-help@cordova.apache.org
> > > >> >> >> > > >
> > > >> >> >> > > >
> > > >> >> >> > >
> > > >> >> >>
> > > >> >> >>
> > ---------------------------------------------------------------------
> > > >> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > > >> >> >>
> > > >> >> >
> > > >> >> >
> > ---------------------------------------------------------------------
> > > >> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >> >> >
> > > >> >>
> > > >> >>
> > ---------------------------------------------------------------------
> > > >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > > >> >>
> > > >> >>
> > > >>
> > > >> ------------------------------------------------------------
> ---------
> > > >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > > >>
> > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: Dealing with deprecated repos
Posted by julio cesar sanchez <jc...@gmail.com>.
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 (<sh...@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 <pi...@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 <jc...@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 (<
> piotrowski@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 <
> jcesarmobile@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 <
> piotrowski@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 <de...@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
> > >> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> > >> >> >> > > > For additional commands, e-mail:
> dev-help@cordova.apache.org
> > >> >> >> > > >
> > >> >> >> > > >
> > >> >> >> > >
> > >> >> >>
> > >> >> >>
> ---------------------------------------------------------------------
> > >> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >> >>
> > >> >> >
> > >> >> >
> ---------------------------------------------------------------------
> > >> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >> >
> > >> >>
> > >> >>
> ---------------------------------------------------------------------
> > >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >> >>
> > >> >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > >> For additional commands, e-mail: dev-help@cordova.apache.org
> > >>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Shazron <sh...@gmail.com>.
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 <pi...@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 <jc...@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 (<pi...@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 <jc...@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 <pi...@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 <de...@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
> >> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> >> >> >> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >> >> > > >
> >> >> >> > > >
> >> >> >> > >
> >> >> >>
> >> >> >> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >> >>
> >> >> >
> >> >> > ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>
> >> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Chris Brody <ch...@gmail.com>.
> 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 was also able to enable issues on my fork.
> Then adding a link to that
> in the deprecation notice would be a nice move.
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 <jc...@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 (<pi...@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 <jc...@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 <pi...@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 <de...@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
>> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
>> >> >> > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> >> >> > > >
>> >> >> > > >
>> >> >> > >
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >> >>
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> > For additional commands, e-mail: dev-help@cordova.apache.org
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by julio cesar sanchez <jc...@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 (<pi...@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 <jc...@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 <pi...@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 <de...@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
> >> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> >> >> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >> > > >
> >> >> > > >
> >> >> > >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> > For additional commands, e-mail: dev-help@cordova.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 <jc...@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 <pi...@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 <de...@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
>> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
>> >> > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> >> > > >
>> >> > > >
>> >> > >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> >> For additional commands, e-mail: dev-help@cordova.apache.org
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > For additional commands, e-mail: dev-help@cordova.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by julio cesar sanchez <jc...@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 <pi...@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 <de...@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
> >> <jc...@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, <ra...@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 <ch...@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-unsubscribe@cordova.apache.org
> >> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> >> > > >
> >> > > >
> >> > >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> >> For additional commands, e-mail: dev-help@cordova.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 <de...@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
>> <jc...@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, <ra...@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 <ch...@gmail.com> schrieb am Di., 7. Aug. 2018, 17:16:
>> > >
>> > > > 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 if there are people still using the deprecated repos who are
>> > > > motivated to take them over?
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> > > > For additional commands, e-mail: dev-help@cordova.apache.org
>> > > >
>> > > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Gearóid M <de...@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
> <jc...@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, <ra...@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 <ch...@gmail.com> schrieb am Di., 7. Aug. 2018, 17:16:
> > >
> > > > 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 if there are people still using the deprecated repos who are
> > > > motivated to take them over?
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by Chris Brody <ch...@gmail.com>.
+1
On Tue, Aug 7, 2018 at 11:32 AM julio cesar sanchez
<jc...@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, <ra...@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 <ch...@gmail.com> schrieb am Di., 7. Aug. 2018, 17:16:
> >
> > > 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 if there are people still using the deprecated repos who are
> > > motivated to take them over?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Dealing with deprecated repos
Posted by julio cesar sanchez <jc...@gmail.com>.
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, <ra...@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 <ch...@gmail.com> schrieb am Di., 7. Aug. 2018, 17:16:
>
> > 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 if there are people still using the deprecated repos who are
> > motivated to take them over?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
>
Re: Dealing with deprecated repos
Posted by ra...@gmail.com.
I suggest archiving them all and deal with any issues as they appear. After
all, repos can be unarchived if necessary.
Chris Brody <ch...@gmail.com> schrieb am Di., 7. Aug. 2018, 17:16:
> 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 if there are people still using the deprecated repos who are
> motivated to take them over?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Dealing with deprecated repos
Posted by Jan Piotrowski <pi...@gmail.com>.
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 <ch...@gmail.com>:
> 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 if there are people still using the deprecated repos who are
> motivated to take them over?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org