Last week we manage to finish and polish the second round on the APIs refactoring and we attended an AWS 2 days training for cloud deployments. We already started a third iteration around the Java Runtime APIs related to security, security policies and further refinements on usability. This week we will be moving forward this work to close Beta1 release. We are also doing some testing on Pivotal PKS to validate that our HELM charts are supported across different cloud providers.
@igdianovworked on a PoC for Activiti Cloud
@almericoWorking on running latest runtime-bundle and Activiti cloud infrastructure with latest JenkinsX release.
@daisuke-yoshimotoworked on
@miguelruizdevworked on activiti-cloud-acceptance-tests, adding a new security policies module and refactoring default process definitions and users to specific ones. Attended AWS training.
@balsarorihelped with some extensions to the engine APIs to support Owner queries for tasks.
@mteodorifixed Batik vulnerability
@constantin-ciobotaru- holidays -
@ryandawsonukAdded a connector process to the example-runtime-bundle and a connector chart to activiti-cloud-charts then tested the example connector image. Started working with @miguelruizdevto improve the acceptance-tests with some refactoring to support adding tests for security-policies and for the example connector scenario. Attended AWS + EKS training.
@erdemedeirosworked with @salaboy on the next iteration for the Java API. Added Activiti Spring Boot starter to Activiti/Activiti. Attended AWS + EKS training.
@salaboyworked on the 3rd round of refactorings for the API, now focused on security and security policies. Attended AWS + EKS training.
Get in touch if you want to contribute: https://gitter.im/Activiti/Activiti7
We are looking forward to mentor people on the technologies that we are using to submit their first Pull Request 
