You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Jan Piotrowski <pi...@gmail.com> on 2018/08/01 13:22:57 UTC
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Another one:
f) Find and activate way for Github issue (and PR) updates to be
posted so Slack #issues
2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> The npm forum solves a very different problem for npm - they had too
> much noise in Github issues because of the project's popularity. Too
> much popularity is not one of Cordova's problems ;)
>
> Many uses of cordova-discuss will be able to move to the individual
> project repositories issues, maybe we can even think about getting rid
> of it. Good thing to keep in mind after everything is migrated.
> The mailing list can be used much more to just point people to a
> specific issue (as I also did in my original mail here) where the
> actual discussion will happen.
>
> -J
>
> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> +1 (+100) for migrating away from JIRA issues
>>
>> npm took a different approach that I am starting to really like: using
>> npm.community (Discourse) with GitHub login for issues and discussions
>>
>> solves another major problem since I don't like mail list for
>> discussing issues and cordova-discuss has proven to be such an
>> unpopular repo
>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <pi...@gmail.com> wrote:
>>>
>>> While our repositories are already fully on GitHub [1], our issues
>>> mainly still live in JIRA. We previously decided this should be
>>> changed [2] so issues live with code.
>>>
>>> We also did some first switches that were pretty successful:
>>>
>>> https://github.com/apache/cordova-docs/issues
>>> https://github.com/apache/cordova-windows/issues
>>>
>>> So I suggest we move forward with the rest. Here is a list of stuff to do:
>>>
>>>
>>> a) Enable GitHub issues on all repositories via INFRA ticket
>>>
>>> b) Define and update Contributor documentation:
>>> * Contributor guidelines
>>> - https://cordova.apache.org/contribute/contribute_guidelines.html
>>> - https://cordova.apache.org/contribute/
>>> - https://cordova.apache.org/contribute/issues.html
>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
>>> => https://github.com/apache/cordova-docs/issues/861
>>> * Issue template(s)
>>> * Pull Request template(s)
>>> * Github labels / issue triaging documentation
>>> * Usage of GitHub merge functionality
>>> * READMEs of all repositories
>>> * Prepare all these changes as PRs that can merged when a) is taken care of.
>>>
>>> c) Define and document handling of security issues
>>> => https://github.com/apache/cordova-docs/issues/860
>>>
>>> d) Define and execute issue migration from JIRA to GitHub
>>> e) Define and execute "disabling" of JIRA (if applies)
>>>
>>> Related:
>>> - Check if ICLA documentation is correct and fix if necessary
>>>
>>>
>>> Any input or objections?
>>>
>>> I expect d) and e) to require some more discussion and planning, but
>>> think it is ok to just leave this to be done later after everything
>>> else was taken care of. Agree?
>>>
>>> Did I miss any documents for b) that will have to be updated?
>>>
>>>
>>> Best regards,
>>> Jan
>>>
>>>
>>> PS:
>>>
>>> For future reference, the links I collected while researching the
>>> previous work done and current state:
>>>
>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
>>> https://issues.apache.org/jira/browse/INFRA-14347
>>> https://issues.apache.org/jira/browse/INFRA-14398
>>> https://issues.apache.org/jira/browse/INFRA-14399
>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
>>> https://issues.apache.org/jira/browse/INFRA-14994
>>> https://issues.apache.org/jira/browse/INFRA-14815
>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
>>>
>>> [2] Migrate Jira issues over to Github:
>>> https://issues.apache.org/jira/browse/CB-13157
>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
>>> https://github.com/apache/cordova-discuss/pull/75
>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
>>> https://issues.apache.org/jira/browse/INFRA-16503
>>>
>>> ---------------------------------------------------------------------
>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
Please open a new discussion re the archiving/deprecation topic - this
is a very different thing.
Sure, feel free to transfer the links to a Github Wiki or whatever -
as I wanted to generate the links automatically I had to use a
scripting language.
2018-08-07 17:07 GMT+02:00 Chris Brody <ch...@gmail.com>:
> I would favor archiving the deprecated repos asap so we don't have to
> deal with traffic on those anymore.
>
> Thanks for making the nice GitHub filter and group repo links. I would
> really favor using a wiki, which is supported by GitHub, for this kind
> of thing for the sake of easy writing & editing.
>
> Really nice!
> On Tue, Aug 7, 2018 at 11:01 AM Jan Piotrowski <pi...@gmail.com> wrote:
>>
>> You may have noticed the first issues coming in on some repositories.
>>
>> 1. In hindsight enabling issues for deprecated platforms, plugins etc
>> may not have been the smartest decision. We will have to find out how
>> to handle this - we should probably write down a "deprecation /
>> archivation policy" anyway.
>>
>> 2. Some people are missing the "all tickets in one view" interface. I
>> quickly built http://cordova.betamo.de/ as a workaround.
>> The second link on there generates a few prepared Github search links,
>> including one that is valid for _all_ Cordova repositories:
>> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
>> Nice, isn't it?
>> Do you have any specific requests for filters or interface you need or
>> want? What did you use in JIRA that you couldn't find for Github?
>> Shouldn't be too hard to whip something up.
>>
>> -J
>>
>>
>>
>>
>> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
>> > That worked, the ticket was just resolved and issues are now enabled
>> > for all repos (beside cordova-weinre which is archived):
>> >
>> > https://github.com/apache/cordova-android/issues
>> > https://github.com/apache/cordova-ios/issues
>> > https://github.com/apache/cordova-plugin-inappbrowser/issues
>> > ...
>> >
>> > On to b), c) etc.
>> >
>> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
>> >>>
>> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
>> >>
>> >> +100
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Chris Brody <ch...@gmail.com>.
I would favor archiving the deprecated repos asap so we don't have to
deal with traffic on those anymore.
Thanks for making the nice GitHub filter and group repo links. I would
really favor using a wiki, which is supported by GitHub, for this kind
of thing for the sake of easy writing & editing.
Really nice!
On Tue, Aug 7, 2018 at 11:01 AM Jan Piotrowski <pi...@gmail.com> wrote:
>
> You may have noticed the first issues coming in on some repositories.
>
> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> may not have been the smartest decision. We will have to find out how
> to handle this - we should probably write down a "deprecation /
> archivation policy" anyway.
>
> 2. Some people are missing the "all tickets in one view" interface. I
> quickly built http://cordova.betamo.de/ as a workaround.
> The second link on there generates a few prepared Github search links,
> including one that is valid for _all_ Cordova repositories:
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> Nice, isn't it?
> Do you have any specific requests for filters or interface you need or
> want? What did you use in JIRA that you couldn't find for Github?
> Shouldn't be too hard to whip something up.
>
> -J
>
>
>
>
> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > That worked, the ticket was just resolved and issues are now enabled
> > for all repos (beside cordova-weinre which is archived):
> >
> > https://github.com/apache/cordova-android/issues
> > https://github.com/apache/cordova-ios/issues
> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > ...
> >
> > On to b), c) etc.
> >
> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> >>>
> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> >>
> >> +100
> >>
> >> ---------------------------------------------------------------------
> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
We could whip something up using https://glitch.com for a start
On Wed, Aug 8, 2018 at 11:34 AM Shazron <sh...@gmail.com> wrote:
>
> Thanks Jan!
>
> 1. Should we just disable those then? One other way is to add in bold
> big letters about the deprecation in the New Issue template
> 2. These links are super useful. Perhaps they should be on the
> website, what do you all think? Not sure if the scripting for the
> second link is server side or it could be client side as well (via
> JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> (contribute.cordova.io) page. That massive github link could also be
> auto-generated as well on that page, somehow. Let me know how I can
> help.
> On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
> >
> > You may have noticed the first issues coming in on some repositories.
> >
> > 1. In hindsight enabling issues for deprecated platforms, plugins etc
> > may not have been the smartest decision. We will have to find out how
> > to handle this - we should probably write down a "deprecation /
> > archivation policy" anyway.
> >
> > 2. Some people are missing the "all tickets in one view" interface. I
> > quickly built http://cordova.betamo.de/ as a workaround.
> > The second link on there generates a few prepared Github search links,
> > including one that is valid for _all_ Cordova repositories:
> > https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > Nice, isn't it?
> > Do you have any specific requests for filters or interface you need or
> > want? What did you use in JIRA that you couldn't find for Github?
> > Shouldn't be too hard to whip something up.
> >
> > -J
> >
> >
> >
> >
> > 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > That worked, the ticket was just resolved and issues are now enabled
> > > for all repos (beside cordova-weinre which is archived):
> > >
> > > https://github.com/apache/cordova-android/issues
> > > https://github.com/apache/cordova-ios/issues
> > > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > ...
> > >
> > > On to b), c) etc.
> > >
> > > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> > >>>
> > >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> > >>
> > >> +100
> > >>
> > >> ---------------------------------------------------------------------
> > >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
I was under the impression that JIRA was already locked down for everyone
but PMC members. But yesterday I received a comment on an old JIRA issue.
Under these circumstances, I see the benefits of bulk-closing all JIRA
issues.
Nevertheless, I would really like to
1. have a two way link between corresponding GH and JIRA issues
2. be able to distinguish between these issue types on JIRA
1. Bulk-closed with appeal to re-file on GH
2. Bulk-closed and re-filed on GH
3. Bulk-closed and actually fixed after the fact
1. would require the users to include some recognizable string in the GH
issue, preferably as a link to the original issue. For example "Migrate
CB-XXXX".
2.1 can be achieved by labeling during bulk-close
2.2 depends on 1. working. We would then have to link to the GH issue from
the JIRA issue and update the labels there (would be nice if that was done
automatically).
For 2.3 I suggest we apply a suitable resolution to the bulk-closed JIRA
issues (could be "Migration Requested"). If the issue is actually fixed,
the resolution can be changed to "Fixed".
Again, automatically doing this for fixed GH-issues would be nice.
I know it's not realistic to keep JIRA entirely up-to-date. But we can at
least try.
Am Fr., 24. Aug. 2018 um 05:08 Uhr schrieb Bryan Ellis <
ellis.bryan@gmail.com>:
> Auto-correction sorry!
>
> Anyways, I also agree with *Shazron's* point of view on this and will also
> > go with the consensus.
>
>
>
> On Fri, Aug 24, 2018 at 12:06 PM Bryan Ellis <el...@gmail.com>
> wrote:
>
> > Personally, I am also in favor for the issue bankruptcy.
> >
> >
> > I use the LIFO method more when deciding tickets; so looking at JIRA
> might
> > become less over time as GH issues grow.
> >
> >
> > I know that there can be relevant tickets, but someone will have to spend
> > time determining that.
> >
> >
> >
> > -
> >
> > Sort out tickets that are support vs actually issues/feature related
> > to our tooling, platforms, plugins.
> > -
> >
> > Close out tickets that actually had PRs submitted and merged but not
> > closed. Seen a few of these
> > -
> >
> > Test if a report is still valid, and I mean really sit down and try to
> > reproduce.
> > -
> >
> > …
> >
> >
> > Anyways, I also agree with Sharon point of view on this and will also go
> > with the consensus.
> >
> >
> >
> >
> > On Fri, Aug 24, 2018 at 11:29 AM Shazron <sh...@gmail.com> wrote:
> >
> >> I think we have to take a look at whether we actually *will* look at
> >> GH Issues *and* JIRA. This assumes that us, with limited time and
> >> resources will actually do it.
> >> I don't think I will, tbh. The issues are not lost, they are still in
> >> JIRA for reference when the user wants to take it up again.
> >>
> >> This is just declaring issue bankruptcy (a detached break, Cortés
> >> burning his ships) and requiring the user to re-file if still relevant
> >> (they get an email notification), and puts the onus on the user, for
> >> them to have a stake in issues they have so that they can get
> >> resolved. They must be part of this and care also, we can't babysit
> >> everything. We are a technically a volunteer operation here, I think
> >> it's too much for us to maintain two sources of issues. We already
> >> have a lot on our plate already, IMO.
> >>
> >> That being said, I will go with the consensus on this list (if we
> >> believe we have consensus), and I will bring it up again in a few
> >> months time to see where we are with JIRA, and I will do my best with
> >> bridging the two personally.
> >> On Thu, Aug 23, 2018 at 5:56 PM julio cesar sanchez
> >> <jc...@gmail.com> wrote:
> >> >
> >> > Realistically, if they created an issue more than 6 months ago and
> >> nobody
> >> > looked at it in that time, they wouldn't bother to recreate. So we
> would
> >> > lose ~1700 issues.
> >> >
> >> > I agree with Raphael, if options are bulk close and ask for migration
> or
> >> > keep them open, I vote for keeping them open.
> >> >
> >> > If somebody creates a new issue that is already in JIRA and we notice
> >> it,
> >> > we can close the JIRA one as duplicate of the github one. (it has
> >> already
> >> > happened in at least one issue that I have noticed)
> >> >
> >> > El jue., 23 ago. 2018 a las 11:42, Shazron (<sh...@gmail.com>)
> >> escribió:
> >> >
> >> > > Back of the napkin calculation... if we took 5 mins (which is quite
> >> > > conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
> >> > > days of 8 hours a day full time). That's about a month of work for
> one
> >> > > person (not including weekends), but realistically it will be
> greater
> >> > > than this of course, definitely a few months. (of course the work
> can
> >> > > be run in parallel with more people...)
> >> > > On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
> >> > > >
> >> > > > Realistically doing it one by one will take a very long time, nor
> is
> >> > > > it necessary -- as a volunteer or if you were paid by your
> employer.
> >> > > > Some of these issues might be not relevant anymore. If it was
> >> > > > relevant, they can re-file in GH. I really don't want this to drag
> >> out
> >> > > > for another year.
> >> > > >
> >> > > > In my proposal - nothing will be moved, everything will be closed,
> >> > > > with a note to re-file in GH if relevant. There will be no
> >> "dangling"
> >> > > > issues - it's like what you've seen in some open sourced projects,
> >> > > > "Closing this stale issue. Re-open if still relevant" (but we say
> >> > > > re-file).
> >> > > > On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> >> > > > <jc...@gmail.com> wrote:
> >> > > > >
> >> > > > > I wouldn't do a bulk close neither, I think we should migrate
> >> them one
> >> > > by
> >> > > > > one to the respective github repo, even using same JIRA id so
> they
> >> > > still
> >> > > > > get linked, and then manually close as duplicate of the new
> >> github one.
> >> > > > >
> >> > > > > It's going to be a lot of work, but we don't need to do it right
> >> away,
> >> > > we
> >> > > > > can start by the latest ones and migrate a few every day until
> we
> >> > > finish.
> >> > > > > Would be good to actually try to reproduce them before
> migrating,
> >> so we
> >> > > > > make sure it's still an issue, but as this will take even more
> >> time,
> >> > > > > wouldn't make it mandatory.
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > El jue., 23 ago. 2018 a las 11:06, Shazron (<shazron@gmail.com
> >)
> >> > > escribió:
> >> > > > >
> >> > > > > > Thanks Jan - I will hold off until we are ready of course.
> >> > > > > >
> >> > > > > > Raphael - close as in there can not be any more comments added
> >> or
> >> > > > > > additions to the issue, not deletion. They will still exist
> and
> >> be
> >> > > > > > searchable. We definitely can add a label when we close them.
> >> > > > > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <
> >> piotrowski@gmail.com
> >> > > >
> >> > > > > > wrote:
> >> > > > > > >
> >> > > > > > > Just a note to make sure: Please do not proceed with this
> >> before
> >> > > issue
> >> > > > > > > and PR templates are in place, labels are unified etc -
> >> meaning:
> >> > > > > > > GitHub repos are ready.
> >> > > > > > > (Working on this right now)
> >> > > > > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
> >> > > shazron@gmail.com>:
> >> > > > > > > >
> >> > > > > > > > I've done this for our JIRA:
> >> > > > > > > > - I've changed "Resolved" issues to "Closed" (about 8000+
> of
> >> > > them)
> >> > > > > > > > - I've changed issues with "No Component" to the relevant
> >> > > component
> >> > > > > > > >
> >> > > > > > > > What's left:
> >> > > > > > > > - We have 1881 Open, Reopened or In Progress issues
> >> > > > > > > > - 474 were created in the last year (52 weeks)
> >> > > > > > > > - thus 1,407 were created more than a year ago
> >> > > > > > > > - 199 were created in the last 6 months (26 weeks)
> >> > > > > > > >
> >> > > > > > > > What's next:
> >> > > > > > > > 1. I can Bulk Resolve all issues with a comment so the
> >> reporters
> >> > > will
> >> > > > > > > > know where to re-file, with instructions, and point them
> to
> >> > > > > > > > issues.cordova.io [FAST]
> >> > > > > > > > OR
> >> > > > > > > > 2. I can Bulk Resolve issues by component, and point them
> >> to the
> >> > > right
> >> > > > > > > > GH repo to file the new issue [SLOW]
> >> > > > > > > >
> >> > > > > > > > Since this is a bulk operation, if we still need to keep
> >> some
> >> > > issues
> >> > > > > > > > open in JIRA, we need to tag with a label so I can skip
> >> those.
> >> > > > > > > >
> >> > > > > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
> >> > > piotrowski@gmail.com>
> >> > > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > > > 1. Should we just disable those then? One other way is
> >> to
> >> > > add in
> >> > > > > > bold
> >> > > > > > > > > > big letters about the deprecation in the New Issue
> >> template
> >> > > > > > > > >
> >> > > > > > > > > We should probably "just" define our deprecation and
> >> archival
> >> > > policy
> >> > > > > > > > > (see other active thread). Depending on that, we can
> >> create
> >> > > another
> >> > > > > > > > > INFRA issue to get taken care of that. There is no flood
> >> of
> >> > > Github
> >> > > > > > > > > issues for these repos right now, so no harm done.
> >> > > > > > > > >
> >> > > > > > > > > > 2. These links are super useful. Perhaps they should
> be
> >> on
> >> > > the
> >> > > > > > > > > > website, what do you all think? Not sure if the
> >> scripting
> >> > > for the
> >> > > > > > > > > > second link is server side or it could be client side
> as
> >> > > well (via
> >> > > > > > > > > > JavaScript). Perhaps on the
> >> > > https://cordova.apache.org/contribute/
> >> > > > > > > > > > (contribute.cordova.io) page. That massive github
> link
> >> > > could also
> >> > > > > > be
> >> > > > > > > > > > auto-generated as well on that page, somehow. Let me
> >> know
> >> > > how I can
> >> > > > > > > > > > help.
> >> > > > > > > > >
> >> > > > > > > > > Yes, I think those could very well be on the Cordova web
> >> site
> >> > > as
> >> > > > > > well.
> >> > > > > > > > > http://cordova.betamo.de/ is built with PHP, I will put
> >> its
> >> > > source
> >> > > > > > up
> >> > > > > > > > > on Github later so someone can rebuild it with JS if
> >> > > needed/wanted.
> >> > > > > > > > > For now it is just a solution for us committers (and
> >> especially
> >> > > > > > > > > myself).
> >> > > > > > > > >
> >> > > > > > > > > -J
> >> > > > > > > > >
> >> > > > > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> >> > > > > > > > > > Thanks Jan!
> >> > > > > > > > > >
> >> > > > > > > > > > 1. Should we just disable those then? One other way is
> >> to
> >> > > add in
> >> > > > > > bold
> >> > > > > > > > > > big letters about the deprecation in the New Issue
> >> template
> >> > > > > > > > > > 2. These links are super useful. Perhaps they should
> be
> >> on
> >> > > the
> >> > > > > > > > > > website, what do you all think? Not sure if the
> >> scripting
> >> > > for the
> >> > > > > > > > > > second link is server side or it could be client side
> as
> >> > > well (via
> >> > > > > > > > > > JavaScript). Perhaps on the
> >> > > https://cordova.apache.org/contribute/
> >> > > > > > > > > > (contribute.cordova.io) page. That massive github
> link
> >> > > could also
> >> > > > > > be
> >> > > > > > > > > > auto-generated as well on that page, somehow. Let me
> >> know
> >> > > how I can
> >> > > > > > > > > > help.
> >> > > > > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> >> > > > > > piotrowski@gmail.com> wrote:
> >> > > > > > > > > >>
> >> > > > > > > > > >> You may have noticed the first issues coming in on
> some
> >> > > > > > repositories.
> >> > > > > > > > > >>
> >> > > > > > > > > >> 1. In hindsight enabling issues for deprecated
> >> platforms,
> >> > > plugins
> >> > > > > > etc
> >> > > > > > > > > >> may not have been the smartest decision. We will have
> >> to
> >> > > find out
> >> > > > > > how
> >> > > > > > > > > >> to handle this - we should probably write down a
> >> > > "deprecation /
> >> > > > > > > > > >> archivation policy" anyway.
> >> > > > > > > > > >>
> >> > > > > > > > > >> 2. Some people are missing the "all tickets in one
> >> view"
> >> > > > > > interface. I
> >> > > > > > > > > >> quickly built http://cordova.betamo.de/ as a
> >> workaround.
> >> > > > > > > > > >> The second link on there generates a few prepared
> >> Github
> >> > > search
> >> > > > > > links,
> >> > > > > > > > > >> including one that is valid for _all_ Cordova
> >> repositories:
> >> > > > > > > > > >>
> >> > > > > >
> >> > >
> >>
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> >> > > > > > > > > >> Nice, isn't it?
> >> > > > > > > > > >> Do you have any specific requests for filters or
> >> interface
> >> > > you
> >> > > > > > need or
> >> > > > > > > > > >> want? What did you use in JIRA that you couldn't find
> >> for
> >> > > Github?
> >> > > > > > > > > >> Shouldn't be too hard to whip something up.
> >> > > > > > > > > >>
> >> > > > > > > > > >> -J
> >> > > > > > > > > >>
> >> > > > > > > > > >>
> >> > > > > > > > > >>
> >> > > > > > > > > >>
> >> > > > > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
> >> > > piotrowski@gmail.com>:
> >> > > > > > > > > >> > That worked, the ticket was just resolved and
> issues
> >> are
> >> > > now
> >> > > > > > enabled
> >> > > > > > > > > >> > for all repos (beside cordova-weinre which is
> >> archived):
> >> > > > > > > > > >> >
> >> > > > > > > > > >> > https://github.com/apache/cordova-android/issues
> >> > > > > > > > > >> > https://github.com/apache/cordova-ios/issues
> >> > > > > > > > > >> >
> >> > > https://github.com/apache/cordova-plugin-inappbrowser/issues
> >> > > > > > > > > >> > ...
> >> > > > > > > > > >> >
> >> > > > > > > > > >> > On to b), c) etc.
> >> > > > > > > > > >> >
> >> > > > > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
> >> > > chris.brody@gmail.com>:
> >> > > > > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> >> > > > > > piotrowski@gmail.com> wrote:
> >> > > > > > > > > >> >>>
> >> > > > > > > > > >> >>> Created INFRA issue at
> >> > > > > > https://issues.apache.org/jira/browse/INFRA-16876
> >> > > > > > > > > >> >>
> >> > > > > > > > > >> >> +100
> >> > > > > > > > > >> >>
> >> > > > > > > > > >> >>
> >> > > > > >
> >> ---------------------------------------------------------------------
> >> > > > > > > > > >> >> 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
> >> > > > > >
> >> > > > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Bryan Ellis <el...@gmail.com>.
Auto-correction sorry!
Anyways, I also agree with *Shazron's* point of view on this and will also
> go with the consensus.
On Fri, Aug 24, 2018 at 12:06 PM Bryan Ellis <el...@gmail.com> wrote:
> Personally, I am also in favor for the issue bankruptcy.
>
>
> I use the LIFO method more when deciding tickets; so looking at JIRA might
> become less over time as GH issues grow.
>
>
> I know that there can be relevant tickets, but someone will have to spend
> time determining that.
>
>
>
> -
>
> Sort out tickets that are support vs actually issues/feature related
> to our tooling, platforms, plugins.
> -
>
> Close out tickets that actually had PRs submitted and merged but not
> closed. Seen a few of these
> -
>
> Test if a report is still valid, and I mean really sit down and try to
> reproduce.
> -
>
> …
>
>
> Anyways, I also agree with Sharon point of view on this and will also go
> with the consensus.
>
>
>
>
> On Fri, Aug 24, 2018 at 11:29 AM Shazron <sh...@gmail.com> wrote:
>
>> I think we have to take a look at whether we actually *will* look at
>> GH Issues *and* JIRA. This assumes that us, with limited time and
>> resources will actually do it.
>> I don't think I will, tbh. The issues are not lost, they are still in
>> JIRA for reference when the user wants to take it up again.
>>
>> This is just declaring issue bankruptcy (a detached break, Cortés
>> burning his ships) and requiring the user to re-file if still relevant
>> (they get an email notification), and puts the onus on the user, for
>> them to have a stake in issues they have so that they can get
>> resolved. They must be part of this and care also, we can't babysit
>> everything. We are a technically a volunteer operation here, I think
>> it's too much for us to maintain two sources of issues. We already
>> have a lot on our plate already, IMO.
>>
>> That being said, I will go with the consensus on this list (if we
>> believe we have consensus), and I will bring it up again in a few
>> months time to see where we are with JIRA, and I will do my best with
>> bridging the two personally.
>> On Thu, Aug 23, 2018 at 5:56 PM julio cesar sanchez
>> <jc...@gmail.com> wrote:
>> >
>> > Realistically, if they created an issue more than 6 months ago and
>> nobody
>> > looked at it in that time, they wouldn't bother to recreate. So we would
>> > lose ~1700 issues.
>> >
>> > I agree with Raphael, if options are bulk close and ask for migration or
>> > keep them open, I vote for keeping them open.
>> >
>> > If somebody creates a new issue that is already in JIRA and we notice
>> it,
>> > we can close the JIRA one as duplicate of the github one. (it has
>> already
>> > happened in at least one issue that I have noticed)
>> >
>> > El jue., 23 ago. 2018 a las 11:42, Shazron (<sh...@gmail.com>)
>> escribió:
>> >
>> > > Back of the napkin calculation... if we took 5 mins (which is quite
>> > > conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
>> > > days of 8 hours a day full time). That's about a month of work for one
>> > > person (not including weekends), but realistically it will be greater
>> > > than this of course, definitely a few months. (of course the work can
>> > > be run in parallel with more people...)
>> > > On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
>> > > >
>> > > > Realistically doing it one by one will take a very long time, nor is
>> > > > it necessary -- as a volunteer or if you were paid by your employer.
>> > > > Some of these issues might be not relevant anymore. If it was
>> > > > relevant, they can re-file in GH. I really don't want this to drag
>> out
>> > > > for another year.
>> > > >
>> > > > In my proposal - nothing will be moved, everything will be closed,
>> > > > with a note to re-file in GH if relevant. There will be no
>> "dangling"
>> > > > issues - it's like what you've seen in some open sourced projects,
>> > > > "Closing this stale issue. Re-open if still relevant" (but we say
>> > > > re-file).
>> > > > On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
>> > > > <jc...@gmail.com> wrote:
>> > > > >
>> > > > > I wouldn't do a bulk close neither, I think we should migrate
>> them one
>> > > by
>> > > > > one to the respective github repo, even using same JIRA id so they
>> > > still
>> > > > > get linked, and then manually close as duplicate of the new
>> github one.
>> > > > >
>> > > > > It's going to be a lot of work, but we don't need to do it right
>> away,
>> > > we
>> > > > > can start by the latest ones and migrate a few every day until we
>> > > finish.
>> > > > > Would be good to actually try to reproduce them before migrating,
>> so we
>> > > > > make sure it's still an issue, but as this will take even more
>> time,
>> > > > > wouldn't make it mandatory.
>> > > > >
>> > > > >
>> > > > >
>> > > > > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>)
>> > > escribió:
>> > > > >
>> > > > > > Thanks Jan - I will hold off until we are ready of course.
>> > > > > >
>> > > > > > Raphael - close as in there can not be any more comments added
>> or
>> > > > > > additions to the issue, not deletion. They will still exist and
>> be
>> > > > > > searchable. We definitely can add a label when we close them.
>> > > > > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <
>> piotrowski@gmail.com
>> > > >
>> > > > > > wrote:
>> > > > > > >
>> > > > > > > Just a note to make sure: Please do not proceed with this
>> before
>> > > issue
>> > > > > > > and PR templates are in place, labels are unified etc -
>> meaning:
>> > > > > > > GitHub repos are ready.
>> > > > > > > (Working on this right now)
>> > > > > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
>> > > shazron@gmail.com>:
>> > > > > > > >
>> > > > > > > > I've done this for our JIRA:
>> > > > > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of
>> > > them)
>> > > > > > > > - I've changed issues with "No Component" to the relevant
>> > > component
>> > > > > > > >
>> > > > > > > > What's left:
>> > > > > > > > - We have 1881 Open, Reopened or In Progress issues
>> > > > > > > > - 474 were created in the last year (52 weeks)
>> > > > > > > > - thus 1,407 were created more than a year ago
>> > > > > > > > - 199 were created in the last 6 months (26 weeks)
>> > > > > > > >
>> > > > > > > > What's next:
>> > > > > > > > 1. I can Bulk Resolve all issues with a comment so the
>> reporters
>> > > will
>> > > > > > > > know where to re-file, with instructions, and point them to
>> > > > > > > > issues.cordova.io [FAST]
>> > > > > > > > OR
>> > > > > > > > 2. I can Bulk Resolve issues by component, and point them
>> to the
>> > > right
>> > > > > > > > GH repo to file the new issue [SLOW]
>> > > > > > > >
>> > > > > > > > Since this is a bulk operation, if we still need to keep
>> some
>> > > issues
>> > > > > > > > open in JIRA, we need to tag with a label so I can skip
>> those.
>> > > > > > > >
>> > > > > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
>> > > piotrowski@gmail.com>
>> > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > 1. Should we just disable those then? One other way is
>> to
>> > > add in
>> > > > > > bold
>> > > > > > > > > > big letters about the deprecation in the New Issue
>> template
>> > > > > > > > >
>> > > > > > > > > We should probably "just" define our deprecation and
>> archival
>> > > policy
>> > > > > > > > > (see other active thread). Depending on that, we can
>> create
>> > > another
>> > > > > > > > > INFRA issue to get taken care of that. There is no flood
>> of
>> > > Github
>> > > > > > > > > issues for these repos right now, so no harm done.
>> > > > > > > > >
>> > > > > > > > > > 2. These links are super useful. Perhaps they should be
>> on
>> > > the
>> > > > > > > > > > website, what do you all think? Not sure if the
>> scripting
>> > > for the
>> > > > > > > > > > second link is server side or it could be client side as
>> > > well (via
>> > > > > > > > > > JavaScript). Perhaps on the
>> > > https://cordova.apache.org/contribute/
>> > > > > > > > > > (contribute.cordova.io) page. That massive github link
>> > > could also
>> > > > > > be
>> > > > > > > > > > auto-generated as well on that page, somehow. Let me
>> know
>> > > how I can
>> > > > > > > > > > help.
>> > > > > > > > >
>> > > > > > > > > Yes, I think those could very well be on the Cordova web
>> site
>> > > as
>> > > > > > well.
>> > > > > > > > > http://cordova.betamo.de/ is built with PHP, I will put
>> its
>> > > source
>> > > > > > up
>> > > > > > > > > on Github later so someone can rebuild it with JS if
>> > > needed/wanted.
>> > > > > > > > > For now it is just a solution for us committers (and
>> especially
>> > > > > > > > > myself).
>> > > > > > > > >
>> > > > > > > > > -J
>> > > > > > > > >
>> > > > > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
>> > > > > > > > > > Thanks Jan!
>> > > > > > > > > >
>> > > > > > > > > > 1. Should we just disable those then? One other way is
>> to
>> > > add in
>> > > > > > bold
>> > > > > > > > > > big letters about the deprecation in the New Issue
>> template
>> > > > > > > > > > 2. These links are super useful. Perhaps they should be
>> on
>> > > the
>> > > > > > > > > > website, what do you all think? Not sure if the
>> scripting
>> > > for the
>> > > > > > > > > > second link is server side or it could be client side as
>> > > well (via
>> > > > > > > > > > JavaScript). Perhaps on the
>> > > https://cordova.apache.org/contribute/
>> > > > > > > > > > (contribute.cordova.io) page. That massive github link
>> > > could also
>> > > > > > be
>> > > > > > > > > > auto-generated as well on that page, somehow. Let me
>> know
>> > > how I can
>> > > > > > > > > > help.
>> > > > > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
>> > > > > > piotrowski@gmail.com> wrote:
>> > > > > > > > > >>
>> > > > > > > > > >> You may have noticed the first issues coming in on some
>> > > > > > repositories.
>> > > > > > > > > >>
>> > > > > > > > > >> 1. In hindsight enabling issues for deprecated
>> platforms,
>> > > plugins
>> > > > > > etc
>> > > > > > > > > >> may not have been the smartest decision. We will have
>> to
>> > > find out
>> > > > > > how
>> > > > > > > > > >> to handle this - we should probably write down a
>> > > "deprecation /
>> > > > > > > > > >> archivation policy" anyway.
>> > > > > > > > > >>
>> > > > > > > > > >> 2. Some people are missing the "all tickets in one
>> view"
>> > > > > > interface. I
>> > > > > > > > > >> quickly built http://cordova.betamo.de/ as a
>> workaround.
>> > > > > > > > > >> The second link on there generates a few prepared
>> Github
>> > > search
>> > > > > > links,
>> > > > > > > > > >> including one that is valid for _all_ Cordova
>> repositories:
>> > > > > > > > > >>
>> > > > > >
>> > >
>> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
>> > > > > > > > > >> Nice, isn't it?
>> > > > > > > > > >> Do you have any specific requests for filters or
>> interface
>> > > you
>> > > > > > need or
>> > > > > > > > > >> want? What did you use in JIRA that you couldn't find
>> for
>> > > Github?
>> > > > > > > > > >> Shouldn't be too hard to whip something up.
>> > > > > > > > > >>
>> > > > > > > > > >> -J
>> > > > > > > > > >>
>> > > > > > > > > >>
>> > > > > > > > > >>
>> > > > > > > > > >>
>> > > > > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
>> > > piotrowski@gmail.com>:
>> > > > > > > > > >> > That worked, the ticket was just resolved and issues
>> are
>> > > now
>> > > > > > enabled
>> > > > > > > > > >> > for all repos (beside cordova-weinre which is
>> archived):
>> > > > > > > > > >> >
>> > > > > > > > > >> > https://github.com/apache/cordova-android/issues
>> > > > > > > > > >> > https://github.com/apache/cordova-ios/issues
>> > > > > > > > > >> >
>> > > https://github.com/apache/cordova-plugin-inappbrowser/issues
>> > > > > > > > > >> > ...
>> > > > > > > > > >> >
>> > > > > > > > > >> > On to b), c) etc.
>> > > > > > > > > >> >
>> > > > > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
>> > > chris.brody@gmail.com>:
>> > > > > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
>> > > > > > piotrowski@gmail.com> wrote:
>> > > > > > > > > >> >>>
>> > > > > > > > > >> >>> Created INFRA issue at
>> > > > > > https://issues.apache.org/jira/browse/INFRA-16876
>> > > > > > > > > >> >>
>> > > > > > > > > >> >> +100
>> > > > > > > > > >> >>
>> > > > > > > > > >> >>
>> > > > > >
>> ---------------------------------------------------------------------
>> > > > > > > > > >> >> 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
>> > > > > >
>> > > > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Bryan Ellis <el...@gmail.com>.
Personally, I am also in favor for the issue bankruptcy.
I use the LIFO method more when deciding tickets; so looking at JIRA might
become less over time as GH issues grow.
I know that there can be relevant tickets, but someone will have to spend
time determining that.
-
Sort out tickets that are support vs actually issues/feature related to
our tooling, platforms, plugins.
-
Close out tickets that actually had PRs submitted and merged but not
closed. Seen a few of these
-
Test if a report is still valid, and I mean really sit down and try to
reproduce.
-
…
Anyways, I also agree with Sharon point of view on this and will also go
with the consensus.
On Fri, Aug 24, 2018 at 11:29 AM Shazron <sh...@gmail.com> wrote:
> I think we have to take a look at whether we actually *will* look at
> GH Issues *and* JIRA. This assumes that us, with limited time and
> resources will actually do it.
> I don't think I will, tbh. The issues are not lost, they are still in
> JIRA for reference when the user wants to take it up again.
>
> This is just declaring issue bankruptcy (a detached break, Cortés
> burning his ships) and requiring the user to re-file if still relevant
> (they get an email notification), and puts the onus on the user, for
> them to have a stake in issues they have so that they can get
> resolved. They must be part of this and care also, we can't babysit
> everything. We are a technically a volunteer operation here, I think
> it's too much for us to maintain two sources of issues. We already
> have a lot on our plate already, IMO.
>
> That being said, I will go with the consensus on this list (if we
> believe we have consensus), and I will bring it up again in a few
> months time to see where we are with JIRA, and I will do my best with
> bridging the two personally.
> On Thu, Aug 23, 2018 at 5:56 PM julio cesar sanchez
> <jc...@gmail.com> wrote:
> >
> > Realistically, if they created an issue more than 6 months ago and nobody
> > looked at it in that time, they wouldn't bother to recreate. So we would
> > lose ~1700 issues.
> >
> > I agree with Raphael, if options are bulk close and ask for migration or
> > keep them open, I vote for keeping them open.
> >
> > If somebody creates a new issue that is already in JIRA and we notice it,
> > we can close the JIRA one as duplicate of the github one. (it has already
> > happened in at least one issue that I have noticed)
> >
> > El jue., 23 ago. 2018 a las 11:42, Shazron (<sh...@gmail.com>)
> escribió:
> >
> > > Back of the napkin calculation... if we took 5 mins (which is quite
> > > conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
> > > days of 8 hours a day full time). That's about a month of work for one
> > > person (not including weekends), but realistically it will be greater
> > > than this of course, definitely a few months. (of course the work can
> > > be run in parallel with more people...)
> > > On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
> > > >
> > > > Realistically doing it one by one will take a very long time, nor is
> > > > it necessary -- as a volunteer or if you were paid by your employer.
> > > > Some of these issues might be not relevant anymore. If it was
> > > > relevant, they can re-file in GH. I really don't want this to drag
> out
> > > > for another year.
> > > >
> > > > In my proposal - nothing will be moved, everything will be closed,
> > > > with a note to re-file in GH if relevant. There will be no "dangling"
> > > > issues - it's like what you've seen in some open sourced projects,
> > > > "Closing this stale issue. Re-open if still relevant" (but we say
> > > > re-file).
> > > > On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> > > > <jc...@gmail.com> wrote:
> > > > >
> > > > > I wouldn't do a bulk close neither, I think we should migrate them
> one
> > > by
> > > > > one to the respective github repo, even using same JIRA id so they
> > > still
> > > > > get linked, and then manually close as duplicate of the new github
> one.
> > > > >
> > > > > It's going to be a lot of work, but we don't need to do it right
> away,
> > > we
> > > > > can start by the latest ones and migrate a few every day until we
> > > finish.
> > > > > Would be good to actually try to reproduce them before migrating,
> so we
> > > > > make sure it's still an issue, but as this will take even more
> time,
> > > > > wouldn't make it mandatory.
> > > > >
> > > > >
> > > > >
> > > > > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>)
> > > escribió:
> > > > >
> > > > > > Thanks Jan - I will hold off until we are ready of course.
> > > > > >
> > > > > > Raphael - close as in there can not be any more comments added or
> > > > > > additions to the issue, not deletion. They will still exist and
> be
> > > > > > searchable. We definitely can add a label when we close them.
> > > > > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <
> piotrowski@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Just a note to make sure: Please do not proceed with this
> before
> > > issue
> > > > > > > and PR templates are in place, labels are unified etc -
> meaning:
> > > > > > > GitHub repos are ready.
> > > > > > > (Working on this right now)
> > > > > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
> > > shazron@gmail.com>:
> > > > > > > >
> > > > > > > > I've done this for our JIRA:
> > > > > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of
> > > them)
> > > > > > > > - I've changed issues with "No Component" to the relevant
> > > component
> > > > > > > >
> > > > > > > > What's left:
> > > > > > > > - We have 1881 Open, Reopened or In Progress issues
> > > > > > > > - 474 were created in the last year (52 weeks)
> > > > > > > > - thus 1,407 were created more than a year ago
> > > > > > > > - 199 were created in the last 6 months (26 weeks)
> > > > > > > >
> > > > > > > > What's next:
> > > > > > > > 1. I can Bulk Resolve all issues with a comment so the
> reporters
> > > will
> > > > > > > > know where to re-file, with instructions, and point them to
> > > > > > > > issues.cordova.io [FAST]
> > > > > > > > OR
> > > > > > > > 2. I can Bulk Resolve issues by component, and point them to
> the
> > > right
> > > > > > > > GH repo to file the new issue [SLOW]
> > > > > > > >
> > > > > > > > Since this is a bulk operation, if we still need to keep some
> > > issues
> > > > > > > > open in JIRA, we need to tag with a label so I can skip
> those.
> > > > > > > >
> > > > > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
> > > piotrowski@gmail.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > 1. Should we just disable those then? One other way is to
> > > add in
> > > > > > bold
> > > > > > > > > > big letters about the deprecation in the New Issue
> template
> > > > > > > > >
> > > > > > > > > We should probably "just" define our deprecation and
> archival
> > > policy
> > > > > > > > > (see other active thread). Depending on that, we can create
> > > another
> > > > > > > > > INFRA issue to get taken care of that. There is no flood of
> > > Github
> > > > > > > > > issues for these repos right now, so no harm done.
> > > > > > > > >
> > > > > > > > > > 2. These links are super useful. Perhaps they should be
> on
> > > the
> > > > > > > > > > website, what do you all think? Not sure if the scripting
> > > for the
> > > > > > > > > > second link is server side or it could be client side as
> > > well (via
> > > > > > > > > > JavaScript). Perhaps on the
> > > https://cordova.apache.org/contribute/
> > > > > > > > > > (contribute.cordova.io) page. That massive github link
> > > could also
> > > > > > be
> > > > > > > > > > auto-generated as well on that page, somehow. Let me know
> > > how I can
> > > > > > > > > > help.
> > > > > > > > >
> > > > > > > > > Yes, I think those could very well be on the Cordova web
> site
> > > as
> > > > > > well.
> > > > > > > > > http://cordova.betamo.de/ is built with PHP, I will put
> its
> > > source
> > > > > > up
> > > > > > > > > on Github later so someone can rebuild it with JS if
> > > needed/wanted.
> > > > > > > > > For now it is just a solution for us committers (and
> especially
> > > > > > > > > myself).
> > > > > > > > >
> > > > > > > > > -J
> > > > > > > > >
> > > > > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > > > > > Thanks Jan!
> > > > > > > > > >
> > > > > > > > > > 1. Should we just disable those then? One other way is to
> > > add in
> > > > > > bold
> > > > > > > > > > big letters about the deprecation in the New Issue
> template
> > > > > > > > > > 2. These links are super useful. Perhaps they should be
> on
> > > the
> > > > > > > > > > website, what do you all think? Not sure if the scripting
> > > for the
> > > > > > > > > > second link is server side or it could be client side as
> > > well (via
> > > > > > > > > > JavaScript). Perhaps on the
> > > https://cordova.apache.org/contribute/
> > > > > > > > > > (contribute.cordova.io) page. That massive github link
> > > could also
> > > > > > be
> > > > > > > > > > auto-generated as well on that page, somehow. Let me know
> > > how I can
> > > > > > > > > > help.
> > > > > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > > > > > piotrowski@gmail.com> wrote:
> > > > > > > > > >>
> > > > > > > > > >> You may have noticed the first issues coming in on some
> > > > > > repositories.
> > > > > > > > > >>
> > > > > > > > > >> 1. In hindsight enabling issues for deprecated
> platforms,
> > > plugins
> > > > > > etc
> > > > > > > > > >> may not have been the smartest decision. We will have to
> > > find out
> > > > > > how
> > > > > > > > > >> to handle this - we should probably write down a
> > > "deprecation /
> > > > > > > > > >> archivation policy" anyway.
> > > > > > > > > >>
> > > > > > > > > >> 2. Some people are missing the "all tickets in one view"
> > > > > > interface. I
> > > > > > > > > >> quickly built http://cordova.betamo.de/ as a
> workaround.
> > > > > > > > > >> The second link on there generates a few prepared Github
> > > search
> > > > > > links,
> > > > > > > > > >> including one that is valid for _all_ Cordova
> repositories:
> > > > > > > > > >>
> > > > > >
> > >
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > > > > > >> Nice, isn't it?
> > > > > > > > > >> Do you have any specific requests for filters or
> interface
> > > you
> > > > > > need or
> > > > > > > > > >> want? What did you use in JIRA that you couldn't find
> for
> > > Github?
> > > > > > > > > >> Shouldn't be too hard to whip something up.
> > > > > > > > > >>
> > > > > > > > > >> -J
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
> > > piotrowski@gmail.com>:
> > > > > > > > > >> > That worked, the ticket was just resolved and issues
> are
> > > now
> > > > > > enabled
> > > > > > > > > >> > for all repos (beside cordova-weinre which is
> archived):
> > > > > > > > > >> >
> > > > > > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > > > > > >> >
> > > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > > > > > >> > ...
> > > > > > > > > >> >
> > > > > > > > > >> > On to b), c) etc.
> > > > > > > > > >> >
> > > > > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
> > > chris.brody@gmail.com>:
> > > > > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > > > > > piotrowski@gmail.com> wrote:
> > > > > > > > > >> >>>
> > > > > > > > > >> >>> Created INFRA issue at
> > > > > > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > > > > > >> >>
> > > > > > > > > >> >> +100
> > > > > > > > > >> >>
> > > > > > > > > >> >>
> > > > > >
> ---------------------------------------------------------------------
> > > > > > > > > >> >> 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
> > > > > >
> > > > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
I think we have to take a look at whether we actually *will* look at
GH Issues *and* JIRA. This assumes that us, with limited time and
resources will actually do it.
I don't think I will, tbh. The issues are not lost, they are still in
JIRA for reference when the user wants to take it up again.
This is just declaring issue bankruptcy (a detached break, Cortés
burning his ships) and requiring the user to re-file if still relevant
(they get an email notification), and puts the onus on the user, for
them to have a stake in issues they have so that they can get
resolved. They must be part of this and care also, we can't babysit
everything. We are a technically a volunteer operation here, I think
it's too much for us to maintain two sources of issues. We already
have a lot on our plate already, IMO.
That being said, I will go with the consensus on this list (if we
believe we have consensus), and I will bring it up again in a few
months time to see where we are with JIRA, and I will do my best with
bridging the two personally.
On Thu, Aug 23, 2018 at 5:56 PM julio cesar sanchez
<jc...@gmail.com> wrote:
>
> Realistically, if they created an issue more than 6 months ago and nobody
> looked at it in that time, they wouldn't bother to recreate. So we would
> lose ~1700 issues.
>
> I agree with Raphael, if options are bulk close and ask for migration or
> keep them open, I vote for keeping them open.
>
> If somebody creates a new issue that is already in JIRA and we notice it,
> we can close the JIRA one as duplicate of the github one. (it has already
> happened in at least one issue that I have noticed)
>
> El jue., 23 ago. 2018 a las 11:42, Shazron (<sh...@gmail.com>) escribió:
>
> > Back of the napkin calculation... if we took 5 mins (which is quite
> > conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
> > days of 8 hours a day full time). That's about a month of work for one
> > person (not including weekends), but realistically it will be greater
> > than this of course, definitely a few months. (of course the work can
> > be run in parallel with more people...)
> > On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
> > >
> > > Realistically doing it one by one will take a very long time, nor is
> > > it necessary -- as a volunteer or if you were paid by your employer.
> > > Some of these issues might be not relevant anymore. If it was
> > > relevant, they can re-file in GH. I really don't want this to drag out
> > > for another year.
> > >
> > > In my proposal - nothing will be moved, everything will be closed,
> > > with a note to re-file in GH if relevant. There will be no "dangling"
> > > issues - it's like what you've seen in some open sourced projects,
> > > "Closing this stale issue. Re-open if still relevant" (but we say
> > > re-file).
> > > On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> > > <jc...@gmail.com> wrote:
> > > >
> > > > I wouldn't do a bulk close neither, I think we should migrate them one
> > by
> > > > one to the respective github repo, even using same JIRA id so they
> > still
> > > > get linked, and then manually close as duplicate of the new github one.
> > > >
> > > > It's going to be a lot of work, but we don't need to do it right away,
> > we
> > > > can start by the latest ones and migrate a few every day until we
> > finish.
> > > > Would be good to actually try to reproduce them before migrating, so we
> > > > make sure it's still an issue, but as this will take even more time,
> > > > wouldn't make it mandatory.
> > > >
> > > >
> > > >
> > > > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>)
> > escribió:
> > > >
> > > > > Thanks Jan - I will hold off until we are ready of course.
> > > > >
> > > > > Raphael - close as in there can not be any more comments added or
> > > > > additions to the issue, not deletion. They will still exist and be
> > > > > searchable. We definitely can add a label when we close them.
> > > > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <piotrowski@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > Just a note to make sure: Please do not proceed with this before
> > issue
> > > > > > and PR templates are in place, labels are unified etc - meaning:
> > > > > > GitHub repos are ready.
> > > > > > (Working on this right now)
> > > > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
> > shazron@gmail.com>:
> > > > > > >
> > > > > > > I've done this for our JIRA:
> > > > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of
> > them)
> > > > > > > - I've changed issues with "No Component" to the relevant
> > component
> > > > > > >
> > > > > > > What's left:
> > > > > > > - We have 1881 Open, Reopened or In Progress issues
> > > > > > > - 474 were created in the last year (52 weeks)
> > > > > > > - thus 1,407 were created more than a year ago
> > > > > > > - 199 were created in the last 6 months (26 weeks)
> > > > > > >
> > > > > > > What's next:
> > > > > > > 1. I can Bulk Resolve all issues with a comment so the reporters
> > will
> > > > > > > know where to re-file, with instructions, and point them to
> > > > > > > issues.cordova.io [FAST]
> > > > > > > OR
> > > > > > > 2. I can Bulk Resolve issues by component, and point them to the
> > right
> > > > > > > GH repo to file the new issue [SLOW]
> > > > > > >
> > > > > > > Since this is a bulk operation, if we still need to keep some
> > issues
> > > > > > > open in JIRA, we need to tag with a label so I can skip those.
> > > > > > >
> > > > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
> > piotrowski@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > 1. Should we just disable those then? One other way is to
> > add in
> > > > > bold
> > > > > > > > > big letters about the deprecation in the New Issue template
> > > > > > > >
> > > > > > > > We should probably "just" define our deprecation and archival
> > policy
> > > > > > > > (see other active thread). Depending on that, we can create
> > another
> > > > > > > > INFRA issue to get taken care of that. There is no flood of
> > Github
> > > > > > > > issues for these repos right now, so no harm done.
> > > > > > > >
> > > > > > > > > 2. These links are super useful. Perhaps they should be on
> > the
> > > > > > > > > website, what do you all think? Not sure if the scripting
> > for the
> > > > > > > > > second link is server side or it could be client side as
> > well (via
> > > > > > > > > JavaScript). Perhaps on the
> > https://cordova.apache.org/contribute/
> > > > > > > > > (contribute.cordova.io) page. That massive github link
> > could also
> > > > > be
> > > > > > > > > auto-generated as well on that page, somehow. Let me know
> > how I can
> > > > > > > > > help.
> > > > > > > >
> > > > > > > > Yes, I think those could very well be on the Cordova web site
> > as
> > > > > well.
> > > > > > > > http://cordova.betamo.de/ is built with PHP, I will put its
> > source
> > > > > up
> > > > > > > > on Github later so someone can rebuild it with JS if
> > needed/wanted.
> > > > > > > > For now it is just a solution for us committers (and especially
> > > > > > > > myself).
> > > > > > > >
> > > > > > > > -J
> > > > > > > >
> > > > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > > > > Thanks Jan!
> > > > > > > > >
> > > > > > > > > 1. Should we just disable those then? One other way is to
> > add in
> > > > > bold
> > > > > > > > > big letters about the deprecation in the New Issue template
> > > > > > > > > 2. These links are super useful. Perhaps they should be on
> > the
> > > > > > > > > website, what do you all think? Not sure if the scripting
> > for the
> > > > > > > > > second link is server side or it could be client side as
> > well (via
> > > > > > > > > JavaScript). Perhaps on the
> > https://cordova.apache.org/contribute/
> > > > > > > > > (contribute.cordova.io) page. That massive github link
> > could also
> > > > > be
> > > > > > > > > auto-generated as well on that page, somehow. Let me know
> > how I can
> > > > > > > > > help.
> > > > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > > > > piotrowski@gmail.com> wrote:
> > > > > > > > >>
> > > > > > > > >> You may have noticed the first issues coming in on some
> > > > > repositories.
> > > > > > > > >>
> > > > > > > > >> 1. In hindsight enabling issues for deprecated platforms,
> > plugins
> > > > > etc
> > > > > > > > >> may not have been the smartest decision. We will have to
> > find out
> > > > > how
> > > > > > > > >> to handle this - we should probably write down a
> > "deprecation /
> > > > > > > > >> archivation policy" anyway.
> > > > > > > > >>
> > > > > > > > >> 2. Some people are missing the "all tickets in one view"
> > > > > interface. I
> > > > > > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > > > > > >> The second link on there generates a few prepared Github
> > search
> > > > > links,
> > > > > > > > >> including one that is valid for _all_ Cordova repositories:
> > > > > > > > >>
> > > > >
> > https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > > > > >> Nice, isn't it?
> > > > > > > > >> Do you have any specific requests for filters or interface
> > you
> > > > > need or
> > > > > > > > >> want? What did you use in JIRA that you couldn't find for
> > Github?
> > > > > > > > >> Shouldn't be too hard to whip something up.
> > > > > > > > >>
> > > > > > > > >> -J
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
> > piotrowski@gmail.com>:
> > > > > > > > >> > That worked, the ticket was just resolved and issues are
> > now
> > > > > enabled
> > > > > > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > > > > > >> >
> > > > > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > > > > >> >
> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > > > > >> > ...
> > > > > > > > >> >
> > > > > > > > >> > On to b), c) etc.
> > > > > > > > >> >
> > > > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
> > chris.brody@gmail.com>:
> > > > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > > > > piotrowski@gmail.com> wrote:
> > > > > > > > >> >>>
> > > > > > > > >> >>> Created INFRA issue at
> > > > > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > > > > >> >>
> > > > > > > > >> >> +100
> > > > > > > > >> >>
> > > > > > > > >> >>
> > > > > ---------------------------------------------------------------------
> > > > > > > > >> >> 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
> > > > >
> > > > >
> >
> > ---------------------------------------------------------------------
> > 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by julio cesar sanchez <jc...@gmail.com>.
Realistically, if they created an issue more than 6 months ago and nobody
looked at it in that time, they wouldn't bother to recreate. So we would
lose ~1700 issues.
I agree with Raphael, if options are bulk close and ask for migration or
keep them open, I vote for keeping them open.
If somebody creates a new issue that is already in JIRA and we notice it,
we can close the JIRA one as duplicate of the github one. (it has already
happened in at least one issue that I have noticed)
El jue., 23 ago. 2018 a las 11:42, Shazron (<sh...@gmail.com>) escribió:
> Back of the napkin calculation... if we took 5 mins (which is quite
> conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
> days of 8 hours a day full time). That's about a month of work for one
> person (not including weekends), but realistically it will be greater
> than this of course, definitely a few months. (of course the work can
> be run in parallel with more people...)
> On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
> >
> > Realistically doing it one by one will take a very long time, nor is
> > it necessary -- as a volunteer or if you were paid by your employer.
> > Some of these issues might be not relevant anymore. If it was
> > relevant, they can re-file in GH. I really don't want this to drag out
> > for another year.
> >
> > In my proposal - nothing will be moved, everything will be closed,
> > with a note to re-file in GH if relevant. There will be no "dangling"
> > issues - it's like what you've seen in some open sourced projects,
> > "Closing this stale issue. Re-open if still relevant" (but we say
> > re-file).
> > On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> > <jc...@gmail.com> wrote:
> > >
> > > I wouldn't do a bulk close neither, I think we should migrate them one
> by
> > > one to the respective github repo, even using same JIRA id so they
> still
> > > get linked, and then manually close as duplicate of the new github one.
> > >
> > > It's going to be a lot of work, but we don't need to do it right away,
> we
> > > can start by the latest ones and migrate a few every day until we
> finish.
> > > Would be good to actually try to reproduce them before migrating, so we
> > > make sure it's still an issue, but as this will take even more time,
> > > wouldn't make it mandatory.
> > >
> > >
> > >
> > > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>)
> escribió:
> > >
> > > > Thanks Jan - I will hold off until we are ready of course.
> > > >
> > > > Raphael - close as in there can not be any more comments added or
> > > > additions to the issue, not deletion. They will still exist and be
> > > > searchable. We definitely can add a label when we close them.
> > > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <piotrowski@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > Just a note to make sure: Please do not proceed with this before
> issue
> > > > > and PR templates are in place, labels are unified etc - meaning:
> > > > > GitHub repos are ready.
> > > > > (Working on this right now)
> > > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
> shazron@gmail.com>:
> > > > > >
> > > > > > I've done this for our JIRA:
> > > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of
> them)
> > > > > > - I've changed issues with "No Component" to the relevant
> component
> > > > > >
> > > > > > What's left:
> > > > > > - We have 1881 Open, Reopened or In Progress issues
> > > > > > - 474 were created in the last year (52 weeks)
> > > > > > - thus 1,407 were created more than a year ago
> > > > > > - 199 were created in the last 6 months (26 weeks)
> > > > > >
> > > > > > What's next:
> > > > > > 1. I can Bulk Resolve all issues with a comment so the reporters
> will
> > > > > > know where to re-file, with instructions, and point them to
> > > > > > issues.cordova.io [FAST]
> > > > > > OR
> > > > > > 2. I can Bulk Resolve issues by component, and point them to the
> right
> > > > > > GH repo to file the new issue [SLOW]
> > > > > >
> > > > > > Since this is a bulk operation, if we still need to keep some
> issues
> > > > > > open in JIRA, we need to tag with a label so I can skip those.
> > > > > >
> > > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
> piotrowski@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > > 1. Should we just disable those then? One other way is to
> add in
> > > > bold
> > > > > > > > big letters about the deprecation in the New Issue template
> > > > > > >
> > > > > > > We should probably "just" define our deprecation and archival
> policy
> > > > > > > (see other active thread). Depending on that, we can create
> another
> > > > > > > INFRA issue to get taken care of that. There is no flood of
> Github
> > > > > > > issues for these repos right now, so no harm done.
> > > > > > >
> > > > > > > > 2. These links are super useful. Perhaps they should be on
> the
> > > > > > > > website, what do you all think? Not sure if the scripting
> for the
> > > > > > > > second link is server side or it could be client side as
> well (via
> > > > > > > > JavaScript). Perhaps on the
> https://cordova.apache.org/contribute/
> > > > > > > > (contribute.cordova.io) page. That massive github link
> could also
> > > > be
> > > > > > > > auto-generated as well on that page, somehow. Let me know
> how I can
> > > > > > > > help.
> > > > > > >
> > > > > > > Yes, I think those could very well be on the Cordova web site
> as
> > > > well.
> > > > > > > http://cordova.betamo.de/ is built with PHP, I will put its
> source
> > > > up
> > > > > > > on Github later so someone can rebuild it with JS if
> needed/wanted.
> > > > > > > For now it is just a solution for us committers (and especially
> > > > > > > myself).
> > > > > > >
> > > > > > > -J
> > > > > > >
> > > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > > > Thanks Jan!
> > > > > > > >
> > > > > > > > 1. Should we just disable those then? One other way is to
> add in
> > > > bold
> > > > > > > > big letters about the deprecation in the New Issue template
> > > > > > > > 2. These links are super useful. Perhaps they should be on
> the
> > > > > > > > website, what do you all think? Not sure if the scripting
> for the
> > > > > > > > second link is server side or it could be client side as
> well (via
> > > > > > > > JavaScript). Perhaps on the
> https://cordova.apache.org/contribute/
> > > > > > > > (contribute.cordova.io) page. That massive github link
> could also
> > > > be
> > > > > > > > auto-generated as well on that page, somehow. Let me know
> how I can
> > > > > > > > help.
> > > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > > > piotrowski@gmail.com> wrote:
> > > > > > > >>
> > > > > > > >> You may have noticed the first issues coming in on some
> > > > repositories.
> > > > > > > >>
> > > > > > > >> 1. In hindsight enabling issues for deprecated platforms,
> plugins
> > > > etc
> > > > > > > >> may not have been the smartest decision. We will have to
> find out
> > > > how
> > > > > > > >> to handle this - we should probably write down a
> "deprecation /
> > > > > > > >> archivation policy" anyway.
> > > > > > > >>
> > > > > > > >> 2. Some people are missing the "all tickets in one view"
> > > > interface. I
> > > > > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > > > > >> The second link on there generates a few prepared Github
> search
> > > > links,
> > > > > > > >> including one that is valid for _all_ Cordova repositories:
> > > > > > > >>
> > > >
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > > > >> Nice, isn't it?
> > > > > > > >> Do you have any specific requests for filters or interface
> you
> > > > need or
> > > > > > > >> want? What did you use in JIRA that you couldn't find for
> Github?
> > > > > > > >> Shouldn't be too hard to whip something up.
> > > > > > > >>
> > > > > > > >> -J
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
> piotrowski@gmail.com>:
> > > > > > > >> > That worked, the ticket was just resolved and issues are
> now
> > > > enabled
> > > > > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > > > > >> >
> > > > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > > > >> >
> https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > > > >> > ...
> > > > > > > >> >
> > > > > > > >> > On to b), c) etc.
> > > > > > > >> >
> > > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
> chris.brody@gmail.com>:
> > > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > > > piotrowski@gmail.com> wrote:
> > > > > > > >> >>>
> > > > > > > >> >>> Created INFRA issue at
> > > > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > > > >> >>
> > > > > > > >> >> +100
> > > > > > > >> >>
> > > > > > > >> >>
> > > > ---------------------------------------------------------------------
> > > > > > > >> >> 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
> > > >
> > > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
Back of the napkin calculation... if we took 5 mins (which is quite
conservative) to migrate one by one, 1,811*5 = 9,055 minutes (or ~19
days of 8 hours a day full time). That's about a month of work for one
person (not including weekends), but realistically it will be greater
than this of course, definitely a few months. (of course the work can
be run in parallel with more people...)
On Thu, Aug 23, 2018 at 5:34 PM Shazron <sh...@gmail.com> wrote:
>
> Realistically doing it one by one will take a very long time, nor is
> it necessary -- as a volunteer or if you were paid by your employer.
> Some of these issues might be not relevant anymore. If it was
> relevant, they can re-file in GH. I really don't want this to drag out
> for another year.
>
> In my proposal - nothing will be moved, everything will be closed,
> with a note to re-file in GH if relevant. There will be no "dangling"
> issues - it's like what you've seen in some open sourced projects,
> "Closing this stale issue. Re-open if still relevant" (but we say
> re-file).
> On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> <jc...@gmail.com> wrote:
> >
> > I wouldn't do a bulk close neither, I think we should migrate them one by
> > one to the respective github repo, even using same JIRA id so they still
> > get linked, and then manually close as duplicate of the new github one.
> >
> > It's going to be a lot of work, but we don't need to do it right away, we
> > can start by the latest ones and migrate a few every day until we finish.
> > Would be good to actually try to reproduce them before migrating, so we
> > make sure it's still an issue, but as this will take even more time,
> > wouldn't make it mandatory.
> >
> >
> >
> > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>) escribió:
> >
> > > Thanks Jan - I will hold off until we are ready of course.
> > >
> > > Raphael - close as in there can not be any more comments added or
> > > additions to the issue, not deletion. They will still exist and be
> > > searchable. We definitely can add a label when we close them.
> > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com>
> > > wrote:
> > > >
> > > > Just a note to make sure: Please do not proceed with this before issue
> > > > and PR templates are in place, labels are unified etc - meaning:
> > > > GitHub repos are ready.
> > > > (Working on this right now)
> > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> > > > >
> > > > > I've done this for our JIRA:
> > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > > > > - I've changed issues with "No Component" to the relevant component
> > > > >
> > > > > What's left:
> > > > > - We have 1881 Open, Reopened or In Progress issues
> > > > > - 474 were created in the last year (52 weeks)
> > > > > - thus 1,407 were created more than a year ago
> > > > > - 199 were created in the last 6 months (26 weeks)
> > > > >
> > > > > What's next:
> > > > > 1. I can Bulk Resolve all issues with a comment so the reporters will
> > > > > know where to re-file, with instructions, and point them to
> > > > > issues.cordova.io [FAST]
> > > > > OR
> > > > > 2. I can Bulk Resolve issues by component, and point them to the right
> > > > > GH repo to file the new issue [SLOW]
> > > > >
> > > > > Since this is a bulk operation, if we still need to keep some issues
> > > > > open in JIRA, we need to tag with a label so I can skip those.
> > > > >
> > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > 1. Should we just disable those then? One other way is to add in
> > > bold
> > > > > > > big letters about the deprecation in the New Issue template
> > > > > >
> > > > > > We should probably "just" define our deprecation and archival policy
> > > > > > (see other active thread). Depending on that, we can create another
> > > > > > INFRA issue to get taken care of that. There is no flood of Github
> > > > > > issues for these repos right now, so no harm done.
> > > > > >
> > > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > > website, what do you all think? Not sure if the scripting for the
> > > > > > > second link is server side or it could be client side as well (via
> > > > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > > > (contribute.cordova.io) page. That massive github link could also
> > > be
> > > > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > > > help.
> > > > > >
> > > > > > Yes, I think those could very well be on the Cordova web site as
> > > well.
> > > > > > http://cordova.betamo.de/ is built with PHP, I will put its source
> > > up
> > > > > > on Github later so someone can rebuild it with JS if needed/wanted.
> > > > > > For now it is just a solution for us committers (and especially
> > > > > > myself).
> > > > > >
> > > > > > -J
> > > > > >
> > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > > Thanks Jan!
> > > > > > >
> > > > > > > 1. Should we just disable those then? One other way is to add in
> > > bold
> > > > > > > big letters about the deprecation in the New Issue template
> > > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > > website, what do you all think? Not sure if the scripting for the
> > > > > > > second link is server side or it could be client side as well (via
> > > > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > > > (contribute.cordova.io) page. That massive github link could also
> > > be
> > > > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > > > help.
> > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > > piotrowski@gmail.com> wrote:
> > > > > > >>
> > > > > > >> You may have noticed the first issues coming in on some
> > > repositories.
> > > > > > >>
> > > > > > >> 1. In hindsight enabling issues for deprecated platforms, plugins
> > > etc
> > > > > > >> may not have been the smartest decision. We will have to find out
> > > how
> > > > > > >> to handle this - we should probably write down a "deprecation /
> > > > > > >> archivation policy" anyway.
> > > > > > >>
> > > > > > >> 2. Some people are missing the "all tickets in one view"
> > > interface. I
> > > > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > > > >> The second link on there generates a few prepared Github search
> > > links,
> > > > > > >> including one that is valid for _all_ Cordova repositories:
> > > > > > >>
> > > https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > > >> Nice, isn't it?
> > > > > > >> Do you have any specific requests for filters or interface you
> > > need or
> > > > > > >> want? What did you use in JIRA that you couldn't find for Github?
> > > > > > >> Shouldn't be too hard to whip something up.
> > > > > > >>
> > > > > > >> -J
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > > > > >> > That worked, the ticket was just resolved and issues are now
> > > enabled
> > > > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > > > >> >
> > > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > > >> > ...
> > > > > > >> >
> > > > > > >> > On to b), c) etc.
> > > > > > >> >
> > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > > piotrowski@gmail.com> wrote:
> > > > > > >> >>>
> > > > > > >> >>> Created INFRA issue at
> > > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > > >> >>
> > > > > > >> >> +100
> > > > > > >> >>
> > > > > > >> >>
> > > ---------------------------------------------------------------------
> > > > > > >> >> 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
> > >
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
I'm against migrating everything. I would just leave them in JIRA as is and
resolve them when resolved.
Regarding the "dangling" issues: If we re-file issues in GitHub, we would
have to make sure that the corresponding issue in JIRA is properly marked
as obsolete.
In other words, I as a developer want to get a list of issues without
duplicates. Therefore there need to be two issue states in JIRA:
- "Closed with request to re-file"
- "Re-filed (obsolete)"
To make that happen, we have to rely on users to reference the original
issue when re-filing, which is unreliable.
Therefore I think it's easier to leave the remaining JIRA issues as they
are and resolve them as they are resolved.
Am Do., 23. Aug. 2018 um 11:35 Uhr schrieb Shazron <sh...@gmail.com>:
> Realistically doing it one by one will take a very long time, nor is
> it necessary -- as a volunteer or if you were paid by your employer.
> Some of these issues might be not relevant anymore. If it was
> relevant, they can re-file in GH. I really don't want this to drag out
> for another year.
>
> In my proposal - nothing will be moved, everything will be closed,
> with a note to re-file in GH if relevant. There will be no "dangling"
> issues - it's like what you've seen in some open sourced projects,
> "Closing this stale issue. Re-open if still relevant" (but we say
> re-file).
> On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
> <jc...@gmail.com> wrote:
> >
> > I wouldn't do a bulk close neither, I think we should migrate them one by
> > one to the respective github repo, even using same JIRA id so they still
> > get linked, and then manually close as duplicate of the new github one.
> >
> > It's going to be a lot of work, but we don't need to do it right away, we
> > can start by the latest ones and migrate a few every day until we finish.
> > Would be good to actually try to reproduce them before migrating, so we
> > make sure it's still an issue, but as this will take even more time,
> > wouldn't make it mandatory.
> >
> >
> >
> > El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>)
> escribió:
> >
> > > Thanks Jan - I will hold off until we are ready of course.
> > >
> > > Raphael - close as in there can not be any more comments added or
> > > additions to the issue, not deletion. They will still exist and be
> > > searchable. We definitely can add a label when we close them.
> > > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com>
> > > wrote:
> > > >
> > > > Just a note to make sure: Please do not proceed with this before
> issue
> > > > and PR templates are in place, labels are unified etc - meaning:
> > > > GitHub repos are ready.
> > > > (Working on this right now)
> > > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <
> shazron@gmail.com>:
> > > > >
> > > > > I've done this for our JIRA:
> > > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > > > > - I've changed issues with "No Component" to the relevant component
> > > > >
> > > > > What's left:
> > > > > - We have 1881 Open, Reopened or In Progress issues
> > > > > - 474 were created in the last year (52 weeks)
> > > > > - thus 1,407 were created more than a year ago
> > > > > - 199 were created in the last 6 months (26 weeks)
> > > > >
> > > > > What's next:
> > > > > 1. I can Bulk Resolve all issues with a comment so the reporters
> will
> > > > > know where to re-file, with instructions, and point them to
> > > > > issues.cordova.io [FAST]
> > > > > OR
> > > > > 2. I can Bulk Resolve issues by component, and point them to the
> right
> > > > > GH repo to file the new issue [SLOW]
> > > > >
> > > > > Since this is a bulk operation, if we still need to keep some
> issues
> > > > > open in JIRA, we need to tag with a label so I can skip those.
> > > > >
> > > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <
> piotrowski@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > 1. Should we just disable those then? One other way is to add
> in
> > > bold
> > > > > > > big letters about the deprecation in the New Issue template
> > > > > >
> > > > > > We should probably "just" define our deprecation and archival
> policy
> > > > > > (see other active thread). Depending on that, we can create
> another
> > > > > > INFRA issue to get taken care of that. There is no flood of
> Github
> > > > > > issues for these repos right now, so no harm done.
> > > > > >
> > > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > > website, what do you all think? Not sure if the scripting for
> the
> > > > > > > second link is server side or it could be client side as well
> (via
> > > > > > > JavaScript). Perhaps on the
> https://cordova.apache.org/contribute/
> > > > > > > (contribute.cordova.io) page. That massive github link could
> also
> > > be
> > > > > > > auto-generated as well on that page, somehow. Let me know how
> I can
> > > > > > > help.
> > > > > >
> > > > > > Yes, I think those could very well be on the Cordova web site as
> > > well.
> > > > > > http://cordova.betamo.de/ is built with PHP, I will put its
> source
> > > up
> > > > > > on Github later so someone can rebuild it with JS if
> needed/wanted.
> > > > > > For now it is just a solution for us committers (and especially
> > > > > > myself).
> > > > > >
> > > > > > -J
> > > > > >
> > > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > > Thanks Jan!
> > > > > > >
> > > > > > > 1. Should we just disable those then? One other way is to add
> in
> > > bold
> > > > > > > big letters about the deprecation in the New Issue template
> > > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > > website, what do you all think? Not sure if the scripting for
> the
> > > > > > > second link is server side or it could be client side as well
> (via
> > > > > > > JavaScript). Perhaps on the
> https://cordova.apache.org/contribute/
> > > > > > > (contribute.cordova.io) page. That massive github link could
> also
> > > be
> > > > > > > auto-generated as well on that page, somehow. Let me know how
> I can
> > > > > > > help.
> > > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > > piotrowski@gmail.com> wrote:
> > > > > > >>
> > > > > > >> You may have noticed the first issues coming in on some
> > > repositories.
> > > > > > >>
> > > > > > >> 1. In hindsight enabling issues for deprecated platforms,
> plugins
> > > etc
> > > > > > >> may not have been the smartest decision. We will have to find
> out
> > > how
> > > > > > >> to handle this - we should probably write down a "deprecation
> /
> > > > > > >> archivation policy" anyway.
> > > > > > >>
> > > > > > >> 2. Some people are missing the "all tickets in one view"
> > > interface. I
> > > > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > > > >> The second link on there generates a few prepared Github
> search
> > > links,
> > > > > > >> including one that is valid for _all_ Cordova repositories:
> > > > > > >>
> > >
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > > >> Nice, isn't it?
> > > > > > >> Do you have any specific requests for filters or interface you
> > > need or
> > > > > > >> want? What did you use in JIRA that you couldn't find for
> Github?
> > > > > > >> Shouldn't be too hard to whip something up.
> > > > > > >>
> > > > > > >> -J
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <
> piotrowski@gmail.com>:
> > > > > > >> > That worked, the ticket was just resolved and issues are now
> > > enabled
> > > > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > > > >> >
> > > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > > >> >
> https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > > >> > ...
> > > > > > >> >
> > > > > > >> > On to b), c) etc.
> > > > > > >> >
> > > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <
> chris.brody@gmail.com>:
> > > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > > piotrowski@gmail.com> wrote:
> > > > > > >> >>>
> > > > > > >> >>> Created INFRA issue at
> > > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > > >> >>
> > > > > > >> >> +100
> > > > > > >> >>
> > > > > > >> >>
> > > ---------------------------------------------------------------------
> > > > > > >> >> 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
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
Realistically doing it one by one will take a very long time, nor is
it necessary -- as a volunteer or if you were paid by your employer.
Some of these issues might be not relevant anymore. If it was
relevant, they can re-file in GH. I really don't want this to drag out
for another year.
In my proposal - nothing will be moved, everything will be closed,
with a note to re-file in GH if relevant. There will be no "dangling"
issues - it's like what you've seen in some open sourced projects,
"Closing this stale issue. Re-open if still relevant" (but we say
re-file).
On Thu, Aug 23, 2018 at 5:19 PM julio cesar sanchez
<jc...@gmail.com> wrote:
>
> I wouldn't do a bulk close neither, I think we should migrate them one by
> one to the respective github repo, even using same JIRA id so they still
> get linked, and then manually close as duplicate of the new github one.
>
> It's going to be a lot of work, but we don't need to do it right away, we
> can start by the latest ones and migrate a few every day until we finish.
> Would be good to actually try to reproduce them before migrating, so we
> make sure it's still an issue, but as this will take even more time,
> wouldn't make it mandatory.
>
>
>
> El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>) escribió:
>
> > Thanks Jan - I will hold off until we are ready of course.
> >
> > Raphael - close as in there can not be any more comments added or
> > additions to the issue, not deletion. They will still exist and be
> > searchable. We definitely can add a label when we close them.
> > On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com>
> > wrote:
> > >
> > > Just a note to make sure: Please do not proceed with this before issue
> > > and PR templates are in place, labels are unified etc - meaning:
> > > GitHub repos are ready.
> > > (Working on this right now)
> > > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> > > >
> > > > I've done this for our JIRA:
> > > > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > > > - I've changed issues with "No Component" to the relevant component
> > > >
> > > > What's left:
> > > > - We have 1881 Open, Reopened or In Progress issues
> > > > - 474 were created in the last year (52 weeks)
> > > > - thus 1,407 were created more than a year ago
> > > > - 199 were created in the last 6 months (26 weeks)
> > > >
> > > > What's next:
> > > > 1. I can Bulk Resolve all issues with a comment so the reporters will
> > > > know where to re-file, with instructions, and point them to
> > > > issues.cordova.io [FAST]
> > > > OR
> > > > 2. I can Bulk Resolve issues by component, and point them to the right
> > > > GH repo to file the new issue [SLOW]
> > > >
> > > > Since this is a bulk operation, if we still need to keep some issues
> > > > open in JIRA, we need to tag with a label so I can skip those.
> > > >
> > > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com>
> > wrote:
> > > > >
> > > > > > 1. Should we just disable those then? One other way is to add in
> > bold
> > > > > > big letters about the deprecation in the New Issue template
> > > > >
> > > > > We should probably "just" define our deprecation and archival policy
> > > > > (see other active thread). Depending on that, we can create another
> > > > > INFRA issue to get taken care of that. There is no flood of Github
> > > > > issues for these repos right now, so no harm done.
> > > > >
> > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > website, what do you all think? Not sure if the scripting for the
> > > > > > second link is server side or it could be client side as well (via
> > > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > > (contribute.cordova.io) page. That massive github link could also
> > be
> > > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > > help.
> > > > >
> > > > > Yes, I think those could very well be on the Cordova web site as
> > well.
> > > > > http://cordova.betamo.de/ is built with PHP, I will put its source
> > up
> > > > > on Github later so someone can rebuild it with JS if needed/wanted.
> > > > > For now it is just a solution for us committers (and especially
> > > > > myself).
> > > > >
> > > > > -J
> > > > >
> > > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > > Thanks Jan!
> > > > > >
> > > > > > 1. Should we just disable those then? One other way is to add in
> > bold
> > > > > > big letters about the deprecation in the New Issue template
> > > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > > website, what do you all think? Not sure if the scripting for the
> > > > > > second link is server side or it could be client side as well (via
> > > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > > (contribute.cordova.io) page. That massive github link could also
> > be
> > > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > > help.
> > > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> > piotrowski@gmail.com> wrote:
> > > > > >>
> > > > > >> You may have noticed the first issues coming in on some
> > repositories.
> > > > > >>
> > > > > >> 1. In hindsight enabling issues for deprecated platforms, plugins
> > etc
> > > > > >> may not have been the smartest decision. We will have to find out
> > how
> > > > > >> to handle this - we should probably write down a "deprecation /
> > > > > >> archivation policy" anyway.
> > > > > >>
> > > > > >> 2. Some people are missing the "all tickets in one view"
> > interface. I
> > > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > > >> The second link on there generates a few prepared Github search
> > links,
> > > > > >> including one that is valid for _all_ Cordova repositories:
> > > > > >>
> > https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > > >> Nice, isn't it?
> > > > > >> Do you have any specific requests for filters or interface you
> > need or
> > > > > >> want? What did you use in JIRA that you couldn't find for Github?
> > > > > >> Shouldn't be too hard to whip something up.
> > > > > >>
> > > > > >> -J
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > > > >> > That worked, the ticket was just resolved and issues are now
> > enabled
> > > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > > >> >
> > > > > >> > https://github.com/apache/cordova-android/issues
> > > > > >> > https://github.com/apache/cordova-ios/issues
> > > > > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > > >> > ...
> > > > > >> >
> > > > > >> > On to b), c) etc.
> > > > > >> >
> > > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> > piotrowski@gmail.com> wrote:
> > > > > >> >>>
> > > > > >> >>> Created INFRA issue at
> > https://issues.apache.org/jira/browse/INFRA-16876
> > > > > >> >>
> > > > > >> >> +100
> > > > > >> >>
> > > > > >> >>
> > ---------------------------------------------------------------------
> > > > > >> >> 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
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by julio cesar sanchez <jc...@gmail.com>.
I wouldn't do a bulk close neither, I think we should migrate them one by
one to the respective github repo, even using same JIRA id so they still
get linked, and then manually close as duplicate of the new github one.
It's going to be a lot of work, but we don't need to do it right away, we
can start by the latest ones and migrate a few every day until we finish.
Would be good to actually try to reproduce them before migrating, so we
make sure it's still an issue, but as this will take even more time,
wouldn't make it mandatory.
El jue., 23 ago. 2018 a las 11:06, Shazron (<sh...@gmail.com>) escribió:
> Thanks Jan - I will hold off until we are ready of course.
>
> Raphael - close as in there can not be any more comments added or
> additions to the issue, not deletion. They will still exist and be
> searchable. We definitely can add a label when we close them.
> On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> >
> > Just a note to make sure: Please do not proceed with this before issue
> > and PR templates are in place, labels are unified etc - meaning:
> > GitHub repos are ready.
> > (Working on this right now)
> > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> > >
> > > I've done this for our JIRA:
> > > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > > - I've changed issues with "No Component" to the relevant component
> > >
> > > What's left:
> > > - We have 1881 Open, Reopened or In Progress issues
> > > - 474 were created in the last year (52 weeks)
> > > - thus 1,407 were created more than a year ago
> > > - 199 were created in the last 6 months (26 weeks)
> > >
> > > What's next:
> > > 1. I can Bulk Resolve all issues with a comment so the reporters will
> > > know where to re-file, with instructions, and point them to
> > > issues.cordova.io [FAST]
> > > OR
> > > 2. I can Bulk Resolve issues by component, and point them to the right
> > > GH repo to file the new issue [SLOW]
> > >
> > > Since this is a bulk operation, if we still need to keep some issues
> > > open in JIRA, we need to tag with a label so I can skip those.
> > >
> > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> > > >
> > > > > 1. Should we just disable those then? One other way is to add in
> bold
> > > > > big letters about the deprecation in the New Issue template
> > > >
> > > > We should probably "just" define our deprecation and archival policy
> > > > (see other active thread). Depending on that, we can create another
> > > > INFRA issue to get taken care of that. There is no flood of Github
> > > > issues for these repos right now, so no harm done.
> > > >
> > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > website, what do you all think? Not sure if the scripting for the
> > > > > second link is server side or it could be client side as well (via
> > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > (contribute.cordova.io) page. That massive github link could also
> be
> > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > help.
> > > >
> > > > Yes, I think those could very well be on the Cordova web site as
> well.
> > > > http://cordova.betamo.de/ is built with PHP, I will put its source
> up
> > > > on Github later so someone can rebuild it with JS if needed/wanted.
> > > > For now it is just a solution for us committers (and especially
> > > > myself).
> > > >
> > > > -J
> > > >
> > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > Thanks Jan!
> > > > >
> > > > > 1. Should we just disable those then? One other way is to add in
> bold
> > > > > big letters about the deprecation in the New Issue template
> > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > website, what do you all think? Not sure if the scripting for the
> > > > > second link is server side or it could be client side as well (via
> > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > (contribute.cordova.io) page. That massive github link could also
> be
> > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > help.
> > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> > > > >>
> > > > >> You may have noticed the first issues coming in on some
> repositories.
> > > > >>
> > > > >> 1. In hindsight enabling issues for deprecated platforms, plugins
> etc
> > > > >> may not have been the smartest decision. We will have to find out
> how
> > > > >> to handle this - we should probably write down a "deprecation /
> > > > >> archivation policy" anyway.
> > > > >>
> > > > >> 2. Some people are missing the "all tickets in one view"
> interface. I
> > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > >> The second link on there generates a few prepared Github search
> links,
> > > > >> including one that is valid for _all_ Cordova repositories:
> > > > >>
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > >> Nice, isn't it?
> > > > >> Do you have any specific requests for filters or interface you
> need or
> > > > >> want? What did you use in JIRA that you couldn't find for Github?
> > > > >> Shouldn't be too hard to whip something up.
> > > > >>
> > > > >> -J
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > > >> > That worked, the ticket was just resolved and issues are now
> enabled
> > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > >> >
> > > > >> > https://github.com/apache/cordova-android/issues
> > > > >> > https://github.com/apache/cordova-ios/issues
> > > > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > >> > ...
> > > > >> >
> > > > >> > On to b), c) etc.
> > > > >> >
> > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> > > > >> >>>
> > > > >> >>> Created INFRA issue at
> https://issues.apache.org/jira/browse/INFRA-16876
> > > > >> >>
> > > > >> >> +100
> > > > >> >>
> > > > >> >>
> ---------------------------------------------------------------------
> > > > >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
I thought JIRA was locked anyway. So only PMC Members can make changes.
If we just leave them as is, I can simply resolve an issue I fix in JIRA
and all is obvious.
If we ask people to reopen in GitHub, we will have a dangling seemingly
unresolved duplicate in JIRA,
so JIRA becomes less useful with every moved issue.
I'm not completely against bulk closing, I just don't see the clear
benefits.
Am Do., 23. Aug. 2018 um 11:06 Uhr schrieb Shazron <sh...@gmail.com>:
> Thanks Jan - I will hold off until we are ready of course.
>
> Raphael - close as in there can not be any more comments added or
> additions to the issue, not deletion. They will still exist and be
> searchable. We definitely can add a label when we close them.
> On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> >
> > Just a note to make sure: Please do not proceed with this before issue
> > and PR templates are in place, labels are unified etc - meaning:
> > GitHub repos are ready.
> > (Working on this right now)
> > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> > >
> > > I've done this for our JIRA:
> > > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > > - I've changed issues with "No Component" to the relevant component
> > >
> > > What's left:
> > > - We have 1881 Open, Reopened or In Progress issues
> > > - 474 were created in the last year (52 weeks)
> > > - thus 1,407 were created more than a year ago
> > > - 199 were created in the last 6 months (26 weeks)
> > >
> > > What's next:
> > > 1. I can Bulk Resolve all issues with a comment so the reporters will
> > > know where to re-file, with instructions, and point them to
> > > issues.cordova.io [FAST]
> > > OR
> > > 2. I can Bulk Resolve issues by component, and point them to the right
> > > GH repo to file the new issue [SLOW]
> > >
> > > Since this is a bulk operation, if we still need to keep some issues
> > > open in JIRA, we need to tag with a label so I can skip those.
> > >
> > > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> > > >
> > > > > 1. Should we just disable those then? One other way is to add in
> bold
> > > > > big letters about the deprecation in the New Issue template
> > > >
> > > > We should probably "just" define our deprecation and archival policy
> > > > (see other active thread). Depending on that, we can create another
> > > > INFRA issue to get taken care of that. There is no flood of Github
> > > > issues for these repos right now, so no harm done.
> > > >
> > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > website, what do you all think? Not sure if the scripting for the
> > > > > second link is server side or it could be client side as well (via
> > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > (contribute.cordova.io) page. That massive github link could also
> be
> > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > help.
> > > >
> > > > Yes, I think those could very well be on the Cordova web site as
> well.
> > > > http://cordova.betamo.de/ is built with PHP, I will put its source
> up
> > > > on Github later so someone can rebuild it with JS if needed/wanted.
> > > > For now it is just a solution for us committers (and especially
> > > > myself).
> > > >
> > > > -J
> > > >
> > > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > > Thanks Jan!
> > > > >
> > > > > 1. Should we just disable those then? One other way is to add in
> bold
> > > > > big letters about the deprecation in the New Issue template
> > > > > 2. These links are super useful. Perhaps they should be on the
> > > > > website, what do you all think? Not sure if the scripting for the
> > > > > second link is server side or it could be client side as well (via
> > > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > > (contribute.cordova.io) page. That massive github link could also
> be
> > > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > > help.
> > > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> > > > >>
> > > > >> You may have noticed the first issues coming in on some
> repositories.
> > > > >>
> > > > >> 1. In hindsight enabling issues for deprecated platforms, plugins
> etc
> > > > >> may not have been the smartest decision. We will have to find out
> how
> > > > >> to handle this - we should probably write down a "deprecation /
> > > > >> archivation policy" anyway.
> > > > >>
> > > > >> 2. Some people are missing the "all tickets in one view"
> interface. I
> > > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > > >> The second link on there generates a few prepared Github search
> links,
> > > > >> including one that is valid for _all_ Cordova repositories:
> > > > >>
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > > >> Nice, isn't it?
> > > > >> Do you have any specific requests for filters or interface you
> need or
> > > > >> want? What did you use in JIRA that you couldn't find for Github?
> > > > >> Shouldn't be too hard to whip something up.
> > > > >>
> > > > >> -J
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > > >> > That worked, the ticket was just resolved and issues are now
> enabled
> > > > >> > for all repos (beside cordova-weinre which is archived):
> > > > >> >
> > > > >> > https://github.com/apache/cordova-android/issues
> > > > >> > https://github.com/apache/cordova-ios/issues
> > > > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > > >> > ...
> > > > >> >
> > > > >> > On to b), c) etc.
> > > > >> >
> > > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> > > > >> >>>
> > > > >> >>> Created INFRA issue at
> https://issues.apache.org/jira/browse/INFRA-16876
> > > > >> >>
> > > > >> >> +100
> > > > >> >>
> > > > >> >>
> ---------------------------------------------------------------------
> > > > >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
Thanks Jan - I will hold off until we are ready of course.
Raphael - close as in there can not be any more comments added or
additions to the issue, not deletion. They will still exist and be
searchable. We definitely can add a label when we close them.
On Thu, Aug 23, 2018 at 5:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
>
> Just a note to make sure: Please do not proceed with this before issue
> and PR templates are in place, labels are unified etc - meaning:
> GitHub repos are ready.
> (Working on this right now)
> Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> >
> > I've done this for our JIRA:
> > - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> > - I've changed issues with "No Component" to the relevant component
> >
> > What's left:
> > - We have 1881 Open, Reopened or In Progress issues
> > - 474 were created in the last year (52 weeks)
> > - thus 1,407 were created more than a year ago
> > - 199 were created in the last 6 months (26 weeks)
> >
> > What's next:
> > 1. I can Bulk Resolve all issues with a comment so the reporters will
> > know where to re-file, with instructions, and point them to
> > issues.cordova.io [FAST]
> > OR
> > 2. I can Bulk Resolve issues by component, and point them to the right
> > GH repo to file the new issue [SLOW]
> >
> > Since this is a bulk operation, if we still need to keep some issues
> > open in JIRA, we need to tag with a label so I can skip those.
> >
> > On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com> wrote:
> > >
> > > > 1. Should we just disable those then? One other way is to add in bold
> > > > big letters about the deprecation in the New Issue template
> > >
> > > We should probably "just" define our deprecation and archival policy
> > > (see other active thread). Depending on that, we can create another
> > > INFRA issue to get taken care of that. There is no flood of Github
> > > issues for these repos right now, so no harm done.
> > >
> > > > 2. These links are super useful. Perhaps they should be on the
> > > > website, what do you all think? Not sure if the scripting for the
> > > > second link is server side or it could be client side as well (via
> > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > (contribute.cordova.io) page. That massive github link could also be
> > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > help.
> > >
> > > Yes, I think those could very well be on the Cordova web site as well.
> > > http://cordova.betamo.de/ is built with PHP, I will put its source up
> > > on Github later so someone can rebuild it with JS if needed/wanted.
> > > For now it is just a solution for us committers (and especially
> > > myself).
> > >
> > > -J
> > >
> > > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > > Thanks Jan!
> > > >
> > > > 1. Should we just disable those then? One other way is to add in bold
> > > > big letters about the deprecation in the New Issue template
> > > > 2. These links are super useful. Perhaps they should be on the
> > > > website, what do you all think? Not sure if the scripting for the
> > > > second link is server side or it could be client side as well (via
> > > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > > (contribute.cordova.io) page. That massive github link could also be
> > > > auto-generated as well on that page, somehow. Let me know how I can
> > > > help.
> > > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
> > > >>
> > > >> You may have noticed the first issues coming in on some repositories.
> > > >>
> > > >> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> > > >> may not have been the smartest decision. We will have to find out how
> > > >> to handle this - we should probably write down a "deprecation /
> > > >> archivation policy" anyway.
> > > >>
> > > >> 2. Some people are missing the "all tickets in one view" interface. I
> > > >> quickly built http://cordova.betamo.de/ as a workaround.
> > > >> The second link on there generates a few prepared Github search links,
> > > >> including one that is valid for _all_ Cordova repositories:
> > > >> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > > >> Nice, isn't it?
> > > >> Do you have any specific requests for filters or interface you need or
> > > >> want? What did you use in JIRA that you couldn't find for Github?
> > > >> Shouldn't be too hard to whip something up.
> > > >>
> > > >> -J
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > > >> > That worked, the ticket was just resolved and issues are now enabled
> > > >> > for all repos (beside cordova-weinre which is archived):
> > > >> >
> > > >> > https://github.com/apache/cordova-android/issues
> > > >> > https://github.com/apache/cordova-ios/issues
> > > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > > >> > ...
> > > >> >
> > > >> > On to b), c) etc.
> > > >> >
> > > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> > > >> >>>
> > > >> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> > > >> >>
> > > >> >> +100
> > > >> >>
> > > >> >> ---------------------------------------------------------------------
> > > >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
Just a note to make sure: Please do not proceed with this before issue
and PR templates are in place, labels are unified etc - meaning:
GitHub repos are ready.
(Working on this right now)
Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
>
> I've done this for our JIRA:
> - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> - I've changed issues with "No Component" to the relevant component
>
> What's left:
> - We have 1881 Open, Reopened or In Progress issues
> - 474 were created in the last year (52 weeks)
> - thus 1,407 were created more than a year ago
> - 199 were created in the last 6 months (26 weeks)
>
> What's next:
> 1. I can Bulk Resolve all issues with a comment so the reporters will
> know where to re-file, with instructions, and point them to
> issues.cordova.io [FAST]
> OR
> 2. I can Bulk Resolve issues by component, and point them to the right
> GH repo to file the new issue [SLOW]
>
> Since this is a bulk operation, if we still need to keep some issues
> open in JIRA, we need to tag with a label so I can skip those.
>
> On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com> wrote:
> >
> > > 1. Should we just disable those then? One other way is to add in bold
> > > big letters about the deprecation in the New Issue template
> >
> > We should probably "just" define our deprecation and archival policy
> > (see other active thread). Depending on that, we can create another
> > INFRA issue to get taken care of that. There is no flood of Github
> > issues for these repos right now, so no harm done.
> >
> > > 2. These links are super useful. Perhaps they should be on the
> > > website, what do you all think? Not sure if the scripting for the
> > > second link is server side or it could be client side as well (via
> > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > (contribute.cordova.io) page. That massive github link could also be
> > > auto-generated as well on that page, somehow. Let me know how I can
> > > help.
> >
> > Yes, I think those could very well be on the Cordova web site as well.
> > http://cordova.betamo.de/ is built with PHP, I will put its source up
> > on Github later so someone can rebuild it with JS if needed/wanted.
> > For now it is just a solution for us committers (and especially
> > myself).
> >
> > -J
> >
> > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > Thanks Jan!
> > >
> > > 1. Should we just disable those then? One other way is to add in bold
> > > big letters about the deprecation in the New Issue template
> > > 2. These links are super useful. Perhaps they should be on the
> > > website, what do you all think? Not sure if the scripting for the
> > > second link is server side or it could be client side as well (via
> > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > (contribute.cordova.io) page. That massive github link could also be
> > > auto-generated as well on that page, somehow. Let me know how I can
> > > help.
> > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
> > >>
> > >> You may have noticed the first issues coming in on some repositories.
> > >>
> > >> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> > >> may not have been the smartest decision. We will have to find out how
> > >> to handle this - we should probably write down a "deprecation /
> > >> archivation policy" anyway.
> > >>
> > >> 2. Some people are missing the "all tickets in one view" interface. I
> > >> quickly built http://cordova.betamo.de/ as a workaround.
> > >> The second link on there generates a few prepared Github search links,
> > >> including one that is valid for _all_ Cordova repositories:
> > >> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > >> Nice, isn't it?
> > >> Do you have any specific requests for filters or interface you need or
> > >> want? What did you use in JIRA that you couldn't find for Github?
> > >> Shouldn't be too hard to whip something up.
> > >>
> > >> -J
> > >>
> > >>
> > >>
> > >>
> > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > >> > That worked, the ticket was just resolved and issues are now enabled
> > >> > for all repos (beside cordova-weinre which is archived):
> > >> >
> > >> > https://github.com/apache/cordova-android/issues
> > >> > https://github.com/apache/cordova-ios/issues
> > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > >> > ...
> > >> >
> > >> > On to b), c) etc.
> > >> >
> > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> > >> >>>
> > >> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> > >> >>
> > >> >> +100
> > >> >>
> > >> >> ---------------------------------------------------------------------
> > >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
Thanks for doing this!
I'm not sure about the bulk closing. Last time I checked, at least for our
tooling even very old issues were often still valid and provided some
valuable insight for me. I'd leave them.
If we want to close them, They should definitely get some label that makes
them easily distinguishable from actually resolved issues.
Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron <sh...@gmail.com>:
> I've done this for our JIRA:
> - I've changed "Resolved" issues to "Closed" (about 8000+ of them)
> - I've changed issues with "No Component" to the relevant component
>
> What's left:
> - We have 1881 Open, Reopened or In Progress issues
> - 474 were created in the last year (52 weeks)
> - thus 1,407 were created more than a year ago
> - 199 were created in the last 6 months (26 weeks)
>
> What's next:
> 1. I can Bulk Resolve all issues with a comment so the reporters will
> know where to re-file, with instructions, and point them to
> issues.cordova.io [FAST]
> OR
> 2. I can Bulk Resolve issues by component, and point them to the right
> GH repo to file the new issue [SLOW]
>
> Since this is a bulk operation, if we still need to keep some issues
> open in JIRA, we need to tag with a label so I can skip those.
>
> On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> >
> > > 1. Should we just disable those then? One other way is to add in bold
> > > big letters about the deprecation in the New Issue template
> >
> > We should probably "just" define our deprecation and archival policy
> > (see other active thread). Depending on that, we can create another
> > INFRA issue to get taken care of that. There is no flood of Github
> > issues for these repos right now, so no harm done.
> >
> > > 2. These links are super useful. Perhaps they should be on the
> > > website, what do you all think? Not sure if the scripting for the
> > > second link is server side or it could be client side as well (via
> > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > (contribute.cordova.io) page. That massive github link could also be
> > > auto-generated as well on that page, somehow. Let me know how I can
> > > help.
> >
> > Yes, I think those could very well be on the Cordova web site as well.
> > http://cordova.betamo.de/ is built with PHP, I will put its source up
> > on Github later so someone can rebuild it with JS if needed/wanted.
> > For now it is just a solution for us committers (and especially
> > myself).
> >
> > -J
> >
> > 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > > Thanks Jan!
> > >
> > > 1. Should we just disable those then? One other way is to add in bold
> > > big letters about the deprecation in the New Issue template
> > > 2. These links are super useful. Perhaps they should be on the
> > > website, what do you all think? Not sure if the scripting for the
> > > second link is server side or it could be client side as well (via
> > > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > > (contribute.cordova.io) page. That massive github link could also be
> > > auto-generated as well on that page, somehow. Let me know how I can
> > > help.
> > > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> > >>
> > >> You may have noticed the first issues coming in on some repositories.
> > >>
> > >> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> > >> may not have been the smartest decision. We will have to find out how
> > >> to handle this - we should probably write down a "deprecation /
> > >> archivation policy" anyway.
> > >>
> > >> 2. Some people are missing the "all tickets in one view" interface. I
> > >> quickly built http://cordova.betamo.de/ as a workaround.
> > >> The second link on there generates a few prepared Github search links,
> > >> including one that is valid for _all_ Cordova repositories:
> > >>
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> > >> Nice, isn't it?
> > >> Do you have any specific requests for filters or interface you need or
> > >> want? What did you use in JIRA that you couldn't find for Github?
> > >> Shouldn't be too hard to whip something up.
> > >>
> > >> -J
> > >>
> > >>
> > >>
> > >>
> > >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > >> > That worked, the ticket was just resolved and issues are now enabled
> > >> > for all repos (beside cordova-weinre which is archived):
> > >> >
> > >> > https://github.com/apache/cordova-android/issues
> > >> > https://github.com/apache/cordova-ios/issues
> > >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > >> > ...
> > >> >
> > >> > On to b), c) etc.
> > >> >
> > >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> > >> >>>
> > >> >>> Created INFRA issue at
> https://issues.apache.org/jira/browse/INFRA-16876
> > >> >>
> > >> >> +100
> > >> >>
> > >> >>
> ---------------------------------------------------------------------
> > >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
I've done this for our JIRA:
- I've changed "Resolved" issues to "Closed" (about 8000+ of them)
- I've changed issues with "No Component" to the relevant component
What's left:
- We have 1881 Open, Reopened or In Progress issues
- 474 were created in the last year (52 weeks)
- thus 1,407 were created more than a year ago
- 199 were created in the last 6 months (26 weeks)
What's next:
1. I can Bulk Resolve all issues with a comment so the reporters will
know where to re-file, with instructions, and point them to
issues.cordova.io [FAST]
OR
2. I can Bulk Resolve issues by component, and point them to the right
GH repo to file the new issue [SLOW]
Since this is a bulk operation, if we still need to keep some issues
open in JIRA, we need to tag with a label so I can skip those.
On Wed, Aug 8, 2018 at 4:36 PM Jan Piotrowski <pi...@gmail.com> wrote:
>
> > 1. Should we just disable those then? One other way is to add in bold
> > big letters about the deprecation in the New Issue template
>
> We should probably "just" define our deprecation and archival policy
> (see other active thread). Depending on that, we can create another
> INFRA issue to get taken care of that. There is no flood of Github
> issues for these repos right now, so no harm done.
>
> > 2. These links are super useful. Perhaps they should be on the
> > website, what do you all think? Not sure if the scripting for the
> > second link is server side or it could be client side as well (via
> > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > (contribute.cordova.io) page. That massive github link could also be
> > auto-generated as well on that page, somehow. Let me know how I can
> > help.
>
> Yes, I think those could very well be on the Cordova web site as well.
> http://cordova.betamo.de/ is built with PHP, I will put its source up
> on Github later so someone can rebuild it with JS if needed/wanted.
> For now it is just a solution for us committers (and especially
> myself).
>
> -J
>
> 2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> > Thanks Jan!
> >
> > 1. Should we just disable those then? One other way is to add in bold
> > big letters about the deprecation in the New Issue template
> > 2. These links are super useful. Perhaps they should be on the
> > website, what do you all think? Not sure if the scripting for the
> > second link is server side or it could be client side as well (via
> > JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> > (contribute.cordova.io) page. That massive github link could also be
> > auto-generated as well on that page, somehow. Let me know how I can
> > help.
> > On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
> >>
> >> You may have noticed the first issues coming in on some repositories.
> >>
> >> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> >> may not have been the smartest decision. We will have to find out how
> >> to handle this - we should probably write down a "deprecation /
> >> archivation policy" anyway.
> >>
> >> 2. Some people are missing the "all tickets in one view" interface. I
> >> quickly built http://cordova.betamo.de/ as a workaround.
> >> The second link on there generates a few prepared Github search links,
> >> including one that is valid for _all_ Cordova repositories:
> >> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> >> Nice, isn't it?
> >> Do you have any specific requests for filters or interface you need or
> >> want? What did you use in JIRA that you couldn't find for Github?
> >> Shouldn't be too hard to whip something up.
> >>
> >> -J
> >>
> >>
> >>
> >>
> >> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> >> > That worked, the ticket was just resolved and issues are now enabled
> >> > for all repos (beside cordova-weinre which is archived):
> >> >
> >> > https://github.com/apache/cordova-android/issues
> >> > https://github.com/apache/cordova-ios/issues
> >> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> >> > ...
> >> >
> >> > On to b), c) etc.
> >> >
> >> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> >> >>>
> >> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> >> >>
> >> >> +100
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
> 1. Should we just disable those then? One other way is to add in bold
> big letters about the deprecation in the New Issue template
We should probably "just" define our deprecation and archival policy
(see other active thread). Depending on that, we can create another
INFRA issue to get taken care of that. There is no flood of Github
issues for these repos right now, so no harm done.
> 2. These links are super useful. Perhaps they should be on the
> website, what do you all think? Not sure if the scripting for the
> second link is server side or it could be client side as well (via
> JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> (contribute.cordova.io) page. That massive github link could also be
> auto-generated as well on that page, somehow. Let me know how I can
> help.
Yes, I think those could very well be on the Cordova web site as well.
http://cordova.betamo.de/ is built with PHP, I will put its source up
on Github later so someone can rebuild it with JS if needed/wanted.
For now it is just a solution for us committers (and especially
myself).
-J
2018-08-08 5:34 GMT+02:00 Shazron <sh...@gmail.com>:
> Thanks Jan!
>
> 1. Should we just disable those then? One other way is to add in bold
> big letters about the deprecation in the New Issue template
> 2. These links are super useful. Perhaps they should be on the
> website, what do you all think? Not sure if the scripting for the
> second link is server side or it could be client side as well (via
> JavaScript). Perhaps on the https://cordova.apache.org/contribute/
> (contribute.cordova.io) page. That massive github link could also be
> auto-generated as well on that page, somehow. Let me know how I can
> help.
> On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
>>
>> You may have noticed the first issues coming in on some repositories.
>>
>> 1. In hindsight enabling issues for deprecated platforms, plugins etc
>> may not have been the smartest decision. We will have to find out how
>> to handle this - we should probably write down a "deprecation /
>> archivation policy" anyway.
>>
>> 2. Some people are missing the "all tickets in one view" interface. I
>> quickly built http://cordova.betamo.de/ as a workaround.
>> The second link on there generates a few prepared Github search links,
>> including one that is valid for _all_ Cordova repositories:
>> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
>> Nice, isn't it?
>> Do you have any specific requests for filters or interface you need or
>> want? What did you use in JIRA that you couldn't find for Github?
>> Shouldn't be too hard to whip something up.
>>
>> -J
>>
>>
>>
>>
>> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
>> > That worked, the ticket was just resolved and issues are now enabled
>> > for all repos (beside cordova-weinre which is archived):
>> >
>> > https://github.com/apache/cordova-android/issues
>> > https://github.com/apache/cordova-ios/issues
>> > https://github.com/apache/cordova-plugin-inappbrowser/issues
>> > ...
>> >
>> > On to b), c) etc.
>> >
>> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
>> >>>
>> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
>> >>
>> >> +100
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Shazron <sh...@gmail.com>.
Thanks Jan!
1. Should we just disable those then? One other way is to add in bold
big letters about the deprecation in the New Issue template
2. These links are super useful. Perhaps they should be on the
website, what do you all think? Not sure if the scripting for the
second link is server side or it could be client side as well (via
JavaScript). Perhaps on the https://cordova.apache.org/contribute/
(contribute.cordova.io) page. That massive github link could also be
auto-generated as well on that page, somehow. Let me know how I can
help.
On Tue, Aug 7, 2018 at 11:01 PM Jan Piotrowski <pi...@gmail.com> wrote:
>
> You may have noticed the first issues coming in on some repositories.
>
> 1. In hindsight enabling issues for deprecated platforms, plugins etc
> may not have been the smartest decision. We will have to find out how
> to handle this - we should probably write down a "deprecation /
> archivation policy" anyway.
>
> 2. Some people are missing the "all tickets in one view" interface. I
> quickly built http://cordova.betamo.de/ as a workaround.
> The second link on there generates a few prepared Github search links,
> including one that is valid for _all_ Cordova repositories:
> https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
> Nice, isn't it?
> Do you have any specific requests for filters or interface you need or
> want? What did you use in JIRA that you couldn't find for Github?
> Shouldn't be too hard to whip something up.
>
> -J
>
>
>
>
> 2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > That worked, the ticket was just resolved and issues are now enabled
> > for all repos (beside cordova-weinre which is archived):
> >
> > https://github.com/apache/cordova-android/issues
> > https://github.com/apache/cordova-ios/issues
> > https://github.com/apache/cordova-plugin-inappbrowser/issues
> > ...
> >
> > On to b), c) etc.
> >
> > 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
> >>>
> >>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
> >>
> >> +100
> >>
> >> ---------------------------------------------------------------------
> >> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
You may have noticed the first issues coming in on some repositories.
1. In hindsight enabling issues for deprecated platforms, plugins etc
may not have been the smartest decision. We will have to find out how
to handle this - we should probably write down a "deprecation /
archivation policy" anyway.
2. Some people are missing the "all tickets in one view" interface. I
quickly built http://cordova.betamo.de/ as a workaround.
The second link on there generates a few prepared Github search links,
including one that is valid for _all_ Cordova repositories:
https://github.com/issues?q=type%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server&s=created&type=Issues
Nice, isn't it?
Do you have any specific requests for filters or interface you need or
want? What did you use in JIRA that you couldn't find for Github?
Shouldn't be too hard to whip something up.
-J
2018-08-06 16:05 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> That worked, the ticket was just resolved and issues are now enabled
> for all repos (beside cordova-weinre which is archived):
>
> https://github.com/apache/cordova-android/issues
> https://github.com/apache/cordova-ios/issues
> https://github.com/apache/cordova-plugin-inappbrowser/issues
> ...
>
> On to b), c) etc.
>
> 2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
>>>
>>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
>>
>> +100
>>
>> ---------------------------------------------------------------------
>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
That worked, the ticket was just resolved and issues are now enabled
for all repos (beside cordova-weinre which is archived):
https://github.com/apache/cordova-android/issues
https://github.com/apache/cordova-ios/issues
https://github.com/apache/cordova-plugin-inappbrowser/issues
...
On to b), c) etc.
2018-08-06 13:09 GMT+02:00 Chris Brody <ch...@gmail.com>:
> On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
>>
>> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
>
> +100
>
> ---------------------------------------------------------------------
> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Chris Brody <ch...@gmail.com>.
On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski <pi...@gmail.com> wrote:
>
> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
+100
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876
2018-08-02 17:29 GMT+02:00 <ra...@gmail.com>:
>>
>> For Cordova tooling I expect no one outside of the developers to
>>
> really know what happens where - but if I see it correctly we almost
>> don't have any tooling JIRA issues as well, right?
>>
> There's plenty tooling related JIRA issues. And rightly so.
>
> IMHO, joining all tooling packages in a mono-repo might be beneficial for
> this and other problems. But that is something for another day.
>
> That is indeed a problem that Github hasn't solved yet (afaik). One
>> can of course create individual issues, then mention the parent issue
>> there to create an automatic link between the issues.
>>
>> > (Can we
>> > productively use whatever tools GitHub provides here, or will we have to
>> > get permission from INFRA for every little thing we do?)
>>
>> Which tools do you refer to? External Kanban tool or something similar?
>> In general we are just Members of the Github repos and don't have any
>> power to change settings etc - Admin is only Apache, which means
>> INFRA.
>>
> I was thinking of "Projects". I saw them on the team level. Don't really
> know what they do though.
> But basically I was speaking hypothetically. Hoping someone with experience
> of that kind of GitHub usage would chime in.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
>
> For Cordova tooling I expect no one outside of the developers to
>
really know what happens where - but if I see it correctly we almost
> don't have any tooling JIRA issues as well, right?
>
There's plenty tooling related JIRA issues. And rightly so.
IMHO, joining all tooling packages in a mono-repo might be beneficial for
this and other problems. But that is something for another day.
That is indeed a problem that Github hasn't solved yet (afaik). One
> can of course create individual issues, then mention the parent issue
> there to create an automatic link between the issues.
>
> > (Can we
> > productively use whatever tools GitHub provides here, or will we have to
> > get permission from INFRA for every little thing we do?)
>
> Which tools do you refer to? External Kanban tool or something similar?
> In general we are just Members of the Github repos and don't have any
> power to change settings etc - Admin is only Apache, which means
> INFRA.
>
I was thinking of "Projects". I saw them on the team level. Don't really
know what they do though.
But basically I was speaking hypothetically. Hoping someone with experience
of that kind of GitHub usage would chime in.
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
> - How do people know in which of the numerous Cordova repos to create
> their issues (especially bad for tooling)
As Julio already indicated this is a communication problem, that we
can solve by having a page at issues.cordova.io. Pages like
https://cordova.apache.org/contribute/ also have links to JIRA now,
this should then be of course adapted as well, complete with an
explanation how to find the correct issue list to create a new one.
The problem of people just _using_ the wrong place can't really be
solved, but we will have to find a way to deal with them. One option
is to use something like https://github-issue-mover.appspot.com/ to
fix what users mess up. Another way is to be very strict with closing
issues and pointing people in the right direction (which users usually
don't like at all though).
For Cordova tooling I expect no one outside of the developers to
really know what happens where - but if I see it correctly we almost
don't have any tooling JIRA issues as well, right?
> - How to manage meta-issues that concern more than one repo
That is indeed a problem that Github hasn't solved yet (afaik). One
can of course create individual issues, then mention the parent issue
there to create an automatic link between the issues.
> (Can we
> productively use whatever tools GitHub provides here, or will we have to
> get permission from INFRA for every little thing we do?)
Which tools do you refer to? External Kanban tool or something similar?
In general we are just Members of the Github repos and don't have any
power to change settings etc - Admin is only Apache, which means
INFRA.
2018-08-02 16:51 GMT+02:00 <ra...@gmail.com>:
> There is much I don't like about JIRA and in general I prefer GitHub
> issues. However, there's issues that did came up during previous
> discussions of this topic, and that have no proper solution that I know of
>
> - How do people know in which of the numerous Cordova repos to create
> their issues (especially bad for tooling)
> - How to manage meta-issues that concern more than one repo (Can we
> productively use whatever tools GitHub provides here, or will we have to
> get permission from INFRA for every little thing we do?)
>
> I fear that if we blindly rush into this, all we will get is an even more
> fragmented landscape of issues and discussions
>
> Am Do., 2. Aug. 2018 um 16:34 Uhr schrieb Jan Piotrowski <
> piotrowski@gmail.com>:
>
>> Decision making for Apache projects is described here:
>> https://community.apache.org/committers/decisionMaking.html
>>
>> So to make it official:
>> I hereby declare that I will start implementing the stuff from my
>> initial email if nobody objects in the next 72 hours (meaning: before
>> next Monday). After that I will create the INFRA issue.
>>
>> The other, preliminary taks can already be started - I did by creating
>> 2 cordova-docs issues that I already linked. For the rest of b) I will
>> probably start another mailing list thread.
>>
>> 2018-08-02 15:35 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> > What will it take to take care of a) Enable GitHub issues on all
>> > repositories via INFRA ticket?
>> >
>> > I think this is needed really badly. There are way too many cases of
>> > questions and issues being raised in the wrong place, lost in diverse
>> > discussion forums, or not even asked at all.
>> > On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com>
>> wrote:
>> >>
>> >> +1
>> >>
>> >> Not sure if (f) was a task, as in to find a way to integrate GH and
>> Slack, but it does exist.
>> >>
>> >> https://slack.github.com/ <https://slack.github.com/>
>> >>
>> >> It covers a lot including new commits, pr, new issues, code reviews,
>> and more.
>> >>
>> >>
>> >> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com>
>> wrote:
>> >> >
>> >> > Another one:
>> >> >
>> >> > f) Find and activate way for Github issue (and PR) updates to be
>> >> > posted so Slack #issues
>> >> >
>> >> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
>> >> >> The npm forum solves a very different problem for npm - they had too
>> >> >> much noise in Github issues because of the project's popularity. Too
>> >> >> much popularity is not one of Cordova's problems ;)
>> >> >>
>> >> >> Many uses of cordova-discuss will be able to move to the individual
>> >> >> project repositories issues, maybe we can even think about getting
>> rid
>> >> >> of it. Good thing to keep in mind after everything is migrated.
>> >> >> The mailing list can be used much more to just point people to a
>> >> >> specific issue (as I also did in my original mail here) where the
>> >> >> actual discussion will happen.
>> >> >>
>> >> >> -J
>> >> >>
>> >> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> >> >>> +1 (+100) for migrating away from JIRA issues
>> >> >>>
>> >> >>> npm took a different approach that I am starting to really like:
>> using
>> >> >>> npm.community (Discourse) with GitHub login for issues and
>> discussions
>> >> >>>
>> >> >>> solves another major problem since I don't like mail list for
>> >> >>> discussing issues and cordova-discuss has proven to be such an
>> >> >>> unpopular repo
>> >> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <
>> piotrowski@gmail.com> wrote:
>> >> >>>>
>> >> >>>> While our repositories are already fully on GitHub [1], our issues
>> >> >>>> mainly still live in JIRA. We previously decided this should be
>> >> >>>> changed [2] so issues live with code.
>> >> >>>>
>> >> >>>> We also did some first switches that were pretty successful:
>> >> >>>>
>> >> >>>> https://github.com/apache/cordova-docs/issues
>> >> >>>> https://github.com/apache/cordova-windows/issues
>> >> >>>>
>> >> >>>> So I suggest we move forward with the rest. Here is a list of
>> stuff to do:
>> >> >>>>
>> >> >>>>
>> >> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
>> >> >>>>
>> >> >>>> b) Define and update Contributor documentation:
>> >> >>>> * Contributor guidelines
>> >> >>>> -
>> https://cordova.apache.org/contribute/contribute_guidelines.html
>> >> >>>> - https://cordova.apache.org/contribute/
>> >> >>>> - https://cordova.apache.org/contribute/issues.html
>> >> >>>> -
>> https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
>> >> >>>> => https://github.com/apache/cordova-docs/issues/861
>> >> >>>> * Issue template(s)
>> >> >>>> * Pull Request template(s)
>> >> >>>> * Github labels / issue triaging documentation
>> >> >>>> * Usage of GitHub merge functionality
>> >> >>>> * READMEs of all repositories
>> >> >>>> * Prepare all these changes as PRs that can merged when a) is
>> taken care of.
>> >> >>>>
>> >> >>>> c) Define and document handling of security issues
>> >> >>>> => https://github.com/apache/cordova-docs/issues/860
>> >> >>>>
>> >> >>>> d) Define and execute issue migration from JIRA to GitHub
>> >> >>>> e) Define and execute "disabling" of JIRA (if applies)
>> >> >>>>
>> >> >>>> Related:
>> >> >>>> - Check if ICLA documentation is correct and fix if necessary
>> >> >>>>
>> >> >>>>
>> >> >>>> Any input or objections?
>> >> >>>>
>> >> >>>> I expect d) and e) to require some more discussion and planning,
>> but
>> >> >>>> think it is ok to just leave this to be done later after everything
>> >> >>>> else was taken care of. Agree?
>> >> >>>>
>> >> >>>> Did I miss any documents for b) that will have to be updated?
>> >> >>>>
>> >> >>>>
>> >> >>>> Best regards,
>> >> >>>> Jan
>> >> >>>>
>> >> >>>>
>> >> >>>> PS:
>> >> >>>>
>> >> >>>> For future reference, the links I collected while researching the
>> >> >>>> previous work done and current state:
>> >> >>>>
>> >> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
>> >> >>>>
>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-14347
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-14398
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-14399
>> >> >>>>
>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-14994
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-14815
>> >> >>>>
>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
>> >> >>>>
>> >> >>>> [2] Migrate Jira issues over to Github:
>> >> >>>> https://issues.apache.org/jira/browse/CB-13157
>> >> >>>>
>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
>> >> >>>> https://github.com/apache/cordova-discuss/pull/75
>> >> >>>>
>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
>> >> >>>> https://issues.apache.org/jira/browse/INFRA-16503
>> >> >>>>
>> >> >>>>
>> ---------------------------------------------------------------------
>> >> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Chris Brody <ch...@gmail.com>.
> we have issues.cordova.io that right now it just redirects to jira, so
> maybe we should have a web page were we list all the repos instead?
+1
> > - How to manage meta-issues that concern more than one repo (Can we
+1
> > productively use whatever tools GitHub provides here, or will we have to
> > get permission from INFRA for every little thing we do?)
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by julio cesar sanchez <jc...@gmail.com>.
we have issues.cordova.io that right now it just redirects to jira, so
maybe we should have a web page were we list all the repos instead?
2018-08-02 16:51 GMT+02:00 <ra...@gmail.com>:
> There is much I don't like about JIRA and in general I prefer GitHub
> issues. However, there's issues that did came up during previous
> discussions of this topic, and that have no proper solution that I know of
>
> - How do people know in which of the numerous Cordova repos to create
> their issues (especially bad for tooling)
> - How to manage meta-issues that concern more than one repo (Can we
> productively use whatever tools GitHub provides here, or will we have to
> get permission from INFRA for every little thing we do?)
>
> I fear that if we blindly rush into this, all we will get is an even more
> fragmented landscape of issues and discussions
>
> Am Do., 2. Aug. 2018 um 16:34 Uhr schrieb Jan Piotrowski <
> piotrowski@gmail.com>:
>
> > Decision making for Apache projects is described here:
> > https://community.apache.org/committers/decisionMaking.html
> >
> > So to make it official:
> > I hereby declare that I will start implementing the stuff from my
> > initial email if nobody objects in the next 72 hours (meaning: before
> > next Monday). After that I will create the INFRA issue.
> >
> > The other, preliminary taks can already be started - I did by creating
> > 2 cordova-docs issues that I already linked. For the rest of b) I will
> > probably start another mailing list thread.
> >
> > 2018-08-02 15:35 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > > What will it take to take care of a) Enable GitHub issues on all
> > > repositories via INFRA ticket?
> > >
> > > I think this is needed really badly. There are way too many cases of
> > > questions and issues being raised in the wrong place, lost in diverse
> > > discussion forums, or not even asked at all.
> > > On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com>
> > wrote:
> > >>
> > >> +1
> > >>
> > >> Not sure if (f) was a task, as in to find a way to integrate GH and
> > Slack, but it does exist.
> > >>
> > >> https://slack.github.com/ <https://slack.github.com/>
> > >>
> > >> It covers a lot including new commits, pr, new issues, code reviews,
> > and more.
> > >>
> > >>
> > >> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com>
> > wrote:
> > >> >
> > >> > Another one:
> > >> >
> > >> > f) Find and activate way for Github issue (and PR) updates to be
> > >> > posted so Slack #issues
> > >> >
> > >> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> > >> >> The npm forum solves a very different problem for npm - they had
> too
> > >> >> much noise in Github issues because of the project's popularity.
> Too
> > >> >> much popularity is not one of Cordova's problems ;)
> > >> >>
> > >> >> Many uses of cordova-discuss will be able to move to the individual
> > >> >> project repositories issues, maybe we can even think about getting
> > rid
> > >> >> of it. Good thing to keep in mind after everything is migrated.
> > >> >> The mailing list can be used much more to just point people to a
> > >> >> specific issue (as I also did in my original mail here) where the
> > >> >> actual discussion will happen.
> > >> >>
> > >> >> -J
> > >> >>
> > >> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > >> >>> +1 (+100) for migrating away from JIRA issues
> > >> >>>
> > >> >>> npm took a different approach that I am starting to really like:
> > using
> > >> >>> npm.community (Discourse) with GitHub login for issues and
> > discussions
> > >> >>>
> > >> >>> solves another major problem since I don't like mail list for
> > >> >>> discussing issues and cordova-discuss has proven to be such an
> > >> >>> unpopular repo
> > >> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <
> > piotrowski@gmail.com> wrote:
> > >> >>>>
> > >> >>>> While our repositories are already fully on GitHub [1], our
> issues
> > >> >>>> mainly still live in JIRA. We previously decided this should be
> > >> >>>> changed [2] so issues live with code.
> > >> >>>>
> > >> >>>> We also did some first switches that were pretty successful:
> > >> >>>>
> > >> >>>> https://github.com/apache/cordova-docs/issues
> > >> >>>> https://github.com/apache/cordova-windows/issues
> > >> >>>>
> > >> >>>> So I suggest we move forward with the rest. Here is a list of
> > stuff to do:
> > >> >>>>
> > >> >>>>
> > >> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
> > >> >>>>
> > >> >>>> b) Define and update Contributor documentation:
> > >> >>>> * Contributor guidelines
> > >> >>>> -
> > https://cordova.apache.org/contribute/contribute_guidelines.html
> > >> >>>> - https://cordova.apache.org/contribute/
> > >> >>>> - https://cordova.apache.org/contribute/issues.html
> > >> >>>> -
> > https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
> > >> >>>> => https://github.com/apache/cordova-docs/issues/861
> > >> >>>> * Issue template(s)
> > >> >>>> * Pull Request template(s)
> > >> >>>> * Github labels / issue triaging documentation
> > >> >>>> * Usage of GitHub merge functionality
> > >> >>>> * READMEs of all repositories
> > >> >>>> * Prepare all these changes as PRs that can merged when a) is
> > taken care of.
> > >> >>>>
> > >> >>>> c) Define and document handling of security issues
> > >> >>>> => https://github.com/apache/cordova-docs/issues/860
> > >> >>>>
> > >> >>>> d) Define and execute issue migration from JIRA to GitHub
> > >> >>>> e) Define and execute "disabling" of JIRA (if applies)
> > >> >>>>
> > >> >>>> Related:
> > >> >>>> - Check if ICLA documentation is correct and fix if necessary
> > >> >>>>
> > >> >>>>
> > >> >>>> Any input or objections?
> > >> >>>>
> > >> >>>> I expect d) and e) to require some more discussion and planning,
> > but
> > >> >>>> think it is ok to just leave this to be done later after
> everything
> > >> >>>> else was taken care of. Agree?
> > >> >>>>
> > >> >>>> Did I miss any documents for b) that will have to be updated?
> > >> >>>>
> > >> >>>>
> > >> >>>> Best regards,
> > >> >>>> Jan
> > >> >>>>
> > >> >>>>
> > >> >>>> PS:
> > >> >>>>
> > >> >>>> For future reference, the links I collected while researching the
> > >> >>>> previous work done and current state:
> > >> >>>>
> > >> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
> > >> >>>>
> > https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9
> ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-14347
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-14398
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-14399
> > >> >>>>
> > https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9
> f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-14994
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-14815
> > >> >>>>
> > https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca422
> 82426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
> > >> >>>>
> > >> >>>> [2] Migrate Jira issues over to Github:
> > >> >>>> https://issues.apache.org/jira/browse/CB-13157
> > >> >>>>
> > https://github.com/audreyso/cordova-discuss/blob/
> 6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
> > >> >>>> https://github.com/apache/cordova-discuss/pull/75
> > >> >>>>
> > https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8a
> cc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
> > >> >>>> https://issues.apache.org/jira/browse/INFRA-16503
> > >> >>>>
> > >> >>>>
> > ---------------------------------------------------------------------
> > >> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by ra...@gmail.com.
There is much I don't like about JIRA and in general I prefer GitHub
issues. However, there's issues that did came up during previous
discussions of this topic, and that have no proper solution that I know of
- How do people know in which of the numerous Cordova repos to create
their issues (especially bad for tooling)
- How to manage meta-issues that concern more than one repo (Can we
productively use whatever tools GitHub provides here, or will we have to
get permission from INFRA for every little thing we do?)
I fear that if we blindly rush into this, all we will get is an even more
fragmented landscape of issues and discussions
Am Do., 2. Aug. 2018 um 16:34 Uhr schrieb Jan Piotrowski <
piotrowski@gmail.com>:
> Decision making for Apache projects is described here:
> https://community.apache.org/committers/decisionMaking.html
>
> So to make it official:
> I hereby declare that I will start implementing the stuff from my
> initial email if nobody objects in the next 72 hours (meaning: before
> next Monday). After that I will create the INFRA issue.
>
> The other, preliminary taks can already be started - I did by creating
> 2 cordova-docs issues that I already linked. For the rest of b) I will
> probably start another mailing list thread.
>
> 2018-08-02 15:35 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > What will it take to take care of a) Enable GitHub issues on all
> > repositories via INFRA ticket?
> >
> > I think this is needed really badly. There are way too many cases of
> > questions and issues being raised in the wrong place, lost in diverse
> > discussion forums, or not even asked at all.
> > On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com>
> wrote:
> >>
> >> +1
> >>
> >> Not sure if (f) was a task, as in to find a way to integrate GH and
> Slack, but it does exist.
> >>
> >> https://slack.github.com/ <https://slack.github.com/>
> >>
> >> It covers a lot including new commits, pr, new issues, code reviews,
> and more.
> >>
> >>
> >> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com>
> wrote:
> >> >
> >> > Another one:
> >> >
> >> > f) Find and activate way for Github issue (and PR) updates to be
> >> > posted so Slack #issues
> >> >
> >> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> >> >> The npm forum solves a very different problem for npm - they had too
> >> >> much noise in Github issues because of the project's popularity. Too
> >> >> much popularity is not one of Cordova's problems ;)
> >> >>
> >> >> Many uses of cordova-discuss will be able to move to the individual
> >> >> project repositories issues, maybe we can even think about getting
> rid
> >> >> of it. Good thing to keep in mind after everything is migrated.
> >> >> The mailing list can be used much more to just point people to a
> >> >> specific issue (as I also did in my original mail here) where the
> >> >> actual discussion will happen.
> >> >>
> >> >> -J
> >> >>
> >> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >> >>> +1 (+100) for migrating away from JIRA issues
> >> >>>
> >> >>> npm took a different approach that I am starting to really like:
> using
> >> >>> npm.community (Discourse) with GitHub login for issues and
> discussions
> >> >>>
> >> >>> solves another major problem since I don't like mail list for
> >> >>> discussing issues and cordova-discuss has proven to be such an
> >> >>> unpopular repo
> >> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <
> piotrowski@gmail.com> wrote:
> >> >>>>
> >> >>>> While our repositories are already fully on GitHub [1], our issues
> >> >>>> mainly still live in JIRA. We previously decided this should be
> >> >>>> changed [2] so issues live with code.
> >> >>>>
> >> >>>> We also did some first switches that were pretty successful:
> >> >>>>
> >> >>>> https://github.com/apache/cordova-docs/issues
> >> >>>> https://github.com/apache/cordova-windows/issues
> >> >>>>
> >> >>>> So I suggest we move forward with the rest. Here is a list of
> stuff to do:
> >> >>>>
> >> >>>>
> >> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
> >> >>>>
> >> >>>> b) Define and update Contributor documentation:
> >> >>>> * Contributor guidelines
> >> >>>> -
> https://cordova.apache.org/contribute/contribute_guidelines.html
> >> >>>> - https://cordova.apache.org/contribute/
> >> >>>> - https://cordova.apache.org/contribute/issues.html
> >> >>>> -
> https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
> >> >>>> => https://github.com/apache/cordova-docs/issues/861
> >> >>>> * Issue template(s)
> >> >>>> * Pull Request template(s)
> >> >>>> * Github labels / issue triaging documentation
> >> >>>> * Usage of GitHub merge functionality
> >> >>>> * READMEs of all repositories
> >> >>>> * Prepare all these changes as PRs that can merged when a) is
> taken care of.
> >> >>>>
> >> >>>> c) Define and document handling of security issues
> >> >>>> => https://github.com/apache/cordova-docs/issues/860
> >> >>>>
> >> >>>> d) Define and execute issue migration from JIRA to GitHub
> >> >>>> e) Define and execute "disabling" of JIRA (if applies)
> >> >>>>
> >> >>>> Related:
> >> >>>> - Check if ICLA documentation is correct and fix if necessary
> >> >>>>
> >> >>>>
> >> >>>> Any input or objections?
> >> >>>>
> >> >>>> I expect d) and e) to require some more discussion and planning,
> but
> >> >>>> think it is ok to just leave this to be done later after everything
> >> >>>> else was taken care of. Agree?
> >> >>>>
> >> >>>> Did I miss any documents for b) that will have to be updated?
> >> >>>>
> >> >>>>
> >> >>>> Best regards,
> >> >>>> Jan
> >> >>>>
> >> >>>>
> >> >>>> PS:
> >> >>>>
> >> >>>> For future reference, the links I collected while researching the
> >> >>>> previous work done and current state:
> >> >>>>
> >> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
> >> >>>>
> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14347
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14398
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14399
> >> >>>>
> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14994
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14815
> >> >>>>
> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
> >> >>>>
> >> >>>> [2] Migrate Jira issues over to Github:
> >> >>>> https://issues.apache.org/jira/browse/CB-13157
> >> >>>>
> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
> >> >>>> https://github.com/apache/cordova-discuss/pull/75
> >> >>>>
> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-16503
> >> >>>>
> >> >>>>
> ---------------------------------------------------------------------
> >> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Chris Brody <ch...@gmail.com>.
+1
On Thu, Aug 2, 2018 at 10:34 AM Jan Piotrowski <pi...@gmail.com> wrote:
>
> Decision making for Apache projects is described here:
> https://community.apache.org/committers/decisionMaking.html
>
> So to make it official:
> I hereby declare that I will start implementing the stuff from my
> initial email if nobody objects in the next 72 hours (meaning: before
> next Monday). After that I will create the INFRA issue.
>
> The other, preliminary taks can already be started - I did by creating
> 2 cordova-docs issues that I already linked. For the rest of b) I will
> probably start another mailing list thread.
>
> 2018-08-02 15:35 GMT+02:00 Chris Brody <ch...@gmail.com>:
> > What will it take to take care of a) Enable GitHub issues on all
> > repositories via INFRA ticket?
> >
> > I think this is needed really badly. There are way too many cases of
> > questions and issues being raised in the wrong place, lost in diverse
> > discussion forums, or not even asked at all.
> > On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com> wrote:
> >>
> >> +1
> >>
> >> Not sure if (f) was a task, as in to find a way to integrate GH and Slack, but it does exist.
> >>
> >> https://slack.github.com/ <https://slack.github.com/>
> >>
> >> It covers a lot including new commits, pr, new issues, code reviews, and more.
> >>
> >>
> >> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com> wrote:
> >> >
> >> > Another one:
> >> >
> >> > f) Find and activate way for Github issue (and PR) updates to be
> >> > posted so Slack #issues
> >> >
> >> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> >> >> The npm forum solves a very different problem for npm - they had too
> >> >> much noise in Github issues because of the project's popularity. Too
> >> >> much popularity is not one of Cordova's problems ;)
> >> >>
> >> >> Many uses of cordova-discuss will be able to move to the individual
> >> >> project repositories issues, maybe we can even think about getting rid
> >> >> of it. Good thing to keep in mind after everything is migrated.
> >> >> The mailing list can be used much more to just point people to a
> >> >> specific issue (as I also did in my original mail here) where the
> >> >> actual discussion will happen.
> >> >>
> >> >> -J
> >> >>
> >> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >> >>> +1 (+100) for migrating away from JIRA issues
> >> >>>
> >> >>> npm took a different approach that I am starting to really like: using
> >> >>> npm.community (Discourse) with GitHub login for issues and discussions
> >> >>>
> >> >>> solves another major problem since I don't like mail list for
> >> >>> discussing issues and cordova-discuss has proven to be such an
> >> >>> unpopular repo
> >> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <pi...@gmail.com> wrote:
> >> >>>>
> >> >>>> While our repositories are already fully on GitHub [1], our issues
> >> >>>> mainly still live in JIRA. We previously decided this should be
> >> >>>> changed [2] so issues live with code.
> >> >>>>
> >> >>>> We also did some first switches that were pretty successful:
> >> >>>>
> >> >>>> https://github.com/apache/cordova-docs/issues
> >> >>>> https://github.com/apache/cordova-windows/issues
> >> >>>>
> >> >>>> So I suggest we move forward with the rest. Here is a list of stuff to do:
> >> >>>>
> >> >>>>
> >> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
> >> >>>>
> >> >>>> b) Define and update Contributor documentation:
> >> >>>> * Contributor guidelines
> >> >>>> - https://cordova.apache.org/contribute/contribute_guidelines.html
> >> >>>> - https://cordova.apache.org/contribute/
> >> >>>> - https://cordova.apache.org/contribute/issues.html
> >> >>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
> >> >>>> => https://github.com/apache/cordova-docs/issues/861
> >> >>>> * Issue template(s)
> >> >>>> * Pull Request template(s)
> >> >>>> * Github labels / issue triaging documentation
> >> >>>> * Usage of GitHub merge functionality
> >> >>>> * READMEs of all repositories
> >> >>>> * Prepare all these changes as PRs that can merged when a) is taken care of.
> >> >>>>
> >> >>>> c) Define and document handling of security issues
> >> >>>> => https://github.com/apache/cordova-docs/issues/860
> >> >>>>
> >> >>>> d) Define and execute issue migration from JIRA to GitHub
> >> >>>> e) Define and execute "disabling" of JIRA (if applies)
> >> >>>>
> >> >>>> Related:
> >> >>>> - Check if ICLA documentation is correct and fix if necessary
> >> >>>>
> >> >>>>
> >> >>>> Any input or objections?
> >> >>>>
> >> >>>> I expect d) and e) to require some more discussion and planning, but
> >> >>>> think it is ok to just leave this to be done later after everything
> >> >>>> else was taken care of. Agree?
> >> >>>>
> >> >>>> Did I miss any documents for b) that will have to be updated?
> >> >>>>
> >> >>>>
> >> >>>> Best regards,
> >> >>>> Jan
> >> >>>>
> >> >>>>
> >> >>>> PS:
> >> >>>>
> >> >>>> For future reference, the links I collected while researching the
> >> >>>> previous work done and current state:
> >> >>>>
> >> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
> >> >>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14347
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14398
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14399
> >> >>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14994
> >> >>>> https://issues.apache.org/jira/browse/INFRA-14815
> >> >>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
> >> >>>>
> >> >>>> [2] Migrate Jira issues over to Github:
> >> >>>> https://issues.apache.org/jira/browse/CB-13157
> >> >>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
> >> >>>> https://github.com/apache/cordova-discuss/pull/75
> >> >>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
> >> >>>> https://issues.apache.org/jira/browse/INFRA-16503
> >> >>>>
> >> >>>> ---------------------------------------------------------------------
> >> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Jan Piotrowski <pi...@gmail.com>.
Decision making for Apache projects is described here:
https://community.apache.org/committers/decisionMaking.html
So to make it official:
I hereby declare that I will start implementing the stuff from my
initial email if nobody objects in the next 72 hours (meaning: before
next Monday). After that I will create the INFRA issue.
The other, preliminary taks can already be started - I did by creating
2 cordova-docs issues that I already linked. For the rest of b) I will
probably start another mailing list thread.
2018-08-02 15:35 GMT+02:00 Chris Brody <ch...@gmail.com>:
> What will it take to take care of a) Enable GitHub issues on all
> repositories via INFRA ticket?
>
> I think this is needed really badly. There are way too many cases of
> questions and issues being raised in the wrong place, lost in diverse
> discussion forums, or not even asked at all.
> On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com> wrote:
>>
>> +1
>>
>> Not sure if (f) was a task, as in to find a way to integrate GH and Slack, but it does exist.
>>
>> https://slack.github.com/ <https://slack.github.com/>
>>
>> It covers a lot including new commits, pr, new issues, code reviews, and more.
>>
>>
>> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com> wrote:
>> >
>> > Another one:
>> >
>> > f) Find and activate way for Github issue (and PR) updates to be
>> > posted so Slack #issues
>> >
>> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
>> >> The npm forum solves a very different problem for npm - they had too
>> >> much noise in Github issues because of the project's popularity. Too
>> >> much popularity is not one of Cordova's problems ;)
>> >>
>> >> Many uses of cordova-discuss will be able to move to the individual
>> >> project repositories issues, maybe we can even think about getting rid
>> >> of it. Good thing to keep in mind after everything is migrated.
>> >> The mailing list can be used much more to just point people to a
>> >> specific issue (as I also did in my original mail here) where the
>> >> actual discussion will happen.
>> >>
>> >> -J
>> >>
>> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
>> >>> +1 (+100) for migrating away from JIRA issues
>> >>>
>> >>> npm took a different approach that I am starting to really like: using
>> >>> npm.community (Discourse) with GitHub login for issues and discussions
>> >>>
>> >>> solves another major problem since I don't like mail list for
>> >>> discussing issues and cordova-discuss has proven to be such an
>> >>> unpopular repo
>> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <pi...@gmail.com> wrote:
>> >>>>
>> >>>> While our repositories are already fully on GitHub [1], our issues
>> >>>> mainly still live in JIRA. We previously decided this should be
>> >>>> changed [2] so issues live with code.
>> >>>>
>> >>>> We also did some first switches that were pretty successful:
>> >>>>
>> >>>> https://github.com/apache/cordova-docs/issues
>> >>>> https://github.com/apache/cordova-windows/issues
>> >>>>
>> >>>> So I suggest we move forward with the rest. Here is a list of stuff to do:
>> >>>>
>> >>>>
>> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
>> >>>>
>> >>>> b) Define and update Contributor documentation:
>> >>>> * Contributor guidelines
>> >>>> - https://cordova.apache.org/contribute/contribute_guidelines.html
>> >>>> - https://cordova.apache.org/contribute/
>> >>>> - https://cordova.apache.org/contribute/issues.html
>> >>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
>> >>>> => https://github.com/apache/cordova-docs/issues/861
>> >>>> * Issue template(s)
>> >>>> * Pull Request template(s)
>> >>>> * Github labels / issue triaging documentation
>> >>>> * Usage of GitHub merge functionality
>> >>>> * READMEs of all repositories
>> >>>> * Prepare all these changes as PRs that can merged when a) is taken care of.
>> >>>>
>> >>>> c) Define and document handling of security issues
>> >>>> => https://github.com/apache/cordova-docs/issues/860
>> >>>>
>> >>>> d) Define and execute issue migration from JIRA to GitHub
>> >>>> e) Define and execute "disabling" of JIRA (if applies)
>> >>>>
>> >>>> Related:
>> >>>> - Check if ICLA documentation is correct and fix if necessary
>> >>>>
>> >>>>
>> >>>> Any input or objections?
>> >>>>
>> >>>> I expect d) and e) to require some more discussion and planning, but
>> >>>> think it is ok to just leave this to be done later after everything
>> >>>> else was taken care of. Agree?
>> >>>>
>> >>>> Did I miss any documents for b) that will have to be updated?
>> >>>>
>> >>>>
>> >>>> Best regards,
>> >>>> Jan
>> >>>>
>> >>>>
>> >>>> PS:
>> >>>>
>> >>>> For future reference, the links I collected while researching the
>> >>>> previous work done and current state:
>> >>>>
>> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
>> >>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
>> >>>> https://issues.apache.org/jira/browse/INFRA-14347
>> >>>> https://issues.apache.org/jira/browse/INFRA-14398
>> >>>> https://issues.apache.org/jira/browse/INFRA-14399
>> >>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
>> >>>> https://issues.apache.org/jira/browse/INFRA-14994
>> >>>> https://issues.apache.org/jira/browse/INFRA-14815
>> >>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
>> >>>>
>> >>>> [2] Migrate Jira issues over to Github:
>> >>>> https://issues.apache.org/jira/browse/CB-13157
>> >>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
>> >>>> https://github.com/apache/cordova-discuss/pull/75
>> >>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
>> >>>> https://issues.apache.org/jira/browse/INFRA-16503
>> >>>>
>> >>>> ---------------------------------------------------------------------
>> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Chris Brody <ch...@gmail.com>.
What will it take to take care of a) Enable GitHub issues on all
repositories via INFRA ticket?
I think this is needed really badly. There are way too many cases of
questions and issues being raised in the wrong place, lost in diverse
discussion forums, or not even asked at all.
On Wed, Aug 1, 2018 at 9:59 AM Bryan Ellis <el...@gmail.com> wrote:
>
> +1
>
> Not sure if (f) was a task, as in to find a way to integrate GH and Slack, but it does exist.
>
> https://slack.github.com/ <https://slack.github.com/>
>
> It covers a lot including new commits, pr, new issues, code reviews, and more.
>
>
> > On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com> wrote:
> >
> > Another one:
> >
> > f) Find and activate way for Github issue (and PR) updates to be
> > posted so Slack #issues
> >
> > 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
> >> The npm forum solves a very different problem for npm - they had too
> >> much noise in Github issues because of the project's popularity. Too
> >> much popularity is not one of Cordova's problems ;)
> >>
> >> Many uses of cordova-discuss will be able to move to the individual
> >> project repositories issues, maybe we can even think about getting rid
> >> of it. Good thing to keep in mind after everything is migrated.
> >> The mailing list can be used much more to just point people to a
> >> specific issue (as I also did in my original mail here) where the
> >> actual discussion will happen.
> >>
> >> -J
> >>
> >> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
> >>> +1 (+100) for migrating away from JIRA issues
> >>>
> >>> npm took a different approach that I am starting to really like: using
> >>> npm.community (Discourse) with GitHub login for issues and discussions
> >>>
> >>> solves another major problem since I don't like mail list for
> >>> discussing issues and cordova-discuss has proven to be such an
> >>> unpopular repo
> >>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <pi...@gmail.com> wrote:
> >>>>
> >>>> While our repositories are already fully on GitHub [1], our issues
> >>>> mainly still live in JIRA. We previously decided this should be
> >>>> changed [2] so issues live with code.
> >>>>
> >>>> We also did some first switches that were pretty successful:
> >>>>
> >>>> https://github.com/apache/cordova-docs/issues
> >>>> https://github.com/apache/cordova-windows/issues
> >>>>
> >>>> So I suggest we move forward with the rest. Here is a list of stuff to do:
> >>>>
> >>>>
> >>>> a) Enable GitHub issues on all repositories via INFRA ticket
> >>>>
> >>>> b) Define and update Contributor documentation:
> >>>> * Contributor guidelines
> >>>> - https://cordova.apache.org/contribute/contribute_guidelines.html
> >>>> - https://cordova.apache.org/contribute/
> >>>> - https://cordova.apache.org/contribute/issues.html
> >>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
> >>>> => https://github.com/apache/cordova-docs/issues/861
> >>>> * Issue template(s)
> >>>> * Pull Request template(s)
> >>>> * Github labels / issue triaging documentation
> >>>> * Usage of GitHub merge functionality
> >>>> * READMEs of all repositories
> >>>> * Prepare all these changes as PRs that can merged when a) is taken care of.
> >>>>
> >>>> c) Define and document handling of security issues
> >>>> => https://github.com/apache/cordova-docs/issues/860
> >>>>
> >>>> d) Define and execute issue migration from JIRA to GitHub
> >>>> e) Define and execute "disabling" of JIRA (if applies)
> >>>>
> >>>> Related:
> >>>> - Check if ICLA documentation is correct and fix if necessary
> >>>>
> >>>>
> >>>> Any input or objections?
> >>>>
> >>>> I expect d) and e) to require some more discussion and planning, but
> >>>> think it is ok to just leave this to be done later after everything
> >>>> else was taken care of. Agree?
> >>>>
> >>>> Did I miss any documents for b) that will have to be updated?
> >>>>
> >>>>
> >>>> Best regards,
> >>>> Jan
> >>>>
> >>>>
> >>>> PS:
> >>>>
> >>>> For future reference, the links I collected while researching the
> >>>> previous work done and current state:
> >>>>
> >>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
> >>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
> >>>> https://issues.apache.org/jira/browse/INFRA-14347
> >>>> https://issues.apache.org/jira/browse/INFRA-14398
> >>>> https://issues.apache.org/jira/browse/INFRA-14399
> >>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
> >>>> https://issues.apache.org/jira/browse/INFRA-14994
> >>>> https://issues.apache.org/jira/browse/INFRA-14815
> >>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
> >>>>
> >>>> [2] Migrate Jira issues over to Github:
> >>>> https://issues.apache.org/jira/browse/CB-13157
> >>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
> >>>> https://github.com/apache/cordova-discuss/pull/75
> >>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
> >>>> https://issues.apache.org/jira/browse/INFRA-16503
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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: [DISCUSS] [JIRA -> GitHub Issues] The way forward
Posted by Bryan Ellis <el...@gmail.com>.
+1
Not sure if (f) was a task, as in to find a way to integrate GH and Slack, but it does exist.
https://slack.github.com/ <https://slack.github.com/>
It covers a lot including new commits, pr, new issues, code reviews, and more.
> On Aug 1, 2018, at 22:22, Jan Piotrowski <pi...@gmail.com> wrote:
>
> Another one:
>
> f) Find and activate way for Github issue (and PR) updates to be
> posted so Slack #issues
>
> 2018-07-31 18:14 GMT+02:00 Jan Piotrowski <pi...@gmail.com>:
>> The npm forum solves a very different problem for npm - they had too
>> much noise in Github issues because of the project's popularity. Too
>> much popularity is not one of Cordova's problems ;)
>>
>> Many uses of cordova-discuss will be able to move to the individual
>> project repositories issues, maybe we can even think about getting rid
>> of it. Good thing to keep in mind after everything is migrated.
>> The mailing list can be used much more to just point people to a
>> specific issue (as I also did in my original mail here) where the
>> actual discussion will happen.
>>
>> -J
>>
>> 2018-07-31 17:39 GMT+02:00 Chris Brody <ch...@gmail.com>:
>>> +1 (+100) for migrating away from JIRA issues
>>>
>>> npm took a different approach that I am starting to really like: using
>>> npm.community (Discourse) with GitHub login for issues and discussions
>>>
>>> solves another major problem since I don't like mail list for
>>> discussing issues and cordova-discuss has proven to be such an
>>> unpopular repo
>>> On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski <pi...@gmail.com> wrote:
>>>>
>>>> While our repositories are already fully on GitHub [1], our issues
>>>> mainly still live in JIRA. We previously decided this should be
>>>> changed [2] so issues live with code.
>>>>
>>>> We also did some first switches that were pretty successful:
>>>>
>>>> https://github.com/apache/cordova-docs/issues
>>>> https://github.com/apache/cordova-windows/issues
>>>>
>>>> So I suggest we move forward with the rest. Here is a list of stuff to do:
>>>>
>>>>
>>>> a) Enable GitHub issues on all repositories via INFRA ticket
>>>>
>>>> b) Define and update Contributor documentation:
>>>> * Contributor guidelines
>>>> - https://cordova.apache.org/contribute/contribute_guidelines.html
>>>> - https://cordova.apache.org/contribute/
>>>> - https://cordova.apache.org/contribute/issues.html
>>>> - https://github.com/apache/cordova-coho/search?l=Markdown&q=JIRA
>>>> => https://github.com/apache/cordova-docs/issues/861
>>>> * Issue template(s)
>>>> * Pull Request template(s)
>>>> * Github labels / issue triaging documentation
>>>> * Usage of GitHub merge functionality
>>>> * READMEs of all repositories
>>>> * Prepare all these changes as PRs that can merged when a) is taken care of.
>>>>
>>>> c) Define and document handling of security issues
>>>> => https://github.com/apache/cordova-docs/issues/860
>>>>
>>>> d) Define and execute issue migration from JIRA to GitHub
>>>> e) Define and execute "disabling" of JIRA (if applies)
>>>>
>>>> Related:
>>>> - Check if ICLA documentation is correct and fix if necessary
>>>>
>>>>
>>>> Any input or objections?
>>>>
>>>> I expect d) and e) to require some more discussion and planning, but
>>>> think it is ok to just leave this to be done later after everything
>>>> else was taken care of. Agree?
>>>>
>>>> Did I miss any documents for b) that will have to be updated?
>>>>
>>>>
>>>> Best regards,
>>>> Jan
>>>>
>>>>
>>>> PS:
>>>>
>>>> For future reference, the links I collected while researching the
>>>> previous work done and current state:
>>>>
>>>> [1] Move repositories to Github / Gitbox for Apache Cordova:
>>>> https://lists.apache.org/thread.html/af0ec86818674bd1a8c4a9372685a9ae8e6200c478ad8e859606f3a3@%3Cdev.cordova.apache.org%3E
>>>> https://issues.apache.org/jira/browse/INFRA-14347
>>>> https://issues.apache.org/jira/browse/INFRA-14398
>>>> https://issues.apache.org/jira/browse/INFRA-14399
>>>> https://lists.apache.org/thread.html/23e927ad58441685a3fb3bbfe8e4d9f52369afa24e6e57f74b247d17@%3Cdev.cordova.apache.org%3E
>>>> https://issues.apache.org/jira/browse/INFRA-14994
>>>> https://issues.apache.org/jira/browse/INFRA-14815
>>>> https://lists.apache.org/thread.html/649d83cd05ae7029327cd4734ca42282426c5564b291257da1b8b75e@%3Cdev.cordova.apache.org%3E
>>>>
>>>> [2] Migrate Jira issues over to Github:
>>>> https://issues.apache.org/jira/browse/CB-13157
>>>> https://github.com/audreyso/cordova-discuss/blob/6bece4125d389036461e25036e51e0fdfd712567/proposals/GithubMigration.md
>>>> https://github.com/apache/cordova-discuss/pull/75
>>>> https://lists.apache.org/thread.html/a992eaf62c8475a4576784ca3f9d8acc575220f0c53e6016bc4455e7@%3Cdev.cordova.apache.org%3E
>>>> https://issues.apache.org/jira/browse/INFRA-16503
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>