From matzew at apache.org  Thu Jun  1 03:28:04 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 1 Jun 2017 09:28:04 +0200
Subject: [aerogear-dev] Good first bug!
Message-ID: <CAAg5f2R=fFXBAQ69z36nrdbDeyKXkH7cNFeo-FP0BJKPPak+_A@mail.gmail.com>

Hi,

in order to allow new contributors an "easy" start for their contributions,
I think it's a good idea to label AeroGear JIRAs as "good_first_bug".

Currently we have a handful of those:
https://issues.jboss.org/issues/?filter=12332262

The above filter is public, so is also visible to users that are not logged
in to JIRA, this also lowers the entry-point for potential contributors!


-Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/79407e87/attachment.html 

From matzew at apache.org  Thu Jun  1 04:58:52 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 1 Jun 2017 10:58:52 +0200
Subject: [aerogear-dev] Digger Java client - release
Message-ID: <CAAg5f2RA-ENW_xYVRKSofVRbp7-a3_ReSzrJ2m0WMkX0Zi4BDQ@mail.gmail.com>

Hi,

there is currently no version of the digger-java released to maven central.

The pom says 1.0.0-SNAPSHOT, which also means nothing :-)

How about starting to release some alpha to maven central? To also give
others a chance to pick that JAR up easily ?

We could even use some version below 1.0.0 as well

Thoughts?
-M

[1] https://github.com/aerogear/digger-java



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/303bdc0e/attachment.html 

From dimitrazuccarelli at gmail.com  Thu Jun  1 05:55:15 2017
From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli)
Date: Thu, 1 Jun 2017 10:55:15 +0100
Subject: [aerogear-dev] Good first bug!
In-Reply-To: <CAAg5f2R=fFXBAQ69z36nrdbDeyKXkH7cNFeo-FP0BJKPPak+_A@mail.gmail.com>
References: <CAAg5f2R=fFXBAQ69z36nrdbDeyKXkH7cNFeo-FP0BJKPPak+_A@mail.gmail.com>
Message-ID: <CAFia+60uRofBmS+kpw=nKF6haOC-etn=JmUrNt2aGcZTB_ciQA@mail.gmail.com>

Great idea!

On Thu, Jun 1, 2017 at 8:28 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> in order to allow new contributors an "easy" start for their
> contributions, I think it's a good idea to label AeroGear JIRAs as
> "good_first_bug".
>
> Currently we have a handful of those:
> https://issues.jboss.org/issues/?filter=12332262
>
> The above filter is public, so is also visible to users that are not
> logged in to JIRA, this also lowers the entry-point for potential
> contributors!
>
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/3c009ff3/attachment.html 

From aliok at redhat.com  Thu Jun  1 08:05:06 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 1 Jun 2017 15:05:06 +0300
Subject: [aerogear-dev] Good first bug!
In-Reply-To: <CAFia+60uRofBmS+kpw=nKF6haOC-etn=JmUrNt2aGcZTB_ciQA@mail.gmail.com>
References: <CAAg5f2R=fFXBAQ69z36nrdbDeyKXkH7cNFeo-FP0BJKPPak+_A@mail.gmail.com>
	<CAFia+60uRofBmS+kpw=nKF6haOC-etn=JmUrNt2aGcZTB_ciQA@mail.gmail.com>
Message-ID: <CABoO8Ld1jSWbXSd-rx-8TCikJwUxOHBUH-89dd9Ed6PiFR9+iw@mail.gmail.com>

Good idea Matthias.

I will keep this in mind next time we go through the backlog with the team.

On Thu, Jun 1, 2017 at 12:55 PM, Dimitra Zuccarelli <
dimitrazuccarelli at gmail.com> wrote:

> Great idea!
>
> On Thu, Jun 1, 2017 at 8:28 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> in order to allow new contributors an "easy" start for their
>> contributions, I think it's a good idea to label AeroGear JIRAs as
>> "good_first_bug".
>>
>> Currently we have a handful of those:
>> https://issues.jboss.org/issues/?filter=12332262
>>
>> The above filter is public, so is also visible to users that are not
>> logged in to JIRA, this also lowers the entry-point for potential
>> contributors!
>>
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

ALI OK

SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM

Red Hat

<https://www.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/a378d87b/attachment.html 

From dpassos at redhat.com  Thu Jun  1 11:08:47 2017
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 1 Jun 2017 12:08:47 -0300
Subject: [aerogear-dev] Digger Java client - release
In-Reply-To: <CAAg5f2RA-ENW_xYVRKSofVRbp7-a3_ReSzrJ2m0WMkX0Zi4BDQ@mail.gmail.com>
References: <CAAg5f2RA-ENW_xYVRKSofVRbp7-a3_ReSzrJ2m0WMkX0Zi4BDQ@mail.gmail.com>
Message-ID: <CADF=h2sgzZeM4rxMMvKeWCQpwej1UQGUbu7c-o_ypumf8H+5kg@mail.gmail.com>

On Thu, Jun 1, 2017 at 5:58 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> there is currently no version of the digger-java released to maven central.
>
> The pom says 1.0.0-SNAPSHOT, which also means nothing :-)
>
> How about starting to release some alpha to maven central? To also give
> others a chance to pick that JAR up easily ?
>

+1

In related new I have published[1] a SNAPSHOT in the JBoss Nexus

[1]
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/aerogear/digger-java-client/



> We could even use some version below 1.0.0 as well
>
> Thoughts?
> -M
>
> [1] https://github.com/aerogear/digger-java
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/673de2f1/attachment.html 

From aliok at redhat.com  Thu Jun  1 11:28:48 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 1 Jun 2017 18:28:48 +0300
Subject: [aerogear-dev] Jenkins Java client - fork?
Message-ID: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>

Hi,

In order to make our Digger Java client working as we like, we needed to
make changes in the underlying Jenkins Java client [1].
We sent a PR, but we don't know when the project owner will merge it. So,
for testing purposes of our own, we would like to release our fork of
Jenkins Java client in a snapshot repository.

What do you say? Any other and better approach?

Where can we publish the snapshots of our fork?

Note: The project owner is a kind guy and will perhaps publish a snapshot
release for us after merging our PR, but we cannot rely on that workflow
for long time for other needed changes.

-- 

ALI OK

SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM

Red Hat

<https://www.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/5b6c7283/attachment-0001.html 

From weil at redhat.com  Thu Jun  1 12:49:43 2017
From: weil at redhat.com (Wei Li)
Date: Thu, 1 Jun 2017 17:49:43 +0100
Subject: [aerogear-dev] Digger Java client - release
In-Reply-To: <CADF=h2sgzZeM4rxMMvKeWCQpwej1UQGUbu7c-o_ypumf8H+5kg@mail.gmail.com>
References: <CAAg5f2RA-ENW_xYVRKSofVRbp7-a3_ReSzrJ2m0WMkX0Zi4BDQ@mail.gmail.com>
	<CADF=h2sgzZeM4rxMMvKeWCQpwej1UQGUbu7c-o_ypumf8H+5kg@mail.gmail.com>
Message-ID: <CAHmyU2pJVWxz6LAJs5=+SQ0KRKeBu7Ny=bH=U9xsW0sYZ_P5RQ@mail.gmail.com>

I think that will be good to have.

I have another question about the Jenkins java client api module [1] which
is one of the dependencies of the digger java client. We have submitted
some PRs to that module which are required for our integration work, but I
think it probably will take a while for it to be released.

So to speed things up, is it a good idea to fork the original project, and
change the group id and publish it ourselves, or can we just publish it to
maven central by us?

[1] https://github.com/jenkinsci/java-client-api

On Thu, Jun 1, 2017 at 4:08 PM, Daniel Passos <dpassos at redhat.com> wrote:

>
>
> On Thu, Jun 1, 2017 at 5:58 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> there is currently no version of the digger-java released to maven
>> central.
>>
>> The pom says 1.0.0-SNAPSHOT, which also means nothing :-)
>>
>> How about starting to release some alpha to maven central? To also give
>> others a chance to pick that JAR up easily ?
>>
>
> +1
>
> In related new I have published[1] a SNAPSHOT in the JBoss Nexus
>
> [1] https://repository.jboss.org/nexus/content/repositories/
> snapshots/org/jboss/aerogear/digger-java-client/
>
>
>
>> We could even use some version below 1.0.0 as well
>>
>> Thoughts?
>> -M
>>
>> [1] https://github.com/aerogear/digger-java
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> -- Passos
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

WEI LI

SENIOR SOFTWARE ENGINEER

Red Hat Mobile <https://www.redhat.com/>

weil at redhat.com    M: +353862393272
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/6301ec4e/attachment.html 

From matzew at apache.org  Fri Jun  2 01:47:55 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 2 Jun 2017 07:47:55 +0200
Subject: [aerogear-dev] Digger Java client - release
In-Reply-To: <CAHmyU2pJVWxz6LAJs5=+SQ0KRKeBu7Ny=bH=U9xsW0sYZ_P5RQ@mail.gmail.com>
References: <CAAg5f2RA-ENW_xYVRKSofVRbp7-a3_ReSzrJ2m0WMkX0Zi4BDQ@mail.gmail.com>
	<CADF=h2sgzZeM4rxMMvKeWCQpwej1UQGUbu7c-o_ypumf8H+5kg@mail.gmail.com>
	<CAHmyU2pJVWxz6LAJs5=+SQ0KRKeBu7Ny=bH=U9xsW0sYZ_P5RQ@mail.gmail.com>
Message-ID: <CAAg5f2Sj0vys=Ux2pYZeU5hdA+mP76V+p6jJt9R6WMbf2sWFdQ@mail.gmail.com>

On Thu, Jun 1, 2017 at 6:49 PM, Wei Li <weil at redhat.com> wrote:

> I think that will be good to have.
>
> I have another question about the Jenkins java client api module [1] which
> is one of the dependencies of the digger java client. We have submitted
> some PRs to that module which are required for our integration work, but I
> think it probably will take a while for it to be released.
>
> So to speed things up, is it a good idea to fork the original project, and
> change the group id and publish it ourselves, or can we just publish it to
> maven central by us?
>

we could do that, if needed - but before doing that, I'd suggest we reach
out to the upstream project, and let them know.

Perhaps it's better to work hand-in-hand w/ the project and help (e.g.
drive releases).


>
> [1] https://github.com/jenkinsci/java-client-api
>
> On Thu, Jun 1, 2017 at 4:08 PM, Daniel Passos <dpassos at redhat.com> wrote:
>
>>
>>
>> On Thu, Jun 1, 2017 at 5:58 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> there is currently no version of the digger-java released to maven
>>> central.
>>>
>>> The pom says 1.0.0-SNAPSHOT, which also means nothing :-)
>>>
>>> How about starting to release some alpha to maven central? To also give
>>> others a chance to pick that JAR up easily ?
>>>
>>
>> +1
>>
>> In related new I have published[1] a SNAPSHOT in the JBoss Nexus
>>
>> [1] https://repository.jboss.org/nexus/content/repositories/snap
>> shots/org/jboss/aerogear/digger-java-client/
>>
>>
>>
>>> We could even use some version below 1.0.0 as well
>>>
>>> Thoughts?
>>> -M
>>>
>>> [1] https://github.com/aerogear/digger-java
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> -- Passos
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> WEI LI
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> weil at redhat.com    M: +353862393272
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/06a128bb/attachment.html 

From matzew at apache.org  Fri Jun  2 01:54:28 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 2 Jun 2017 07:54:28 +0200
Subject: [aerogear-dev] Jenkins Java client - fork?
In-Reply-To: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>
References: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>
Message-ID: <CAAg5f2TxWSmaFzERXVW-nLepTHWtryeCCU62x0ddKp4L3REKTw@mail.gmail.com>

Hey,

I just replied to Wei's mail, which addresses a similar concern. If a
dependency is not properly maintained, and released, there is always room
for that kinda stuff.
If we do it, we should be doing it w/ different packages (e.g. org.aerogear.
com.offbytwo.jenkins), as a last resort :-)

I'd suggest to get in touch w/ the maintainer, and explain him, that we are
interested in helping, and would also like to have frequent releases :)
Perhaps that's the first strategy, before going hard on a fork - that has
the risk of being always different than the rest of the usptream community.


-M


On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <aliok at redhat.com> wrote:

> Hi,
>
> In order to make our Digger Java client working as we like, we needed to
> make changes in the underlying Jenkins Java client [1].
> We sent a PR, but we don't know when the project owner will merge it. So,
> for testing purposes of our own, we would like to release our fork of
> Jenkins Java client in a snapshot repository.
>
> What do you say? Any other and better approach?
>
> Where can we publish the snapshots of our fork?
>
> Note: The project owner is a kind guy and will perhaps publish a snapshot
> release for us after merging our PR, but we cannot rely on that workflow
> for long time for other needed changes.
>
> --
>
> ALI OK
>
> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>
> Red Hat
>
> <https://www.redhat.com/>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/17ce5b85/attachment-0001.html 

From matzew at apache.org  Fri Jun  2 01:57:42 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 2 Jun 2017 07:57:42 +0200
Subject: [aerogear-dev] Jenkins Java client - fork?
In-Reply-To: <CAAg5f2TxWSmaFzERXVW-nLepTHWtryeCCU62x0ddKp4L3REKTw@mail.gmail.com>
References: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>
	<CAAg5f2TxWSmaFzERXVW-nLepTHWtryeCCU62x0ddKp4L3REKTw@mail.gmail.com>
Message-ID: <CAAg5f2S_E2TAe3SQaeF+ZO0M5dRbfX1CVy64wiM7H0ayQ3tzUg@mail.gmail.com>

Ali, Wei,

if we fork it, I'd strongly suggest to use the aerogear Github org, not the
feedhenry one. It feels a bit weird using two different GH orgs for one
project and its fork/dependency

On Fri, Jun 2, 2017 at 7:54 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hey,
>
> I just replied to Wei's mail, which addresses a similar concern. If a
> dependency is not properly maintained, and released, there is always room
> for that kinda stuff.
> If we do it, we should be doing it w/ different packages (e.g.
> org.aerogear.com.offbytwo.jenkins), as a last resort :-)
>
> I'd suggest to get in touch w/ the maintainer, and explain him, that we
> are interested in helping, and would also like to have frequent releases :)
> Perhaps that's the first strategy, before going hard on a fork - that has
> the risk of being always different than the rest of the usptream community.
>
>
> -M
>
>
> On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hi,
>>
>> In order to make our Digger Java client working as we like, we needed to
>> make changes in the underlying Jenkins Java client [1].
>> We sent a PR, but we don't know when the project owner will merge it. So,
>> for testing purposes of our own, we would like to release our fork of
>> Jenkins Java client in a snapshot repository.
>>
>> What do you say? Any other and better approach?
>>
>> Where can we publish the snapshots of our fork?
>>
>> Note: The project owner is a kind guy and will perhaps publish a snapshot
>> release for us after merging our PR, but we cannot rely on that workflow
>> for long time for other needed changes.
>>
>> --
>>
>> ALI OK
>>
>> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/201d873d/attachment.html 

From idel.pivnitskiy at gmail.com  Fri Jun  2 02:47:14 2017
From: idel.pivnitskiy at gmail.com (Idel Pivnitskiy)
Date: Thu, 1 Jun 2017 23:47:14 -0700
Subject: [aerogear-dev] Good first bug!
In-Reply-To: <CABoO8Ld1jSWbXSd-rx-8TCikJwUxOHBUH-89dd9Ed6PiFR9+iw@mail.gmail.com>
References: <CAAg5f2R=fFXBAQ69z36nrdbDeyKXkH7cNFeo-FP0BJKPPak+_A@mail.gmail.com>
	<CAFia+60uRofBmS+kpw=nKF6haOC-etn=JmUrNt2aGcZTB_ciQA@mail.gmail.com>
	<CABoO8Ld1jSWbXSd-rx-8TCikJwUxOHBUH-89dd9Ed6PiFR9+iw@mail.gmail.com>
Message-ID: <CAN+BUJrAxNHguOLH=gpnzGzWXTGkhJhJhKu2_8iZ7FReE_hTSg@mail.gmail.com>

Great idea, Matthias!

There are a few project, which focused on the searching of easy open issues
for beginners:

   - http://up-for-grabs.net
   - https://openhatch.org
   - https://www.codetriage.com
   - http://issuehub.io

They scan open bug trackers for the issues with specific labels, like
"easy", "trivial", "beginner", "easy pick", "up-for-grabs", etc. Once all
of them work with Github issues, up-for-grabs and openhatch support
different bug trackers (JIRA included). We can add our repos to this lists
and mark which label to use for searching.

Best,
Idel

On Thu, Jun 1, 2017 at 5:05 AM, Ali Ok <aliok at redhat.com> wrote:

> Good idea Matthias.
>
> I will keep this in mind next time we go through the backlog with the team.
>
> On Thu, Jun 1, 2017 at 12:55 PM, Dimitra Zuccarelli <
> dimitrazuccarelli at gmail.com> wrote:
>
>> Great idea!
>>
>> On Thu, Jun 1, 2017 at 8:28 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> in order to allow new contributors an "easy" start for their
>>> contributions, I think it's a good idea to label AeroGear JIRAs as
>>> "good_first_bug".
>>>
>>> Currently we have a handful of those:
>>> https://issues.jboss.org/issues/?filter=12332262
>>>
>>> The above filter is public, so is also visible to users that are not
>>> logged in to JIRA, this also lowers the entry-point for potential
>>> contributors!
>>>
>>>
>>> -Matthias
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> ALI OK
>
> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>
> Red Hat
>
> <https://www.redhat.com/>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170601/384e2c8e/attachment.html 

From weil at redhat.com  Fri Jun  2 06:33:56 2017
From: weil at redhat.com (Wei Li)
Date: Fri, 2 Jun 2017 11:33:56 +0100
Subject: [aerogear-dev] Jenkins Java client - fork?
In-Reply-To: <CAAg5f2S_E2TAe3SQaeF+ZO0M5dRbfX1CVy64wiM7H0ayQ3tzUg@mail.gmail.com>
References: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>
	<CAAg5f2TxWSmaFzERXVW-nLepTHWtryeCCU62x0ddKp4L3REKTw@mail.gmail.com>
	<CAAg5f2S_E2TAe3SQaeF+ZO0M5dRbfX1CVy64wiM7H0ayQ3tzUg@mail.gmail.com>
Message-ID: <CAHmyU2q7tPF+K9YiH=Z6UQPQzmi5=8eWLQWA+=AMx6R4t6ik5g@mail.gmail.com>

Completely agree. I just noticed it is already forked in the AG org here:
https://github.com/aerogear/java-client-api.

I will remove the one from FeedHenry GH org.

On Fri, Jun 2, 2017 at 6:57 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Ali, Wei,
>
> if we fork it, I'd strongly suggest to use the aerogear Github org, not
> the feedhenry one. It feels a bit weird using two different GH orgs for one
> project and its fork/dependency
>
> On Fri, Jun 2, 2017 at 7:54 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hey,
>>
>> I just replied to Wei's mail, which addresses a similar concern. If a
>> dependency is not properly maintained, and released, there is always room
>> for that kinda stuff.
>> If we do it, we should be doing it w/ different packages (e.g.
>> org.aerogear.com.offbytwo.jenkins), as a last resort :-)
>>
>> I'd suggest to get in touch w/ the maintainer, and explain him, that we
>> are interested in helping, and would also like to have frequent releases :)
>> Perhaps that's the first strategy, before going hard on a fork - that has
>> the risk of being always different than the rest of the usptream community.
>>
>>
>> -M
>>
>>
>> On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <aliok at redhat.com> wrote:
>>
>>> Hi,
>>>
>>> In order to make our Digger Java client working as we like, we needed to
>>> make changes in the underlying Jenkins Java client [1].
>>> We sent a PR, but we don't know when the project owner will merge it.
>>> So, for testing purposes of our own, we would like to release our fork of
>>> Jenkins Java client in a snapshot repository.
>>>
>>> What do you say? Any other and better approach?
>>>
>>> Where can we publish the snapshots of our fork?
>>>
>>> Note: The project owner is a kind guy and will perhaps publish a
>>> snapshot release for us after merging our PR, but we cannot rely on that
>>> workflow for long time for other needed changes.
>>>
>>> --
>>>
>>> ALI OK
>>>
>>> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>>>
>>> Red Hat
>>>
>>> <https://www.redhat.com/>
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

WEI LI

SENIOR SOFTWARE ENGINEER

Red Hat Mobile <https://www.redhat.com/>

weil at redhat.com    M: +353862393272
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/36278fe0/attachment-0001.html 

From weil at redhat.com  Fri Jun  2 06:38:59 2017
From: weil at redhat.com (Wei Li)
Date: Fri, 2 Jun 2017 11:38:59 +0100
Subject: [aerogear-dev] Jenkins Java client - fork?
In-Reply-To: <CAHmyU2q7tPF+K9YiH=Z6UQPQzmi5=8eWLQWA+=AMx6R4t6ik5g@mail.gmail.com>
References: <CABoO8Ld80dXUOWOa8J016EgS7sUSPQ2QkbwTMbsZOuZN1vJdww@mail.gmail.com>
	<CAAg5f2TxWSmaFzERXVW-nLepTHWtryeCCU62x0ddKp4L3REKTw@mail.gmail.com>
	<CAAg5f2S_E2TAe3SQaeF+ZO0M5dRbfX1CVy64wiM7H0ayQ3tzUg@mail.gmail.com>
	<CAHmyU2q7tPF+K9YiH=Z6UQPQzmi5=8eWLQWA+=AMx6R4t6ik5g@mail.gmail.com>
Message-ID: <CAHmyU2p+8XaNCLnQhWXJYFoVqDqSGNJHLTAsnmtr4vR=SZ5yRA@mail.gmail.com>

@Matthias can you give me write access to this repo:
https://github.com/aerogear/java-client-api. Thanks.

On Fri, Jun 2, 2017 at 11:33 AM, Wei Li <weil at redhat.com> wrote:

> Completely agree. I just noticed it is already forked in the AG org here:
> https://github.com/aerogear/java-client-api.
>
> I will remove the one from FeedHenry GH org.
>
> On Fri, Jun 2, 2017 at 6:57 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Ali, Wei,
>>
>> if we fork it, I'd strongly suggest to use the aerogear Github org, not
>> the feedhenry one. It feels a bit weird using two different GH orgs for one
>> project and its fork/dependency
>>
>> On Fri, Jun 2, 2017 at 7:54 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hey,
>>>
>>> I just replied to Wei's mail, which addresses a similar concern. If a
>>> dependency is not properly maintained, and released, there is always room
>>> for that kinda stuff.
>>> If we do it, we should be doing it w/ different packages (e.g.
>>> org.aerogear.com.offbytwo.jenkins), as a last resort :-)
>>>
>>> I'd suggest to get in touch w/ the maintainer, and explain him, that we
>>> are interested in helping, and would also like to have frequent releases :)
>>> Perhaps that's the first strategy, before going hard on a fork - that has
>>> the risk of being always different than the rest of the usptream community.
>>>
>>>
>>> -M
>>>
>>>
>>> On Thu, Jun 1, 2017 at 5:28 PM, Ali Ok <aliok at redhat.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> In order to make our Digger Java client working as we like, we needed
>>>> to make changes in the underlying Jenkins Java client [1].
>>>> We sent a PR, but we don't know when the project owner will merge it.
>>>> So, for testing purposes of our own, we would like to release our fork of
>>>> Jenkins Java client in a snapshot repository.
>>>>
>>>> What do you say? Any other and better approach?
>>>>
>>>> Where can we publish the snapshots of our fork?
>>>>
>>>> Note: The project owner is a kind guy and will perhaps publish a
>>>> snapshot release for us after merging our PR, but we cannot rely on that
>>>> workflow for long time for other needed changes.
>>>>
>>>> --
>>>>
>>>> ALI OK
>>>>
>>>> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE APPLICATION PLATFORM
>>>>
>>>> Red Hat
>>>>
>>>> <https://www.redhat.com/>
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> WEI LI
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> weil at redhat.com    M: +353862393272
> <https://red.ht/sig>
>



-- 

WEI LI

SENIOR SOFTWARE ENGINEER

Red Hat Mobile <https://www.redhat.com/>

weil at redhat.com    M: +353862393272
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/f1080914/attachment.html 

From matzew at apache.org  Fri Jun  2 09:49:51 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 2 Jun 2017 15:49:51 +0200
Subject: [aerogear-dev] GSoC 2017: UPS and Apache Kafka
Message-ID: <CAAg5f2TaTau0FJzQPiS2C5bqPUykBsenDkJfU9kOB1CadVO0zQ@mail.gmail.com>

Hi,

for this years project, we are now beyond community bonding, and coding on
the project, and required research do start.

In last meeting w/ our students we discussed a bit the basics for the next
week or so.
The initial POC/spike should be this JIRA:
https://issues.jboss.org/browse/AGPUSH-2098

Note, all work should be done on the "GSOC_2017_kafka" branch:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/GSOC_2017_kafka

For starters, I've sent a first basic PR against the branch:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/835

Besides the initial epic, we are going to create more and more JIRAs, in
AGPUSH, with the "gsoc_2017" label. Here is a public filter for those
tagged JIRA tickets:
https://issues.jboss.org/issues/?filter=12332273

We should also create a JIRA board for sprint planing and our backlog, on
the GSoC project.


Cheers!
Matthias


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170602/c2e33b9c/attachment.html 

From aliok at redhat.com  Mon Jun  5 08:42:56 2017
From: aliok at redhat.com (Ali Ok)
Date: Mon, 5 Jun 2017 15:42:56 +0300
Subject: [aerogear-dev] [digger-java-client] POM broken in JBoss Nexus
Message-ID: <CABoO8Lfx55RGa1eNPSE3vZW8Yxu3JGi0Td9gxoeABHFWjsk_Dg@mail.gmail.com>

Hi,

There is something wrong with the POM file in Jboss Nexus for Digger Java
Client:
http://repository.jboss.org/nexus/content/groups/public/org/jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/digger-java-client-1.0.0-20170530.204446-3.pom

I am talking about the POM file that is sibling to the JAR file; not the
pom.xml inside the JAR.

FYI: this is the POM file for previous snapshot release (Dec 2016)
http://repository.jboss.org/nexus/content/groups/public/org/jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/digger-java-client-1.0.0-20161214.152240-2.pom

Can I help the previous publisher to fix the problem?

Cheers,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170605/98387733/attachment.html 

From matzew at apache.org  Tue Jun  6 06:14:44 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 6 Jun 2017 12:14:44 +0200
Subject: [aerogear-dev] [digger-java-client] POM broken in JBoss Nexus
In-Reply-To: <CABoO8Lfx55RGa1eNPSE3vZW8Yxu3JGi0Td9gxoeABHFWjsk_Dg@mail.gmail.com>
References: <CABoO8Lfx55RGa1eNPSE3vZW8Yxu3JGi0Td9gxoeABHFWjsk_Dg@mail.gmail.com>
Message-ID: <CAAg5f2QWtYEOpz94zxuT2fJtz-63QH-q=JcjQHdr8vOFuTim7w@mail.gmail.com>

hey,

Ali, here we go:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/digger-java-client-1.0.0-20170606.101303-4.pom

-M

On Mon, Jun 5, 2017 at 2:42 PM, Ali Ok <aliok at redhat.com> wrote:

> Hi,
>
> There is something wrong with the POM file in Jboss Nexus for Digger Java
> Client:
> http://repository.jboss.org/nexus/content/groups/public/
> org/jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/
> digger-java-client-1.0.0-20170530.204446-3.pom
>
> I am talking about the POM file that is sibling to the JAR file; not the
> pom.xml inside the JAR.
>
> FYI: this is the POM file for previous snapshot release (Dec 2016)
> http://repository.jboss.org/nexus/content/groups/public/
> org/jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/
> digger-java-client-1.0.0-20161214.152240-2.pom
>
> Can I help the previous publisher to fix the problem?
>
> Cheers,
> Ali
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170606/8b40d2e0/attachment-0001.html 

From aliok at redhat.com  Tue Jun  6 08:47:53 2017
From: aliok at redhat.com (Ali Ok)
Date: Tue, 6 Jun 2017 15:47:53 +0300
Subject: [aerogear-dev] [digger-java-client] POM broken in JBoss Nexus
In-Reply-To: <CAAg5f2QWtYEOpz94zxuT2fJtz-63QH-q=JcjQHdr8vOFuTim7w@mail.gmail.com>
References: <CABoO8Lfx55RGa1eNPSE3vZW8Yxu3JGi0Td9gxoeABHFWjsk_Dg@mail.gmail.com>
	<CAAg5f2QWtYEOpz94zxuT2fJtz-63QH-q=JcjQHdr8vOFuTim7w@mail.gmail.com>
Message-ID: <CABoO8LdAfGMNoh=_3UncisiSkEQVy3Fs8o0y-qbtUHqEwznOOw@mail.gmail.com>

Thanks Matthias

On Tue, Jun 6, 2017 at 1:14 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> hey,
>
> Ali, here we go:
> https://repository.jboss.org/nexus/content/repositories/
> snapshots/org/jboss/aerogear/digger-java-client/1.0.0-
> SNAPSHOT/digger-java-client-1.0.0-20170606.101303-4.pom
>
> -M
>
> On Mon, Jun 5, 2017 at 2:42 PM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hi,
>>
>> There is something wrong with the POM file in Jboss Nexus for Digger Java
>> Client:
>> http://repository.jboss.org/nexus/content/groups/public/org/
>> jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/digger-
>> java-client-1.0.0-20170530.204446-3.pom
>>
>> I am talking about the POM file that is sibling to the JAR file; not the
>> pom.xml inside the JAR.
>>
>> FYI: this is the POM file for previous snapshot release (Dec 2016)
>> http://repository.jboss.org/nexus/content/groups/public/org/
>> jboss/aerogear/digger-java-client/1.0.0-SNAPSHOT/digger-
>> java-client-1.0.0-20161214.152240-2.pom
>>
>> Can I help the previous publisher to fix the problem?
>>
>> Cheers,
>> Ali
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170606/8bbc5c11/attachment.html 

From polina.n.koleva at gmail.com  Tue Jun 13 16:04:18 2017
From: polina.n.koleva at gmail.com (Polina Koleva)
Date: Tue, 13 Jun 2017 13:04:18 -0700 (MST)
Subject: [aerogear-dev] GSoC Project Blogs
Message-ID: <1497384258450-13020.post@n5.nabble.com>

Hey :)

Me and Dimitra have decided to create blogs where we can share our
experience working on the project so that everyone interested can see our
progress. Moreover, a blog can make the initiative GSoC more popular because
it is a pity that some students are not familiar with it. 
My  blog <https://polinankoleva.github.io/>   is already set up and  my
first intro post
<https://polinankoleva.github.io/personal/2017/06/12/me-the-intro.html>   is
waiting for you to read it. Soon I plan to add an article about the project
itself. Excited to hear your feedback. Stay tuned.

Polina



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/GSoC-Project-Blogs-tp13020.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

From matzew at apache.org  Fri Jun 16 07:16:52 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 16 Jun 2017 13:16:52 +0200
Subject: [aerogear-dev] WildFly 11
In-Reply-To: <CAAg5f2T=5sg5wgQHYZQwYSMR0BJeuV++cx1js2TiirZxptD5rg@mail.gmail.com>
References: <CAAg5f2T=5sg5wgQHYZQwYSMR0BJeuV++cx1js2TiirZxptD5rg@mail.gmail.com>
Message-ID: <CAAg5f2SgK5fEp5iUo1Myb2CWnEM4+eXk+fTf=kZky2TsymweQg@mail.gmail.com>

just tested alpha1, but our legacy keycloak is biting us:

https://issues.jboss.org/browse/AGPUSH-2117

-M



On Fri, May 26, 2017 at 1:16 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> while WF 11.0 is not yet release, I'd like to see us getting on to WF 11
> on the master branch
>
> http://wildfly.org/downloads/
>
> I think that our master branch should be exclusively target the latest
> from WF stable, which is 11 in the future. So getting to know what's
> problematic w/ the WF 11-alpha series is a good thing.
>
> Comments ?
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170616/78e7a02b/attachment.html 

From jgallaso at redhat.com  Mon Jun 19 03:53:20 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Mon, 19 Jun 2017 09:53:20 +0200
Subject: [aerogear-dev] WildFly 11
In-Reply-To: <CAAg5f2SgK5fEp5iUo1Myb2CWnEM4+eXk+fTf=kZky2TsymweQg@mail.gmail.com>
References: <CAAg5f2T=5sg5wgQHYZQwYSMR0BJeuV++cx1js2TiirZxptD5rg@mail.gmail.com>
	<CAAg5f2SgK5fEp5iUo1Myb2CWnEM4+eXk+fTf=kZky2TsymweQg@mail.gmail.com>
Message-ID: <CAGsbZmG=CuQ+65KZk3kMty3giL0RmMqZoqh3v38u0eNeo+PZPw@mail.gmail.com>

Does make sense to update Keycloak so it doesn't fail? It seems to be a
dependency issue.

On 16 June 2017 at 13:16, Matthias Wessendorf <matzew at apache.org> wrote:

> just tested alpha1, but our legacy keycloak is biting us:
>
> https://issues.jboss.org/browse/AGPUSH-2117
>
> -M
>
>
>
> On Fri, May 26, 2017 at 1:16 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> while WF 11.0 is not yet release, I'd like to see us getting on to WF 11
>> on the master branch
>>
>> http://wildfly.org/downloads/
>>
>> I think that our master branch should be exclusively target the latest
>> from WF stable, which is 11 in the future. So getting to know what's
>> problematic w/ the WF 11-alpha series is a good thing.
>>
>> Comments ?
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170619/76b6c222/attachment.html 

From matzew at apache.org  Mon Jun 19 04:15:16 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 Jun 2017 10:15:16 +0200
Subject: [aerogear-dev] WildFly 11
In-Reply-To: <CAGsbZmG=CuQ+65KZk3kMty3giL0RmMqZoqh3v38u0eNeo+PZPw@mail.gmail.com>
References: <CAAg5f2T=5sg5wgQHYZQwYSMR0BJeuV++cx1js2TiirZxptD5rg@mail.gmail.com>
	<CAAg5f2SgK5fEp5iUo1Myb2CWnEM4+eXk+fTf=kZky2TsymweQg@mail.gmail.com>
	<CAGsbZmG=CuQ+65KZk3kMty3giL0RmMqZoqh3v38u0eNeo+PZPw@mail.gmail.com>
Message-ID: <CAAg5f2QVq2tCfH+cSELtFUyQ4Tjhk4oXRtpkt-xHxzrM8oSr3A@mail.gmail.com>

we cant do that simply.

Unfortunately we buld a custom KC server, based on 1.5 years APIs. we do
have a JIRA to decouple, so we can just point against latest of KC


On Mon, Jun 19, 2017 at 9:53 AM, Jose Miguel Gallas Olmedo <
jgallaso at redhat.com> wrote:

> Does make sense to update Keycloak so it doesn't fail? It seems to be a
> dependency issue.
>
> On 16 June 2017 at 13:16, Matthias Wessendorf <matzew at apache.org> wrote:
>
>> just tested alpha1, but our legacy keycloak is biting us:
>>
>> https://issues.jboss.org/browse/AGPUSH-2117
>>
>> -M
>>
>>
>>
>> On Fri, May 26, 2017 at 1:16 PM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> while WF 11.0 is not yet release, I'd like to see us getting on to WF 11
>>> on the master branch
>>>
>>> http://wildfly.org/downloads/
>>>
>>> I think that our master branch should be exclusively target the latest
>>> from WF stable, which is 11 in the future. So getting to know what's
>>> problematic w/ the WF 11-alpha series is a good thing.
>>>
>>> Comments ?
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170619/b2c6f067/attachment-0001.html 

From matzew at apache.org  Mon Jun 19 04:15:54 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 19 Jun 2017 10:15:54 +0200
Subject: [aerogear-dev] Fwd: [Aerogear-users] AeroGear Digger Logo
In-Reply-To: <CABoO8Le_xkQMiTx1Xemd_CJXw3B-zCgvZyyFF0XLLXTdNDNUng@mail.gmail.com>
References: <CABoO8Le_xkQMiTx1Xemd_CJXw3B-zCgvZyyFF0XLLXTdNDNUng@mail.gmail.com>
Message-ID: <CAAg5f2SCAtfEPiYnnBq5eO-epk6QPr7LD4QeKeb47v8mmvrZ3A@mail.gmail.com>

---------- Forwarded message ----------
From: Ali Ok <aliok at redhat.com>
Date: Mon, Jun 19, 2017 at 9:40 AM
Subject: [Aerogear-users] AeroGear Digger Logo
To: aerogear-users at lists.jboss.org


Hello,

We would like to pick a logo for the new AeroGear module, Digger [1].

James Cobb has already prepared some great designs and now we vote to pick
the best one [2].

We have prepared a Google poll (no login required) here:
https://goo.gl/forms/WdUoHecQtrshMkBg1

The poll will be open for 10 days (until June 29th 10:00 AM UTC).


[1] : https://github.com/aerogear/digger-jenkins
[2] : https://issues.jboss.org/browse/DESIGN-943

Cheers,
Ali

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users




-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170619/f0d103e9/attachment.html 

From dlisnich at redhat.com  Tue Jun 20 08:35:10 2017
From: dlisnich at redhat.com (Dmytro Lisnichenko)
Date: Tue, 20 Jun 2017 14:35:10 +0200
Subject: [aerogear-dev] Test email, please ignore
Message-ID: <CAB9k3DGOy06r=dJXUdUU04qbgbojr2BwSScy7Enjox4sUiwEOg@mail.gmail.com>

Hello,

I am sending this email to see the traces in the logs and see how fast it
will be delivered. Please ignore it.

Thnx.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170620/eb56d950/attachment.html 

From lrossett at redhat.com  Wed Jun 21 05:59:44 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Wed, 21 Jun 2017 06:59:44 -0300
Subject: [aerogear-dev] digger-jenkins repo and dockerhub
Message-ID: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>

Hello,

We currently have the following in our digger-jenkins repo[1]:

   - android-sdk docker image (which includes androidctl cli);
   - jenkins android slave image;
   - openshift templates;
   - some osx related scripts;

I wanted to automatically build/push the docker images to dockerhub after a
PR is merged but I believe dockerhub has a "per repo" integration, which
means that both images would be built/pushed every time we send a pr/commit
into this repo.

Does anyone know if we can create a "per folder" integration where it
detects Dockerfile changes per folder (if we change android-sdk dockerfile
it should only build this image) and not re-build and re-push both images
on every commit?

Other options would be:

   - Move those images to their own repo;
   - Create/host a jenkins instance somewhere so we can automate this
   workflow with custom scripts.


Regards,

[1] - https://github.com/aerogear/digger-jenkins

-- 

LEONARDO ROSSETTI

SOFTWARE ENGINEER

Red Hat SP <https://www.redhat.com/>

lrossett at redhat.com    M: 11997030621
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170621/d79d4cc2/attachment.html 

From wtrocki at redhat.com  Wed Jun 21 06:31:07 2017
From: wtrocki at redhat.com (Wojciech Trocki)
Date: Wed, 21 Jun 2017 11:31:07 +0100
Subject: [aerogear-dev] digger-jenkins repo and dockerhub
In-Reply-To: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>
References: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>
Message-ID: <CAO0+n+qgACj42nWbvt9Wwoa3F0JT0xRoRScuir6pJH+gmJMtmw@mail.gmail.com>

I have done couple investigations for this particular problem. For both
Travis and Jenkins we do not have any build in way to know what was
changed.
One of the ways is just to have custom script to diff specific folders and
suppress builds in build matrix if there are no changes.
Moving images to own repo will be the easiest solution here.
We done that for all RHMAP core images.

WOJCIECH TROCKI

SOFTWARE ENGINEER

Red Hat Mobile <https://www.redhat.com/>

IM: wtrocki
<https://red.ht/sig>

On Wed, Jun 21, 2017 at 10:59 AM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> Hello,
>
> We currently have the following in our digger-jenkins repo[1]:
>
>    - android-sdk docker image (which includes androidctl cli);
>    - jenkins android slave image;
>    - openshift templates;
>    - some osx related scripts;
>
> I wanted to automatically build/push the docker images to dockerhub after
> a PR is merged but I believe dockerhub has a "per repo" integration, which
> means that both images would be built/pushed every time we send a pr/commit
> into this repo.
>
> Does anyone know if we can create a "per folder" integration where it
> detects Dockerfile changes per folder (if we change android-sdk dockerfile
> it should only build this image) and not re-build and re-push both images
> on every commit?
>
> Other options would be:
>
>    - Move those images to their own repo;
>    - Create/host a jenkins instance somewhere so we can automate this
>    workflow with custom scripts.
>
>
> Regards,
>
> [1] - https://github.com/aerogear/digger-jenkins
>
> --
>
> LEONARDO ROSSETTI
>
> SOFTWARE ENGINEER
>
> Red Hat SP <https://www.redhat.com/>
>
> lrossett at redhat.com    M: 11997030621
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170621/ae608142/attachment.html 

From aliok at redhat.com  Wed Jun 21 07:45:49 2017
From: aliok at redhat.com (Ali Ok)
Date: Wed, 21 Jun 2017 14:45:49 +0300
Subject: [aerogear-dev] digger-jenkins repo and dockerhub
In-Reply-To: <CAO0+n+qgACj42nWbvt9Wwoa3F0JT0xRoRScuir6pJH+gmJMtmw@mail.gmail.com>
References: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>
	<CAO0+n+qgACj42nWbvt9Wwoa3F0JT0xRoRScuir6pJH+gmJMtmw@mail.gmail.com>
Message-ID: <CABoO8Ld6QWtOB+rinNAyc2YTX=8w07RaPgv=78hu1m9M=0Tofg@mail.gmail.com>

>
> For both Travis and Jenkins we do not have any build in way to know what
> was changed.


In Jenkins, one can use "Included Regions". This is how I did it in a
private project of mine:

[image: Inline image 1]

This means, you can have 5 different plans that use the same repository and
the same branch, but you can trigger builds only if something has changed
in a subpath.

Anyway, I don't like having a Jenkins instance that is accessible and that
is managed by Red Hat employees only. Travis and DockerHub is more
independent and fits better to AeroGear. If only there was a way...

Cheers

On Wed, Jun 21, 2017 at 1:31 PM, Wojciech Trocki <wtrocki at redhat.com> wrote:

> I have done couple investigations for this particular problem. For both
> Travis and Jenkins we do not have any build in way to know what was
> changed.
> One of the ways is just to have custom script to diff specific folders and
> suppress builds in build matrix if there are no changes.
> Moving images to own repo will be the easiest solution here.
> We done that for all RHMAP core images.
>
> WOJCIECH TROCKI
>
> SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> IM: wtrocki
> <https://red.ht/sig>
>
> On Wed, Jun 21, 2017 at 10:59 AM, Leonardo Rossetti <lrossett at redhat.com>
> wrote:
>
>> Hello,
>>
>> We currently have the following in our digger-jenkins repo[1]:
>>
>>    - android-sdk docker image (which includes androidctl cli);
>>    - jenkins android slave image;
>>    - openshift templates;
>>    - some osx related scripts;
>>
>> I wanted to automatically build/push the docker images to dockerhub after
>> a PR is merged but I believe dockerhub has a "per repo" integration, which
>> means that both images would be built/pushed every time we send a pr/commit
>> into this repo.
>>
>> Does anyone know if we can create a "per folder" integration where it
>> detects Dockerfile changes per folder (if we change android-sdk dockerfile
>> it should only build this image) and not re-build and re-push both images
>> on every commit?
>>
>> Other options would be:
>>
>>    - Move those images to their own repo;
>>    - Create/host a jenkins instance somewhere so we can automate this
>>    workflow with custom scripts.
>>
>>
>> Regards,
>>
>> [1] - https://github.com/aerogear/digger-jenkins
>>
>> --
>>
>> LEONARDO ROSSETTI
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat SP <https://www.redhat.com/>
>>
>> lrossett at redhat.com    M: 11997030621
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170621/0534dcc0/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-21 at 14.42.12.png
Type: image/png
Size: 118628 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170621/0534dcc0/attachment-0001.png 

From lrossett at redhat.com  Thu Jun 22 05:43:08 2017
From: lrossett at redhat.com (Leonardo Rossetti)
Date: Thu, 22 Jun 2017 06:43:08 -0300
Subject: [aerogear-dev] digger-jenkins repo and dockerhub
In-Reply-To: <CABoO8Ld6QWtOB+rinNAyc2YTX=8w07RaPgv=78hu1m9M=0Tofg@mail.gmail.com>
References: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>
	<CAO0+n+qgACj42nWbvt9Wwoa3F0JT0xRoRScuir6pJH+gmJMtmw@mail.gmail.com>
	<CABoO8Ld6QWtOB+rinNAyc2YTX=8w07RaPgv=78hu1m9M=0Tofg@mail.gmail.com>
Message-ID: <CAF-nxa-vRhgFjK_UVeRyLO9=sQ_uJN02XpW7WdsNXtT0PDErRg@mail.gmail.com>

I personally think moving images to their own repo is the way to go.

On Wed, Jun 21, 2017 at 8:45 AM, Ali Ok <aliok at redhat.com> wrote:

> For both Travis and Jenkins we do not have any build in way to know what
>> was changed.
>
>
> In Jenkins, one can use "Included Regions". This is how I did it in a
> private project of mine:
>
> [image: Inline image 1]
>
> This means, you can have 5 different plans that use the same repository
> and the same branch, but you can trigger builds only if something has
> changed in a subpath.
>
> Anyway, I don't like having a Jenkins instance that is accessible and that
> is managed by Red Hat employees only. Travis and DockerHub is more
> independent and fits better to AeroGear. If only there was a way...
>
> Cheers
>
> On Wed, Jun 21, 2017 at 1:31 PM, Wojciech Trocki <wtrocki at redhat.com>
> wrote:
>
>> I have done couple investigations for this particular problem. For both
>> Travis and Jenkins we do not have any build in way to know what was
>> changed.
>> One of the ways is just to have custom script to diff specific folders
>> and suppress builds in build matrix if there are no changes.
>> Moving images to own repo will be the easiest solution here.
>> We done that for all RHMAP core images.
>>
>> WOJCIECH TROCKI
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat Mobile <https://www.redhat.com/>
>>
>> IM: wtrocki
>> <https://red.ht/sig>
>>
>> On Wed, Jun 21, 2017 at 10:59 AM, Leonardo Rossetti <lrossett at redhat.com>
>> wrote:
>>
>>> Hello,
>>>
>>> We currently have the following in our digger-jenkins repo[1]:
>>>
>>>    - android-sdk docker image (which includes androidctl cli);
>>>    - jenkins android slave image;
>>>    - openshift templates;
>>>    - some osx related scripts;
>>>
>>> I wanted to automatically build/push the docker images to dockerhub
>>> after a PR is merged but I believe dockerhub has a "per repo" integration,
>>> which means that both images would be built/pushed every time we send a
>>> pr/commit into this repo.
>>>
>>> Does anyone know if we can create a "per folder" integration where it
>>> detects Dockerfile changes per folder (if we change android-sdk dockerfile
>>> it should only build this image) and not re-build and re-push both images
>>> on every commit?
>>>
>>> Other options would be:
>>>
>>>    - Move those images to their own repo;
>>>    - Create/host a jenkins instance somewhere so we can automate this
>>>    workflow with custom scripts.
>>>
>>>
>>> Regards,
>>>
>>> [1] - https://github.com/aerogear/digger-jenkins
>>>
>>> --
>>>
>>> LEONARDO ROSSETTI
>>>
>>> SOFTWARE ENGINEER
>>>
>>> Red Hat SP <https://www.redhat.com/>
>>>
>>> lrossett at redhat.com    M: 11997030621
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEONARDO ROSSETTI

SOFTWARE ENGINEER

Red Hat SP <https://www.redhat.com/>

lrossett at redhat.com    M: 11997030621
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170622/d9511eb3/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-21 at 14.42.12.png
Type: image/png
Size: 118628 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170622/d9511eb3/attachment-0001.png 

From aliok at redhat.com  Thu Jun 22 05:55:34 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 22 Jun 2017 12:55:34 +0300
Subject: [aerogear-dev] digger-jenkins repo and dockerhub
In-Reply-To: <CAF-nxa-vRhgFjK_UVeRyLO9=sQ_uJN02XpW7WdsNXtT0PDErRg@mail.gmail.com>
References: <CAF-nxa_mhzNSsyLkEYP4_ZyyNFpikGiNw2ocpWx7HqkZKx4KGA@mail.gmail.com>
	<CAO0+n+qgACj42nWbvt9Wwoa3F0JT0xRoRScuir6pJH+gmJMtmw@mail.gmail.com>
	<CABoO8Ld6QWtOB+rinNAyc2YTX=8w07RaPgv=78hu1m9M=0Tofg@mail.gmail.com>
	<CAF-nxa-vRhgFjK_UVeRyLO9=sQ_uJN02XpW7WdsNXtT0PDErRg@mail.gmail.com>
Message-ID: <CABoO8Lf3xw1LBSmdE54nxLO77xsMx0xBYO5v7MLz8p2NxBTmdA@mail.gmail.com>

I am ok with that. Maybe I would wait a bit to gather more feedback, if
there will be any new.


On Thu, Jun 22, 2017 at 12:43 PM, Leonardo Rossetti <lrossett at redhat.com>
wrote:

> I personally think moving images to their own repo is the way to go.
>
> On Wed, Jun 21, 2017 at 8:45 AM, Ali Ok <aliok at redhat.com> wrote:
>
>> For both Travis and Jenkins we do not have any build in way to know what
>>> was changed.
>>
>>
>> In Jenkins, one can use "Included Regions". This is how I did it in a
>> private project of mine:
>>
>> [image: Inline image 1]
>>
>> This means, you can have 5 different plans that use the same repository
>> and the same branch, but you can trigger builds only if something has
>> changed in a subpath.
>>
>> Anyway, I don't like having a Jenkins instance that is accessible and
>> that is managed by Red Hat employees only. Travis and DockerHub is more
>> independent and fits better to AeroGear. If only there was a way...
>>
>> Cheers
>>
>> On Wed, Jun 21, 2017 at 1:31 PM, Wojciech Trocki <wtrocki at redhat.com>
>> wrote:
>>
>>> I have done couple investigations for this particular problem. For both
>>> Travis and Jenkins we do not have any build in way to know what was
>>> changed.
>>> One of the ways is just to have custom script to diff specific folders
>>> and suppress builds in build matrix if there are no changes.
>>> Moving images to own repo will be the easiest solution here.
>>> We done that for all RHMAP core images.
>>>
>>> WOJCIECH TROCKI
>>>
>>> SOFTWARE ENGINEER
>>>
>>> Red Hat Mobile <https://www.redhat.com/>
>>>
>>> IM: wtrocki
>>> <https://red.ht/sig>
>>>
>>> On Wed, Jun 21, 2017 at 10:59 AM, Leonardo Rossetti <lrossett at redhat.com
>>> > wrote:
>>>
>>>> Hello,
>>>>
>>>> We currently have the following in our digger-jenkins repo[1]:
>>>>
>>>>    - android-sdk docker image (which includes androidctl cli);
>>>>    - jenkins android slave image;
>>>>    - openshift templates;
>>>>    - some osx related scripts;
>>>>
>>>> I wanted to automatically build/push the docker images to dockerhub
>>>> after a PR is merged but I believe dockerhub has a "per repo" integration,
>>>> which means that both images would be built/pushed every time we send a
>>>> pr/commit into this repo.
>>>>
>>>> Does anyone know if we can create a "per folder" integration where it
>>>> detects Dockerfile changes per folder (if we change android-sdk dockerfile
>>>> it should only build this image) and not re-build and re-push both images
>>>> on every commit?
>>>>
>>>> Other options would be:
>>>>
>>>>    - Move those images to their own repo;
>>>>    - Create/host a jenkins instance somewhere so we can automate this
>>>>    workflow with custom scripts.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> [1] - https://github.com/aerogear/digger-jenkins
>>>>
>>>> --
>>>>
>>>> LEONARDO ROSSETTI
>>>>
>>>> SOFTWARE ENGINEER
>>>>
>>>> Red Hat SP <https://www.redhat.com/>
>>>>
>>>> lrossett at redhat.com    M: 11997030621
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> LEONARDO ROSSETTI
>
> SOFTWARE ENGINEER
>
> Red Hat SP <https://www.redhat.com/>
>
> lrossett at redhat.com    M: 11997030621
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170622/608b515f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-21 at 14.42.12.png
Type: image/png
Size: 118628 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170622/608b515f/attachment-0001.png 

From jgallaso at redhat.com  Fri Jun 23 10:08:11 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Fri, 23 Jun 2017 16:08:11 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
Message-ID: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>

Hi all,

I recently create a Docker image of our push FCM proxy, made with Wiremock.
Since we are no longer using the FCM proxy in
https://github.com/aerogear/push-network-proxies (even the Dockerfile there
only consider APNs) I think we could remove it from there and refactor the
repository like this:

push-network-proxies/
   fcm/
      Dockerfile
      ...
   apns/
      Dockerfile
      ...
   push-network-proxies-template.yml

So that we have everything in the same place. I also made a template for
Openshift so that we can setup a testing environment for UPS quickly. I
think that's the ultimate point of having the mocks together.

WDYT?

-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170623/fd22ab51/attachment.html 

From matzew at apache.org  Sat Jun 24 09:33:42 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 24 Jun 2017 15:33:42 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
Message-ID: <CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>

On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
jgallaso at redhat.com> wrote:

> Hi all,
>
> I recently create a Docker image of our push FCM proxy, made with
> Wiremock. Since we are no longer using the FCM proxy in
> https://github.com/aerogear/push-network-proxies (even the Dockerfile
> there only consider APNs) I think we could remove it from there and
> refactor the repository like this:
>

not sure if we should delete it yet - I think it was written by QE to test
GCMv2 - but push server is now GCMv3/FCM compliant. I think there is some
features missing there. Perhaps it's still good - not really sure.

But if Wiremock offers what we need -> fine, better to use things that are
supported through a larger community ;-)


>
> push-network-proxies/
>    fcm/
>       Dockerfile
>       ...
>    apns/
>       Dockerfile
>       ...
>    push-network-proxies-template.yml
>
> So that we have everything in the same place. I also made a template for
> Openshift so that we can setup a testing environment for UPS quickly. I
> think that's the ultimate point of having the mocks together.
>

I like that, having this structure, where FCM is based on Wiremock, right?


>
> WDYT?
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170624/9b6db82c/attachment.html 

From jgallaso at redhat.com  Mon Jun 26 03:19:50 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Mon, 26 Jun 2017 09:19:50 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
	<CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
Message-ID: <CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>

> not sure if we should delete it yet - I think it was written by QE to test
> GCMv2 - but push server is now GCMv3/FCM compliant. I think there is some
> features missing there. Perhaps it's still good - not really sure.


Actually, we could keep the old gcm-proxy as well. The repo is
"push-network-proxies" which means many proxies. We could store the new one
under "fcm-wiremock" and the old one under "gcm-java" but for this, I
think, we ought to extract GCM logic from the current project, leaving only
APNS stuff.

push-network-proxies/
   fcm-wiremock/
      ...
   apns-java/
      ...
   gcm-java/
      ...
   push-network-proxies-template.yml

In the future we might want to add new different implementations (or new
proxies) so it makes sense to me to have push-network-proxies as an
extensible repository, not as a only-2-proxies one.

On 24 June 2017 at 15:33, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
> jgallaso at redhat.com> wrote:
>
>> Hi all,
>>
>> I recently create a Docker image of our push FCM proxy, made with
>> Wiremock. Since we are no longer using the FCM proxy in
>> https://github.com/aerogear/push-network-proxies (even the Dockerfile
>> there only consider APNs) I think we could remove it from there and
>> refactor the repository like this:
>>
>
> not sure if we should delete it yet - I think it was written by QE to test
> GCMv2 - but push server is now GCMv3/FCM compliant. I think there is some
> features missing there. Perhaps it's still good - not really sure.
>
> But if Wiremock offers what we need -> fine, better to use things that are
> supported through a larger community ;-)
>
>
>>
>> push-network-proxies/
>>    fcm/
>>       Dockerfile
>>       ...
>>    apns/
>>       Dockerfile
>>       ...
>>    push-network-proxies-template.yml
>>
>> So that we have everything in the same place. I also made a template for
>> Openshift so that we can setup a testing environment for UPS quickly. I
>> think that's the ultimate point of having the mocks together.
>>
>
> I like that, having this structure, where FCM is based on Wiremock, right?
>
>
>>
>> WDYT?
>>
>> --
>>
>> JOSE MIGUEL GALLAS OLMEDO
>>
>> ASSOCIATE QE, mobile
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>>
>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170626/aafbbbc5/attachment-0001.html 

From matzew at apache.org  Mon Jun 26 04:19:50 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 26 Jun 2017 10:19:50 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
	<CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
	<CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>
Message-ID: <CAAg5f2RbXrJGShHZxy7F5bCC-fnd9eZjq5pgiuLynCgzbiu6uQ@mail.gmail.com>

On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
jgallaso at redhat.com> wrote:

>
> not sure if we should delete it yet - I think it was written by QE to test
>> GCMv2 - but push server is now GCMv3/FCM compliant. I think there is some
>> features missing there. Perhaps it's still good - not really sure.
>
>
> Actually, we could keep the old gcm-proxy as well. The repo is
> "push-network-proxies" which means many proxies. We could store the new one
> under "fcm-wiremock" and the old one under "gcm-java"
>

+1


> but for this, I think, we ought to extract GCM logic from the current
> project, leaving only APNS stuff.
>

no, not just APNs, IMO

>
> push-network-proxies/
>    fcm-wiremock/
>       ...
>    apns-java/
>       ...
>    gcm-java/
>       ...
>    push-network-proxies-template.yml
>

I think this is a good structure


>
> In the future we might want to add new different implementations (or new
> proxies) so it makes sense to me to have push-network-proxies as an
> extensible repository, not as a only-2-proxies one.
>
> On 24 June 2017 at 15:33, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
>> jgallaso at redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> I recently create a Docker image of our push FCM proxy, made with
>>> Wiremock. Since we are no longer using the FCM proxy in
>>> https://github.com/aerogear/push-network-proxies (even the Dockerfile
>>> there only consider APNs) I think we could remove it from there and
>>> refactor the repository like this:
>>>
>>
>> not sure if we should delete it yet - I think it was written by QE to
>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>> some features missing there. Perhaps it's still good - not really sure.
>>
>> But if Wiremock offers what we need -> fine, better to use things that
>> are supported through a larger community ;-)
>>
>>
>>>
>>> push-network-proxies/
>>>    fcm/
>>>       Dockerfile
>>>       ...
>>>    apns/
>>>       Dockerfile
>>>       ...
>>>    push-network-proxies-template.yml
>>>
>>> So that we have everything in the same place. I also made a template for
>>> Openshift so that we can setup a testing environment for UPS quickly. I
>>> think that's the ultimate point of having the mocks together.
>>>
>>
>> I like that, having this structure, where FCM is based on Wiremock,
>> right?
>>
>>
>>>
>>> WDYT?
>>>
>>> --
>>>
>>> JOSE MIGUEL GALLAS OLMEDO
>>>
>>> ASSOCIATE QE, mobile
>>>
>>> Red Hat
>>>
>>> <https://www.redhat.com/>
>>>
>>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170626/5d992e20/attachment.html 

From jgallaso at redhat.com  Mon Jun 26 05:02:31 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Mon, 26 Jun 2017 11:02:31 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAAg5f2RbXrJGShHZxy7F5bCC-fnd9eZjq5pgiuLynCgzbiu6uQ@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
	<CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
	<CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>
	<CAAg5f2RbXrJGShHZxy7F5bCC-fnd9eZjq5pgiuLynCgzbiu6uQ@mail.gmail.com>
Message-ID: <CAGsbZmF4sv33dWwr3mUFKPZD1ZbqykU-GpYiR3zydFxStVmHpw@mail.gmail.com>

?On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
> jgallaso at redhat.com> wrote:
>
>>
>> not sure if we should delete it yet - I think it was written by QE to
>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>> some features missing there. Perhaps it's still good - not really sure.
>>
>>
>> Actually, we could keep the old gcm-proxy as well. The repo is
>> "push-network-proxies" which means many proxies. We could store the new one
>> under "fcm-wiremock" and the old one under "gcm-java"
>>
>
> +1
>
>
>> but for this, I think, we ought to extract GCM logic from the current
>> project, leaving only APNS stuff.
>>
>
> no, not just APNs, IMO
>

I think I didn't explain it clear enough, let me start again: The current
repository is a java project that implements both GCM and APNS proxies.
What I mean with "extract GCM logic from the project" is exactly what you
see in the structure: "apns-java" would have the original
"push-network-proxies" java project but only with the APNS implementation
and "gcm-java" would have the original "push-network-proxies" java project
but only with GCM implementation. Maybe "decouple" would be a better term.

Does it make more sense now or didn't I understand you point maybe?

-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>

On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:

>
>
> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
> jgallaso at redhat.com> wrote:
>
>>
>> not sure if we should delete it yet - I think it was written by QE to
>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>> some features missing there. Perhaps it's still good - not really sure.
>>
>>
>> Actually, we could keep the old gcm-proxy as well. The repo is
>> "push-network-proxies" which means many proxies. We could store the new one
>> under "fcm-wiremock" and the old one under "gcm-java"
>>
>
> +1
>
>
>> but for this, I think, we ought to extract GCM logic from the current
>> project, leaving only APNS stuff.
>>
>
> no, not just APNs, IMO
>
>>
>> push-network-proxies/
>>    fcm-wiremock/
>>       ...
>>    apns-java/
>>       ...
>>    gcm-java/
>>       ...
>>    push-network-proxies-template.yml
>>
>
> I think this is a good structure
>
>
>>
>> In the future we might want to add new different implementations (or new
>> proxies) so it makes sense to me to have push-network-proxies as an
>> extensible repository, not as a only-2-proxies one.
>>
>> On 24 June 2017 at 15:33, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>>
>>>
>>> On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
>>> jgallaso at redhat.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I recently create a Docker image of our push FCM proxy, made with
>>>> Wiremock. Since we are no longer using the FCM proxy in
>>>> https://github.com/aerogear/push-network-proxies (even the Dockerfile
>>>> there only consider APNs) I think we could remove it from there and
>>>> refactor the repository like this:
>>>>
>>>
>>> not sure if we should delete it yet - I think it was written by QE to
>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>> some features missing there. Perhaps it's still good - not really sure.
>>>
>>> But if Wiremock offers what we need -> fine, better to use things that
>>> are supported through a larger community ;-)
>>>
>>>
>>>>
>>>> push-network-proxies/
>>>>    fcm/
>>>>       Dockerfile
>>>>       ...
>>>>    apns/
>>>>       Dockerfile
>>>>       ...
>>>>    push-network-proxies-template.yml
>>>>
>>>> So that we have everything in the same place. I also made a template
>>>> for Openshift so that we can setup a testing environment for UPS quickly. I
>>>> think that's the ultimate point of having the mocks together.
>>>>
>>>
>>> I like that, having this structure, where FCM is based on Wiremock,
>>> right?
>>>
>>>
>>>>
>>>> WDYT?
>>>>
>>>> --
>>>>
>>>> JOSE MIGUEL GALLAS OLMEDO
>>>>
>>>> ASSOCIATE QE, mobile
>>>>
>>>> Red Hat
>>>>
>>>> <https://www.redhat.com/>
>>>>
>>>> M: +34618488633
>>>> <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>>
>> JOSE MIGUEL GALLAS OLMEDO
>>
>> ASSOCIATE QE, mobile
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>>
>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>
>> <https://red.ht/sig>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170626/71ab7516/attachment-0001.html 

From jgallaso at redhat.com  Wed Jun 28 05:57:50 2017
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Wed, 28 Jun 2017 11:57:50 +0200
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAGsbZmF4sv33dWwr3mUFKPZD1ZbqykU-GpYiR3zydFxStVmHpw@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
	<CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
	<CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>
	<CAAg5f2RbXrJGShHZxy7F5bCC-fnd9eZjq5pgiuLynCgzbiu6uQ@mail.gmail.com>
	<CAGsbZmF4sv33dWwr3mUFKPZD1ZbqykU-GpYiR3zydFxStVmHpw@mail.gmail.com>
Message-ID: <CAGsbZmH2TcDcEMC3pF4bPmAW1c7w1y-WmXSEcWxT1HKVSjL1PQ@mail.gmail.com>

Matthias is already unreachable but I think he agreed on this idea so I
will proceed to send a PR with this changes.
Maybe @Leigh or @Summers want to add some comments on this?

I've created this ticket <https://issues.jboss.org/browse/AGPUSH-2127> so
far and will work on the PR now.

On 26 June 2017 at 11:02, Jose Miguel Gallas Olmedo <jgallaso at redhat.com>
wrote:

> ?On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
>> jgallaso at redhat.com> wrote:
>>
>>>
>>> not sure if we should delete it yet - I think it was written by QE to
>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>> some features missing there. Perhaps it's still good - not really sure.
>>>
>>>
>>> Actually, we could keep the old gcm-proxy as well. The repo is
>>> "push-network-proxies" which means many proxies. We could store the new one
>>> under "fcm-wiremock" and the old one under "gcm-java"
>>>
>>
>> +1
>>
>>
>>> but for this, I think, we ought to extract GCM logic from the current
>>> project, leaving only APNS stuff.
>>>
>>
>> no, not just APNs, IMO
>>
>
> I think I didn't explain it clear enough, let me start again: The current
> repository is a java project that implements both GCM and APNS proxies.
> What I mean with "extract GCM logic from the project" is exactly what you
> see in the structure: "apns-java" would have the original
> "push-network-proxies" java project but only with the APNS implementation
> and "gcm-java" would have the original "push-network-proxies" java project
> but only with GCM implementation. Maybe "decouple" would be a better term.
>
> Does it make more sense now or didn't I understand you point maybe?
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
>
> On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:
>
>>
>>
>> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
>> jgallaso at redhat.com> wrote:
>>
>>>
>>> not sure if we should delete it yet - I think it was written by QE to
>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>> some features missing there. Perhaps it's still good - not really sure.
>>>
>>>
>>> Actually, we could keep the old gcm-proxy as well. The repo is
>>> "push-network-proxies" which means many proxies. We could store the new one
>>> under "fcm-wiremock" and the old one under "gcm-java"
>>>
>>
>> +1
>>
>>
>>> but for this, I think, we ought to extract GCM logic from the current
>>> project, leaving only APNS stuff.
>>>
>>
>> no, not just APNs, IMO
>>
>>>
>>> push-network-proxies/
>>>    fcm-wiremock/
>>>       ...
>>>    apns-java/
>>>       ...
>>>    gcm-java/
>>>       ...
>>>    push-network-proxies-template.yml
>>>
>>
>> I think this is a good structure
>>
>>
>>>
>>> In the future we might want to add new different implementations (or new
>>> proxies) so it makes sense to me to have push-network-proxies as an
>>> extensible repository, not as a only-2-proxies one.
>>>
>>> On 24 June 2017 at 15:33, Matthias Wessendorf <matzew at apache.org> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
>>>> jgallaso at redhat.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I recently create a Docker image of our push FCM proxy, made with
>>>>> Wiremock. Since we are no longer using the FCM proxy in
>>>>> https://github.com/aerogear/push-network-proxies (even the Dockerfile
>>>>> there only consider APNs) I think we could remove it from there and
>>>>> refactor the repository like this:
>>>>>
>>>>
>>>> not sure if we should delete it yet - I think it was written by QE to
>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>> some features missing there. Perhaps it's still good - not really sure.
>>>>
>>>> But if Wiremock offers what we need -> fine, better to use things that
>>>> are supported through a larger community ;-)
>>>>
>>>>
>>>>>
>>>>> push-network-proxies/
>>>>>    fcm/
>>>>>       Dockerfile
>>>>>       ...
>>>>>    apns/
>>>>>       Dockerfile
>>>>>       ...
>>>>>    push-network-proxies-template.yml
>>>>>
>>>>> So that we have everything in the same place. I also made a template
>>>>> for Openshift so that we can setup a testing environment for UPS quickly. I
>>>>> think that's the ultimate point of having the mocks together.
>>>>>
>>>>
>>>> I like that, having this structure, where FCM is based on Wiremock,
>>>> right?
>>>>
>>>>
>>>>>
>>>>> WDYT?
>>>>>
>>>>> --
>>>>>
>>>>> JOSE MIGUEL GALLAS OLMEDO
>>>>>
>>>>> ASSOCIATE QE, mobile
>>>>>
>>>>> Red Hat
>>>>>
>>>>> <https://www.redhat.com/>
>>>>>
>>>>> M: +34618488633
>>>>> <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>>> <https://red.ht/sig>
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> JOSE MIGUEL GALLAS OLMEDO
>>>
>>> ASSOCIATE QE, mobile
>>>
>>> Red Hat
>>>
>>> <https://www.redhat.com/>
>>>
>>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>
>>> <https://red.ht/sig>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
>



-- 

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

Red Hat

<https://www.redhat.com/>

M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170628/54d7ec0a/attachment-0001.html 

From matzew at apache.org  Wed Jun 28 07:30:29 2017
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 28 Jun 2017 11:30:29 +0000
Subject: [aerogear-dev] Refactoring push-network-proxies
In-Reply-To: <CAGsbZmH2TcDcEMC3pF4bPmAW1c7w1y-WmXSEcWxT1HKVSjL1PQ@mail.gmail.com>
References: <CAGsbZmFf_Y3D7VQ=wOjQi8OoH5kTWg8FMaArLEORv_R459mvFg@mail.gmail.com>
	<CAAg5f2TL1CYdAshcjY3UbG8qE7_TBiA+4K=SiYd1Je8c1QYtHA@mail.gmail.com>
	<CAGsbZmHNQ_0NLYB8hTTcdtBOYN2UbCexm8pP3zRoGLxg25EY+Q@mail.gmail.com>
	<CAAg5f2RbXrJGShHZxy7F5bCC-fnd9eZjq5pgiuLynCgzbiu6uQ@mail.gmail.com>
	<CAGsbZmF4sv33dWwr3mUFKPZD1ZbqykU-GpYiR3zydFxStVmHpw@mail.gmail.com>
	<CAGsbZmH2TcDcEMC3pF4bPmAW1c7w1y-WmXSEcWxT1HKVSjL1PQ@mail.gmail.com>
Message-ID: <CAAg5f2TBqH0rSUfbARmcVp+9fm3WNe+Ha+FS6kjaKPiz-iZFLQ@mail.gmail.com>

On Wed, 28 Jun 2017 at 12:08, Jose Miguel Gallas Olmedo <jgallaso at redhat.com>
wrote:

> Matthias is already unreachable but I think he agreed on this idea so I
> will proceed to send a PR with this changes.
>

+1



Maybe @Leigh or @Summers want to add some comments on this?
>
> I've created this ticket <https://issues.jboss.org/browse/AGPUSH-2127> so
> far and will work on the PR now.
>
> On 26 June 2017 at 11:02, Jose Miguel Gallas Olmedo <jgallaso at redhat.com>
> wrote:
>
>> ?On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>>
>>>
>>> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
>>> jgallaso at redhat.com> wrote:
>>>
>>>>
>>>> not sure if we should delete it yet - I think it was written by QE to
>>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>>> some features missing there. Perhaps it's still good - not really sure.
>>>>
>>>>
>>>> Actually, we could keep the old gcm-proxy as well. The repo is
>>>> "push-network-proxies" which means many proxies. We could store the new one
>>>> under "fcm-wiremock" and the old one under "gcm-java"
>>>>
>>>
>>> +1
>>>
>>>
>>>> but for this, I think, we ought to extract GCM logic from the current
>>>> project, leaving only APNS stuff.
>>>>
>>>
>>> no, not just APNs, IMO
>>>
>>
>> I think I didn't explain it clear enough, let me start again: The current
>> repository is a java project that implements both GCM and APNS proxies.
>> What I mean with "extract GCM logic from the project" is exactly what you
>> see in the structure: "apns-java" would have the original
>> "push-network-proxies" java project but only with the APNS implementation
>> and "gcm-java" would have the original "push-network-proxies" java project
>> but only with GCM implementation. Maybe "decouple" would be a better term.
>>
>> Does it make more sense now or didn't I understand you point maybe?
>>
>> --
>>
>> JOSE MIGUEL GALLAS OLMEDO
>>
>> ASSOCIATE QE, mobile
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>>
>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>
>> <https://red.ht/sig>
>>
>> On 26 June 2017 at 10:19, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>>>
>>>
>>> On Mon, Jun 26, 2017 at 9:19 AM, Jose Miguel Gallas Olmedo <
>>> jgallaso at redhat.com> wrote:
>>>
>>>>
>>>> not sure if we should delete it yet - I think it was written by QE to
>>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>>> some features missing there. Perhaps it's still good - not really sure.
>>>>
>>>>
>>>> Actually, we could keep the old gcm-proxy as well. The repo is
>>>> "push-network-proxies" which means many proxies. We could store the new one
>>>> under "fcm-wiremock" and the old one under "gcm-java"
>>>>
>>>
>>> +1
>>>
>>>
>>>> but for this, I think, we ought to extract GCM logic from the current
>>>> project, leaving only APNS stuff.
>>>>
>>>
>>> no, not just APNs, IMO
>>>
>>>>
>>>> push-network-proxies/
>>>>    fcm-wiremock/
>>>>       ...
>>>>    apns-java/
>>>>       ...
>>>>    gcm-java/
>>>>       ...
>>>>    push-network-proxies-template.yml
>>>>
>>>
>>> I think this is a good structure
>>>
>>>
>>>>
>>>> In the future we might want to add new different implementations (or
>>>> new proxies) so it makes sense to me to have push-network-proxies as an
>>>> extensible repository, not as a only-2-proxies one.
>>>>
>>>> On 24 June 2017 at 15:33, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jun 23, 2017 at 4:08 PM, Jose Miguel Gallas Olmedo <
>>>>> jgallaso at redhat.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I recently create a Docker image of our push FCM proxy, made with
>>>>>> Wiremock. Since we are no longer using the FCM proxy in
>>>>>> https://github.com/aerogear/push-network-proxies (even the
>>>>>> Dockerfile there only consider APNs) I think we could remove it from there
>>>>>> and refactor the repository like this:
>>>>>>
>>>>>
>>>>> not sure if we should delete it yet - I think it was written by QE to
>>>>> test GCMv2 - but push server is now GCMv3/FCM compliant. I think there is
>>>>> some features missing there. Perhaps it's still good - not really sure.
>>>>>
>>>>> But if Wiremock offers what we need -> fine, better to use things that
>>>>> are supported through a larger community ;-)
>>>>>
>>>>>
>>>>>>
>>>>>> push-network-proxies/
>>>>>>    fcm/
>>>>>>       Dockerfile
>>>>>>       ...
>>>>>>    apns/
>>>>>>       Dockerfile
>>>>>>       ...
>>>>>>    push-network-proxies-template.yml
>>>>>>
>>>>>> So that we have everything in the same place. I also made a template
>>>>>> for Openshift so that we can setup a testing environment for UPS quickly. I
>>>>>> think that's the ultimate point of having the mocks together.
>>>>>>
>>>>>
>>>>> I like that, having this structure, where FCM is based on Wiremock,
>>>>> right?
>>>>>
>>>>>
>>>>>>
>>>>>> WDYT?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> JOSE MIGUEL GALLAS OLMEDO
>>>>>>
>>>>>> ASSOCIATE QE, mobile
>>>>>>
>>>>>> Red Hat
>>>>>>
>>>>>> <https://www.redhat.com/>
>>>>>>
>>>>>> M: +34618488633
>>>>>> <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>>>> <https://red.ht/sig>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthias Wessendorf
>>>>>
>>>>> blog: http://matthiaswessendorf.wordpress.com/
>>>>> twitter: http://twitter.com/mwessendorf
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> JOSE MIGUEL GALLAS OLMEDO
>>>>
>>>> ASSOCIATE QE, mobile
>>>>
>>>> Red Hat
>>>>
>>>> <https://www.redhat.com/>
>>>>
>>>> M: +34618488633
>>>> <http://redhatemailsignature-marketing.itos.redhat.com/>
>>>> <https://red.ht/sig>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>>
>> JOSE MIGUEL GALLAS OLMEDO
>>
>> ASSOCIATE QE, mobile
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>>
>> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>>
>> <https://red.ht/sig>
>>
>
>
>
> --
>
> JOSE MIGUEL GALLAS OLMEDO
>
> ASSOCIATE QE, mobile
>
> Red Hat
>
> <https://www.redhat.com/>
>
> M: +34618488633 <http://redhatemailsignature-marketing.itos.redhat.com/>
>
> <https://red.ht/sig>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170628/c6dbff37/attachment-0001.html 

From polina.n.koleva at gmail.com  Thu Jun 29 06:01:16 2017
From: polina.n.koleva at gmail.com (Polina Koleva)
Date: Thu, 29 Jun 2017 12:01:16 +0200
Subject: [aerogear-dev] GSOC First month update
Message-ID: <CAKaJ2U+MiiJLpQJv9BoyWi9s7=jTfSMe4GbW+z5Fs9DctQT8Tw@mail.gmail.com>

Hey :)

This first month of GSOC is almost finished. The integration of Kafka in
UPS is 90% done. We now have our first consumer and producer in the
project. The next step is working on Java EE programming model for Kafka.
Matthias has already implemented a library kafka-cdi
<https://github.com/matzew/kafka-cdi>which provides some basic
functionality, so we can extend it if we need something more in the UPS.
Another topic that we will work on during the next month is Kafka Security,
Kafka Streams and Kafka on Openshift. We are still in process of defining
more concrete tasks for these epics.

We have done some pull requests and we will be really happy if we receive
your feedback so we can improve the code and merge them as soon as possible
so we can continue our work.

1) First Kafka consumer
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/853> -
an addition of first Kafka consumer. It updates metrics how many times the
app was opened because of push notification.
2) Set up Kafka test environment
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/848> -  add
really simple Kafka producer/consumer test cases
3) Add Kafka CDI library dependency
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/855> -
include the library for Kafka CDI in the project
4) Add first Kafka producer
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/841> - add a
first producer that writes to a topic how many times an app was opened
because of a push notification (metrics update)
5) Describe installation of Kafka
<https://github.com/aerogear/aerogear-unifiedpush-server/pull/838> - write
readme file about the installation of Kafka and how to integrate it with UPS

Thanks in advance.

Polina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/f345e317/attachment.html 

From supittma at redhat.com  Thu Jun 29 08:17:48 2017
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 29 Jun 2017 08:17:48 -0400
Subject: [aerogear-dev] GSOC First month update
In-Reply-To: <CAKaJ2U+MiiJLpQJv9BoyWi9s7=jTfSMe4GbW+z5Fs9DctQT8Tw@mail.gmail.com>
References: <CAKaJ2U+MiiJLpQJv9BoyWi9s7=jTfSMe4GbW+z5Fs9DctQT8Tw@mail.gmail.com>
Message-ID: <CAEQz2CuotV9in-iCj0ceiR35qH1pA_VRN7C41WM6r8ZWRFP+YQ@mail.gmail.com>

Very cool!  Keep up the good work.

On Thu, Jun 29, 2017 at 6:01 AM, Polina Koleva <polina.n.koleva at gmail.com>
wrote:

> Hey :)
>
> This first month of GSOC is almost finished. The integration of Kafka in
> UPS is 90% done. We now have our first consumer and producer in the
> project. The next step is working on Java EE programming model for Kafka.
> Matthias has already implemented a library kafka-cdi
> <https://github.com/matzew/kafka-cdi>which provides some basic
> functionality, so we can extend it if we need something more in the UPS.
> Another topic that we will work on during the next month is Kafka Security,
> Kafka Streams and Kafka on Openshift. We are still in process of defining
> more concrete tasks for these epics.
>
> We have done some pull requests and we will be really happy if we receive
> your feedback so we can improve the code and merge them as soon as possible
> so we can continue our work.
>
> 1) First Kafka consumer
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/853> -
> an addition of first Kafka consumer. It updates metrics how many times the
> app was opened because of push notification.
> 2) Set up Kafka test environment
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/848> -  add
> really simple Kafka producer/consumer test cases
> 3) Add Kafka CDI library dependency
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/855> -
> include the library for Kafka CDI in the project
> 4) Add first Kafka producer
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/841> - add
> a first producer that writes to a topic how many times an app was opened
> because of a push notification (metrics update)
> 5) Describe installation of Kafka
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/838> -
> write readme file about the installation of Kafka and how to integrate it
> with UPS
>
> Thanks in advance.
>
> Polina
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/36aabc02/attachment.html 

From lgriffin at redhat.com  Thu Jun 29 11:15:51 2017
From: lgriffin at redhat.com (Leigh Griffin)
Date: Thu, 29 Jun 2017 16:15:51 +0100
Subject: [aerogear-dev] GSOC First month update
In-Reply-To: <CAKaJ2U+MiiJLpQJv9BoyWi9s7=jTfSMe4GbW+z5Fs9DctQT8Tw@mail.gmail.com>
References: <CAKaJ2U+MiiJLpQJv9BoyWi9s7=jTfSMe4GbW+z5Fs9DctQT8Tw@mail.gmail.com>
Message-ID: <CAOQ+WroNW0jgdhuw7bEorngw-1uXy7qzzYTz1FYW5CX98ekWvg@mail.gmail.com>

Great work, keep it up!

Would be super if we could have some of the community review the 5 PRs that
are listed above. The pace that the girls are going to be working at will
require regular reviews from the community. Expect to see more digest mails
like this asking for reviews and help to land them!

Leigh

On Thu, Jun 29, 2017 at 11:01 AM, Polina Koleva <polina.n.koleva at gmail.com>
wrote:

> Hey :)
>
> This first month of GSOC is almost finished. The integration of Kafka in
> UPS is 90% done. We now have our first consumer and producer in the
> project. The next step is working on Java EE programming model for Kafka.
> Matthias has already implemented a library kafka-cdi
> <https://github.com/matzew/kafka-cdi>which provides some basic
> functionality, so we can extend it if we need something more in the UPS.
> Another topic that we will work on during the next month is Kafka Security,
> Kafka Streams and Kafka on Openshift. We are still in process of defining
> more concrete tasks for these epics.
>
> We have done some pull requests and we will be really happy if we receive
> your feedback so we can improve the code and merge them as soon as possible
> so we can continue our work.
>
> 1) First Kafka consumer
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/853> -
> an addition of first Kafka consumer. It updates metrics how many times the
> app was opened because of push notification.
> 2) Set up Kafka test environment
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/848> -  add
> really simple Kafka producer/consumer test cases
> 3) Add Kafka CDI library dependency
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/855> -
> include the library for Kafka CDI in the project
> 4) Add first Kafka producer
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/841> - add
> a first producer that writes to a topic how many times an app was opened
> because of a push notification (metrics update)
> 5) Describe installation of Kafka
> <https://github.com/aerogear/aerogear-unifiedpush-server/pull/838> -
> write readme file about the installation of Kafka and how to integrate it
> with UPS
>
> Thanks in advance.
>
> Polina
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEIGH GRIFFIN

ENGINEERING MANAGER, MOBILE

Red Hat Ireland <https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

lgriffin at redhat.com    M: +353877545162     IM: lgriffin
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

@redhatway <https://twitter.com/redhatway>   @redhatinc
<https://instagram.com/redhatinc>   @redhatsnaps
<https://snapchat.com/add/redhatsnaps>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/e768c2f8/attachment.html 

From aliok at redhat.com  Thu Jun 29 16:05:22 2017
From: aliok at redhat.com (Ali Ok)
Date: Thu, 29 Jun 2017 23:05:22 +0300
Subject: [aerogear-dev] AeroGear Digger Logo
In-Reply-To: <CABoO8Le_xkQMiTx1Xemd_CJXw3B-zCgvZyyFF0XLLXTdNDNUng@mail.gmail.com>
References: <CABoO8Le_xkQMiTx1Xemd_CJXw3B-zCgvZyyFF0XLLXTdNDNUng@mail.gmail.com>
Message-ID: <CABoO8LfdhDCaQbEogwzp1fwtGdS6UogETey-4pN4ZaDQcQJUfw@mail.gmail.com>

Hello,

According to the voting, logo #6 is the most favorite one. Here is the
summary:

[image: Inline image 1]

I am delighted to present you AeroGear Digger's logo:

[image: Inline image 2]

Cheers,
Ali

On Mon, Jun 19, 2017 at 10:40 AM, Ali Ok <aliok at redhat.com> wrote:

> Hello,
>
> We would like to pick a logo for the new AeroGear module, Digger [1].
>
> James Cobb has already prepared some great designs and now we vote to pick
> the best one [2].
>
> We have prepared a Google poll (no login required) here:
> https://goo.gl/forms/WdUoHecQtrshMkBg1
>
> The poll will be open for 10 days (until June 29th 10:00 AM UTC).
>
>
> [1] : https://github.com/aerogear/digger-jenkins
> [2] : https://issues.jboss.org/browse/DESIGN-943
>
> Cheers,
> Ali
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/3a7a809b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-29 at 22.58.31.png
Type: image/png
Size: 77274 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/3a7a809b/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aerogeardigger_logo_r1v6.png
Type: image/png
Size: 30735 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170629/3a7a809b/attachment-0003.png 

From dpassos at redhat.com  Fri Jun 30 07:50:29 2017
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 30 Jun 2017 08:50:29 -0300
Subject: [aerogear-dev] AeroGear Android Authz 3.1.1
Message-ID: <CADF=h2sTdw0SgAW0L-p_8LMWR7Lk2JmZA4yprpv7F8bVYi9yPw@mail.gmail.com>

Hi,

I just release a new version of Authz (3.1.1). It will be available on
Maven Central in 2 days.
Bug

   - AGDROID-602 <https://issues.jboss.org/browse/AGDROID-602> - OAuth2
   deleteAccount does not remove the account from memory

?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170630/0dd2f165/attachment.html 

From lgriffin at redhat.com  Fri Jun 30 09:21:30 2017
From: lgriffin at redhat.com (Leigh Griffin)
Date: Fri, 30 Jun 2017 14:21:30 +0100
Subject: [aerogear-dev] AeroGear Digger Logo
In-Reply-To: <CABoO8LfdhDCaQbEogwzp1fwtGdS6UogETey-4pN4ZaDQcQJUfw@mail.gmail.com>
References: <CABoO8Le_xkQMiTx1Xemd_CJXw3B-zCgvZyyFF0XLLXTdNDNUng@mail.gmail.com>
	<CABoO8LfdhDCaQbEogwzp1fwtGdS6UogETey-4pN4ZaDQcQJUfw@mail.gmail.com>
Message-ID: <CAOQ+Wro+LRbibF=XbSWwLpanRa-GzBfpfP7d0demkmGvfoK_mg@mail.gmail.com>

Really cool logo :)

On Thu, Jun 29, 2017 at 9:05 PM, Ali Ok <aliok at redhat.com> wrote:

> Hello,
>
> According to the voting, logo #6 is the most favorite one. Here is the
> summary:
>
> [image: Inline image 1]
>
> I am delighted to present you AeroGear Digger's logo:
>
> [image: Inline image 2]
>
> Cheers,
> Ali
>
> On Mon, Jun 19, 2017 at 10:40 AM, Ali Ok <aliok at redhat.com> wrote:
>
>> Hello,
>>
>> We would like to pick a logo for the new AeroGear module, Digger [1].
>>
>> James Cobb has already prepared some great designs and now we vote to
>> pick the best one [2].
>>
>> We have prepared a Google poll (no login required) here:
>> https://goo.gl/forms/WdUoHecQtrshMkBg1
>>
>> The poll will be open for 10 days (until June 29th 10:00 AM UTC).
>>
>>
>> [1] : https://github.com/aerogear/digger-jenkins
>> [2] : https://issues.jboss.org/browse/DESIGN-943
>>
>> Cheers,
>> Ali
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

LEIGH GRIFFIN

ENGINEERING MANAGER, MOBILE

Red Hat Ireland <https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

lgriffin at redhat.com    M: +353877545162     IM: lgriffin
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

@redhatway <https://twitter.com/redhatway>   @redhatinc
<https://instagram.com/redhatinc>   @redhatsnaps
<https://snapchat.com/add/redhatsnaps>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170630/8f316497/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-06-29 at 22.58.31.png
Type: image/png
Size: 77274 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170630/8f316497/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aerogeardigger_logo_r1v6.png
Type: image/png
Size: 30735 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170630/8f316497/attachment-0003.png