[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #20: September board report
purplecabbage merged PR #20: URL: https://github.com/apache/cordova-apache-board-reports/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] timbru31 commented on a diff in pull request #20: September board report
timbru31 commented on code in PR #20: URL: https://github.com/apache/cordova-apache-board-reports/pull/20#discussion_r1322988712 ## 2023/09.md: ## @@ -0,0 +1,70 @@ +## Status report for the Apache Cordova project - September 2023 + +## Description: + - A platform for building native mobile applications using HTML, CSS and JavaScript. + +## Activity + +Current work continues to be keeping up with changes to iOS and Android, our most used platforms, and updating plugins. + +Github discussions has become how our community supports each other. + +Committers made large releases this quarter with major version bumps to cordova-ios@7, cordova-plugin-file@8, cordova-plugin-media-capture@5, cordova-plugin-camera@7, cordova-plugin-file-transfer@2, cordova-plugin-media@7 + +## Issues: + - There are no issues requiring board attention at this time. + +## Health report: + +Our status dashboard at http://status.cordova.io remains mostly all green and our nightly builds are still extremely stable. + +ASF Project Statistics gives the project a Community Health Score (Chi): 4.70 Healthy + +A small group of dedicated individuals continue to contribute and make incremental releases. +The project remains stable and continues to see good traffic. + +Our discussion area is live at https://github.com/apache/cordova/discussions and activity is forwarded to the 'issues' list. + + +## Membership Data: +- There are currently 99 committers and 96 PMC members in this project. +- The Committer-to-PMC ratio is roughly 1:1. + +### Community changes, past quarter: + +- No new PMC members. Last addition was Pieter Van Poyer on 2021-04-05. +- No new committers. Last addition was Pieter Van Poyer on 2021-04-05. + +## Releases: + +- TODO: add camera 7.0, file-transfer 2.0, media 7.0 when they are released + +- cordova-ios@7.0.1 was released on 2023-09-06. +- cordova-android@12.0.1 was released on 2023-08-28. +- cordova-plugin-media-capture@5.0.0 was released on 2023-08-18. +- cordova-ios@7.0.0 was released on 2023-07-10. +- cordova-plugin-file@8.0.0 was released on 2023-07-10. + + +## Github activity: + +Issue close rate of 99% +101 issues opened on GitHub, past quarter (-15% change) +100 issues closed on GitHub, past quarter (-55% change) + + +PR close rate of 91% +141 PRs opened on GitHub, past quarter (-4% change) +128 PRs closed on GitHub, past quarter (-27% change) + +Commits +146 commits in the past quarter (-30% decrease) +14 code contributors in the past quarter (-41% change) + + + + + + + + Review Comment: ```suggestion ``` I think we can strip a few newlines đź‘Ť ## 2023/09.md: ## @@ -0,0 +1,70 @@ +## Status report for the Apache Cordova project - September 2023 + +## Description: + - A platform for building native mobile applications using HTML, CSS and JavaScript. + +## Activity + +Current work continues to be keeping up with changes to iOS and Android, our most used platforms, and updating plugins. + +Github discussions has become how our community supports each other. + +Committers made large releases this quarter with major version bumps to cordova-ios@7, cordova-plugin-file@8, cordova-plugin-media-capture@5, cordova-plugin-camera@7, cordova-plugin-file-transfer@2, cordova-plugin-media@7 + +## Issues: + - There are no issues requiring board attention at this time. + +## Health report: + +Our status dashboard at http://status.cordova.io remains mostly all green and our nightly builds are still extremely stable. + +ASF Project Statistics gives the project a Community Health Score (Chi): 4.70 Healthy + +A small group of dedicated individuals continue to contribute and make incremental releases. +The project remains stable and continues to see good traffic. + +Our discussion area is live at https://github.com/apache/cordova/discussions and activity is forwarded to the 'issues' list. + + +## Membership Data: +- There are currently 99 committers and 96 PMC members in this project. +- The Committer-to-PMC ratio is roughly 1:1. + +### Community changes, past quarter: + +- No new PMC members. Last addition was Pieter Van Poyer on 2021-04-05. +- No new committers. Last addition was Pieter Van Poyer on 2021-04-05. + +## Releases: + +- TODO: add camera 7.0, file-transfer 2.0, media 7.0 when they are released + +- cordova-ios@7.0.1 was released on 2023-09-06. +- cordova-android@12.0.1 was released on 2023-08-28. +- cordova-plugin-media-capture@5.0.0 was released on 2023-08-18. +- cordova-ios@7.0.0 was released on 2023-07-10. +- cordova-plugin-file@8.0.0 was released on 2023-07-10. + + +## Github activity: + +Issue close rate of 99% +101 issues opened on GitHub, past quarter (-15% change) +100 issues closed on GitHub, past quarter (-55% change) + + +PR close rate of 91% +141 PRs opened on GitHub, past quarter (-4% change) +128 PRs closed on GitHub, past quarter (-27% change) + +Commits +146 commits in the past quarter
[GitHub] [cordova-apache-board-reports] purplecabbage opened a new pull request, #20: Sept board report draft
purplecabbage opened a new pull request, #20: URL: https://github.com/apache/cordova-apache-board-reports/pull/20 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE} mailing list for logging github discussions
The vote has now closed. The results are: Positive Binding Votes: 4 Jesse MacFadyen Darryl Pogue Norman Breau Niklas Merz Negative Binding Votes: 0 Other Votes: 0 The vote has passed. On Sun, Jul 9, 2023 at 8:07 AM Niklas Merz wrote: > I vote +1 > > On July 9, 2023, Norman Breau wrote: > > I vote +1 > > > > On 2023-07-08 1:00 a.m., Darryl Pogue wrote: > > > I vote +1 > > > > > > On Fri, Jul 7, 2023 at 8:38 PM Jesse > > wrote: > > > > > >> Please review and vote by replying to this email, and keeping > > discussion on > > >> the [DISCUSS] thread. ( note: subject is changed ) > > >>> [DISCUSS] Create new mailing list for logging github discussions > > >> This vote is to direct all github discussion generated email to > > >> iss...@cordova.apache.org, instead of the current setting which > > sends it > > >> all to the dev list. > > >> > > >> Upon a successful vote I will update infra settings to direct all > > github > > >> discussion activity to iss...@cordova.apache.org. > > >> > > >> Voting guidelines: > > >> https://github.com/apache/cordova-coho/blob/master/docs/release- > > voting.md > > >> > > >> Voting will go on for a minimum of 48 hours. > > >> > > >> === > > >> > > >> I vote +1 > > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org >
Re: [VOTE} mailing list for logging github discussions
I vote +1 On July 9, 2023, Norman Breau wrote: > I vote +1 > > On 2023-07-08 1:00 a.m., Darryl Pogue wrote: > > I vote +1 > > > > On Fri, Jul 7, 2023 at 8:38 PM Jesse > wrote: > > > >> Please review and vote by replying to this email, and keeping > discussion on > >> the [DISCUSS] thread. ( note: subject is changed ) > >>> [DISCUSS] Create new mailing list for logging github discussions > >> This vote is to direct all github discussion generated email to > >> iss...@cordova.apache.org, instead of the current setting which > sends it > >> all to the dev list. > >> > >> Upon a successful vote I will update infra settings to direct all > github > >> discussion activity to iss...@cordova.apache.org. > >> > >> Voting guidelines: > >> https://github.com/apache/cordova-coho/blob/master/docs/release- > voting.md > >> > >> Voting will go on for a minimum of 48 hours. > >> > >> === > >> > >> I vote +1 > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE} mailing list for logging github discussions
I vote +1 On 2023-07-08 1:00 a.m., Darryl Pogue wrote: I vote +1 On Fri, Jul 7, 2023 at 8:38 PM Jesse wrote: Please review and vote by replying to this email, and keeping discussion on the [DISCUSS] thread. ( note: subject is changed ) [DISCUSS] Create new mailing list for logging github discussions This vote is to direct all github discussion generated email to iss...@cordova.apache.org, instead of the current setting which sends it all to the dev list. Upon a successful vote I will update infra settings to direct all github discussion activity to iss...@cordova.apache.org. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. === I vote +1 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [VOTE} mailing list for logging github discussions
I vote +1 On Fri, Jul 7, 2023 at 8:38 PM Jesse wrote: > Please review and vote by replying to this email, and keeping discussion on > the [DISCUSS] thread. ( note: subject is changed ) > > [DISCUSS] Create new mailing list for logging github discussions > > This vote is to direct all github discussion generated email to > iss...@cordova.apache.org, instead of the current setting which sends it > all to the dev list. > > Upon a successful vote I will update infra settings to direct all github > discussion activity to iss...@cordova.apache.org. > > Voting guidelines: > https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md > > Voting will go on for a minimum of 48 hours. > > === > > I vote +1 >
[VOTE} mailing list for logging github discussions
Please review and vote by replying to this email, and keeping discussion on the [DISCUSS] thread. ( note: subject is changed ) > [DISCUSS] Create new mailing list for logging github discussions This vote is to direct all github discussion generated email to iss...@cordova.apache.org, instead of the current setting which sends it all to the dev list. Upon a successful vote I will update infra settings to direct all github discussion activity to iss...@cordova.apache.org. Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md Voting will go on for a minimum of 48 hours. === I vote +1
Re: [DISCUSS] Create new mailing list for logging github discussions
I was waiting for that vote thread. I didn't voice any alternatives as I think what was already mentioned. I prefer to keep the dev mailing clean for discussions/votes. Forwarding github discussion actions to the existing issues mailing list I think is fine. On 2023-07-06 2:11 a.m., Jesse wrote: Since I have not heard anything here, I am assuming that the way things are is fine. Cheers, Jesse On Wed, Jun 28, 2023 at 11:31 PM Jesse wrote: I have made the change to github.com/apache/cordova so that all discussion activity will be sent to our (dev) mailing list. There has been some concern raised in slack#pmc that this will flood the dev list which we use specifically for cordova development, and NOT for support. For years now, when anyone has sent a message to the dev list asking a 'how to use cordova' question, we have flatly told them: | "This mailing list is for discussions regarding the development of Apache Cordova and not for support. For support and/or questions about how to use Apache Cordova, please use GitHub Discussions ... " So it does seem a little weird if those discussions end up right back here. A vote will follow shortly (tomorrow) proposing that we create a new mailing list disc...@cordova.apache.org and route all github discussion activity there. Please use this thread to weigh alternatives, of which I see a few: - do nothing, set up your own filters if you are annoyed by the extra email on dev - route this traffic to issues, which is already collecting all gh issues, pull requests and comments - create a new list, but with some other name to avoid confusion with [DISCUSS] threads Cheers, Jesse - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Create new mailing list for logging github discussions
I would prefer that discussions don't go to the dev@ list as they create much noise and I usually check things on Github using the notifications there. We could send them to issues@ or create discussions@. I personally don't care as I see the list only for archival. For me discussions and issues on GH are somewhat related so having them on the issue list would be the easiest but a new list could be cleaner. Regards Niklas On July 6, 2023, Jesse wrote: > Since I have not heard anything here, I am assuming that the way > things are > is fine. > > Cheers, > Â Jesse > > On Wed, Jun 28, 2023 at 11:31 PM Jesse > wrote: > > > I have made the change to github.com/apache/cordova so that all > > discussion activity will be sent to our (dev) mailing list. There > has been > > some concern raised in slack#pmc that this will flood the dev list > which we > > use specifically for cordova development, and NOT for support. > > For years now, when anyone has sent a message to the dev list asking > a > > 'how to use cordova' question, we have flatly told them: > > | "This mailing list is for discussions regarding the development of > > Apache Cordova and not for support. For support and/or questions > about how > > to use Apache Cordova, please use GitHub Discussions ... " > > So it does seem a little weird if those discussions end up right > back here. > > > > A vote will follow shortly (tomorrow) proposing that we create a new > > mailing list disc...@cordova.apache.org and route all github > discussion > > activity there. > > > > Please use this thread to weigh alternatives, of which I see a few: > > - do nothing, set up your own filters if you are annoyed by the > extra > > email on dev > > - route this traffic to issues, which is already collecting all gh > issues, > > pull requests and comments > > - create a new list, but with some other name to avoid confusion > with > > [DISCUSS] threads > > > > Cheers, > > Jesse > >
Re: [DISCUSS] Create new mailing list for logging github discussions
Since I have not heard anything here, I am assuming that the way things are is fine. Cheers, Jesse On Wed, Jun 28, 2023 at 11:31 PM Jesse wrote: > I have made the change to github.com/apache/cordova so that all > discussion activity will be sent to our (dev) mailing list. There has been > some concern raised in slack#pmc that this will flood the dev list which we > use specifically for cordova development, and NOT for support. > For years now, when anyone has sent a message to the dev list asking a > 'how to use cordova' question, we have flatly told them: > | "This mailing list is for discussions regarding the development of > Apache Cordova and not for support. For support and/or questions about how > to use Apache Cordova, please use GitHub Discussions ... " > So it does seem a little weird if those discussions end up right back here. > > A vote will follow shortly (tomorrow) proposing that we create a new > mailing list disc...@cordova.apache.org and route all github discussion > activity there. > > Please use this thread to weigh alternatives, of which I see a few: > - do nothing, set up your own filters if you are annoyed by the extra > email on dev > - route this traffic to issues, which is already collecting all gh issues, > pull requests and comments > - create a new list, but with some other name to avoid confusion with > [DISCUSS] threads > > Cheers, > Jesse >
[GitHub] [cordova] leonelgregioauler closed a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler closed a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) I have a problem. I ran the command: (I use Oracle JET, 14.1) ojet build android --release --buildconfig="C:/PUBLISH/NEOCP3001/build-android.json" The release generates, I upload it to Google Play, I create an internal test version, I download it, I install it on the cell phone, but after the splashscreen is displayed, the screen turns white. The key was generated using the command: keytool -genkey -v -keystore neocp3001.jks -keyalg RSA -keysize 2048 -validity 1 -alias neocp3001 Debug mode installs and runs perfectly! Cordova 12.0.0 Target SDK 33 SDK Build Tools 33.0.2 gradle 7.6 Android Gradle Plugin 7.4.2 JAVA 19    GitHub link: https://github.com/apache/cordova/discussions/422 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler reopened a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler reopened a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) I have a problem. I ran the command: (I use Oracle JET, 14.1) ojet build android --release --buildconfig="C:/PUBLISH/NEOCP3001/build-android.json" The release generates, I upload it to Google Play, I create an internal test version, I download it, I install it on the cell phone, but after the splashscreen is displayed, the screen turns white. The key was generated using the command: keytool -genkey -v -keystore neocp3001.jks -keyalg RSA -keysize 2048 -validity 1 -alias neocp3001 Debug mode installs and runs perfectly! Cordova 12.0.0 Target SDK 33 SDK Build Tools 33.0.2 gradle 7.6 Android Gradle Plugin 7.4.2 JAVA 19    GitHub link: https://github.com/apache/cordova/discussions/422 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler closed a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler closed a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) I have a problem. I ran the command: (I use Oracle JET, 14.1) ojet build android --release --buildconfig="C:/PUBLISH/NEOCP3001/build-android.json" The release generates, I upload it to Google Play, I create an internal test version, I download it, I install it on the cell phone, but after the splashscreen is displayed, the screen turns white. The key was generated using the command: keytool -genkey -v -keystore neocp3001.jks -keyalg RSA -keysize 2048 -validity 1 -alias neocp3001 Debug mode installs and runs perfectly! Cordova 12.0.0 Target SDK 33 SDK Build Tools 33.0.2 gradle 7.6 Android Gradle Plugin 7.4.2 JAVA 19    GitHub link: https://github.com/apache/cordova/discussions/422 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) Good morning ! I used the preference below, and performed the debug, finding the error. It's really an error in Oracle JET, I need to fix it. I didn't know how to debug the release version, this will help me a lot !! Thanks !! preference name="InspectableWebview" value="true"  GitHub link: https://github.com/apache/cordova/discussions/422#discussioncomment-6343946 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler deleted a comment on the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler deleted a comment on the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) Great ! I added the preference. Thank you ! The errors are below:  GitHub link: https://github.com/apache/cordova/discussions/422#discussioncomment-6333646 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) Great ! I added the preference. Thank you ! The errors are below:  GitHub link: https://github.com/apache/cordova/discussions/422#discussioncomment-6333646 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] breautek added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user breautek added a comment to the discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) There is very little information to go on, what pointers that we can give is going to be rather limited. A white screen is likely caused by your index page either not loading at all, or erroring on load. Normally the web inspector is disabled on release builds, but you can enable it by setting the `InspectableWebview` preference to `true`. Additionally you can test release builds locally by using `cordova run android --release -- --packageType=apk`. Pay special attention to the double hyphen! (Windows powershell I think requires quotes: `cordova run android --release "--" --packageType=apk`). Don't forget to remove the preference before you make an actual release, otherwise end users might be able to load up the web inspector for your app. Generally speaking debug builds should work identically to release builds as far as the native cordova shell goes, but release mode has stricter policies for SSL encryptions whereas debug builds often ignore SSL errors to accept self-signed certificates. Loading up the web inspector should give you insight on what is actually happening though. GitHub link: https://github.com/apache/cordova/discussions/422#discussioncomment-6329994 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler edited a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0)
GitHub user leonelgregioauler edited a discussion: Release Version - White screen appears after the splashscreen (only release version, filename.aab) (Cordova 12.0.0) I have a problem. I ran the command: (I use Oracle JET, 14.1) ojet build android --release --buildconfig="C:/PUBLISH/NEOCP3001/build-android.json" The release generates, I upload it to Google Play, I create an internal test version, I download it, I install it on the cell phone, but after the splashscreen is displayed, the screen turns white. The key was generated using the command: keytool -genkey -v -keystore neocp3001.jks -keyalg RSA -keysize 2048 -validity 1 -alias neocp3001 Debug mode installs and runs perfectly! Cordova 12.0.0 Target SDK 33 SDK Build Tools 33.0.2 gradle 7.6 Android Gradle Plugin 7.4.2 JAVA 19    GitHub link: https://github.com/apache/cordova/discussions/422 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an h
GitHub user Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld Thanks @breautek for your info , i will check when i upload my apk or aab to Google Play. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6318028 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] breautek added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an hellowor
GitHub user breautek added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld Google Play Protect is something rather new so I'm not really familiar with the ends and outs of it. But it is software that acts kind of like an antivirus, and if it thinks your app is not trustworthy then it may block it I suppose. https://support.google.com/googleplay/answer/2812853?hl=en So Google Play Protect is a secondary layer of security on top of allowing untrusted APKs. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6317967 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler edited a discussion: Release Version Cordova 12.0.0 - White screen appears after the splashscreen (only release version, filename.aab)
GitHub user leonelgregioauler edited a discussion: Release Version Cordova 12.0.0 - White screen appears after the splashscreen (only release version, filename.aab) I have a problem. I ran the command: (I use Oracle JET, 14.1) ojet build android --release --buildconfig="C:/PUBLISH/NEOCP3001/build-android.json" The release generates, I upload it to Google Play, I create an internal test version, I download it, I install it on the cell phone, but after the splashscreen is displayed, the screen turns white. The key was generated using the command: keytool -genkey -v -keystore neocp3001.jks -keyalg RSA -keysize 2048 -validity 1 -alias neocp3001 Debug mode installs and runs perfectly! Cordova 12.0.0 Target SDK 33 SDK Build Tools 33.0.2 gradle 7.6 Android Gradle Plugin 7.4.2 JAVA 19    GitHub link: https://github.com/apache/cordova/discussions/422 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an h
GitHub user Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld Thanks for your reply , when you said this "if you download an APK from Google Drive, then you must enable Allow from this source on the Google Drive app to install APKs obtained from the Drive app." I did that but also wont let me , i mean , said " the app cannot be installed " but if i disable Play Protect , i can. This change anything but anyway , this app will be upload to Google Store so , i think won't be a problem no ? GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6317833 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] breautek added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an hellowor
GitHub user breautek added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld This is standard Android OS behaviour. By default, only a select few apps can install apps on the device, which is usually Google Play Store and generally the phone manufacturer's app store (e.g. Samsung Galaxy Store). Apps can also be installed to developer devices (phones with USB debugging enabled) via ADB, which is the channel that Cordova uses to install apps onto the device. This is something that needs to be explicitly enabled by the user. If you manually transfer the APK to your device, you must allow the source app that accepted the APK to install APKs on the device. This can be done by going to `Settings -> Security -> Install unknown apps`. On older android versions, install unknown apps is a simple target that was disabled by default, and enabling it will allow you to install APks from untrusted sources. Newer android versions will go into a subscreen where you enable access for specific apps to allow APKs to be installed from specific sources. E.g. if you download an APK from Google Drive, then you must enable `Allow from this source` on the Google Drive app to install APKs obtained from the Drive app. None of these methods is a recommended way of publishing your app if you can help it. Your end users must jump through a lot of security hoops to install your app this fashion. The play stores often have a certain standard that your app must uphere too, which indirectly gives users some sense of trust when they install your app through official play stores. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6317712 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] totalpave deleted a comment on the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an hello
GitHub user totalpave deleted a comment on the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld This is standard Android OS behaviour. By default, only a select few apps can install apps on the device, which is usually Google Play Store and generally the phone manufacturer's app store (e.g. Samsung Galaxy Store). Apps can also be installed to developer devices (phones with USB debugging enabled) via ADB, which is the channel that Cordova uses to install apps onto the device. This is something that needs to be explicitly enabled by the user. If you manually transfer the APK to your device, you must allow the source app that accepted the APK to install APKs on the device. This can be done by going to `Settings -> Security -> Install unknown apps`. On older android versions, install unknown apps is a simple target that was disabled by default, and enabling it will allow you to install APks from untrusted sources. Newer android versions will go into a subscreen where you enable access for specific apps to allow APKs to be installed from specific sources. E.g. if you download an APK from Google Drive, then you must enable `Allow from this source` on the Google Drive app to install APKs obtained from the Drive app. None of these methods is a recommended way of publishing your app if you can help it. Your end users must jump through a lot of security hoops to install your app this fashion. The play stores often have a certain standard that your app must uphere too, which indirectly gives users some sense of trust when they install your app through official play stores. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6317711 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] totalpave added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an hellowo
GitHub user totalpave added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld This is standard Android OS behaviour. By default, only a select few apps can install apps on the device, which is usually Google Play Store and generally the phone manufacturer's app store (e.g. Samsung Galaxy Store). Apps can also be installed to developer devices (phones with USB debugging enabled) via ADB, which is the channel that Cordova uses to install apps onto the device. This is something that needs to be explicitly enabled by the user. If you manually transfer the APK to your device, you must allow the source app that accepted the APK to install APKs on the device. This can be done by going to `Settings -> Security -> Install unknown apps`. On older android versions, install unknown apps is a simple target that was disabled by default, and enabling it will allow you to install APks from untrusted sources. Newer android versions will go into a subscreen where you enable access for specific apps to allow APKs to be installed from specific sources. E.g. if you download an APK from Google Drive, then you must enable `Allow from this source` on the Google Drive app to install APKs obtained from the Drive app. None of these methods is a recommended way of publishing your app if you can help it. Your end users must jump through a lot of security hoops to install your app this fashion. The play stores often have a certain standard that your app must uphere too, which indirectly gives users some sense of trust when they install your app through official play stores. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6317711 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler closed a discussion: Splashscreen - Cordova 12.0.0
GitHub user leonelgregioauler closed a discussion: Splashscreen - Cordova 12.0.0 Hello everyone ! I have a doubt, I'm upgrading to Cordova 12, is the first time that I'm using splashscreen without plugin. Before, my application had used the 10 version. I don't know how is the code that I have to do in config.xml and splashscreen.xml Anyone can help me, please ? Att, GitHub link: https://github.com/apache/cordova/discussions/412 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] leonelgregioauler added a comment to the discussion: Splashscreen - Cordova 12.0.0
GitHub user leonelgregioauler added a comment to the discussion: Splashscreen - Cordova 12.0.0 Hello ! I implemented the functionality and got success! This implementation is better than the old one, certainly Thank you !  GitHub link: https://github.com/apache/cordova/discussions/412#discussioncomment-6317439 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova] Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an h
GitHub user Sebastiangperez added a comment to the discussion: Problem on running apk downloading from whatsapp or google drive, says app not installed, adb and cordova run works, its just an helloworld I know what the problem is , Play Protect , if you disable it , works, but wont work if you press install anyway. GitHub link: https://github.com/apache/cordova/discussions/419#discussioncomment-6316072 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[DISCUSS] Create new mailing list for logging github discussions
I have made the change to github.com/apache/cordova so that all discussion activity will be sent to our (dev) mailing list. There has been some concern raised in slack#pmc that this will flood the dev list which we use specifically for cordova development, and NOT for support. For years now, when anyone has sent a message to the dev list asking a 'how to use cordova' question, we have flatly told them: | "This mailing list is for discussions regarding the development of Apache Cordova and not for support. For support and/or questions about how to use Apache Cordova, please use GitHub Discussions ... " So it does seem a little weird if those discussions end up right back here. A vote will follow shortly (tomorrow) proposing that we create a new mailing list disc...@cordova.apache.org and route all github discussion activity there. Please use this thread to weigh alternatives, of which I see a few: - do nothing, set up your own filters if you are annoyed by the extra email on dev - route this traffic to issues, which is already collecting all gh issues, pull requests and comments - create a new list, but with some other name to avoid confusion with [DISCUSS] threads Cheers, Jesse
[GitHub] [cordova] purplecabbage added a comment to the discussion: We have a new discussion area! 🥳
GitHub user purplecabbage added a comment to the discussion: We have a new discussion area! 🥳 Soon discussions should show up on the dev mailing list too ... GitHub link: https://github.com/apache/cordova/discussions/355#discussioncomment-6310441 This is an automatically sent email for dev@cordova.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #19: june board report
purplecabbage merged PR #19: URL: https://github.com/apache/cordova-apache-board-reports/pull/19 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage opened a new pull request, #19: june board report
purplecabbage opened a new pull request, #19: URL: https://github.com/apache/cordova-apache-board-reports/pull/19 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] purplecabbage commented on pull request #75: GitHub migration proposal
purplecabbage commented on PR #75: URL: https://github.com/apache/cordova-discuss/pull/75#issuecomment-1497997625 This was done ... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] purplecabbage merged pull request #75: GitHub migration proposal
purplecabbage merged PR #75: URL: https://github.com/apache/cordova-discuss/pull/75 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] NiklasMerz closed issue #17: Add reponse to Board feedback on 2022-09-21 to next report
NiklasMerz closed issue #17: Add reponse to Board feedback on 2022-09-21 to next report URL: https://github.com/apache/cordova-apache-board-reports/issues/17 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] jcesarmobile closed issue #59: Document why "AnyCPU" platform is dropped for Windows 10 UWP
jcesarmobile closed issue #59: Document why "AnyCPU" platform is dropped for Windows 10 UWP URL: https://github.com/apache/cordova-discuss/issues/59 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] jcesarmobile commented on issue #59: Document why "AnyCPU" platform is dropped for Windows 10 UWP
jcesarmobile commented on issue #59: URL: https://github.com/apache/cordova-discuss/issues/59#issuecomment-1380589919 closing since the platform is now deprecated -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] jcesarmobile closed issue #96: Rename "osx" platform in a major release?
jcesarmobile closed issue #96: Rename "osx" platform in a major release? URL: https://github.com/apache/cordova-discuss/issues/96 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] jcesarmobile commented on issue #96: Rename "osx" platform in a major release?
jcesarmobile commented on issue #96: URL: https://github.com/apache/cordova-discuss/issues/96#issuecomment-1380589275 closing since the platform is now deprecated -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] jcesarmobile closed issue #25: cordova and languages in projects
jcesarmobile closed issue #25: cordova and languages in projects URL: https://github.com/apache/cordova-discuss/issues/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #18: december
purplecabbage merged PR #18: URL: https://github.com/apache/cordova-apache-board-reports/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Enable github discussions
... and it's live! https://github.com/apache/cordova/discussions On Mon, Nov 21, 2022 at 8:45 AM gandhi rajan wrote: > + 1 > > Github discussions help in easy and transparent interactions. > > On Sun, 20 Nov 2022 at 14:26, Jesse wrote: > > > Hello all, > > > > github discussions are a great way of keeping code conversations very > close > > to the actual code and I think would suit our project better than our use > > of #slack > > > > The apache airflow project switched to use discussions [1] > > This is not configurable via asf.yml [2] and requires an infra ticket > > linking a consensus reaching discussion. [3] > > > > I propose that we enable discussions on the apache/cordova repo [4] to > > evaluate, and we can possibly make a decision to include other repos > later. > > > > What do you think? > > > > Cheers, > > Jesse > > > > [1] > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions-GithubIssuesandDiscussions > > [2] > > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features > > [3] > > > > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions > > [4] https://github.com/apache/cordova > > > > > -- > Regards, > Gandhi > > "The best way to find urself is to lose urself in the service of others > !!!" >
Re: [DISCUSS] Enable github discussions
+ 1 Github discussions help in easy and transparent interactions. On Sun, 20 Nov 2022 at 14:26, Jesse wrote: > Hello all, > > github discussions are a great way of keeping code conversations very close > to the actual code and I think would suit our project better than our use > of #slack > > The apache airflow project switched to use discussions [1] > This is not configurable via asf.yml [2] and requires an infra ticket > linking a consensus reaching discussion. [3] > > I propose that we enable discussions on the apache/cordova repo [4] to > evaluate, and we can possibly make a decision to include other repos later. > > What do you think? > > Cheers, > Jesse > > [1] > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions-GithubIssuesandDiscussions > [2] > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features > [3] > > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions > [4] https://github.com/apache/cordova > -- Regards, Gandhi "The best way to find urself is to lose urself in the service of others !!!"
Re: [DISCUSS] Enable github discussions
+1 to GH Discussions. Hopefully lowers the barrier for folks to engage. And given the amount of "bug reports" that are actually support requests it might be beneficial if we can a) keep the discussion on GitHub b) better preserve the history for future users On Mon, Nov 21, 2022 at 12:52 PM Norman Breau wrote: > For Slack, I've been using an invite link that "does not expire", however, > the invite link does have a limit of 1,000 people. Therefore it's not > very suitable > for a long time usage or as a permanent link and it will need to be > regenerated > occasionally. This is what makes GitHub Discussions much more accessible. > > Additionally, discussions has more powerful organizing features and can > be linked > whereas Slack discussions tends to get lost. > > So +1 from me to use GitHub discussions for support. > > On 2022-11-21 3:10 a.m., Niklas Merz wrote: > > Hey everyone, > > > > I quite like GitHub discussion for support over chat tools like Slack. > > Slack is not really accessible for users and the limitations of the free > > plan are not good. We still could use the official ASF Slack for some > > things like chatting in the PMC, DMs etc. > > > > A nice thing about GitHub discussions is that you can convert > > discussions to issues and vice versa. So it's easy to turn an issue > > which is actually a support question to a discussion or the other way > > around. > > > > Therefore big +1 from me. > > > > On November 20, 2022, Jesse wrote: > >> Hello all, > >> > >> github discussions are a great way of keeping code conversations very > >> close > >> to the actual code and I think would suit our project better than our > >> use > >> of #slack > >> > >> The apache airflow project switched to use discussions [1] > >> This is not configurable via asf.yml [2] and requires an infra ticket > >> linking a consensus reaching discussion. [3] > >> > >> I propose that we enable discussions on the apache/cordova repo [4] to > >> evaluate, and we can possibly make a decision to include other repos > >> later. > >> > >> What do you think? > >> > >> Cheers, > >> Jesse > >> > >> [1] > >> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions- > >> GithubIssuesandDiscussions > >> [2] > >> https://cwiki.apache.org/confluence/display/INFRA/Git+- > >> +.asf.yaml+features > >> [3] > >> https://cwiki.apache.org/confluence/display/INFRA/Git+- > >> +.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions > >> [4] https://github.com/apache/cordova > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > -- Tim Brust timbrust3...@gmail.com
Re: [DISCUSS] Enable github discussions
For Slack, I've been using an invite link that "does not expire", however, the invite link does have a limit of 1,000 people. Therefore it's not very suitable for a long time usage or as a permanent link and it will need to be regenerated occasionally. This is what makes GitHub Discussions much more accessible. Additionally, discussions has more powerful organizing features and can be linked whereas Slack discussions tends to get lost. So +1 from me to use GitHub discussions for support. On 2022-11-21 3:10 a.m., Niklas Merz wrote: Hey everyone, I quite like GitHub discussion for support over chat tools like Slack. Slack is not really accessible for users and the limitations of the free plan are not good. We still could use the official ASF Slack for some things like chatting in the PMC, DMs etc. A nice thing about GitHub discussions is that you can convert discussions to issues and vice versa. So it's easy to turn an issue which is actually a support question to a discussion or the other way around. Therefore big +1 from me. On November 20, 2022, Jesse wrote: Hello all, github discussions are a great way of keeping code conversations very close to the actual code and I think would suit our project better than our use of #slack The apache airflow project switched to use discussions [1] This is not configurable via asf.yml [2] and requires an infra ticket linking a consensus reaching discussion. [3] I propose that we enable discussions on the apache/cordova repo [4] to evaluate, and we can possibly make a decision to include other repos later. What do you think? Cheers, Â Jesse [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions- GithubIssuesandDiscussions [2] https://cwiki.apache.org/confluence/display/INFRA/Git+- +.asf.yaml+features [3] https://cwiki.apache.org/confluence/display/INFRA/Git+- +.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions [4] https://github.com/apache/cordova - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Enable github discussions
Hey everyone, I quite like GitHub discussion for support over chat tools like Slack. Slack is not really accessible for users and the limitations of the free plan are not good. We still could use the official ASF Slack for some things like chatting in the PMC, DMs etc. A nice thing about GitHub discussions is that you can convert discussions to issues and vice versa. So it's easy to turn an issue which is actually a support question to a discussion or the other way around. Therefore big +1 from me. On November 20, 2022, Jesse wrote: > Hello all, > > github discussions are a great way of keeping code conversations very > close > to the actual code and I think would suit our project better than our > use > of #slack > > The apache airflow project switched to use discussions [1] > This is not configurable via asf.yml [2] and requires an infra ticket > linking a consensus reaching discussion. [3] > > I propose that we enable discussions on the apache/cordova repo [4] to > evaluate, and we can possibly make a decision to include other repos > later. > > What do you think? > > Cheers, > Â Jesse > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions- > GithubIssuesandDiscussions > [2] > https://cwiki.apache.org/confluence/display/INFRA/Git+- > +.asf.yaml+features > [3] > https://cwiki.apache.org/confluence/display/INFRA/Git+- > +.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions > [4] https://github.com/apache/cordova
[DISCUSS] Enable github discussions
Hello all, github discussions are a great way of keeping code conversations very close to the actual code and I think would suit our project better than our use of #slack The apache airflow project switched to use discussions [1] This is not configurable via asf.yml [2] and requires an infra ticket linking a consensus reaching discussion. [3] I propose that we enable discussions on the apache/cordova repo [4] to evaluate, and we can possibly make a decision to include other repos later. What do you think? Cheers, Jesse [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions-GithubIssuesandDiscussions [2] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features [3] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions [4] https://github.com/apache/cordova
[GitHub] [cordova-apache-board-reports] NiklasMerz commented on issue #17: Add reponse to Board feedback on 2022-09-21 to next report
NiklasMerz commented on issue #17: URL: https://github.com/apache/cordova-apache-board-reports/issues/17#issuecomment-1284384421 I just created the issue so we don't forget that. Came acros the email again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage commented on issue #17: Add reponse to Board feedback on 2022-09-21 to next report
purplecabbage commented on issue #17: URL: https://github.com/apache/cordova-apache-board-reports/issues/17#issuecomment-1284321120 https://github.com/purplecabbage/slack-digestr -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage commented on issue #17: Add reponse to Board feedback on 2022-09-21 to next report
purplecabbage commented on issue #17: URL: https://github.com/apache/cordova-apache-board-reports/issues/17#issuecomment-1284278837 Yeah, running daily. I was going to answer this at the next meeting. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] timbru31 commented on issue #17: Add reponse to Board feedback on 2022-09-21 to next report
timbru31 commented on issue #17: URL: https://github.com/apache/cordova-apache-board-reports/issues/17#issuecomment-1283978286 Hej @purplecabbage, is the automated export thing still up and running? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] NiklasMerz opened a new issue, #17: Add reponse to Board feedback on 2022-09-21 to next report
NiklasMerz opened a new issue, #17: URL: https://github.com/apache/cordova-apache-board-reports/issues/17 ``` Comments: cd: You say, the primary channel for helping is the cordova slack. As there is no #cordova in the ASF slack, I assume it's an external one. Is there any form of archive of old questions and searchability? Or is this used entirely for support and not for discussions about the project itself? This feedback was generated automatically by the secretary from the comments made on your board report. Comments that do not ask specific questions should be noted by the PMC and taken into consideration as appropriate for future board reports. Where a comment asks a specific question, it should be answered in your next board report unless otherwise stated in the comment. If you have any queries or concerns regarding any of the comments they should be sent to the board@ mailing list. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu merged pull request #20: docs: update README.md
erisu merged PR #20: URL: https://github.com/apache/cordova-status/pull/20 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu opened a new pull request, #20: docs: update README.md
erisu opened a new pull request, #20: URL: https://github.com/apache/cordova-status/pull/20 * Remove deprecated platforms OSX and Windows * Remove deprecated action results Android and iOS for splashscreen plugin * Added ESLint * Sorted lists in ascending order -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #16: June 2022 Board Report
purplecabbage merged PR #16: URL: https://github.com/apache/cordova-apache-board-reports/pull/16 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] jcesarmobile commented on pull request #16: June 2022 Board Report
jcesarmobile commented on PR #16: URL: https://github.com/apache/cordova-apache-board-reports/pull/16#issuecomment-1148479486 Maybe mention the removal of one PMC member on the community changes section? And the deprecation of cordova-osx? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Good and less good ways to handle grumpy GitHub comments
Hi Julio, I apologize for singling out Norman's comment. That was unnecessary. From now on I will limit myself to pointing out positive examples. I agree that it's better not to make grumpy comments in the first place. I will think twice in future. One thing I would say is that, as a maker of software myself, I want more feedback, positive and negative. And I especially want to know when I break something. (This is not to say that you should love my grumpy comments. I'm only describing my approach. Yours is up to you.) So if a user can only manage a grumpy comment, I welcome it the way Adam does in the other repo. Because if I don't, I produce more people who are silently throwing their mouse against the wall after a two-hour troubleshooting session. And this is not what I want. Again, just in case: I'm pointing out my approach as a positive example. I'm not saying that you should do it like that. I'm not saying your way is wrong. I'm not saying my grumpy comment was right. I'm not trying to embarrass anybody. (Although my first email came across that way and I'm sorry for that.) Best, Richard > On 14 May 2022, at 20:34, julio cesar sanchez wrote: > > Being grumpy causes more grumpiness. You can start by not being grumpy to > unpaid volunteers that are dedicating a considerable amount of their spare > time to maintain the tools you use for free. > I see Norman’s comment totally correct, we make breaking changes every year > on every major version. If your problem is related to the whitelist name > change, the fix should be as easy as uninstalling the plugin. That would > have happened even if the name didn’t change because the plugin was > integrated into the platform, so you would have to uninstall the plugin > anyway. > > He invites you to the mail list to discuss how we can improve the release > process to make breaking changes easier to manage and instead of proposing > constructive things like creating an upgrade guide, you bring more > grumpiness by commenting how we should answer to grumpy users and try to > embarrass him in front of the list. > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: Good and less good ways to handle grumpy GitHub comments
Being grumpy causes more grumpiness. You can start by not being grumpy to unpaid volunteers that are dedicating a considerable amount of their spare time to maintain the tools you use for free. I see Norman’s comment totally correct, we make breaking changes every year on every major version. If your problem is related to the whitelist name change, the fix should be as easy as uninstalling the plugin. That would have happened even if the name didn’t change because the plugin was integrated into the platform, so you would have to uninstall the plugin anyway. He invites you to the mail list to discuss how we can improve the release process to make breaking changes easier to manage and instead of proposing constructive things like creating an upgrade guide, you bring more grumpiness by commenting how we should answer to grumpy users and try to embarrass him in front of the list. El El sáb, 14 may 2022 a las 11:46, Richard Möhn escribió: > Hi folks, > > a drive-by note – this is a great way to handle a grumpy comment on GitHub: > > https://github.com/apokalipto/devise_saml_authenticatable/pull/213#issuecomment-1126197865 > > This way of handling a grumpy comment causes more grumpiness: > https://github.com/apache/cordova-android/pull/1138#issuecomment-1104923029 > > Best, > > Richard > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Good and less good ways to handle grumpy GitHub comments
Hi folks, a drive-by note – this is a great way to handle a grumpy comment on GitHub: https://github.com/apokalipto/devise_saml_authenticatable/pull/213#issuecomment-1126197865 This way of handling a grumpy comment causes more grumpiness: https://github.com/apache/cordova-android/pull/1138#issuecomment-1104923029 Best, Richard - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-plugin-splashscreen] NiklasMerz commented on a diff in pull request #310: applied changes in SplashScreen that allows get ScaleType and backgroundColor from preferences
NiklasMerz commented on code in PR #310:
URL:
https://github.com/apache/cordova-plugin-splashscreen/pull/310#discussion_r841481621
##
src/android/SplashScreen.java:
##
@@ -393,6 +390,7 @@ public void onCancel(DialogInterface dialog) {
spinnerDialog.getWindow().clearFlags(WindowManager.LayoutParams.FLAG_DIM_BEHIND);
spinnerDialog.getWindow().setBackgroundDrawable(new
ColorDrawable(Color.TRANSPARENT));
+spinnerDialog.getWindow().setGravity(Gravity.CENTER);
Review Comment:
This [PR](https://github.com/apache/cordova-plugin-splashscreen/pull/234) is
already about this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #15: March 2022 board report
purplecabbage merged pull request #15: URL: https://github.com/apache/cordova-apache-board-reports/pull/15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu merged pull request #19: chore: display formatting & plugman badge path
erisu merged pull request #19: URL: https://github.com/apache/cordova-status/pull/19 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu opened a new pull request #19: chore: display formatting & plugman badge path
erisu opened a new pull request #19: URL: https://github.com/apache/cordova-status/pull/19 * Cleanup the display formatting for plugins & paramedic. Each action displays on its own line. * Updated the plugman badge path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu merged pull request #18: doc: update plugin ci badges
erisu merged pull request #18: URL: https://github.com/apache/cordova-status/pull/18 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] erisu opened a new pull request #18: doc: update plugin ci badges
erisu opened a new pull request #18: URL: https://github.com/apache/cordova-status/pull/18 Display GH Action CI Badges for Plugins -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #14: Create 2021-09.md
purplecabbage merged pull request #14: URL: https://github.com/apache/cordova-apache-board-reports/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage closed issue #12: Board calendar for 2020
purplecabbage closed issue #12: URL: https://github.com/apache/cordova-apache-board-reports/issues/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage commented on issue #12: Board calendar for 2020
purplecabbage commented on issue #12: URL: https://github.com/apache/cordova-apache-board-reports/issues/12#issuecomment-916647601 done -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] purplecabbage commented on issue #24: New committer and PMC member (2021-3-27)
purplecabbage commented on issue #24: URL: https://github.com/apache/cordova-new-committer-and-pmc/issues/24#issuecomment-814392103 Welcome aboard Pieter! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] purplecabbage closed issue #24: New committer and PMC member (2021-3-27)
purplecabbage closed issue #24: URL: https://github.com/apache/cordova-new-committer-and-pmc/issues/24 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] timbru31 merged pull request #25: chore: create .asf.yml file to configure repo metdata
timbru31 merged pull request #25: URL: https://github.com/apache/cordova-new-committer-and-pmc/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] timbru31 commented on a change in pull request #25: chore: create .asf.yml file to configure repo metdata
timbru31 commented on a change in pull request #25: URL: https://github.com/apache/cordova-new-committer-and-pmc/pull/25#discussion_r607834137 ## File path: .asf.yml ## @@ -0,0 +1,41 @@ + Review comment: ```suggestion ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] purplecabbage commented on issue #24: New committer and PMC member (2021-3-27)
purplecabbage commented on issue #24: URL: https://github.com/apache/cordova-new-committer-and-pmc/issues/24#issuecomment-812117934 Account created, waiting for `... 72 hours has elapsed from the board@ notice ...` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] timbru31 opened a new pull request #25: chore: create .asf.yml file to repo metdata
timbru31 opened a new pull request #25: URL: https://github.com/apache/cordova-new-committer-and-pmc/pull/25 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] timbru31 merged pull request #23: [RFC] add pointers to gpg guides
timbru31 merged pull request #23: URL: https://github.com/apache/cordova-new-committer-and-pmc/pull/23 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] timbru31 commented on a change in pull request #23: [RFC] add pointers to gpg guides
timbru31 commented on a change in pull request #23: URL: https://github.com/apache/cordova-new-committer-and-pmc/pull/23#discussion_r603097116 ## File path: .github/ISSUE_TEMPLATE/NEW_COMMITTER_AND_PMC.md ## @@ -20,5 +20,7 @@ See the [README](../README.md) for details on each of the steps. - [ ] 8. Add the PMC member to the JIRA 'PMC' User Role [[details]](https://github.com/apache/cordova-new-committer-and-pmc#8-add-the-pmc-member-to-the-jira-pmc-user-role) - [ ] 9. Ask the PMC member to link their GitHub account [[details]](https://github.com/apache/cordova-new-committer-and-pmc#9-ask-the-pmc-member-to-link-their-github-account) - [ ] 10. Invite the PMC member to the `#pmc` Slack channel [[details]](https://github.com/apache/cordova-new-committer-and-pmc#10-invite-the-pmc-member-to-the-pmc-slack-channel) -- [ ] 11. Optional: offer npm publish rights to the new PMC member, if requested and required +- [ ] 11. Optional: offer npm publish rights to the new PMC member, if requested and required; should send a pointer to the following guides to setting up gpg to sign releases: Review comment: ```suggestion - [ ] 11. Optional: offer npm publish rights to the new PMC member, if requested and required; should send a pointer to the following guides to setting up gpg to sign and validate releases: ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-new-committer-and-pmc] breautek opened a new issue #24: New committer and PMC member (2021-3-27)
breautek opened a new issue #24: URL: https://github.com/apache/cordova-new-committer-and-pmc/issues/24 **DO NOT** add the potential candidate's name here since a vote can fail, an invitation can be rejected, or the Apache Board can veto PMC inclusion (but not the vote for a committer). See the [README](../README.md) for details on each of the steps. # Checklist - [x] 1. Send a [VOTE] thread to private@ [[details]](https://github.com/apache/cordova-new-committer-and-pmc#1-send-a-vote-thread-to-private) - [ ] 2. Wait three days (72 hours) or when there is a clear consensus, then close the [VOTE] [[details]](https://github.com/apache/cordova-new-committer-and-pmc/blob/master/README.md#2-wait-three-days-72-hours-or-when-there-is-a-clear-consensus-then-close-the-vote) - [ ] 3. Send an Invite email to the community member, cc private@ [[details]](https://github.com/apache/cordova-new-committer-and-pmc#3-send-an-invite-email-to-the-community-member-cc-private) - [ ] 4. Send a PMC Notice to board@, and cc private@ [[details]](https://github.com/apache/cordova-new-committer-and-pmc#4-send-a-pmc-notice-to-board-and-cc-private) - [ ] 5. When the new committer accepts the invite, create a new account for the user (PMC Chair only) [[details]](https://github.com/apache/cordova-new-committer-and-pmc#5-when-the-new-committer-accepts-the-invite-create-a-new-account-for-the-user-pmc-chair-only) - [ ] 6. Once 72 hours has elapsed from the board@ notice, add the committer to the PMC committee-info.txt file and LDAP (PMC Chair)[[details]](https://github.com/apache/cordova-new-committer-and-pmc#6-once-72-hours-has-elapsed-from-the-board-notice-add-the-committer-to-the-pmc-committee-infotxt-file-and-ldap-any-pmc-chair) - [ ] 7. Add the PMC member to the private@ list [[details]](https://github.com/apache/cordova-new-committer-and-pmc#7-automatically-subscribe-the-new-pmc-member-to-the-private-list) - [ ] 8. Add the PMC member to the JIRA 'PMC' User Role [[details]](https://github.com/apache/cordova-new-committer-and-pmc#8-add-the-pmc-member-to-the-jira-pmc-user-role) - [ ] 9. Ask the PMC member to link their GitHub account [[details]](https://github.com/apache/cordova-new-committer-and-pmc#9-ask-the-pmc-member-to-link-their-github-account) - [ ] 10. Invite the PMC member to the `#pmc` Slack channel [[details]](https://github.com/apache/cordova-new-committer-and-pmc#10-invite-the-pmc-member-to-the-pmc-slack-channel) - [ ] 11. Optional: offer npm publish rights to the new PMC member, if requested and required - [ ] Close this issue with a resolution note -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] breautek merged pull request #111: Fix markdown syntax for link and misspelling in FAQ
breautek merged pull request #111: URL: https://github.com/apache/cordova-discuss/pull/111 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] theblang opened a new pull request #111: Fix markdown syntax for link in FAQ
theblang opened a new pull request #111: URL: https://github.com/apache/cordova-discuss/pull/111 Was reading the FAQ, particularly the section about cookies, and noticed there was a space between the `[]` and the `()`, preventing the markdown link from rendering properly. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-status] dpogue opened a new issue #17: Update badges to GitHub Actions
dpogue opened a new issue #17: URL: https://github.com/apache/cordova-status/issues/17 We're using GitHub Actions for all the tooling repos now, and most of the platform repos. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #13: Add 2020-12.md
purplecabbage merged pull request #13: URL: https://github.com/apache/cordova-apache-board-reports/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage opened a new pull request #13: Add 2020-12.md
purplecabbage opened a new pull request #13: URL: https://github.com/apache/cordova-apache-board-reports/pull/13 work in progress This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: GitHub Actions for paramedic and plugins
Hey Tim I am maybe a little late to the party. But this is a great effort. It would be absolutely great to have a stable and working CI (testing) system. Now when you submit a PR, the tests on CI are mostly red. That's annoying. Losing ios 11.4 wouldn't be a disaster. Kind regards Pieter Van Poyer 1700 DI/DB Havenbedrijf Antwerpen/Antwerp Port Authority Zaha Hadidplein 1 2030 Antwerpen, België T +32 3 229 76 85 pieter.vanpo...@portofantwerp.com -Oorspronkelijk bericht- Van: Brust, Tim Verzonden: donderdag 26 november 2020 15:26 Aan: dev@cordova.apache.org Onderwerp: GitHub Actions for paramedic and plugins Hi there, As you might have noticed, our CI is currently red. While it's great that we do not block our releases because of it, it's not an ideal situation. A short background why is broken: We use Travis CI's virtual machines to execute our tests in combination with Sauce Labs, i.e., cordova-paramedic that runs on the Travis CI VM opens a secure tunnel to the Sauce Labs selenium grid. This allows for instance to test an iOS simulator on a Windows machine, as the simulator/emulator runs on another machine and communicates via the WebDriver protocol. Sauce Labs offers real mobile devices and virtualized ones. We only use the latter. [1] Unfortunately, there is a network issue between the Sauce Labs and the Travis CI VM's, the tunnel seems established but no network requests come through - but not for all combos, just for some. I've reached out to Travis CI's support and they pointed the finger to Sauce Labs. Multiple attempts to have a real network engineer assigned to this task instead of the service level 1 assignee failed and they've just closed the ticket. On top of this issue lies the problem with external contributions (i.e., outside from the Apache organization). Obviously, Sauce Labs needs some sort of credentials to work. We use the deprecated JWT addon at Travis [2], which might be disabled at any time, too. Sadly, there is no known solution on how to securely pass the credentials to external forks/pull requests. There is no solution on how to make secrets available to forks on GitHub Actions neither. As we are moving to GitHub Actions (or at least that's our goal), I've taken a look how to tackle the above problem. Given the fact that we test simulators and emulators on Sauce Labs anyways, we might be able to execute everything via GitHub Actions only, i.e., no credentials issue. The GitHub Actions runner have a big variety of available Xcode and iOS versions in their virtual environments. [3] And to have some good news - iOS works! [4] - the only downside is that we can't test iOS 11.4, but IMHO this loss would be OK. In theory, Android works, too. With the help of the reactivecircus/android-emulator-runner action we can setup the emulators with a specific target API level. It also handles accepting the permissions etc. [5] At least, the logs show that the emulator booted and some things happened (like installing the APK) For the browser tests, some changes in cordova-serve would be needed. In order to launch Chrome, Firefox etc. in headless mode, we would need to pass those arguments. Currently there is an open issue to add this functionality. [6] My plan for the next week(s) is to investigate the Android timeouts and to test if a patch in cordova-serve would be enough to make headless launching possible to make the CI green. If this works, we would have a blueprint that could be copied to the plugins. With the matrix syntax of GitHub Actions we can generate an easy to maintain and extendable testing matrix. One feature I really like is splitting the configs in different files, as opposed to the gigantic .travis.yml. Let me know what you think, I'm eager to get some feedback. My work can be seen in the feature branch feat/gh-actions [7], especially this commit: [8] Cheers, Tim [1] - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp.saucelabs.com%2Fopen_sauce%2Fuser%2Fsnay%2Ftests&data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ca73853478c014d3b99c508d892172a68%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637419975492593209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4n5QjT2zqfDVCOiu%2FMiz6cMsLn9LvhSBqXBBGpgMnJA%3D&reserved=0 [2] - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.travis-ci.com%2F2018-01-23-jwt-addon-is-deprecated&data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ca73853478c014d3b99c508d892172a68%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637419975492593209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5RZBQeg%2FNYeEUK4VJrLrnDyXKID1dbqMmpFYftkOOeI%3D&reserved=0 [3] - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Factions%2Fvi
[GitHub] [cordova-test-platform] breautek merged pull request #19: chore: package-lock
breautek merged pull request #19: URL: https://github.com/apache/cordova-test-platform/pull/19 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] breautek opened a new pull request #19: chore: package-lock
breautek opened a new pull request #19: URL: https://github.com/apache/cordova-test-platform/pull/19 ### Platforms affected ### Motivation and Context Progresses https://github.com/apache/cordova/issues/4 ### Description ### Testing ### Checklist - [ ] I've run the tests to see all new and existing tests pass - [ ] I added automated test coverage as appropriate for this change - [ ] Commit is prefixed with `(platform)` if this change only applies to one platform (e.g. `(android)`) - [ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct [keyword to close issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)) - [ ] I've updated the documentation if necessary This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
GitHub Actions for paramedic and plugins
Hi there, As you might have noticed, our CI is currently red. While it’s great that we do not block our releases because of it, it’s not an ideal situation. A short background why is broken: We use Travis CI’s virtual machines to execute our tests in combination with Sauce Labs, i.e., cordova-paramedic that runs on the Travis CI VM opens a secure tunnel to the Sauce Labs selenium grid. This allows for instance to test an iOS simulator on a Windows machine, as the simulator/emulator runs on another machine and communicates via the WebDriver protocol. Sauce Labs offers real mobile devices and virtualized ones. We only use the latter. [1] Unfortunately, there is a network issue between the Sauce Labs and the Travis CI VM’s, the tunnel seems established but no network requests come through – but not for all combos, just for some. I’ve reached out to Travis CI’s support and they pointed the finger to Sauce Labs. Multiple attempts to have a real network engineer assigned to this task instead of the service level 1 assignee failed and they’ve just closed the ticket. On top of this issue lies the problem with external contributions (i.e., outside from the Apache organization). Obviously, Sauce Labs needs some sort of credentials to work. We use the deprecated JWT addon at Travis [2], which might be disabled at any time, too. Sadly, there is no known solution on how to securely pass the credentials to external forks/pull requests. There is no solution on how to make secrets available to forks on GitHub Actions neither. As we are moving to GitHub Actions (or at least that’s our goal), I’ve taken a look how to tackle the above problem. Given the fact that we test simulators and emulators on Sauce Labs anyways, we might be able to execute everything via GitHub Actions only, i.e., no credentials issue. The GitHub Actions runner have a big variety of available Xcode and iOS versions in their virtual environments. [3] And to have some good news – iOS works! [4] – the only downside is that we can’t test iOS 11.4, but IMHO this loss would be OK. In theory, Android works, too. With the help of the reactivecircus/android-emulator-runner action we can setup the emulators with a specific target API level. It also handles accepting the permissions etc. [5] At least, the logs show that the emulator booted and some things happened (like installing the APK) For the browser tests, some changes in cordova-serve would be needed. In order to launch Chrome, Firefox etc. in headless mode, we would need to pass those arguments. Currently there is an open issue to add this functionality. [6] My plan for the next week(s) is to investigate the Android timeouts and to test if a patch in cordova-serve would be enough to make headless launching possible to make the CI green. If this works, we would have a blueprint that could be copied to the plugins. With the matrix syntax of GitHub Actions we can generate an easy to maintain and extendable testing matrix. One feature I really like is splitting the configs in different files, as opposed to the gigantic .travis.yml. Let me know what you think, I’m eager to get some feedback. My work can be seen in the feature branch feat/gh-actions [7], especially this commit: [8] Cheers, Tim [1] - https://app.saucelabs.com/open_sauce/user/snay/tests [2] - https://blog.travis-ci.com/2018-01-23-jwt-addon-is-deprecated [3] - https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xcode [4] - https://github.com/apache/cordova-paramedic/actions/runs/385358819 [5] - https://github.com/ReactiveCircus/android-emulator-runner [6] - https://github.com/apache/cordova-serve/issues/18 [7] - https://github.com/apache/cordova-paramedic/tree/feat/gh-actions [8] - https://github.com/apache/cordova-paramedic/commit/6657551feae3840b9f4fa3a8fc23010515b5b87f -- Tim Brust, Product Engineer tim.br...@sinnerschrader.com<mailto:tim.br...@sinnerschrader.com> SinnerSchrader Deutschland GmbH | SinnerSchrader Group Part of Accenture Interactive Völckersstraße 38, 22765 Hamburg, Germany Amtsgericht Hamburg HRB-Nr. 63663 Geschäftsführung: Dr. Axel Averdung (Sprecher), Holger Blank, Kristina Bonitz, Peggy Hutchinson, Philipp Kafkoulas, Florian Langmack, Sven Schmiede, Pia Schott Büros: Berlin, Hamburg, Frankfurt a. M., München, Prag www.sinnerschrader.com | NEXT AGENCY This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.
[GitHub] [cordova-discuss] timbru31 closed issue #57: cordova-android 6.0.0 (installed by cordova-cli 6.4.0) drops result with u2028/u2029
timbru31 closed issue #57: URL: https://github.com/apache/cordova-discuss/issues/57 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-discuss] timbru31 commented on issue #57: cordova-android 6.0.0 (installed by cordova-cli 6.4.0) drops result with u2028/u2029
timbru31 commented on issue #57: URL: https://github.com/apache/cordova-discuss/issues/57#issuecomment-728810659 I'm closing this stale issue, I bet this already has been solved. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] raphinesse merged pull request #17: pkg fixup
raphinesse merged pull request #17: URL: https://github.com/apache/cordova-test-platform/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] raphinesse commented on a change in pull request #17: pkg fixup
raphinesse commented on a change in pull request #17: URL: https://github.com/apache/cordova-test-platform/pull/17#discussion_r499161520 ## File path: package.json ## @@ -18,17 +20,6 @@ "author": "Apache Software Foundation", "license": "Apache-2.0", "bugs": "https://github.com/apache/cordova-test-platform/issues";, - "homepage": "https://github.com/cordova/cordova-test-platform#readme";, Review comment: I removed it since only four packages had this field set at all. Two of them to the default value This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] timbru31 merged pull request #18: chore(asf): update git notification settings
timbru31 merged pull request #18: URL: https://github.com/apache/cordova-test-platform/pull/18 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] timbru31 opened a new pull request #18: chore(asf): update git notification settings
timbru31 opened a new pull request #18: URL: https://github.com/apache/cordova-test-platform/pull/18 ### Platforms affected ### Motivation and Context ### Description ### Testing ### Checklist - [ ] I've run the tests to see all new and existing tests pass - [ ] I added automated test coverage as appropriate for this change - [ ] Commit is prefixed with `(platform)` if this change only applies to one platform (e.g. `(android)`) - [ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct [keyword to close issues using keywords](https://help.github.com/articles/closing-issues-using-keywords/)) - [ ] I've updated the documentation if necessary This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] erisu commented on a change in pull request #17: pkg fixup
erisu commented on a change in pull request #17: URL: https://github.com/apache/cordova-test-platform/pull/17#discussion_r499159095 ## File path: package.json ## @@ -18,17 +20,6 @@ "author": "Apache Software Foundation", "license": "Apache-2.0", "bugs": "https://github.com/apache/cordova-test-platform/issues";, - "homepage": "https://github.com/cordova/cordova-test-platform#readme";, Review comment: Looks like you are removing it instead from everywhere. So I approved it. Thought it might have been better to point to the actual home page so people coming from npmjs has a quick link to our home page. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] erisu commented on a change in pull request #17: pkg fixup
erisu commented on a change in pull request #17: URL: https://github.com/apache/cordova-test-platform/pull/17#discussion_r499158727 ## File path: package.json ## @@ -18,17 +20,6 @@ "author": "Apache Software Foundation", "license": "Apache-2.0", "bugs": "https://github.com/apache/cordova-test-platform/issues";, - "homepage": "https://github.com/cordova/cordova-test-platform#readme";, Review comment: Is this meant to be removed? Description did not mention it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] raphinesse opened a new pull request #17: pkg fixup
raphinesse opened a new pull request #17: URL: https://github.com/apache/cordova-test-platform/pull/17 - chore(pkg): remove field "maintainers" - fix(pkg): fix declaration for binary "create" This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] raphinesse merged pull request #16: chore: clean up package.json
raphinesse merged pull request #16: URL: https://github.com/apache/cordova-test-platform/pull/16 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-test-platform] raphinesse opened a new pull request #16: chore: clean up package.json
raphinesse opened a new pull request #16: URL: https://github.com/apache/cordova-test-platform/pull/16 See https://github.com/apache/cordova/issues/55 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] timbru31 opened a new issue #12: Board calendar for 2020
timbru31 opened a new issue #12: URL: https://github.com/apache/cordova-apache-board-reports/issues/12 @purplecabbage The board calendar is very outdated. Can you gather the newest dates? Otherwise, I'd vote to remove it from the README. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
[GitHub] [cordova-apache-board-reports] purplecabbage merged pull request #11: Sept 2020 board report
purplecabbage merged pull request #11: URL: https://github.com/apache/cordova-apache-board-reports/pull/11 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
