Possibly worth adding: - Refactor the OPC-UA test-suite to run as Integration-Test in the build and to rely on a Milo server started in the pre-integration-test phase and which is stopped in the post-integration-test-phase.
Von: Lukas Ott <[email protected]> Datum: Montag, 18. März 2024 um 11:51 An: [email protected] <[email protected]> Betreff: Re: [DISCUSS] What do we want to look into/talk about on the Meetup/Workshop? Mine are much simpler: - Merge my pull request * https://github.com/apache/plc4x/pull/1419 should be 5-10 minutes with Sebastian. - Go through PLC4PY with Ben and get things running on my side * Add Pip Package to https://pypi.org/ including release integration etc. * What is missing for PLC4Py to get out of the sandbox? * Find little tasks where I can start and not overwhelmed as one of the rare-non developers in that project. - Look into what you (Chris) did with ReactJS on the UI branch and get that running For the rest I am giving a +1 for your points. Lukas Am Mo., 18. März 2024 um 11:17 Uhr schrieb Christofer Dutz < [email protected]>: > Here some things I have on my mind: > > > * Road to 1.0.0 (What’s still missing?) > * Generating larger portions of the code (Mesasages & Request+Response) > * Missing features: > * Optimizer Framework (Optimize requests, by rewriting them) > * Subscription Emulation (General purpose component, that uses the > READ api to simulare subscriptions) > * New/Advanced Scraper (Rewrite of the Scraper, that allows things > like “read, triggered by subscription”) > * How can we distribute the workload a bit better? > * How can we grow the community? > > Chris >
