RE: [DRAFT] December PLC4X board report
Yeah ... guess that was simply a copy+paste error on my side when sending the email. I've submitted the report. Chris -Original Message- From: Sebastian Rühl Sent: Donnerstag, 2. Dezember 2021 20:22 To: dev@plc4x.apache.org Subject: Re: [DRAFT] December PLC4X board report Other than that why do we have 2 times the ## Issues section? - Sebastian On 2021/12/02 15:07:02 Christofer Dutz wrote: > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries > for communicating with industrial programmable logic controllers > (PLCs) using a variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a > bit of an absence of PMC coverage however regarding things cominig up > on the mailinglists (dev and private) > > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries > for communicating with industrial programmable logic controllers > (PLCs) using a variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a > bit of an absence of PMC coverage however regarding things cominig up > on the mailinglists (dev and private) > > ## Membership Data: > Apache PLC4X was founded 2019-04-17 (3 years ago) There are currently > 19 committers and 13 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:4. > > Community changes, past quarter: > - César García was added to the PMC on 2021-10-01 > - No new committers. Last addition was Thomas Frost on 2021-05-07. > > ## Project Activity: > After finishing the work for the next release some members of the > community have invested a lot of time into a complete refactoring of > our codebase for the code-generation. This was needed in order to be > able to support more situations needed for new drivers, but also for > cleaning up stuff to make it more easily understandable for others. > Others have been working on adding very cool new features to the S7 driver as > well as working on the CAN-drivers. > > We had talks at 4 conferences: > - ApacheCon @Home (2 Talks) > - LF OSS-Summit (1 Talk) > - Eclipse Con (1 Talk) > - IoT Conference (1 Talk) > > ## Community Health: > We are getting more and more reports of people using plc4x and getting > bug reports. That's great. However contributions have been coming in > from 11% less individuals compared to the previous quarter. Hopefully, > in 2022 we will be able to do in-person events again, to strengthen the sense > of community again. > I am feeling as we are loosing grip of each other after 2 years of > absolutely no in-person events. In the past especially these events > have been helping with building the commnunity. >
[GitHub] [plc4x] dependabot[bot] closed pull request #277: build(deps): bump scala-library from 2.10.7 to 2.13.6
dependabot[bot] closed pull request #277: URL: https://github.com/apache/plc4x/pull/277 -- 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...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [plc4x] dependabot[bot] commented on pull request #277: build(deps): bump scala-library from 2.10.7 to 2.13.6
dependabot[bot] commented on pull request #277: URL: https://github.com/apache/plc4x/pull/277#issuecomment-985243901 Superseded by #289. -- 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...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [plc4x-build-tools] dependabot[bot] opened a new pull request #16: build(deps): bump commons-io from 2.6 to 2.11.0
dependabot[bot] opened a new pull request #16: URL: https://github.com/apache/plc4x-build-tools/pull/16 Bumps commons-io from 2.6 to 2.11.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-io:commons-io=maven=2.6=2.11.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [plc4x-build-tools] dependabot[bot] opened a new pull request #15: build(deps): bump commons-beanutils from 1.9.3 to 1.9.4
dependabot[bot] opened a new pull request #15: URL: https://github.com/apache/plc4x-build-tools/pull/15 Bumps commons-beanutils from 1.9.3 to 1.9.4. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=commons-beanutils:commons-beanutils=maven=1.9.3=1.9.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[BUILD-UNSTABLE]: Job 'PLC4X/PLC4X/develop [develop] [709]'
BUILD-UNSTABLE: Job 'PLC4X/PLC4X/develop [develop] [709]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/709/;>PLC4X/PLC4X/develop [develop] [709]"
Re: [DRAFT] December PLC4X board report
Other than that why do we have 2 times the ## Issues section? - Sebastian On 2021/12/02 15:07:02 Christofer Dutz wrote: > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Membership Data: > Apache PLC4X was founded 2019-04-17 (3 years ago) > There are currently 19 committers and 13 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:4. > > Community changes, past quarter: > - César García was added to the PMC on 2021-10-01 > - No new committers. Last addition was Thomas Frost on 2021-05-07. > > ## Project Activity: > After finishing the work for the next release some members of the community > have invested a lot of time into a complete refactoring of our codebase for > the code-generation. This was needed in order to be able to support more > situations needed for new drivers, but also for cleaning up stuff to make it > more easily understandable for others. Others have been working on adding very > cool new features to the S7 driver as well as working on the CAN-drivers. > > We had talks at 4 conferences: > - ApacheCon @Home (2 Talks) > - LF OSS-Summit (1 Talk) > - Eclipse Con (1 Talk) > - IoT Conference (1 Talk) > > ## Community Health: > We are getting more and more reports of people using plc4x and getting bug > reports. That's great. However contributions have been coming in from 11% less > individuals compared to the previous quarter. Hopefully, in 2022 we will be > able to do in-person events again, to strengthen the sense of community again. > I am feeling as we are loosing grip of each other after 2 years of absolutely > no in-person events. In the past especially these events have been helping > with building the commnunity. >
Re: [DRAFT] December PLC4X board report
LGTM +1 On 2021/12/02 15:07:02 Christofer Dutz wrote: > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Membership Data: > Apache PLC4X was founded 2019-04-17 (3 years ago) > There are currently 19 committers and 13 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:4. > > Community changes, past quarter: > - César García was added to the PMC on 2021-10-01 > - No new committers. Last addition was Thomas Frost on 2021-05-07. > > ## Project Activity: > After finishing the work for the next release some members of the community > have invested a lot of time into a complete refactoring of our codebase for > the code-generation. This was needed in order to be able to support more > situations needed for new drivers, but also for cleaning up stuff to make it > more easily understandable for others. Others have been working on adding very > cool new features to the S7 driver as well as working on the CAN-drivers. > > We had talks at 4 conferences: > - ApacheCon @Home (2 Talks) > - LF OSS-Summit (1 Talk) > - Eclipse Con (1 Talk) > - IoT Conference (1 Talk) > > ## Community Health: > We are getting more and more reports of people using plc4x and getting bug > reports. That's great. However contributions have been coming in from 11% less > individuals compared to the previous quarter. Hopefully, in 2022 we will be > able to do in-person events again, to strengthen the sense of community again. > I am feeling as we are loosing grip of each other after 2 years of absolutely > no in-person events. In the past especially these events have been helping > with building the commnunity. >
Re: [DRAFT] December PLC4X board report
+1 El jue, 2 dic 2021 a las 11:07, Christofer Dutz () escribió: > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of > an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of > an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Membership Data: > Apache PLC4X was founded 2019-04-17 (3 years ago) > There are currently 19 committers and 13 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:4. > > Community changes, past quarter: > - César García was added to the PMC on 2021-10-01 > - No new committers. Last addition was Thomas Frost on 2021-05-07. > > ## Project Activity: > After finishing the work for the next release some members of the community > have invested a lot of time into a complete refactoring of our codebase for > the code-generation. This was needed in order to be able to support more > situations needed for new drivers, but also for cleaning up stuff to make > it > more easily understandable for others. Others have been working on adding > very > cool new features to the S7 driver as well as working on the CAN-drivers. > > We had talks at 4 conferences: > - ApacheCon @Home (2 Talks) > - LF OSS-Summit (1 Talk) > - Eclipse Con (1 Talk) > - IoT Conference (1 Talk) > > ## Community Health: > We are getting more and more reports of people using plc4x and getting bug > reports. That's great. However contributions have been coming in from 11% > less > individuals compared to the previous quarter. Hopefully, in 2022 we will be > able to do in-person events again, to strengthen the sense of community > again. > I am feeling as we are loosing grip of each other after 2 years of > absolutely > no in-person events. In the past especially these events have been helping > with building the commnunity. > -- *CEOS Automatización, C.A.* *GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,* *PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,* *FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI* *Ing. César García* *Cel: +58 414-760.98.95* *Hotline Técnica SIEMENS: 0800 1005080* *Email: support.aan.automat...@siemens.com *
Re: [DRAFT] December PLC4X board report
+1 Am Do., 2. Dez. 2021 um 16:07 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of > an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Description: > The mission of the Apache PLC4X project is creating a set of libraries for > communicating with industrial programmable logic controllers (PLCs) using a > variety of protocols but with a shared API. > > ## Issues: > There are currently no issues requiring board attention. I do see a bit of > an > absence of PMC coverage however regarding things cominig up on the > mailinglists (dev and private) > > ## Membership Data: > Apache PLC4X was founded 2019-04-17 (3 years ago) > There are currently 19 committers and 13 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:4. > > Community changes, past quarter: > - César García was added to the PMC on 2021-10-01 > - No new committers. Last addition was Thomas Frost on 2021-05-07. > > ## Project Activity: > After finishing the work for the next release some members of the community > have invested a lot of time into a complete refactoring of our codebase for > the code-generation. This was needed in order to be able to support more > situations needed for new drivers, but also for cleaning up stuff to make > it > more easily understandable for others. Others have been working on adding > very > cool new features to the S7 driver as well as working on the CAN-drivers. > > We had talks at 4 conferences: > - ApacheCon @Home (2 Talks) > - LF OSS-Summit (1 Talk) > - Eclipse Con (1 Talk) > - IoT Conference (1 Talk) > > ## Community Health: > We are getting more and more reports of people using plc4x and getting bug > reports. That's great. However contributions have been coming in from 11% > less > individuals compared to the previous quarter. Hopefully, in 2022 we will be > able to do in-person events again, to strengthen the sense of community > again. > I am feeling as we are loosing grip of each other after 2 years of > absolutely > no in-person events. In the past especially these events have been helping > with building the commnunity. >
[DRAFT] December PLC4X board report
## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Issues: There are currently no issues requiring board attention. I do see a bit of an absence of PMC coverage however regarding things cominig up on the mailinglists (dev and private) ## Description: The mission of the Apache PLC4X project is creating a set of libraries for communicating with industrial programmable logic controllers (PLCs) using a variety of protocols but with a shared API. ## Issues: There are currently no issues requiring board attention. I do see a bit of an absence of PMC coverage however regarding things cominig up on the mailinglists (dev and private) ## Membership Data: Apache PLC4X was founded 2019-04-17 (3 years ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - César García was added to the PMC on 2021-10-01 - No new committers. Last addition was Thomas Frost on 2021-05-07. ## Project Activity: After finishing the work for the next release some members of the community have invested a lot of time into a complete refactoring of our codebase for the code-generation. This was needed in order to be able to support more situations needed for new drivers, but also for cleaning up stuff to make it more easily understandable for others. Others have been working on adding very cool new features to the S7 driver as well as working on the CAN-drivers. We had talks at 4 conferences: - ApacheCon @Home (2 Talks) - LF OSS-Summit (1 Talk) - Eclipse Con (1 Talk) - IoT Conference (1 Talk) ## Community Health: We are getting more and more reports of people using plc4x and getting bug reports. That's great. However contributions have been coming in from 11% less individuals compared to the previous quarter. Hopefully, in 2022 we will be able to do in-person events again, to strengthen the sense of community again. I am feeling as we are loosing grip of each other after 2 years of absolutely no in-person events. In the past especially these events have been helping with building the commnunity.
[BUILD-FAILURE]: Job 'PLC4X/PLC4X/develop [develop] [708]'
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [708]': Check console output at "https://ci-builds.apache.org/job/PLC4X/job/PLC4X/job/develop/708/;>PLC4X/PLC4X/develop [develop] [708]"