+1
This would be much appreciated.
On January 20, 2023, Tobias Tschinkowitz
wrote:
> +1
>
> > Am 20.01.2023 um 13:47 schrieb Otto Fowler
> :
> >
> > +1
> >
> > From: Christofer Dutz
> >
> > Reply: dev@plc4x.apache.org
>
> > Date: January 19, 2023 at 12:08:07
> > To: dev@plc4x.apache.org
>
On 2023-01-10 14:33, Christofer Dutz wrote:
> So please speak up … who would be interested to come? And who would
> need assistance and if yes: from where you would be coming.
I would also consider attending on my own cost. Both Frankfurt and
Stuttgart would be great options for me.
Hello all,
I think this is a good compromise to get started and then publish it
with a bit of fanfare (marketing) as an Apache project to the world once
it's ready.
I am also interested in working with you on this project. I think PLC4X
and IoTDB need something like this to become popular in the
I would't stop the release for this small imperfection in the README.
For documentation I always check the online versions like the website
first.
On September 21, 2021, "Sebastian Rühl" wrote:
> I would be fine with that minor imperfection. In case of trouble we
> can always release a new hotfix
+1 (non-binding)
I checked:
- Release tag
- Hash and signature
- Tests and build successful locally
- Rat looks ok
On 2021/09/08 18:17:14, Christofer Dutz
wrote:
> Apache PLC4X Build-Tools Code-Generation 1.5.0 has been staged under
[2]
> and it's time to vote on accepting it for release.
>
>
+1 (non-binding)
I checked:
- Signature and Hash
- Tests and build work locally
- License headers with Apache Rat
On 2021/09/08 18:40:58, Christofer Dutz
wrote:
> Apache PLC4X Build-Tools Site-Skink 1.1.0 has been staged under [2]
> and it's time to vote on accepting it for release.
>
> All Ma
Hi all,
I found just a little typo :-)
> which will probably be invited pretty to join the community soon,
Am 02.09.20 um 14:57 schrieb Christofer Dutz:
> Hi all …
>
> I just prepared our board report and saved it as a draft … please review and
> give feedback if you want me to add/remove
Hi everyone,
>From my perspective renaming "master" like PLC4X uses it to "release"
makes it easier to understand for newcomers. +1 from me.
At first I was kind of confused when I got in touch with PLC4X. Almost
all projects, I know very well, use the branch "master" as the main
development branc
I vote +1 (non-binding)
Niklas
[OK] Download all staged artifacts under the url specified in the
release vote email
[OK] Verify the signature is correct
[OK] Check if the check is successful.
[OK] Check if the signature references an Apache email address.
[OK] Verify the SHA512 hashes.
[OK] Unzip
I vote +1 (non-binding)
[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 LI
mitter on 2020-01-29
>- César García was added as committer on 2020-02-03
>- Niklas Merz was added as committer on 2020-01-29
>- Lukas Ott was added as committer on 2020-01-03
>- Dominik Riemer was added as committer on 2020-02-04
>
>## Project Activity:
>- 0.6.0 was released on 2
I vote +1
[OK] Download staged source artifact
[OK] Verify the signature is correct.
[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] Successfully build the project according README ins
eral very active people to become committer, which all accepted
> the Invitation.
> Thus, we warmly welcome (with no specific order)
>
> * Lukas Ott
> * Cesar Garcia
> * Alvaro Del Castillo
> * Niklas Merz
>
> as new committers for the PLC4X project.
>
> Let me ad
Hi all,
This skin is step in the right direction for. A big +1.
I tried out the new site skin and I like it. The new structure with
Home, User, Dev, Apache is a huge step forward. The old top menu
confused me a lot. Also the static navigation on the left of these pages
is much better to use than
Hi again,
Good news! I got the PlcDriverManager working with Dalvik classloading
in my Cordova plugin.
Turns out my previews finding took me to a wrong route:
> ClassLoader cl = ClassLoader.getSystemClassLoader();
> Thread.currentThread().setContextClassLoader(cl);
I was not really familiar wit
y as a first test. This way you would avoid all of our
> classloading-magic.
>
> Chris
>
>
> Am 07.01.20, 23:03 schrieb "Niklas Merz" :
>
> Hello again,
>
> Julian motivated me and I quickly cobbled together a PLC4X Cordova
> plugi
iltelefon gesendet
>
>
> Ursprüngliche Nachricht
> Von: Niklas Merz
> Datum: Di., 7. Jan. 2020, 20:56
> An: dev@plc4x.apache.org
> Betreff: Re: PLC4X on Android?
> Hi all,
>
> Turns out Netty seems to work just fine on Android, but we forgot to
> give the app n
ories that explicitly use OIO.
> Then we could add a parameter such as
> "androidCompatability=true" to the string and use that instead?
>
> Would that be an option?
>
> Chris
>
>
>
Niklas Merz created PLC4X-166:
-
Summary: Download page has broken links and wrong version number
Key: PLC4X-166
URL: https://issues.apache.org/jira/browse/PLC4X-166
Project: Apache PLC4X
Issue
I vote +1 (non-binding)
I did:
* check signature and hash
* check files for license notice headers (Minor issue NOTICE file
copyright not updated) manually
* check all files by running apache-rat-0.12 for headers with
successfulloutput
* found no binaries :-)
* build successfully from instructions
Congrats Björn. I am sure you are a perfect fit for the PMC.
Am 13. Mai 2019, 18:16, um 18:16, Bjoern Hoeper schrieb:
>Hey everyone,
>I am very happy and honoured to join the PMC. I really enjoy the work
>with the project team and I am really looking excited to really advance
>the project.
>I als
Hi,
My feedback from using the page for the first time.
I noticed that while looking for the getting started. Building the website was
really slow on my machine as well. +1 from me.
I think the main menu item Reports - > Project Informationen is too hard to
find for important stuff.
Niklas
22 matches
Mail list logo
