Re: [VOTE] Apache PLC4X 0.11.0 RC1
Hi, +1 (non-binding) Built under Windows 11, WSL2 (Ubuntu 22.04) Cheers Dominik [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Build the project according to the information in the README.md file. On 2023/10/02 08:28:09 Christofer Dutz wrote: > Apache PLC4X 0.11.0 has been staged under [2] and it’s time to vote > on accepting it for release. All Maven artifacts are available under [1]. > Voting will be open for 72hr. > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > are required to pass. > > Release tag: v0.11.0 > Hash for the release tag: d22042ef079ae93120770a95704571118d9c871e > > Per [3] "Before voting +1 PMC members are required to download > the signed source code package, compile it as provided, and test > the resulting executable on their own platform, along with also > verifying that the package meets the requirements of the ASF policy > on releases." > > You can achieve the above by following [4]. > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items > in [4]) > [ ] -1 reject (explanation required) > > > [1] https://repository.apache.org/content/repositories/orgapacheplc4x-1050 > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.11.0/rc1 > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release > >
Re: [DISCUSS] Add GitHub Discussions?
Hi, +1…our experience at StreamPipes is that GitHub Discussions really help to lower the entry barrier for new users to ask questions! And questions are not asked twice ;-) Cheers Dominik > Am 15.05.2023 um 16:39 schrieb Christofer Dutz : > > Hi all, > > So, my PR for infra just got merged and we can now customize the > auto-generated emails sent for GitHub Discussions … so now I would like to > hear your thoughts on if we want to enable GitHub Discussions for PLC4X > > I would be in favor for it. > > > Chris
RE: [DISCUSS] Having a in-person community meetup?
Hi, great idea, I would also try to join the meetup and maybe we can also do some hacking on the PLC4X UI Cheers Dominik -Original Message- From: Christofer Dutz Sent: Monday, January 9, 2023 10:05 AM To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Having a in-person community meetup? Well … I was thinking of asking TAC and setting something up. As I mentioned. That would be quite a bit of work for me and the rest of the TAC folks. So we’d only do it if offering this, would make a great difference. Chris From: Xiangdong Huang Date: Monday, 9. January 2023 at 08:51 To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Having a in-person community meetup? Ah... if there is TAC support, I will forward this message to IoTDB community to see if there are committers want to join for the Historian development face to face. --- Xiangdong Huang School of Software, Tsinghua University Christofer Dutz 于2023年1月5日周四 18:59写道： > > Hi Jinlin, > > Would you be willing and able to attend such an event? > You would be more than welcome. > > As I’m also part of the Apache Travel Assistance committee … I’d also like to > ask any others here too: > Would you like to attend such an event, but the costs of travelling are what > you can’t afford or would have a too big impact on your budget to be willing > to come? > > Because there theoretically is the option of having Apache cover the costs > for travelling and accommodation. However, this would put quite a lot of > extra work for us for setting it up and running it. > So, if it’s only 1-2 people, this probably doesn’t make much sense, but if > there were more, it might make sense. > > And please … don’t say: “I can’t afford it and would like assistance”, > if the problem is that the fuel has become too expensive for your > Ferrari or the parking costs for your private jet are skyrocketing ;-) > > And if you don’t want to publicly answer … feel free to DM me. > > Chris > > > From: jl hong > Date: Thursday, 5. January 2023 at 02:16 > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Having a in-person community meetup? > This sounds exciting :) > > Jinlin > > Lukas Ott 於 2023年1月5日 週四 上午12:11寫道： > > > cool :-) would be fun so that I can finally ask all my questions in > > person > > ;-) > > > > Am Mi., 4. Jan. 2023 um 16:37 Uhr schrieb Ben Hutcheson < > > ben.hut...@gmail.com>: > > > > > Sounds like fun. > > > > > > Ben > > > > > > On Wed, Jan 4, 2023 at 4:30 PM Christofer Dutz < > > christofer.d...@c-ware.de> > > > wrote: > > > > > > > Ok … > > > > > > > > Uwe from codecentric FFM (the new office) was delighted my me > > > > asking if codecentric would be willing to accommodate us during the > > > > hackathon. > > > > So, that would be one option … I guess Sebastian would like that > > > > option > > > ;-) > > > > > > > > Chris > > > > > > > > > > > > From: Christofer Dutz > > > > Date: Wednesday, 4. January 2023 at 16:24 > > > > To: dev@plc4x.apache.org > > > > Subject: [DISCUSS] Having a in-person community meetup? > > > > Hi all, > > > > > > > > some of you remember the times around our graduation. We had > > > > loads of in-presence meetups and that really fuled the drive in the > > > > community. > > > > Covid sort of was the opposite and it felt like we were sort of > > > > losing > > > our > > > > drive a bit. > > > > > > > > Now that Ben now also lives in Germany, I wanted to bring up > > > > this topic again. > > > > > > > > What do you folks think of a 2-3-day hackathon on PLC4X (and > > > > possibly > > the > > > > Historian)? > > > > Probably we would need to sort of do it Friday to Sunday. > > > > > > > > Also currently probing if we could not get TAC to help finance > > > > the > > > travels > > > > of everyone except me. > > > > > > > > Even if I would love a week on the Bahamas, probably something > > > > in > > Germany > > > > somewhere round Frankfurt or Stuttgart would make sense (from > > > > the perspective of people being able to come there via public > > > > transport and keeping the connection options simple and cheaper) > > > > > > > > What do you folks think. > > > > > > > > > > > > Chris > > > > > > > > >
RE: [DISCUSS] Enable GitHub issues?
> > > > > Category > > > > > > > > > > Values > > > > > > > > > > Priority > > > > > > > > > > "P0", "P1", "P2", "P3" > > > > > > > > > > Type > > > > > > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", > "Outage" > > > > > > > > > > Component > > > > > > > > > > One label per JIRA component, formatted "Component: component>" > > > > (e.g. > > > > > "Component: sdk-go") > > > > > > > > > > Status > > > > > > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate" > > > > > > > > > > > > > > > - Yes we should add a issue template This can be done by > > > > > turning off the create issue permission for all non-admins and > > > > > adding an announcement in Portal Settings > redirecting > > > > people > > > > > to GitHub. > > > > > - Update documentation after migration > > > > > > > > > > Next steps > > > > > - Turn on Github Issues Tab > > > > > - Turn off Jira Tickets (How do we do that?) > > > > > > > > > > > > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer < > > > rie...@fzi.de > > > > >: > > > > > > > > > > > I've recently looked at other ASF projects which discussed > migration > > > > from > > > > > > Jira to Github, e.g., here are some discussions from Apache Beam: > > > > > > > > > > > > Feature Comparison: > > > > > > > > > > > > > > > > > > > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqU > PCmiOslf0/edit#heading=h.r8qwrrbs8odn > > > > > > Migration Plan: > > > > > > > > > > > > > > > > > > > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy > 5MZu75Q5E/edit#heading=h.wskna8eurvjv > > > > > > > > > > > > And Beam also open-sourced the migration tool they used: > > > > > > https://github.com/google/jira-to-issues > > > > > > > > > > > > I've not yet tried it, but looks quite good > > > > > > > > > > > > Cheers > > > > > > Dominik > > > > > > > > > > > > > > > > > > -Original Message- > > > > > > From: Lukas Ott > > > > > > Sent: Monday, October 31, 2022 6:41 PM > > > > > > To: dev@plc4x.apache.org > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues? > > > > > > > > > > > > I will look into that. > > > > > > > > > > > > Currently we have 103 open jira issues. Oldest one is more > > > > > > than 2 > > > years > > > > > > ago. > > > > > > > > > > > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz < > > > > > > christofer.d...@c-ware.de>: > > > > > > > > > > > > > I’m also fine with that. > > > > > > > So anyone willing to work on the migration? > > > > > > > > > > > > > > Chris > > > > > > > > > > > > > > From: Lukas Ott > > > > > > > Date: Monday, 31. October 2022 at 17:50 > > > > > > > To: dev@plc4x.apache.org > > > > > > > Subject: Re: [DISCUSS] Enable GitHub issues? > > > > > > > Hi Chris, > > > > > > > > > > > > > > In my humble opinion we should not run parallel. > > > > > > > > > > > > > > Our Jira has already a lot of issues that are outdated. > > > > > > > > > > > > > > So i opt for enabling GitHub Issues and migrating the few > > > > > > > Jira > > > Issues > > > > > > > that are still worked on. > > > > > > > > > > > > > > This helps us also for cleaning up and having one public > > > > > > > issue tracker, where everyone can easily see what is > > > > > > > worked on and > what > > > is > > > > > > open. > > > > > > > > > > > > > > Luk > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz > > > > > > > < > > > > > > > christofer.d...@c-ware.de>: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > for those of you that haven’t heard of it, Apache will > > > > > > > > be > > > disabling > > > > > > > signup > > > > > > > > to Apache’s Jira due to excessive Spam problems. > > > > > > > > So, for people outside of the project, wanting to submit > issues, > > > > > > > > there will be no simple way to do so. > > > > > > > > > > > > > > > > How about we turn on GitHub Issues and simply run both > > > > > > > > in > > > parallel. > > > > > > > > > > > > > > > > Chris > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
RE: [DISCUSS] Enable GitHub issues?
I've recently looked at other ASF projects which discussed migration from Jira to Github, e.g., here are some discussions from Apache Beam: Feature Comparison: https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn Migration Plan: https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv And Beam also open-sourced the migration tool they used: https://github.com/google/jira-to-issues I've not yet tried it, but looks quite good Cheers Dominik -Original Message- From: Lukas Ott Sent: Monday, October 31, 2022 6:41 PM To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Enable GitHub issues? I will look into that. Currently we have 103 open jira issues. Oldest one is more than 2 years ago. Am Mo., 31. Okt. 2022 um 18:28 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > I’m also fine with that. > So anyone willing to work on the migration? > > Chris > > From: Lukas Ott > Date: Monday, 31. October 2022 at 17:50 > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Enable GitHub issues? > Hi Chris, > > In my humble opinion we should not run parallel. > > Our Jira has already a lot of issues that are outdated. > > So i opt for enabling GitHub Issues and migrating the few Jira Issues > that are still worked on. > > This helps us also for cleaning up and having one public issue > tracker, where everyone can easily see what is worked on and what is open. > > Luk > > Am Mo., 31. Okt. 2022 um 17:07 Uhr schrieb Christofer Dutz < > christofer.d...@c-ware.de>: > > > Hi all, > > > > for those of you that haven’t heard of it, Apache will be disabling > signup > > to Apache’s Jira due to excessive Spam problems. > > So, for people outside of the project, wanting to submit issues, > > there will be no simple way to do so. > > > > How about we turn on GitHub Issues and simply run both in parallel. > > > > Chris > > >
RE: [DISCUSS] Change the UI framework for the GUI application
Hi, in case we choose Angular as the random front end, I'd also be willing to help whenever I find some time! It could also be interesting to configure the Web UI for microfrontend integration, e.g., to integrate the GUI into StreamPipes Dominik -Original Message- From: Ben Hutcheson Sent: Tuesday, October 25, 2022 8:45 PM To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Change the UI framework for the GUI application I think I'm going to hijack Lukas' comment about using electron from a previous post. I'm interested in building a GUI for the OPC-UA server with GraphQL and [insert some random front end] and having a common api would be really cool. Plus there seems to be a lot more selection when you get out of the Java community. On Mon, Oct 24, 2022 at 9:42 AM Łukasz Dywicki wrote: > It's pity that javafx has this trouble. We are compiling our code > against java standard library which is *the* same license. Yet, we do > not distribute standard library, but we would need to distribute > javafx binaries and construct executable form in a proper way. I do > not insist on staying with javafx but I think it is easiest for > developer experience, given quick win Chris had there. Why not letting > ASF LEGAL sorting this stuff for us, given that ISIS, Netbeans, Sis > and others still use it? > > I used swing and swt with jface a long time ago. Swing was a bit of > pain due to limited set of widgets, swt was pain due to native library > handling. Some parts of jface are emulated, if platform does not have > corresponding widget ie. tree table. > I guess we won't have a perfect match any more. We can't do qt, > wxwidgets have custom license too, text ui might be too hard for end > users. With regard to netbeans it gives us some infrastructure, but it > is essentially a swing with all its shine and shadows. :/ > > I looked for swt sources to see how active its development is, and it > seems to be maintained: > https://git.eclipse.org/r/plugins/gitiles/platform/eclipse.platform.sw > t/ yet eclipse project page indicates "archived" status. [1] (its > probably merged with other project) Its binaries should be possible to > fetch via maven repositories. I also found another animal called XWT > which is a declarative UI approach similar to fxml: > https://wiki.eclipse.org/XWT_Documentation, however this one is based > on P2 so it does not usable maven poms. > As far I recall Eclipse folks were debating how to approach P2-maven > repository ecosystem integration for years already, so I do not expect > any quick resolution here. > > Best, > Łukasz > > [1] > https://projects.eclipse.org/projects/eclipse.platform.swt/developer > > On 24.10.2022 17:03, Cesar Garcia wrote: > > Hello, > > > > Netbeans, all in one place. > > > > 1. Easy integration of libraries, > > 2. Graphical interface based on the venerable and stable Swing. > > 3. Graphing tools already available. > > > > and much more. > > > > Against, the learning curve. > > > > I'm already over it > > > > best regards, > > > > El lun, 24 oct 2022 a las 10:07, Christofer Dutz (< > christofer.d...@c-ware.de>) > > escribió: > > > >> Hi all, > >> > >> today we noticed that JavaXF is GPL 2.0 (With classpath exception) > >> licensed. > >> > >> As we don’t want to jump through all the hoops needed to release > >> this in an Apache project, we are planning on switching the UI > >> framework we are basing everything on. > >> > >> Any suggestions? > >> > >> We also might consider building a Web-based application instead … > >> personally I’m open to all. > >> > >> However, I would really like feedback that’s not based on having > >> heard something is cool but having first-hand experience with it. > >> And even > better > >> if you’re willing to help execute the migration. > >> > >> Chris > >> > > > > >
RE: [VOTE] Apache PLC4X 0.9.0 RC2
Hi, +1 (non-binding) I did: [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Search for SNAPSHOT references [OK] Build the project according to the information in the README.md file. Successfully built on Windows 10/WSL 2 (Ubuntu 20.04), OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.8+10) mvnw install Probably this is only a minor issue on my setup, but I had to change the file format of the mvnw file with :set fileformat=unix before the Maven wrapper could be started. Dominik -Original Message- From: Lukas Ott Sent: Saturday, September 18, 2021 6:50 PM To: dev@plc4x.apache.org Subject: Re: [VOTE] Apache PLC4X 0.9.0 RC2 +1 binding Actions performed: Downloaded all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir. Verified the signature is correct gpg: Korrekte Signatur von "Christofer Dutz (Apache Comitter) < cd...@apache.org>" Verified the SHA512 hashes Verified the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. Verified the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. Run RAT externally with no surprises (log to be expected): 9 Unknown Licenses * Files with unapproved licenses: apache-plc4x-0.9.0/code-generation/protocol-base-mspec/src/main/antlr4/org/apache/plc4x/plugins/codegenerator/language/mspec/expression/Expression.g4 apache-plc4x-0.9.0/code-generation/protocol-base-mspec/src/remote-resources/UNLICENSE apache-plc4x-0.9.0/licenses/UNLICENSE apache-plc4x-0.9.0/plc4go/go.sum apache-plc4x-0.9.0/plc4j/examples/hello-webapp/client/asconfig.json apache-plc4x-0.9.0/plc4j/integrations/apache-calcite/src/test/resources/model.json apache-plc4x-0.9.0/plc4j/tools/scraper/src/test/resources/config.json apache-plc4x-0.9.0/sandbox/code-gen/src/main/resources/example.json apache-plc4x-0.9.0/sandbox/code-gen/src/main/resources/example2.json * Successfully built with Ubuntu 20.04 mvn -P with-go install openjdk 11.0.11 2021-04-20 OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04) Am Sa., 18. Sept. 2021 um 18:15 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > Apache PLC4X 0.9.0 has been staged under [2] and it's time to vote on > accepting it for release. All Maven artifacts are available under [1]. > > Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > are required to pass. > > > > Release tag: v0.9.0 > > Hash for the release tag: e9e9a58b057d7df827463f1262ded3a34015666a > > > > Per [3] "Before voting +1 PMC members are required to download the > signed source code package, compile it as provided, and test the > resulting executable on their own platform, along with also verifying > that the package meets the requirements of the ASF policy on releases." > > > > You can achieve the above by following [4]. > > > > [ ] +1 accept (indicate what you validated - e.g. performed the > non-RM items in [4]) [ ] -1 reject (explanation required) > > > > > > [1] > https://repository.apache.org/content/repositories/orgapacheplc4x-1038 > > [2] https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc2 > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] > https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+ > Release > >
RE: [VOTE] Apache PLC4X 0.8.0 RC2
Hi, +1 (non-binding) I checked: [OK] Download all staged artifacts under the url specified in the release vote email [OK] Verify the signature is correct: Additional Apache tutorial on how to verify downloads can be found here [OK] Check if the check is successful [OK] Check if the signature references an Apache email address [OK] Verify the SHA512 hashes [OK] Unzip the archive [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle [OK] Search for SNAPSHOT references [OK] Search for Copyright references [OK] Build the project according to the information in the README.md file Built with Windows 10 under WSL2/Ubuntu Dominik -Original Message- From: Ben Hutcheson Sent: Tuesday, January 26, 2021 11:22 AM To: dev@plc4x.apache.org Subject: Re: [VOTE] Apache PLC4X 0.8.0 RC2 +1 (binding) Ben Remarks, We could certainly do with some cleaning up of the documentation and build instructions e.g. the with-proxies switch doesn't exist anymore, there is a with-opcua-werver switch in the dockerfile, clang is required to build the c stuff but isn't listed. It probably isn't a good idea to use the 0.8.0-SNAPSHOT references in the cpp module pom, will this snapshot exist once we move to 0.9-SNAPSHOT? What is the folder plc4j/protocols for? can we get rid of it? it has some 0.8.1-SNAPSHOT references. with-cpp does build if I change it to use the 0.8.0 release. Built with mvn -P with-go,with-boost,with-logstash,with-proxies,with-python,with-sandbox install -Dmaven.repo.local=../.m2 on Apache Maven 3.6.3 Maven home: /usr/share/maven Java version: 11.0.10-ea, vendor: Debian, runtime: /usr/lib/jvm/java-11-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.10.0-1-amd64", arch: "amd64", family: "unix" On Tue, Jan 26, 2021 at 2:25 AM Lukas Ott wrote: > +1 (binding) > > Lukas > > Built on Ubuntu 20.04 with "mvn -P with-go install" > openjdk 11.0.9.1 2020-11-04 > Maven 3.6.3 > > [OK] Download all staged artifacts under the url specified in the > release vote email [OK] Verify the signature is correct: Additional > Apache tutorial on how to verify downloads can be found here [OK] > Check if the check is successful [OK] Check if the signature > references an Apache email address [OK] Verify the SHA512 hashes [OK] > Unzip the archive [OK] Verify the existence of LICENSE, NOTICE, > README, RELEASE_NOTES files in the extracted source bundle [OK] Verify > the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the > extracted source bundle [OK] [RM] Verify the staged source README, > RELEASE_NOTE files correspond to those in the extracted source bundle > [OK] [RM] Run RAT externally to ensure there are no surprises [OK] > Search for SNAPSHOT references [OK] Search for Copyright references > [OK] Build the project according to the information in the README.md > file > > Am Mo., 25. Jan. 2021 um 21:59 Uhr schrieb Christofer Dutz < > christofer.d...@c-ware.de>: > > > +1 (binding) > > > > Chris > > > > Built on Windows 10 > > Open-JDK 11 > > Maven 3.6.3 > > > > [OK] Download all staged artifacts under the url specified in the > > release vote email [OK] Verify the signature is correct: Additional > > Apache tutorial on how > to > > verify downloads can be found here > > [OK] Check if the check is successful [OK] Check if the signature > > references an Apache email address [OK] Verify the SHA512 hashes > > [OK] Unzip the archive [OK] Verify the existence of LICENSE, NOTICE, > > README, RELEASE_NOTES files in the extracted source bundle [OK] > > Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files > in > > the extracted source bundle > > [OK] [RM] Verify the staged source README, RELEASE_NOTE files > > correspond to those in the extracted source bundle [OK] [RM] Run RAT > > externally to ensure there are no surprises [OK] Search for SNAPSHOT > > references [OK] Search for Copyright references [OK] Build the > > project according to the information in the README.md file [MINOR] > > [RM] Build the project with all with-xyz profiles and tests enabled > > and an empty maven local repo: by appendng > > -Dmaven.repo.local=../.m2. > > > > Remark: > > I built without the with-cpp,with-boost module as building boost > > doesn't work on my machine (But PLC4Cpp doesn't have any use anyway) > > > > -Ursprüngliche Nachricht- > > Von: Christofer Dutz > > Gesendet: Montag, 25. Januar 2021 21:14 > > An: dev@plc4x.apache.org > > Betreff: [VOTE] Apache PLC4X 0.8.0 RC2 > > > > Apache PLC4X 0.8.0 has been staged under [2] and it's time to vote > > on accepting it for release. All Maven artifacts are available under [1]. > > Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > > are required to pass. > > > > Release tag: v0.8.0 > >
RE: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.3.0 RC1
Hi, +1 (non-binding) [OK] Download all staged artifacts under the url specified in the release vote email [OK] Verify the signature is correct and references an Apache Email address [OK] Verify the SHA512 hashes [OK] Unzip the archive [OK] Verify the existence of LICENSE, NOTICE, README and RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README and RELEASE_NOTES files in the extracted source bundle. [OK] Can build from source via "mvn clean install" under Windows 10 (Java 8) and W10 WSL2 (Java 11) Looks good! Dominik -Original Message- From: Lukas Ott Sent: Wednesday, September 9, 2020 6:34 PM To: dev@plc4x.apache.org Subject: Re: [VOTE] Apache PLC4X Build-Tools Code-Generation 1.3.0 RC1 +1 (binding) [OK] Download all staged artifacts under the url specified in the release vote email [OK] Verify the signature is correct and references an Apache Email address [OK] Verify the SHA512 hashes [OK] Unzip the archive [OK] Verify the existence of LICENSE, NOTICE, README and RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README and RELEASE_NOTES files in the extracted source bundle. Can build from Source via "mvn install" OS: Ubuntu 20.04.1 LTS No further remarks. Am Mi., 9. Sept. 2020 um 18:10 Uhr schrieb Christofer Dutz < christofer.d...@c-ware.de>: > +1 (binding) > > Chris > > [OK] Download all staged artifacts under the url specified in the > release vote email [OK] Verify the signature is correct and references > an Apache Email address [OK] Verify the SHA512 hashes [OK] Unzip the > archive [OK] Verify the existence of LICENSE, NOTICE, README and > RELEASE_NOTES files in the extracted source bundle. > [OK] Verify the content of LICENSE, NOTICE, README and RELEASE_NOTES > files in the extracted source bundle. > [OK] Run RAT externally to ensure there are no surprises. > [OK] Search for SNAPSHOT references > [OK] Search for Copyright references, and if they are in headers, make > sure these files containing them are mentioned in the LICENSE file. > [MINOR] Build the project according to the Maven defaults > > Remarks: > > The script "mvnw" seems to not be executable. > > > > Am 08.09.20, 13:46 schrieb "Christofer Dutz" : > >Apache PLC4X Build-Tools Code-Generation 1.3.0 has been staged > under [2] >and it’s time to vote on accepting it for release. > >All Maven artifacts are available under [1]. Voting will be > open for 72hr. > >A minimum of 3 binding +1 votes and more binding +1 than binding -1 >are required to pass. > >Repository: > https://gitbox.apache.org/repos/asf/plc4x-build-tools.git >Release tag: releases/code-generation/1.3.0 >Hash for the release tag: > 7f2fab83d6cd0ccba41b8622d6abe4f8995748bd > >Per [3] "Before voting +1 PMC members are required to download >the signed source code package, compile it as provided, and test >the resulting executable on their own platform, along with also >verifying that the package meets the requirements of the ASF policy >on releases." > >You can achieve the above by following [4]. > >[ ] +1 accept (indicate what you validated - e.g. performed > the non-RM items in [4]) >[ ] -1 reject (explanation required) > > > [1] > https://repository.apache.org/content/repositories/orgapacheplc4x-1029 > [2] > https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.3.0/rc1/ > [3] > https://www.apache.org/dev/release/validation.html#approving-a-release > [4] https://plc4x.apache.org/developers/release/validation.html > > > > >
RE: [VOTE] Apache PLC4X 0.7.0 RC2
Hi, +1 (non-binding) I checked: Download all staged artifacts - OK Verify the signature is correct - OK Verify the SHA512 hashes - OK Verify the existence and content of LICENSE, NOTICE, README, RELEASE_NOTES- OK Search for SNAPSHOT references - OK Build - OK Some comments: The RELEASE_NOTES file (https://dist.apache.org/repos/dist/dev/plc4x/0.7.0/rc2/RELEASE_NOTES) states "Apache PLC4X 0.7.0-SNAPSHOT" in the first line and for the previous release 0.6.0 the headline is " (Unreleased) Apache PLC4X 0.6.0-SNAPSHOT" I was using the Docker-based build and had a few minor problems: - I had to change the base image to use Java 11: FROM azul/zulu-openjdk:11 as build - I got two compile errors in plc4j-hello-integration-iotdb: [ERROR] Failed to execute goal com.offbytwo.maven.plugins:maven-dependency-plugin:3.1.1.MDEP568:go-offline (default-cli) on project plc4j-hello-integration-iotdb: Failed to resolve artifact: com.sun.istack:istack-commons-runtime:jar:3.0.6:compile: Could not find artifact com.sun.istack:istack-commons-runtime:jar:3.0.6 in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] Failed to execute goal com.offbytwo.maven.plugins:maven-dependency-plugin:3.1.1.MDEP568:go-offline (default-cli) on project plc4j-hello-integration-iotdb: Failed to resolve artifact: com.sun.xml.fastinfoset:FastInfoset:jar:1.2.14:compile: Could not find artifact com.sun.xml.fastinfoset:FastInfoset:jar:1.2.14 in central (https://repo.maven.apache.org/maven2) -> [Help 1] I excluded this module to get the build working. Probably this can be considered minor as it only affects the Docker build. Dominik -Original Message- From: Robinet, Etienne <43...@etu.he2b.be> Sent: Thursday, May 21, 2020 9:23 AM To: dev@plc4x.apache.org Subject: Re: [VOTE] Apache PLC4X 0.7.0 RC2 +1 Checklist: - Download all staged artifacts under the url specified in the release vote email - Verify the signature is correct - Check if the signature references an Apache email address. - Verify the SHA512 hashes - Unzip and verify existence and content of LICENSE, NOTICE, README, RELEASE_NOTES - Run RAT externally to ensure there are no surprises (also 7 unknown Licences) apache-plc4x-0.7.0/build-utils/protocol-base-mspec/src/main/antlr4/org/apache/plc4x/plugins/codegenerator/language/mspec/expression/Expression.g4 apache-plc4x-0.7.0/build-utils/protocol-base-mspec/src/remote-resources/UNLICENSE apache-plc4x-0.7.0/licenses/UNLICENSE apache-plc4x-0.7.0/plc4j/examples/hello-webapp/client/asconfig.json apache-plc4x-0.7.0/plc4j/tools/scraper/src/test/resources/config.json apache-plc4x-0.7.0/sandbox/code-gen/src/main/resources/example.json apache-plc4x-0.7.0/sandbox/code-gen/src/main/resources/example2.json -Search for "SNAPSHOT" and "Copyright" reference - Build the project according to the information in the README.md file(./mvnw -P with-sandbox install) OS: Windows 10 Pro. Java: OpenJDK 11.02 Maven: 3.6.0 Le mer. 20 mai 2020 à 08:08, Christofer Dutz a écrit : > +1 Binding > > Chris > > > [OK] Download all staged artifacts under the url specified in the > release vote email into a directory we’ll now call download-dir. > [OK] Verify the signature is correct: Additional Apache tutorial on > how to verify downloads can be found here. > [OK] Check if the signature references an Apache email address. > [OK] Verify the SHA512 hashes: > [OK] Unzip the archive: > [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES > files in the extracted source bundle. > [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES > files in the extracted source bundle. > [OK] [RM] Verify the staged source README, RELEASE_NOTE files > correspond to those in the extracted source bundle. > [OK] [RM] Run RAT externally to ensure there are no surprises. > [OK] Search for SNAPSHOT references: Only found in commented out > dependencies and disabled parts of the project (Parts not yet deleted) > [OK] Search for Copyright references, and if they are in headers, make > sure these files containing them are mentioned in the LICENSE file: No > findings in a bad form, however it seems some files use other apache > headers as others (Some files have apache headers containing the word > "copyright" but most don't) [OK] Build the project according to the > information in the README.md file [OK] [RM] Build the project with all > with-xyz profiles and tests enabled and an empty maven local repo: by > appending -Dmaven.repo.local=../.m2. > > I did notice a copy+paste error in the vote email ... the nexus repo > is missing a "-" before the last 4 digits. > > > Am 19.05.20, 23:19 schrieb "Otto Fowler" : > > +1 ( FWIW) > > Followed the validation steps, built on java 8 > > > > On May 19, 2020 at 15:50:37, Lukas Ott (ott.lukas...@gmail.com) wrote: > > +1 (binding) > Download all staged artifacts - OK > Verify the signature is correct - OK > Verify the SHA512 hashes -
RE: [VOTE] Apache PLC4X 0.6.0 RC3
Hi, +1 (non-binding). I checked: [OK] Download all staged artifacts under the url specified in the release vote email into a directory we’ll now call download-dir: [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes: [OK] Unzip the archive: [OK] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the extracted source bundle. [OK, checked under Windows with Docker] Build the project according to the information in the README.md file. I had to modify the Dockerfile (the base image could not be found, changed it to the tag "8" as already fixed in the develop branch), but I don't think that's important for the release. Dominik -Original Message- From: Julian Feinauer Sent: Wednesday, February 26, 2020 1:34 PM To: dev@plc4x.apache.org Subject: [VOTE] Apache PLC4X 0.6.0 RC3 Hey folks, its release time again! As discussed on multiple occasions, the 0.6 release branch will be a „LTS“ release of the „old fashioned“ or „hand written“ drivers. The develop will be the 0.7.0 branch and will contain the generated drivers. Please check the RELEASE_NOTES for all details. --- Thanks for Justin, Chris and Dominik for finding issues with RC2 and helping fix them. Apache PLC4X 0.6.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag: release/0.6.0 Hash for the release tag: d58c4d5828a3528199584ed51a65d7c896ae1e86 Per [3] "Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapacheplc4x-1023 [2] https://dist.apache.org/repos/dist/dev/plc4x/0.6.0/rc3 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
Re: [WEBSITE] Highly valued possiblity for contributions without coding and hardware ...
Hi Chris, I just pushed another update that includes the carousel and also changes (hopefully improves) the layout of the teaser a bit. Do you have any text on success stories that we could add? Dominik On 2020/01/26 09:57:58, Christofer Dutz wrote: > Hi Dominik, > > thanks for that it looks a LOT better than the boring skeleton I added. > > I would also enjoy a carousel with different things like you mentioned ... > the bootstrap should have all the stuff needed already on-board, I think. > However I am unsure if we should present the different protocol, but more the > use-cases. It's hard to have a picture about a protocol __ > > Would love a carousel with success stories ... and leave the details to the > "users" section. > > Chris > > > > > Am 25.01.20, 21:47 schrieb "Dominik Riemer" : > > Hi all, > > I've created a first draft of the new landing page. > You can find it at https://github.com/dominikriemer/plc4x-build-tools, > just build it as Chris mentioned: > > Change into the directory: plc4x-site-skin > And there just run a “mvn clean install -P run-its” > This will generate a test-website in the directory: > plc4x-site-skin/target/it/plc4x-website/target/site > > Feedback is highly welcome, consider this as a very first draft ;-) > I think it would be nice to add some dynamic content between the feature > highlights, e.g., a carousel showing the different integrations and an > overview of supported protocols. > > Dominik > > > > > > On 2020/01/23 12:48:32, Christofer Dutz > wrote: > > Hi all, > > > > I just let the new version of our website go online ... please check it > out: https://plc4x.apache.org/index.html > > > > And here a list of some things we could need a little help with: > > > > - Make the landing page visually more appealing (Plain HTML & CSS work > ideally utilizing Bootstrap) > > - Make the page display on full height (If you go to the "Apache" main > page, the footer it pretty much at the top, it would be great if it could > stick to the bottom of the screen, but be pushed down if the content requires > it. > > - Write Content: > > - Users > > - Protocols: Documentation on the connection strings > and the address formats. If the protocols have specialities, document them > from a user-perspective (Modbus: Coils are plain Boolean, Registers are short > values) > > - Integrations: Documentation on how to use the > integration modules > > > > As I mentioned ... help is greatly appreciated. > > > > Chris > > > > > > Am 22.01.20, 12:05 schrieb "Christofer Dutz" > : > > > > Hi Dominik, > > > > that would be super awesome ... and regarding the super UX designer > ... well I guess any option will improve the current state. > > But I am sure that your UX capabilities are way better than mine ;-) > > > > Chris > > > > > > > > Am 22.01.20, 11:32 schrieb "Dominik Riemer" : > > > > Hi Chris, > > > > I'd be happy to help improving the PLC4X landing page! > > In case you're looking for some really fancy UX designer, I'm > certainly the wrong person, but I guess I can make one or two proposals on > how to make the homepage look more appealing. > > > > Dominik > > > > On 2020/01/22 09:26:15, Christofer Dutz > wrote: > > > Hi all, > > > > > > I just updated the content of the start-page with some > example content. > > > > > > I didn't want to have anyone distracted by my old crappy > start page ... that is probably the worst starting page any Apache Project > has :-/ > > > > > > Chris > > > > > > > > > Am 21.01.20, 22:23 schrieb "Christofer Dutz" > : > > > > > > Hi all, > > > > > > as you might have noticed from my recent postings, we’re > currently working hard on finally building a nicer looking website. > > > > > &g
Re: [WEBSITE] Highly valued possiblity for contributions without coding and hardware ...
Hi all, I've created a first draft of the new landing page. You can find it at https://github.com/dominikriemer/plc4x-build-tools, just build it as Chris mentioned: Change into the directory: plc4x-site-skin And there just run a “mvn clean install -P run-its” This will generate a test-website in the directory: plc4x-site-skin/target/it/plc4x-website/target/site Feedback is highly welcome, consider this as a very first draft ;-) I think it would be nice to add some dynamic content between the feature highlights, e.g., a carousel showing the different integrations and an overview of supported protocols. Dominik On 2020/01/23 12:48:32, Christofer Dutz wrote: > Hi all, > > I just let the new version of our website go online ... please check it out: > https://plc4x.apache.org/index.html > > And here a list of some things we could need a little help with: > > - Make the landing page visually more appealing (Plain HTML & CSS work > ideally utilizing Bootstrap) > - Make the page display on full height (If you go to the "Apache" main page, > the footer it pretty much at the top, it would be great if it could stick to > the bottom of the screen, but be pushed down if the content requires it. > - Write Content: > - Users > - Protocols: Documentation on the connection strings and the > address formats. If the protocols have specialities, document them from a > user-perspective (Modbus: Coils are plain Boolean, Registers are short values) > - Integrations: Documentation on how to use the integration > modules > > As I mentioned ... help is greatly appreciated. > > Chris > > > Am 22.01.20, 12:05 schrieb "Christofer Dutz" : > > Hi Dominik, > > that would be super awesome ... and regarding the super UX designer ... > well I guess any option will improve the current state. > But I am sure that your UX capabilities are way better than mine ;-) > > Chris > > > > Am 22.01.20, 11:32 schrieb "Dominik Riemer" : > > Hi Chris, > > I'd be happy to help improving the PLC4X landing page! > In case you're looking for some really fancy UX designer, I'm > certainly the wrong person, but I guess I can make one or two proposals on > how to make the homepage look more appealing. > > Dominik > > On 2020/01/22 09:26:15, Christofer Dutz > wrote: > > Hi all, > > > > I just updated the content of the start-page with some example > content. > > > > I didn't want to have anyone distracted by my old crappy start page > ... that is probably the worst starting page any Apache Project has :-/ > > > > Chris > > > > > > Am 21.01.20, 22:23 schrieb "Christofer Dutz" > : > > > > Hi all, > > > > as you might have noticed from my recent postings, we’re > currently working hard on finally building a nicer looking website. > > > > This is generally not that difficult, because a blind > chimpanzee would probably come up with a nicer looking page than what I > created more than 3 years ago ;-) … but this is also a big problem. Very > often I have heard that potential users don’t really accept us as something > industry-grade, because our website sucks so badly. > > > > While I think we have reached a quite reasonable state with the > general content, we desperately need someone to help create our landing-page. > > > > Here we could be using standard HTML and CSS (Ideally with > Bootstrap, cause that’s already there and the site will be using this) > > > > What we’re looking for is something like one of these pages: > > > > https://www.industry-fusion.com/ > > > > https://royale.apache.org/ > > > > https://pragmaticindustries.com/ > > > > So I hope you get the idea … these long scrolling down sites > with, let’s call it … low information density, but high wow-factor. > > > > If you are following this project and was always waiting for > something where you can start contributing … this is probably something we > need more than another driver implementation (Don’t get me wrong … we love > new drivers, but I would definitely also love a nice landing page) > > > > Please, please, please help us and make yourself famous :-) > > > > Chris > > > > > > > > > > >
Re: [WEBSITE] Highly valued possiblity for contributions without coding and hardware ...
Hi Chris, I'd be happy to help improving the PLC4X landing page! In case you're looking for some really fancy UX designer, I'm certainly the wrong person, but I guess I can make one or two proposals on how to make the homepage look more appealing. Dominik On 2020/01/22 09:26:15, Christofer Dutz wrote: > Hi all, > > I just updated the content of the start-page with some example content. > > I didn't want to have anyone distracted by my old crappy start page ... that > is probably the worst starting page any Apache Project has :-/ > > Chris > > > Am 21.01.20, 22:23 schrieb "Christofer Dutz" : > > Hi all, > > as you might have noticed from my recent postings, we’re currently > working hard on finally building a nicer looking website. > > This is generally not that difficult, because a blind chimpanzee would > probably come up with a nicer looking page than what I created more than 3 > years ago ;-) … but this is also a big problem. Very often I have heard that > potential users don’t really accept us as something industry-grade, because > our website sucks so badly. > > While I think we have reached a quite reasonable state with the general > content, we desperately need someone to help create our landing-page. > > Here we could be using standard HTML and CSS (Ideally with Bootstrap, > cause that’s already there and the site will be using this) > > What we’re looking for is something like one of these pages: > > https://www.industry-fusion.com/ > > https://royale.apache.org/ > > https://pragmaticindustries.com/ > > So I hope you get the idea … these long scrolling down sites with, let’s > call it … low information density, but high wow-factor. > > If you are following this project and was always waiting for something > where you can start contributing … this is probably something we need more > than another driver implementation (Don’t get me wrong … we love new drivers, > but I would definitely also love a nice landing page) > > Please, please, please help us and make yourself famous :-) > > Chris > > >
