According to the voting, logo #6 is the most favorite one. Here is the
[image: Inline image 1]
I am delighted to present you AeroGear Digger's logo:
[image: Inline image 2]
On Mon, Jun 19, 2017 at 10:40 AM, Ali Ok <aliok(a)redhat.com> wrote:
> We would like to pick a logo for the new AeroGear module, Digger .
> James Cobb has already prepared some great designs and now we vote to pick
> the best one .
> We have prepared a Google poll (no login required) here:
> The poll will be open for 10 days (until June 29th 10:00 AM UTC).
>  : https://github.com/aerogear/digger-jenkins
>  : https://issues.jboss.org/browse/DESIGN-943
as you all know, Polina Koleva and Dimitra Zuccarelli were our students
this year, working on a POC that brings the UPS towards Apache Kafka as its
internal message bus.
On September 1st, 14:30 UTC, we will do a hangout-on-air, where the
students give a little presentation about their work.
by default the Kafka client APIs log a lot on INFO. On IRC Polina and
Dimitra were mentioning that.
Here is a snippet for the "standalone.xml", to be inserted in the logging
we have server-side support for ADM (Amazon's Kindle Device push) as well
as support for Microsofts' deprecated MPNS (Microsoft Push Notification
Service) and SimplePush (from Firefox).
I was wondering if we should remove those, on the master branch, going
Would mean that UPS would be just supporting:
* APNs (HTTP/2 only)
* FCM (via HTTP only)
* WNS (Windows Push Notification Services)
How do folks feel about that ? Anyone actively using ADM, SimplePush or
GSoC is wrapping up, and Polina and Dimitra have done great work on our
"GSOC_2017_kafka branch" for brining in Apache Kafka. The work will not be
merged to master, and stays for a little bit longer on that branch....
== 1.2.0.Final ==
Our last release for the 1.2.0 series was a BETA1, in May:
In order to move forward and release a 1.2.0 release to the community, I
will be re-starting the looooooooooooong outstanding work to decouple UPS
from our legacy Keycloak:
this also helps us to be able to work on latest of WildFly, our legacy
Keycloak currently is a blocker for moving towards WF11:
Once that decoupling is done and complete, there will be a UPS 1.2.0.Final
release, and Docker images will be updated to relay on WF11.Final (once
== What's next ? ==
After that I'd like to merge the GSOC_2017_kafka branch to master, and also
bump the version to 2.0.0-SNAPSHOT, since than we have Kafka integrated for
the centralized messaging. Also, Docker images (and Openshift templates)
will be updated - but all of that starts really _after_ the 1.2.0.Final is
Any thoughts or comments?
I think we need to update our JIRA components in AGDIGGER project.
- Android support
- IOS support
- Ansible Installer
- Sample (I mean sample Jenkinsfiles)
- Node client
- Java client
Anything missing or strange?
@Matthias, can you do that?