In #1, I'm working on migrating the OpenPGP implementation in pgpainless-wot from an older release of PGPainless to the 2.0 branch.
The 2.0 release makes use of Bouncy Castles new high-level API, so much complexity from PGPainless was moved upstream into Bouncy Castle.
It might make sense to migrate pgpainless-wot away from PGPainless and make use of BCs high level API directly. That way pgpainless-wot (which we might want to rename then) would be better accessible to more projects which do not make use of PGPainless.
In #1, I'm working on migrating the OpenPGP implementation in pgpainless-wot from an older release of PGPainless to the 2.0 branch.
The 2.0 release makes use of Bouncy Castles new high-level API, so much complexity from PGPainless was moved upstream into Bouncy Castle.
It might make sense to migrate pgpainless-wot away from PGPainless and make use of BCs high level API directly. That way pgpainless-wot (which we might want to rename then) would be better accessible to more projects which do not make use of PGPainless.