From matzew at apache.org  Thu Mar  1 09:06:24 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 1 Mar 2018 15:06:24 +0100
Subject: [aerogear-dev] JIRA instances: One for the better (or one to rule
	them all)
Message-ID: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>

Hi folks!

shortly after AeroGear.org project was started, and different technologies
and scopes were added, we started to reflect that with multiple different
JIRA instances. For instance besides the canonical AEROGEAR instance we
have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
(AGPUSH)* or Cordova (AGCORDOVA), to name only a few.

I am proposing to retire all instances and start using only the AEROGEAR
instance.

In Push, we had similar discussion, we had different instances for
simplepush, ups and webpush; For sanity we ended up running all things in
AGPUSH, and using components and better version strings (e.g.
simplepush-1.0.0 or ups-1.2.4). And this works great

So, I think it does make sense to stop hammering new issues into all the
different "technology silos", like AGDROID or AGPUSH. Instead I really
think we should unify one JIRA instance, with proper components and much
better version strings, allowing us to really use one instance for all of
AeroGear.

Today, to me, it does look a bit that our multiple instances of JIRA can be
really done w/ one JIRA (and components/versions) instead - we don't really
have much more value w/ all the different instances.

I'd like to retire the new instances, in the near future, moving forward
with just one JIRA instance. At some point - later this year - we could
than try to delete the other redundant JIRA silos.

Before retiring the instances, we will review the existing backlogs and
port over valid tickets. So no *relevant* ticket will be lost, and outdated
tickets kinda gets cleaned up, doing this excercise :-)

Feedback, thoughts, tomatos ?

-Matthias


-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/fedc0839/attachment.html 

From weil at redhat.com  Thu Mar  1 09:18:03 2018
From: weil at redhat.com (Wei Li)
Date: Thu, 1 Mar 2018 14:18:03 +0000
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>

+1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

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/20180301/8ef7787f/attachment.html 

From wtrocki at redhat.com  Thu Mar  1 09:48:59 2018
From: wtrocki at redhat.com (Wojciech Trocki)
Date: Thu, 1 Mar 2018 14:48:59 +0000
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
	<CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>
Message-ID: <CAO0+n+qN+CDER+us_rcb=+TjZV0Fv_JLF8gX_bQEmqujn5wDNw@mail.gmail.com>

Unification will be awesome.
I have logged issues on the wrong project so many times.
It will help also with new platforms like ReactNative - we currently link
that to JS project, which is not accurate.

On Thu, Mar 1, 2018 at 2:18 PM, Wei Li <weil at redhat.com> wrote:

> +1
>
> On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks!
>>
>> shortly after AeroGear.org project was started, and different
>> technologies and scopes were added, we started to reflect that with
>> multiple different JIRA instances. For instance besides the canonical
>> AEROGEAR instance we have a bunch of them for iOS (AGIOS), Android
>> (AGDROID), All things Push (AGPUSH)* or Cordova (AGCORDOVA), to name only a
>> few.
>>
>> I am proposing to retire all instances and start using only the AEROGEAR
>> instance.
>>
>> In Push, we had similar discussion, we had different instances for
>> simplepush, ups and webpush; For sanity we ended up running all things in
>> AGPUSH, and using components and better version strings (e.g.
>> simplepush-1.0.0 or ups-1.2.4). And this works great
>>
>> So, I think it does make sense to stop hammering new issues into all the
>> different "technology silos", like AGDROID or AGPUSH. Instead I really
>> think we should unify one JIRA instance, with proper components and much
>> better version strings, allowing us to really use one instance for all of
>> AeroGear.
>>
>> Today, to me, it does look a bit that our multiple instances of JIRA can
>> be really done w/ one JIRA (and components/versions) instead - we don't
>> really have much more value w/ all the different instances.
>>
>> I'd like to retire the new instances, in the near future, moving forward
>> with just one JIRA instance. At some point - later this year - we could
>> than try to delete the other redundant JIRA silos.
>>
>> Before retiring the instances, we will review the existing backlogs and
>> port over valid tickets. So no *relevant* ticket will be lost, and
>> outdated tickets kinda gets cleaned up, doing this excercise :-)
>>
>> Feedback, thoughts, tomatos ?
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_
>> mup3OOTF34NiX8Wzw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> WEI LI
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> weil at redhat.com    M: +353862393272
> <https://red.ht/sig>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

WOJCIECH TROCKI

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

IM: wtrocki
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/4a7e4836/attachment-0001.html 

From dara.hayes at redhat.com  Thu Mar  1 10:13:57 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Thu, 1 Mar 2018 15:13:57 +0000
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>

Seems like a no brainer to me. +1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Dara Hayes

Associate software engineer
<https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/5db49aa4/attachment.html 

From jfrizell at redhat.com  Thu Mar  1 10:17:12 2018
From: jfrizell at redhat.com (John Frizelle)
Date: Thu, 1 Mar 2018 15:17:12 +0000
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
	<CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>
Message-ID: <CAJFhnM7vnXVyH6DQWPZOht_7LZedPjvNYW3Y_v8wgcve=iHpow@mail.gmail.com>

HUGE +1 from me.

--
John Frizelle
Chief Architect, Red Hat Mobile
Consulting Engineer

mobile: *+353 87 290 1644 <//+353872901644>*
twitter:* @johnfriz*
skype: *john_frizelle*
mail: *jfrizell at redhat.com <jfrizell at redhat.com>*




On 1 March 2018 at 15:13, Dara Hayes <dara.hayes at redhat.com> wrote:

> Seems like a no brainer to me. +1
>
> On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks!
>>
>> shortly after AeroGear.org project was started, and different
>> technologies and scopes were added, we started to reflect that with
>> multiple different JIRA instances. For instance besides the canonical
>> AEROGEAR instance we have a bunch of them for iOS (AGIOS), Android
>> (AGDROID), All things Push (AGPUSH)* or Cordova (AGCORDOVA), to name only a
>> few.
>>
>> I am proposing to retire all instances and start using only the AEROGEAR
>> instance.
>>
>> In Push, we had similar discussion, we had different instances for
>> simplepush, ups and webpush; For sanity we ended up running all things in
>> AGPUSH, and using components and better version strings (e.g.
>> simplepush-1.0.0 or ups-1.2.4). And this works great
>>
>> So, I think it does make sense to stop hammering new issues into all the
>> different "technology silos", like AGDROID or AGPUSH. Instead I really
>> think we should unify one JIRA instance, with proper components and much
>> better version strings, allowing us to really use one instance for all of
>> AeroGear.
>>
>> Today, to me, it does look a bit that our multiple instances of JIRA can
>> be really done w/ one JIRA (and components/versions) instead - we don't
>> really have much more value w/ all the different instances.
>>
>> I'd like to retire the new instances, in the near future, moving forward
>> with just one JIRA instance. At some point - later this year - we could
>> than try to delete the other redundant JIRA silos.
>>
>> Before retiring the instances, we will review the existing backlogs and
>> port over valid tickets. So no *relevant* ticket will be lost, and
>> outdated tickets kinda gets cleaned up, doing this excercise :-)
>>
>> Feedback, thoughts, tomatos ?
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_
>> mup3OOTF34NiX8Wzw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV%3DSsWhpoA%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV%3DSsWhpoA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/03a263fa/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/03a263fa/attachment-0001.png 

From jmadigan at redhat.com  Thu Mar  1 10:55:10 2018
From: jmadigan at redhat.com (Jason Madigan)
Date: Thu, 1 Mar 2018 15:55:10 +0000
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74+ikoKv++pbdU1jyqOQ@mail.gmail.com>

+1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jason Madigan
Engineering Manager, Red Hat Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180301/007537b4/attachment.html 

From secondsun at gmail.com  Fri Mar  2 11:45:31 2018
From: secondsun at gmail.com (=?UTF-8?Q?Summers_Pittman_=E2=84=9D?=)
Date: Fri, 2 Mar 2018 11:45:31 -0500
Subject: [aerogear-dev] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74+ikoKv++pbdU1jyqOQ@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
	<CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74+ikoKv++pbdU1jyqOQ@mail.gmail.com>
Message-ID: <CAHK_qPsAD4Je+JH7R_+pwqd5+B=zeCa7v6WLMSXDUG0Y0CB63g@mail.gmail.com>

+1

Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.


On Thu, Mar 1, 2018 at 10:55 AM, Jason Madigan <jmadigan at redhat.com> wrote:

> +1
>
> On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks!
>>
>> shortly after AeroGear.org project was started, and different
>> technologies and scopes were added, we started to reflect that with
>> multiple different JIRA instances. For instance besides the canonical
>> AEROGEAR instance we have a bunch of them for iOS (AGIOS), Android
>> (AGDROID), All things Push (AGPUSH)* or Cordova (AGCORDOVA), to name only a
>> few.
>>
>> I am proposing to retire all instances and start using only the AEROGEAR
>> instance.
>>
>> In Push, we had similar discussion, we had different instances for
>> simplepush, ups and webpush; For sanity we ended up running all things in
>> AGPUSH, and using components and better version strings (e.g.
>> simplepush-1.0.0 or ups-1.2.4). And this works great
>>
>> So, I think it does make sense to stop hammering new issues into all the
>> different "technology silos", like AGDROID or AGPUSH. Instead I really
>> think we should unify one JIRA instance, with proper components and much
>> better version strings, allowing us to really use one instance for all of
>> AeroGear.
>>
>> Today, to me, it does look a bit that our multiple instances of JIRA can
>> be really done w/ one JIRA (and components/versions) instead - we don't
>> really have much more value w/ all the different instances.
>>
>> I'd like to retire the new instances, in the near future, moving forward
>> with just one JIRA instance. At some point - later this year - we could
>> than try to delete the other redundant JIRA silos.
>>
>> Before retiring the instances, we will review the existing backlogs and
>> port over valid tickets. So no *relevant* ticket will be lost, and
>> outdated tickets kinda gets cleaned up, doing this excercise :-)
>>
>> Feedback, thoughts, tomatos ?
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_
>> mup3OOTF34NiX8Wzw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jason Madigan
> Engineering Manager, Red Hat Mobile
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74%2BikoKv%2B%2BpbdU1jyqOQ%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74%2BikoKv%2B%2BpbdU1jyqOQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180302/0d025446/attachment-0001.html 

From lzuccare at redhat.com  Wed Mar  7 04:58:16 2018
From: lzuccare at redhat.com (Luigi Zuccarelli)
Date: Wed, 7 Mar 2018 09:58:16 +0000
Subject: [aerogear-dev] Demo of shared keycloak service
In-Reply-To: <CABkcJC0jqs8=71EvJyrf_e2rNK2RdYn7aXQCS25atudjz1qSLw@mail.gmail.com>
References: <CA+-sgVg7E3cGTkL7UhPB7nHebHvWX3fRniMoxRma3y0BF2+L3g@mail.gmail.com>
	<CABkcJC0jqs8=71EvJyrf_e2rNK2RdYn7aXQCS25atudjz1qSLw@mail.gmail.com>
Message-ID: <CAL1xsEU0ciZPvcRNx6xQCFG4j7D0qB9tcS-Z4nuVuAZm6GZnoQ@mail.gmail.com>

Well done Jameel

On Wed, Mar 7, 2018 at 9:25 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> Well done Jameel, great work! :)
>
> On Tue, Mar 6, 2018 at 4:57 PM, Craig Brookes <cbrookes at redhat.com> wrote:
>
>> Hey everyone. Jameel on the core team has put together a great demo of
>> provisioning a shared Keycloak service.
>>
>> https://www.youtube.com/watch?v=p8xvBA6UFRY&feature=youtu.be
>>
>> Feedback welcome
>>
>>  --
>> Craig Brookes
>> RHMAP
>> @maleck13 Github
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CA%2B-sgVg7E3cGTkL7UhPB7nHebHvWX3fRniMoxRma3y0B
>> F2%2BL3g%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CA%2B-sgVg7E3cGTkL7UhPB7nHebHvWX3fRniMoxRma3y0BF2%2BL3g%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CABkcJC0jqs8%3D71EvJyrf_e2rNK2RdYn7aXQCS25atudjz1qSLw%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CABkcJC0jqs8%3D71EvJyrf_e2rNK2RdYn7aXQCS25atudjz1qSLw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

LUIGI ZUCCARELLI

Associate  MANAGER ENGINEERING , REDHAT MOBILE

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

Communications House Ireland

Cork Road Waterford City

X91NY33

lzuccare at redhat.com    M: +353852156995     IM: lzuccarelli
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180307/d548ae91/attachment.html 

From vsazel at redhat.com  Fri Mar  9 06:49:05 2018
From: vsazel at redhat.com (Vojtech Sazel)
Date: Fri, 9 Mar 2018 12:49:05 +0100
Subject: [aerogear-dev] Aerogear SDK E2E testing discussion
Message-ID: <CAGTW8rFN+BCi5vCEQO5M8GBEqaybTgbOjEyvO4ygbcRDpo1rSg@mail.gmail.com>

Hi all,

Wei recommended me to start further discussion about viability of making
E2E tests for regression testing of our SDKs. There was some debate around
it, so I'm putting it also to the mailing list.

I have done Appium UI test
<https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1> of the example
app included in AG Android SDK [1]
<https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1>. It has been
done for Auth functionality. This test checks happy path of login and
logout.

Is it worth doing it this way? Is it worth doing it at least for some
functionality?

My take TLDR:

Pros:
+ it tests real end-user/developer usage of the SDK in the real device
environment

In the middle:
= it requires running emulator or connected device to the test server

Cons:
- test stability (it can go wrong because of load on the test server)
- test speed
- UI change volatility can break the test - this is partially avoided by
using page objects [2] <https://martinfowler.com/bliki/PageObject.html>
pattern

I think the real environment is clear benefit, for OpenID authentication,
it's difficult to do it other way than from UI and using real browser. I
don't know if this is true for other functionality. But writing tests at
least for happy paths can be beneficial.

refs:
[1] https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1
[2] https://martinfowler.com/bliki/PageObject.html
-- 

VOJT?CH S?ZEL

SENIOR SOFTWARE ENGINEER, RED HAT MOBILE

Red Hat

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

Remote Czech Republic

vsazel at redhat.com    IM: vsazel
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180309/8788fa9b/attachment.html 

From jgallaso at redhat.com  Mon Mar 12 13:42:27 2018
From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo)
Date: Mon, 12 Mar 2018 18:42:27 +0100
Subject: [aerogear-dev] Aerogear SDK E2E testing discussion
In-Reply-To: <CAGTW8rFN+BCi5vCEQO5M8GBEqaybTgbOjEyvO4ygbcRDpo1rSg@mail.gmail.com>
References: <CAGTW8rFN+BCi5vCEQO5M8GBEqaybTgbOjEyvO4ygbcRDpo1rSg@mail.gmail.com>
Message-ID: <CAGsbZmF-O76Px+Awa6+FXRt-KEcuAZJrejUxGh4ZFAhiR8DuKw@mail.gmail.com>

Hi Vojta, I recently created some tickets and some of them are about E2E
testing. I should have asked you first and perhaps you created already
tickets for that. In any case, here's the link o the thread and tickets:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/aerogear/FlZUqKwvt8Q/8BNa4O_9CQAJ

Please feel free to elaborate on those tickets or even close them if they
are duplicated (the E2E testing tickets).

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 9 March 2018 at 12:49, Vojtech Sazel <vsazel at redhat.com> wrote:

> Hi all,
>
> Wei recommended me to start further discussion about viability of making
> E2E tests for regression testing of our SDKs. There was some debate around
> it, so I'm putting it also to the mailing list.
>
> I have done Appium UI test
> <https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1> of the
> example app included in AG Android SDK [1]
> <https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1>. It has been
> done for Auth functionality. This test checks happy path of login and
> logout.
>
> Is it worth doing it this way? Is it worth doing it at least for some
> functionality?
>
> My take TLDR:
>
> Pros:
> + it tests real end-user/developer usage of the SDK in the real device
> environment
>
> In the middle:
> = it requires running emulator or connected device to the test server
>
> Cons:
> - test stability (it can go wrong because of load on the test server)
> - test speed
> - UI change volatility can break the test - this is partially avoided by
> using page objects [2] <https://martinfowler.com/bliki/PageObject.html>
> pattern
>
> I think the real environment is clear benefit, for OpenID authentication,
> it's difficult to do it other way than from UI and using real browser. I
> don't know if this is true for other functionality. But writing tests at
> least for happy paths can be beneficial.
>
> refs:
> [1] https://github.com/aerogear/aerogear-sdk-e2e-tests/pull/1
> [2] https://martinfowler.com/bliki/PageObject.html
> --
>
> VOJT?CH S?ZEL
>
> SENIOR SOFTWARE ENGINEER, RED HAT MOBILE
>
> Red Hat
>
> <https://www.redhat.com/>
>
> Remote Czech Republic
>
> vsazel at redhat.com    IM: vsazel
> <https://red.ht/sig>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180312/e96183f9/attachment-0001.html 

From matzew at apache.org  Wed Mar 14 11:15:25 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 14 Mar 2018 16:15:25 +0100
Subject: [aerogear-dev] Graphana docker image ?
Message-ID: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>

Hi,

I am not able to find the image for this container:
https://hub.docker.com/r/aerogearcatalog/grafana/

If not an automated build repo, we should at least point to the actual
aerogear GH repository, where the thing is located.

Thanks

-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180314/5e92e6f5/attachment.html 

From davmarti at redhat.com  Thu Mar 15 05:27:42 2018
From: davmarti at redhat.com (David Martin)
Date: Thu, 15 Mar 2018 09:27:42 +0000
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
Message-ID: <CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>

I remember a rember there's a reason for having a custom image built
(we need specific features that aren't in latest upstream image), but
I'm not sure who pushed it up and from where.

@Dara @Steven, is there a fork of grafana or some repo where we have
the Dockerfile?

On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org> wrote:
> Hi,
>
> I am not able to find the image for this container:
> https://hub.docker.com/r/aerogearcatalog/grafana/
>
> If not an automated build repo, we should at least point to the actual
> aerogear GH repository, where the thing is located.
>
> Thanks
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
David Martin
Red Hat Mobile
Twitter: @irldavem
IRC: @irldavem (#aerogear)

From mwessend at redhat.com  Thu Mar 15 06:08:44 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Thu, 15 Mar 2018 11:08:44 +0100
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
Message-ID: <CAKUFdH1Vc4zL2uStMn1+X8ViZup0o38c1OV28+LrhEg-ffsLdw@mail.gmail.com>

custom image is all fine - but we should share what we did, and have a
(forked) repo :-)

Also, in the long run - this needs to be "reproducable" in terms of builds
;-)

On Thu, Mar 15, 2018 at 10:27 AM, David Martin <davmarti at redhat.com> wrote:

> I remember a rember there's a reason for having a custom image built
> (we need specific features that aren't in latest upstream image), but
> I'm not sure who pushed it up and from where.
>
> @Dara @Steven, is there a fork of grafana or some repo where we have
> the Dockerfile?
>
> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org> wrote:
> > Hi,
> >
> > I am not able to find the image for this container:
> > https://hub.docker.com/r/aerogearcatalog/grafana/
> >
> > If not an automated build repo, we should at least point to the actual
> > aerogear GH repository, where the thing is located.
> >
> > Thanks
> >
> > --
> > Matthias Wessendorf
> >
> > github: https://github.com/matzew
> > twitter: http://twitter.com/mwessendorf
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Aerogear" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to aerogear+unsubscribe at googlegroups.com.
> > To post to this group, send email to aerogear at googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%3DX%3Dj%
> 3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (#aerogear)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg%40mail.
> gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/8e8bf21d/attachment.html 

From dara.hayes at redhat.com  Thu Mar 15 06:19:42 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Thu, 15 Mar 2018 10:19:42 +0000
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
Message-ID: <CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>

TL;DR: We forked the grafana build tools [0] and built a commit off the
master branch that we knew to be stable. In addition we modified the build
scripts to include some Grafana plugins inside the container image. There
were two reasons we did this.

1. We were depending on new features in Grafana that were only available on
the master branch. Grafana was under very heavy development as they geared
up towards their 5.0 release and we were finding new problems arising every
few days while we worked off the master branch. This was really slowing
down APB development.

2. We needed to install additional plugins required by some
dashboards. Grafana's
docker image provides a way to install plugins using environment variables
fed into the container at runtime but this requires root access which is
not feasible in Openshift. The only way we could do it at the time was by
baking in the plugins as part of the docker build. It's a terrible solution
but it was the only way at the time to continue the very fast pace of
development of the APBs.

There are still a some questions to be answered:

* How are we going to distribute Grafana on OpenShift such that it doesn't
require root access?
* What is the best way to install plugins? There was some discussion about
the different options and the consequences of those options in this
document [1]

This all arose during a sprint where one of the primary goals was to
deliver an APB that could provision Grafana + Prometheus and display
dashboard discovery and some other features. We decided at the time that we
were not prepared to answer those bigger questions so we knowingly put this
technical debt on ourselves and implemented a quick and dirty solution.

This entire thing was discussed publicly in a Github PR:
https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
should also have been mentioned on list at the time. Hope this clears
things up.

[0]: https://github.com/aerogear/grafana-docker
[1]:
https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2PU3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w

On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com> wrote:

> I remember a rember there's a reason for having a custom image built
> (we need specific features that aren't in latest upstream image), but
> I'm not sure who pushed it up and from where.
>
> @Dara @Steven, is there a fork of grafana or some repo where we have
> the Dockerfile?
>
> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org> wrote:
> > Hi,
> >
> > I am not able to find the image for this container:
> > https://hub.docker.com/r/aerogearcatalog/grafana/
> >
> > If not an automated build repo, we should at least point to the actual
> > aerogear GH repository, where the thing is located.
> >
> > Thanks
> >
> > --
> > Matthias Wessendorf
> >
> > github: https://github.com/matzew
> > twitter: http://twitter.com/mwessendorf
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Aerogear" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to aerogear+unsubscribe at googlegroups.com.
> > To post to this group, send email to aerogear at googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%3DX%3Dj%
> 3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (#aerogear)
>



-- 

Dara Hayes

Associate software engineer
<https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/139d19d4/attachment-0001.html 

From mwessend at redhat.com  Thu Mar 15 06:25:02 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Thu, 15 Mar 2018 11:25:02 +0100
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
Message-ID: <CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>

there is no issue w/ forks etc :-)

I just found it very annoying not seeing any hint on the repo, in dockerhub
:-)

I will update it

On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> TL;DR: We forked the grafana build tools [0] and built a commit off the
> master branch that we knew to be stable. In addition we modified the build
> scripts to include some Grafana plugins inside the container image. There
> were two reasons we did this.
>
> 1. We were depending on new features in Grafana that were only available
> on the master branch. Grafana was under very heavy development as they
> geared up towards their 5.0 release and we were finding new problems
> arising every few days while we worked off the master branch. This was
> really slowing down APB development.
>
> 2. We needed to install additional plugins required by some dashboards. Grafana's
> docker image provides a way to install plugins using environment variables
> fed into the container at runtime but this requires root access which is
> not feasible in Openshift. The only way we could do it at the time was by
> baking in the plugins as part of the docker build. It's a terrible solution
> but it was the only way at the time to continue the very fast pace of
> development of the APBs.
>
> There are still a some questions to be answered:
>
> * How are we going to distribute Grafana on OpenShift such that it doesn't
> require root access?
> * What is the best way to install plugins? There was some discussion about
> the different options and the consequences of those options in this
> document [1]
>
> This all arose during a sprint where one of the primary goals was to
> deliver an APB that could provision Grafana + Prometheus and display
> dashboard discovery and some other features. We decided at the time that we
> were not prepared to answer those bigger questions so we knowingly put this
> technical debt on ourselves and implemented a quick and dirty solution.
>
> This entire thing was discussed publicly in a Github PR:
> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
> should also have been mentioned on list at the time. Hope this clears
> things up.
>
> [0]: https://github.com/aerogear/grafana-docker
> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2PU3UeRWdpuy
> oKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>
> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com> wrote:
>
>> I remember a rember there's a reason for having a custom image built
>> (we need specific features that aren't in latest upstream image), but
>> I'm not sure who pushed it up and from where.
>>
>> @Dara @Steven, is there a fork of grafana or some repo where we have
>> the Dockerfile?
>>
>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org> wrote:
>> > Hi,
>> >
>> > I am not able to find the image for this container:
>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>> >
>> > If not an automated build repo, we should at least point to the actual
>> > aerogear GH repository, where the thing is located.
>> >
>> > Thanks
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > github: https://github.com/matzew
>> > twitter: http://twitter.com/mwessendorf
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Aerogear" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to aerogear+unsubscribe at googlegroups.com.
>> > To post to this group, send email to aerogear at googlegroups.com.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> David Martin
>> Red Hat Mobile
>> Twitter: @irldavem
>> IRC: @irldavem (#aerogear)
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%
> 2B7Eu8KSfBY4nrg%40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/7a3db5d9/attachment.html 

From mwessend at redhat.com  Thu Mar 15 06:26:02 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Thu, 15 Mar 2018 11:26:02 +0100
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
	<CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
Message-ID: <CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>

The other question is ... is "aerogearcatalog" the right choice ?

IMO no - since that https://github.com/aerogear/grafana-docker is not an APB

IMO it would be better in "aerogear" dh org ;-)

On Thu, Mar 15, 2018 at 11:25 AM, Matthias Wessendorf <mwessend at redhat.com>
wrote:

> there is no issue w/ forks etc :-)
>
> I just found it very annoying not seeing any hint on the repo, in
> dockerhub :-)
>
> I will update it
>
> On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com>
> wrote:
>
>> TL;DR: We forked the grafana build tools [0] and built a commit off the
>> master branch that we knew to be stable. In addition we modified the build
>> scripts to include some Grafana plugins inside the container image. There
>> were two reasons we did this.
>>
>> 1. We were depending on new features in Grafana that were only available
>> on the master branch. Grafana was under very heavy development as they
>> geared up towards their 5.0 release and we were finding new problems
>> arising every few days while we worked off the master branch. This was
>> really slowing down APB development.
>>
>> 2. We needed to install additional plugins required by some dashboards. Grafana's
>> docker image provides a way to install plugins using environment variables
>> fed into the container at runtime but this requires root access which is
>> not feasible in Openshift. The only way we could do it at the time was
>> by baking in the plugins as part of the docker build. It's a terrible
>> solution but it was the only way at the time to continue the very fast pace
>> of development of the APBs.
>>
>> There are still a some questions to be answered:
>>
>> * How are we going to distribute Grafana on OpenShift such that it
>> doesn't require root access?
>> * What is the best way to install plugins? There was some discussion
>> about the different options and the consequences of those options in this
>> document [1]
>>
>> This all arose during a sprint where one of the primary goals was to
>> deliver an APB that could provision Grafana + Prometheus and display
>> dashboard discovery and some other features. We decided at the time that we
>> were not prepared to answer those bigger questions so we knowingly put this
>> technical debt on ourselves and implemented a quick and dirty solution.
>>
>> This entire thing was discussed publicly in a Github PR:
>> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
>> should also have been mentioned on list at the time. Hope this clears
>> things up.
>>
>> [0]: https://github.com/aerogear/grafana-docker
>> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2P
>> U3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>>
>> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com>
>> wrote:
>>
>>> I remember a rember there's a reason for having a custom image built
>>> (we need specific features that aren't in latest upstream image), but
>>> I'm not sure who pushed it up and from where.
>>>
>>> @Dara @Steven, is there a fork of grafana or some repo where we have
>>> the Dockerfile?
>>>
>>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>> > Hi,
>>> >
>>> > I am not able to find the image for this container:
>>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>>> >
>>> > If not an automated build repo, we should at least point to the actual
>>> > aerogear GH repository, where the thing is located.
>>> >
>>> > Thanks
>>> >
>>> > --
>>> > Matthias Wessendorf
>>> >
>>> > github: https://github.com/matzew
>>> > twitter: http://twitter.com/mwessendorf
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "Aerogear" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> > email to aerogear+unsubscribe at googlegroups.com.
>>> > To post to this group, send email to aerogear at googlegroups.com.
>>> > To view this discussion on the web visit
>>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> David Martin
>>> Red Hat Mobile
>>> Twitter: @irldavem
>>> IRC: @irldavem (#aerogear)
>>>
>>
>>
>>
>> --
>>
>> Dara Hayes
>>
>> Associate software engineer
>> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8K
>> SfBY4nrg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Project lead AeroGear.org
>



-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/04f667b5/attachment-0001.html 

From dara.hayes at redhat.com  Thu Mar 15 06:51:03 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Thu, 15 Mar 2018 10:51:03 +0000
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
	<CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
	<CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>
Message-ID: <CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>

I 100% agree that it should be in the aerogear org and I suggested it at
the time. However, we were never given access (even though we asked) :)

On Thu, Mar 15, 2018 at 10:26 AM, Matthias Wessendorf <mwessend at redhat.com>
wrote:

> The other question is ... is "aerogearcatalog" the right choice ?
>
> IMO no - since that https://github.com/aerogear/grafana-docker is not an
> APB
>
> IMO it would be better in "aerogear" dh org ;-)
>
> On Thu, Mar 15, 2018 at 11:25 AM, Matthias Wessendorf <mwessend at redhat.com
> > wrote:
>
>> there is no issue w/ forks etc :-)
>>
>> I just found it very annoying not seeing any hint on the repo, in
>> dockerhub :-)
>>
>> I will update it
>>
>> On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com>
>> wrote:
>>
>>> TL;DR: We forked the grafana build tools [0] and built a commit off the
>>> master branch that we knew to be stable. In addition we modified the build
>>> scripts to include some Grafana plugins inside the container image. There
>>> were two reasons we did this.
>>>
>>> 1. We were depending on new features in Grafana that were only available
>>> on the master branch. Grafana was under very heavy development as they
>>> geared up towards their 5.0 release and we were finding new problems
>>> arising every few days while we worked off the master branch. This was
>>> really slowing down APB development.
>>>
>>> 2. We needed to install additional plugins required by some dashboards. Grafana's
>>> docker image provides a way to install plugins using environment variables
>>> fed into the container at runtime but this requires root access which is
>>> not feasible in Openshift. The only way we could do it at the time was
>>> by baking in the plugins as part of the docker build. It's a terrible
>>> solution but it was the only way at the time to continue the very fast pace
>>> of development of the APBs.
>>>
>>> There are still a some questions to be answered:
>>>
>>> * How are we going to distribute Grafana on OpenShift such that it
>>> doesn't require root access?
>>> * What is the best way to install plugins? There was some discussion
>>> about the different options and the consequences of those options in this
>>> document [1]
>>>
>>> This all arose during a sprint where one of the primary goals was to
>>> deliver an APB that could provision Grafana + Prometheus and display
>>> dashboard discovery and some other features. We decided at the time that we
>>> were not prepared to answer those bigger questions so we knowingly put this
>>> technical debt on ourselves and implemented a quick and dirty solution.
>>>
>>> This entire thing was discussed publicly in a Github PR:
>>> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
>>> should also have been mentioned on list at the time. Hope this clears
>>> things up.
>>>
>>> [0]: https://github.com/aerogear/grafana-docker
>>> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2P
>>> U3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>>>
>>> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com>
>>> wrote:
>>>
>>>> I remember a rember there's a reason for having a custom image built
>>>> (we need specific features that aren't in latest upstream image), but
>>>> I'm not sure who pushed it up and from where.
>>>>
>>>> @Dara @Steven, is there a fork of grafana or some repo where we have
>>>> the Dockerfile?
>>>>
>>>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>> > Hi,
>>>> >
>>>> > I am not able to find the image for this container:
>>>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>>>> >
>>>> > If not an automated build repo, we should at least point to the actual
>>>> > aerogear GH repository, where the thing is located.
>>>> >
>>>> > Thanks
>>>> >
>>>> > --
>>>> > Matthias Wessendorf
>>>> >
>>>> > github: https://github.com/matzew
>>>> > twitter: http://twitter.com/mwessendorf
>>>> >
>>>> > --
>>>> > You received this message because you are subscribed to the Google
>>>> Groups
>>>> > "Aerogear" group.
>>>> > To unsubscribe from this group and stop receiving emails from it,
>>>> send an
>>>> > email to aerogear+unsubscribe at googlegroups.com.
>>>> > To post to this group, send email to aerogear at googlegroups.com.
>>>> > To view this discussion on the web visit
>>>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>>>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>>
>>>> --
>>>> David Martin
>>>> Red Hat Mobile
>>>> Twitter: @irldavem
>>>> IRC: @irldavem (#aerogear)
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Dara Hayes
>>>
>>> Associate software engineer
>>> <https://redhat.com> TRIED. TESTED. TRUSTED.
>>> <https://redhat.com/trusted>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Aerogear" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to aerogear+unsubscribe at googlegroups.com.
>>> To post to this group, send email to aerogear at googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8K
>>> SfBY4nrg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Project lead AeroGear.org
>>
>
>
>
> --
> Project lead AeroGear.org
>



-- 

Dara Hayes

Associate software engineer
<https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/47869ea5/attachment.html 

From pbrookes at redhat.com  Thu Mar 15 06:58:19 2018
From: pbrookes at redhat.com (Phil Brookes)
Date: Thu, 15 Mar 2018 10:58:19 +0000
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
	<CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
	<CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>
	<CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>
Message-ID: <CAKY3PU22WiCem5EOHU38gwF+P4Hw4sN1KS4xYMZJDeE80a5NTw@mail.gmail.com>

Hey Dara,

I have added you to the developers teams in the aerogear org now. Let me
know if any others need to be added, or if it is not working correctly for
you.

Regards,
Phil.
?

On Thu, Mar 15, 2018 at 10:51 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> I 100% agree that it should be in the aerogear org and I suggested it at
> the time. However, we were never given access (even though we asked) :)
>
> On Thu, Mar 15, 2018 at 10:26 AM, Matthias Wessendorf <mwessend at redhat.com
> > wrote:
>
>> The other question is ... is "aerogearcatalog" the right choice ?
>>
>> IMO no - since that https://github.com/aerogear/grafana-docker is not an
>> APB
>>
>> IMO it would be better in "aerogear" dh org ;-)
>>
>> On Thu, Mar 15, 2018 at 11:25 AM, Matthias Wessendorf <
>> mwessend at redhat.com> wrote:
>>
>>> there is no issue w/ forks etc :-)
>>>
>>> I just found it very annoying not seeing any hint on the repo, in
>>> dockerhub :-)
>>>
>>> I will update it
>>>
>>> On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com>
>>> wrote:
>>>
>>>> TL;DR: We forked the grafana build tools [0] and built a commit off the
>>>> master branch that we knew to be stable. In addition we modified the build
>>>> scripts to include some Grafana plugins inside the container image. There
>>>> were two reasons we did this.
>>>>
>>>> 1. We were depending on new features in Grafana that were only
>>>> available on the master branch. Grafana was under very heavy development as
>>>> they geared up towards their 5.0 release and we were finding new problems
>>>> arising every few days while we worked off the master branch. This was
>>>> really slowing down APB development.
>>>>
>>>> 2. We needed to install additional plugins required by some dashboards. Grafana's
>>>> docker image provides a way to install plugins using environment variables
>>>> fed into the container at runtime but this requires root access which is
>>>> not feasible in Openshift. The only way we could do it at the time was
>>>> by baking in the plugins as part of the docker build. It's a terrible
>>>> solution but it was the only way at the time to continue the very fast pace
>>>> of development of the APBs.
>>>>
>>>> There are still a some questions to be answered:
>>>>
>>>> * How are we going to distribute Grafana on OpenShift such that it
>>>> doesn't require root access?
>>>> * What is the best way to install plugins? There was some discussion
>>>> about the different options and the consequences of those options in this
>>>> document [1]
>>>>
>>>> This all arose during a sprint where one of the primary goals was to
>>>> deliver an APB that could provision Grafana + Prometheus and display
>>>> dashboard discovery and some other features. We decided at the time that we
>>>> were not prepared to answer those bigger questions so we knowingly put this
>>>> technical debt on ourselves and implemented a quick and dirty solution.
>>>>
>>>> This entire thing was discussed publicly in a Github PR:
>>>> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
>>>> should also have been mentioned on list at the time. Hope this clears
>>>> things up.
>>>>
>>>> [0]: https://github.com/aerogear/grafana-docker
>>>> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2P
>>>> U3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>>>>
>>>> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com>
>>>> wrote:
>>>>
>>>>> I remember a rember there's a reason for having a custom image built
>>>>> (we need specific features that aren't in latest upstream image), but
>>>>> I'm not sure who pushed it up and from where.
>>>>>
>>>>> @Dara @Steven, is there a fork of grafana or some repo where we have
>>>>> the Dockerfile?
>>>>>
>>>>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org>
>>>>> wrote:
>>>>> > Hi,
>>>>> >
>>>>> > I am not able to find the image for this container:
>>>>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>>>>> >
>>>>> > If not an automated build repo, we should at least point to the
>>>>> actual
>>>>> > aerogear GH repository, where the thing is located.
>>>>> >
>>>>> > Thanks
>>>>> >
>>>>> > --
>>>>> > Matthias Wessendorf
>>>>> >
>>>>> > github: https://github.com/matzew
>>>>> > twitter: http://twitter.com/mwessendorf
>>>>> >
>>>>> > --
>>>>> > You received this message because you are subscribed to the Google
>>>>> Groups
>>>>> > "Aerogear" group.
>>>>> > To unsubscribe from this group and stop receiving emails from it,
>>>>> send an
>>>>> > email to aerogear+unsubscribe at googlegroups.com.
>>>>> > To post to this group, send email to aerogear at googlegroups.com.
>>>>> > To view this discussion on the web visit
>>>>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>>>>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> David Martin
>>>>> Red Hat Mobile
>>>>> Twitter: @irldavem
>>>>> IRC: @irldavem (#aerogear)
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Dara Hayes
>>>>
>>>> Associate software engineer
>>>> <https://redhat.com> TRIED. TESTED. TRUSTED.
>>>> <https://redhat.com/trusted>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Aerogear" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to aerogear+unsubscribe at googlegroups.com.
>>>> To post to this group, send email to aerogear at googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>>> gid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8K
>>>> SfBY4nrg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Project lead AeroGear.org
>>>
>>
>>
>>
>> --
>> Project lead AeroGear.org
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Aerogear" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/aerogear/uG4KaT_EYGg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CABkcJC1JAt_6QD-kvfemhhNE2S5h5%2BgmCDq8MZEXmNKHzzD3%3DQ%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CABkcJC1JAt_6QD-kvfemhhNE2S5h5%2BgmCDq8MZEXmNKHzzD3%3DQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/57130f52/attachment-0001.html 

From mwessend at redhat.com  Thu Mar 15 06:59:30 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Thu, 15 Mar 2018 11:59:30 +0100
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
	<CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
	<CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>
	<CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>
Message-ID: <CAKUFdH3saMaxOaAe-+OE=S8Gn-zpH6N3ifuzmcR_aYP9bDY9DQ@mail.gmail.com>

I see you on the team -> https://hub.docker.com/u/darahayes/ (at least this
account)

On Thu, Mar 15, 2018 at 11:51 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> I 100% agree that it should be in the aerogear org and I suggested it at
> the time. However, we were never given access (even though we asked) :)
>
> On Thu, Mar 15, 2018 at 10:26 AM, Matthias Wessendorf <mwessend at redhat.com
> > wrote:
>
>> The other question is ... is "aerogearcatalog" the right choice ?
>>
>> IMO no - since that https://github.com/aerogear/grafana-docker is not an
>> APB
>>
>> IMO it would be better in "aerogear" dh org ;-)
>>
>> On Thu, Mar 15, 2018 at 11:25 AM, Matthias Wessendorf <
>> mwessend at redhat.com> wrote:
>>
>>> there is no issue w/ forks etc :-)
>>>
>>> I just found it very annoying not seeing any hint on the repo, in
>>> dockerhub :-)
>>>
>>> I will update it
>>>
>>> On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com>
>>> wrote:
>>>
>>>> TL;DR: We forked the grafana build tools [0] and built a commit off the
>>>> master branch that we knew to be stable. In addition we modified the build
>>>> scripts to include some Grafana plugins inside the container image. There
>>>> were two reasons we did this.
>>>>
>>>> 1. We were depending on new features in Grafana that were only
>>>> available on the master branch. Grafana was under very heavy development as
>>>> they geared up towards their 5.0 release and we were finding new problems
>>>> arising every few days while we worked off the master branch. This was
>>>> really slowing down APB development.
>>>>
>>>> 2. We needed to install additional plugins required by some dashboards. Grafana's
>>>> docker image provides a way to install plugins using environment variables
>>>> fed into the container at runtime but this requires root access which is
>>>> not feasible in Openshift. The only way we could do it at the time was
>>>> by baking in the plugins as part of the docker build. It's a terrible
>>>> solution but it was the only way at the time to continue the very fast pace
>>>> of development of the APBs.
>>>>
>>>> There are still a some questions to be answered:
>>>>
>>>> * How are we going to distribute Grafana on OpenShift such that it
>>>> doesn't require root access?
>>>> * What is the best way to install plugins? There was some discussion
>>>> about the different options and the consequences of those options in this
>>>> document [1]
>>>>
>>>> This all arose during a sprint where one of the primary goals was to
>>>> deliver an APB that could provision Grafana + Prometheus and display
>>>> dashboard discovery and some other features. We decided at the time that we
>>>> were not prepared to answer those bigger questions so we knowingly put this
>>>> technical debt on ourselves and implemented a quick and dirty solution.
>>>>
>>>> This entire thing was discussed publicly in a Github PR:
>>>> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps it
>>>> should also have been mentioned on list at the time. Hope this clears
>>>> things up.
>>>>
>>>> [0]: https://github.com/aerogear/grafana-docker
>>>> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2P
>>>> U3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>>>>
>>>> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com>
>>>> wrote:
>>>>
>>>>> I remember a rember there's a reason for having a custom image built
>>>>> (we need specific features that aren't in latest upstream image), but
>>>>> I'm not sure who pushed it up and from where.
>>>>>
>>>>> @Dara @Steven, is there a fork of grafana or some repo where we have
>>>>> the Dockerfile?
>>>>>
>>>>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org>
>>>>> wrote:
>>>>> > Hi,
>>>>> >
>>>>> > I am not able to find the image for this container:
>>>>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>>>>> >
>>>>> > If not an automated build repo, we should at least point to the
>>>>> actual
>>>>> > aerogear GH repository, where the thing is located.
>>>>> >
>>>>> > Thanks
>>>>> >
>>>>> > --
>>>>> > Matthias Wessendorf
>>>>> >
>>>>> > github: https://github.com/matzew
>>>>> > twitter: http://twitter.com/mwessendorf
>>>>> >
>>>>> > --
>>>>> > You received this message because you are subscribed to the Google
>>>>> Groups
>>>>> > "Aerogear" group.
>>>>> > To unsubscribe from this group and stop receiving emails from it,
>>>>> send an
>>>>> > email to aerogear+unsubscribe at googlegroups.com.
>>>>> > To post to this group, send email to aerogear at googlegroups.com.
>>>>> > To view this discussion on the web visit
>>>>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>>>>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> David Martin
>>>>> Red Hat Mobile
>>>>> Twitter: @irldavem
>>>>> IRC: @irldavem (#aerogear)
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Dara Hayes
>>>>
>>>> Associate software engineer
>>>> <https://redhat.com> TRIED. TESTED. TRUSTED.
>>>> <https://redhat.com/trusted>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Aerogear" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to aerogear+unsubscribe at googlegroups.com.
>>>> To post to this group, send email to aerogear at googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>>> gid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8K
>>>> SfBY4nrg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Project lead AeroGear.org
>>>
>>
>>
>>
>> --
>> Project lead AeroGear.org
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>


-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/be0ed234/attachment.html 

From dara.hayes at redhat.com  Thu Mar 15 08:24:02 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Thu, 15 Mar 2018 12:24:02 +0000
Subject: [aerogear-dev] Graphana docker image ?
In-Reply-To: <CAKUFdH3saMaxOaAe-+OE=S8Gn-zpH6N3ifuzmcR_aYP9bDY9DQ@mail.gmail.com>
References: <CAAg5f2RgsYFDWqG=X=j=48fVhCH2nrgjRuXNdNF9za3nt8uhSQ@mail.gmail.com>
	<CADvBQ45BwVHa573piobxuVJUK84oKD5EtJAhPBCJW3hsQCOxZg@mail.gmail.com>
	<CABkcJC19HDKXS2jTUMj+U8Z8e27o4uD55Rea+7Eu8KSfBY4nrg@mail.gmail.com>
	<CAKUFdH1djC46CaW6e4XZ-qbAk2mMepFQAywYwwxb8hTa5zh9wQ@mail.gmail.com>
	<CAKUFdH2QBNJxW+xfuYDT1KBBbdxymPS+Rytdif4m-RaC57N2Jg@mail.gmail.com>
	<CABkcJC1JAt_6QD-kvfemhhNE2S5h5+gmCDq8MZEXmNKHzzD3=Q@mail.gmail.com>
	<CAKUFdH3saMaxOaAe-+OE=S8Gn-zpH6N3ifuzmcR_aYP9bDY9DQ@mail.gmail.com>
Message-ID: <CABkcJC1U2+-5GYRFb8_Q3dQ9to-2zo+4r_cn=9zYQhrejrJjJQ@mail.gmail.com>

Thanks Phil!

@Matthias: yes I got added to the dockerhub one recently for the aerogear
app metrics service :)

- Dara

On 15 Mar 2018 10:59, "Matthias Wessendorf" <mwessend at redhat.com> wrote:

> I see you on the team -> https://hub.docker.com/u/darahayes/ (at least
> this account)
>
> On Thu, Mar 15, 2018 at 11:51 AM, Dara Hayes <dara.hayes at redhat.com>
> wrote:
>
>> I 100% agree that it should be in the aerogear org and I suggested it at
>> the time. However, we were never given access (even though we asked) :)
>>
>> On Thu, Mar 15, 2018 at 10:26 AM, Matthias Wessendorf <
>> mwessend at redhat.com> wrote:
>>
>>> The other question is ... is "aerogearcatalog" the right choice ?
>>>
>>> IMO no - since that https://github.com/aerogear/grafana-docker is not
>>> an APB
>>>
>>> IMO it would be better in "aerogear" dh org ;-)
>>>
>>> On Thu, Mar 15, 2018 at 11:25 AM, Matthias Wessendorf <
>>> mwessend at redhat.com> wrote:
>>>
>>>> there is no issue w/ forks etc :-)
>>>>
>>>> I just found it very annoying not seeing any hint on the repo, in
>>>> dockerhub :-)
>>>>
>>>> I will update it
>>>>
>>>> On Thu, Mar 15, 2018 at 11:19 AM, Dara Hayes <dara.hayes at redhat.com>
>>>> wrote:
>>>>
>>>>> TL;DR: We forked the grafana build tools [0] and built a commit off
>>>>> the master branch that we knew to be stable. In addition we modified the
>>>>> build scripts to include some Grafana plugins inside the container image.
>>>>> There were two reasons we did this.
>>>>>
>>>>> 1. We were depending on new features in Grafana that were only
>>>>> available on the master branch. Grafana was under very heavy development as
>>>>> they geared up towards their 5.0 release and we were finding new problems
>>>>> arising every few days while we worked off the master branch. This was
>>>>> really slowing down APB development.
>>>>>
>>>>> 2. We needed to install additional plugins required by some
>>>>> dashboards. Grafana's docker image provides a way to install plugins
>>>>> using environment variables fed into the container at runtime but this
>>>>> requires root access which is not feasible in Openshift. The only way
>>>>> we could do it at the time was by baking in the plugins as part of the
>>>>> docker build. It's a terrible solution but it was the only way at the time
>>>>> to continue the very fast pace of development of the APBs.
>>>>>
>>>>> There are still a some questions to be answered:
>>>>>
>>>>> * How are we going to distribute Grafana on OpenShift such that it
>>>>> doesn't require root access?
>>>>> * What is the best way to install plugins? There was some discussion
>>>>> about the different options and the consequences of those options in this
>>>>> document [1]
>>>>>
>>>>> This all arose during a sprint where one of the primary goals was to
>>>>> deliver an APB that could provision Grafana + Prometheus and display
>>>>> dashboard discovery and some other features. We decided at the time that we
>>>>> were not prepared to answer those bigger questions so we knowingly put this
>>>>> technical debt on ourselves and implemented a quick and dirty solution.
>>>>>
>>>>> This entire thing was discussed publicly in a Github PR:
>>>>> https://github.com/aerogearcatalog/keycloak-apb/pull/33 But perhaps
>>>>> it should also have been mentioned on list at the time. Hope this clears
>>>>> things up.
>>>>>
>>>>> [0]: https://github.com/aerogear/grafana-docker
>>>>> [1]: https://docs.google.com/document/d/1WAUQ9IfJovSSUsHYR2P
>>>>> U3UeRWdpuyoKN9_ImyVv6dhc/edit#heading=h.yf74gvpjt77w
>>>>>
>>>>> On Thu, Mar 15, 2018 at 9:27 AM, David Martin <davmarti at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> I remember a rember there's a reason for having a custom image built
>>>>>> (we need specific features that aren't in latest upstream image), but
>>>>>> I'm not sure who pushed it up and from where.
>>>>>>
>>>>>> @Dara @Steven, is there a fork of grafana or some repo where we have
>>>>>> the Dockerfile?
>>>>>>
>>>>>> On 14 March 2018 at 15:15, Matthias Wessendorf <matzew at apache.org>
>>>>>> wrote:
>>>>>> > Hi,
>>>>>> >
>>>>>> > I am not able to find the image for this container:
>>>>>> > https://hub.docker.com/r/aerogearcatalog/grafana/
>>>>>> >
>>>>>> > If not an automated build repo, we should at least point to the
>>>>>> actual
>>>>>> > aerogear GH repository, where the thing is located.
>>>>>> >
>>>>>> > Thanks
>>>>>> >
>>>>>> > --
>>>>>> > Matthias Wessendorf
>>>>>> >
>>>>>> > github: https://github.com/matzew
>>>>>> > twitter: http://twitter.com/mwessendorf
>>>>>> >
>>>>>> > --
>>>>>> > You received this message because you are subscribed to the Google
>>>>>> Groups
>>>>>> > "Aerogear" group.
>>>>>> > To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an
>>>>>> > email to aerogear+unsubscribe at googlegroups.com.
>>>>>> > To post to this group, send email to aerogear at googlegroups.com.
>>>>>> > To view this discussion on the web visit
>>>>>> > https://groups.google.com/d/msgid/aerogear/CAAg5f2RgsYFDWqG%
>>>>>> 3DX%3Dj%3D48fVhCH2nrgjRuXNdNF9za3nt8uhSQ%40mail.gmail.com.
>>>>>> > For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> David Martin
>>>>>> Red Hat Mobile
>>>>>> Twitter: @irldavem
>>>>>> IRC: @irldavem (#aerogear)
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Dara Hayes
>>>>>
>>>>> Associate software engineer
>>>>> <https://redhat.com> TRIED. TESTED. TRUSTED.
>>>>> <https://redhat.com/trusted>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Aerogear" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to aerogear+unsubscribe at googlegroups.com.
>>>>> To post to this group, send email to aerogear at googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jT
>>>>> UMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/aerogear/CABkcJC19HDKXS2jTUMj%2BU8Z8e27o4uD55Rea%2B7Eu8KSfBY4nrg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Project lead AeroGear.org
>>>>
>>>
>>>
>>>
>>> --
>>> Project lead AeroGear.org
>>>
>>
>>
>>
>> --
>>
>> Dara Hayes
>>
>> Associate software engineer
>> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>
>>
>
>
> --
> Project lead AeroGear.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180315/46a85ec0/attachment-0001.html 

From matzew at apache.org  Tue Mar 20 06:01:45 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 20 Mar 2018 11:01:45 +0100
Subject: [aerogear-dev] Openshift Auth for UPS
Message-ID: <CAAg5f2SZBXHe9NhwcgmA_XY+nt5VaNK6wJXB4UXnGfwAN7ODMQ@mail.gmail.com>

Hola,

here is a little video showing how to login to UPS, leveraging your
Openshift credentials:

https://youtu.be/2FLoVJ_KWL8

-Matthias

-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180320/89895e20/attachment.html 

From pwright at redhat.com  Tue Mar 20 10:02:54 2018
From: pwright at redhat.com (Paul Wright)
Date: Tue, 20 Mar 2018 14:02:54 +0000
Subject: [aerogear-dev] AeroGear videos
Message-ID: <05d0a15a-a82c-bd64-1269-2324784197b1@redhat.com>

1. I got our RH video ccs guy to review and he's got some good news and 
recommendations:

> Not overly long, good audio/video quality, descriptive voiceover which 
> is easy to follow along with. Only a few minor things:
>
>   * Describing cutting the video until the process finishes usually
>     isn't necessary, it's something you can visualize with a
>     transition/cut/sped up footage, and having the narrator say
>     something along the lines of "This process may take a few minutes"
>     usually suffices. This would probably save you 30 sec to a minute
>     of time.
>
>   * Title and ending slides are good bookends for the video. Instead
>     of doing the intro VO on the catalog screen, which has a lot of
>     visual noise and can be a little distracting, creating a clean,
>     unified title slide with the title, name of the narrator, and
>     their title is a good way to start and end the video, and is
>     overall less distracting. The final slide can simply be a "Thank
>     you" slide or a slide with the Keycloak logo on it.
>
>   * If there are any KBase/documentation articles that relate to the
>     video, putting them in the description is pretty useful for those
>     who want more information.
>
> That's more or less what immediately stands out to me. Overall great job!

2. On the point about title slides, would it make sense to have a 
running slide deck, on which each slide acts as a title for the 
recording and is then updated to capture the url of the video after 
posting, eg 
https://docs.google.com/presentation/d/1powKwbEv2psKpt8cPYYxRqOpYUXZkXkPWMVtkVcMiBo/edit?usp=sharing

Paul

-- 
Paul Wright
Mobile Docs (github: finp)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180320/1a02b30a/attachment.html 

From eshortis at redhat.com  Tue Mar 20 16:34:57 2018
From: eshortis at redhat.com (Evan Shortiss)
Date: Tue, 20 Mar 2018 20:34:57 +0000
Subject: [aerogear-dev] Apple iOS and IBM Watson
Message-ID: <CA+BWC0+2CBZH9TJkoEQ+xZevTgz3i1Y_3wCqFsZa6M6s_hhVUg@mail.gmail.com>

This is interesting[1]. Apple and IBM collaborating on machine learning
with Apple's CoreML and IBM's Watson.

[1] - https://developer.apple.com/ibm/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180320/5cab6d71/attachment.html 

From aliok at redhat.com  Wed Mar 21 02:35:16 2018
From: aliok at redhat.com (Ali Ok)
Date: Wed, 21 Mar 2018 09:35:16 +0300
Subject: [aerogear-dev] Openshift Auth for UPS
In-Reply-To: <CAAg5f2SZBXHe9NhwcgmA_XY+nt5VaNK6wJXB4UXnGfwAN7ODMQ@mail.gmail.com>
References: <CAAg5f2SZBXHe9NhwcgmA_XY+nt5VaNK6wJXB4UXnGfwAN7ODMQ@mail.gmail.com>
Message-ID: <CABoO8LcPciczDY6+S1=bO4NaVBiK2a2_vjiW7SEkwkbkYygZ9Q@mail.gmail.com>

Looks very good Matthias :)

On Tue, Mar 20, 2018 at 1:01 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hola,
>
> here is a little video showing how to login to UPS, leveraging your
> Openshift credentials:
>
> https://youtu.be/2FLoVJ_KWL8
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2SZBXHe9NhwcgmA_XY%2Bnt5VaNK6wJXB4UXnGfwAN7ODMQ%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2SZBXHe9NhwcgmA_XY%2Bnt5VaNK6wJXB4UXnGfwAN7ODMQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180321/3b0365bb/attachment.html 

From matzew at apache.org  Fri Mar 23 05:20:03 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 23 Mar 2018 10:20:03 +0100
Subject: [aerogear-dev] Community Hangout: Automated Releases of
	Containerized Golang Applications
Message-ID: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>

Hi,

with the recent work on the mobile initiative around Openshift, more and
more repositories in AeroGear land are containing GOLANG code.

Our own Dara Hayes is willing to give a little intro and reflect some
experiences from his recent work on this repo:
https://github.com/aerogear/aerogear-app-metrics


Abstract: In this short talk demonstrates a very simple and developer
friendly workflow for releasing containerized services written in Go. It
also cover some lessons the team learned, when starting to build their
first Golang service, and provides some helpful tips and tricks for keeping
developers happy as they work with Go.


Time: Thursday. 29th of March, 2pm (GMT)

Looking forward seeing you all there (yes, the video is going to be
recorded)

-M


-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180323/f4471e3a/attachment.html 

From mwessend at redhat.com  Fri Mar 23 06:06:17 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Fri, 23 Mar 2018 11:06:17 +0100
Subject: [aerogear-dev] Community Hangout: Automated Releases of
	Containerized Golang Applications
In-Reply-To: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
Message-ID: <CAKUFdH00-LgS3ZDRNvBmSB9+3J15hoU8XiiV3f6tk_1sCKnHVg@mail.gmail.com>

URL for the live stream is:

https://www.youtube.com/watch?v=zlnlao9Gkrk



On Fri, Mar 23, 2018 at 10:20 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> with the recent work on the mobile initiative around Openshift, more and
> more repositories in AeroGear land are containing GOLANG code.
>
> Our own Dara Hayes is willing to give a little intro and reflect some
> experiences from his recent work on this repo:
> https://github.com/aerogear/aerogear-app-metrics
>
>
> Abstract: In this short talk demonstrates a very simple and developer
> friendly workflow for releasing containerized services written in Go. It
> also cover some lessons the team learned, when starting to build their
> first Golang service, and provides some helpful tips and tricks for keeping
> developers happy as they work with Go.
>
>
> Time: Thursday. 29th of March, 2pm (GMT)
>
> Looking forward seeing you all there (yes, the video is going to be
> recorded)
>
> -M
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_
> QAtEhyiyryve1vn9__YoQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180323/d43ce567/attachment-0001.html 

From dara.hayes at redhat.com  Fri Mar 23 06:24:53 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Fri, 23 Mar 2018 10:24:53 +0000
Subject: [aerogear-dev] Community Hangout: Automated Releases of
	Containerized Golang Applications
In-Reply-To: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
Message-ID: <CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>

Hey Mathias,

Could we get a calendar invite? Otherwise I'll forget to turn up and that
would be unfortunate :)

Kindest Regards,

Dara

On Fri, Mar 23, 2018 at 9:20 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi,
>
> with the recent work on the mobile initiative around Openshift, more and
> more repositories in AeroGear land are containing GOLANG code.
>
> Our own Dara Hayes is willing to give a little intro and reflect some
> experiences from his recent work on this repo:
> https://github.com/aerogear/aerogear-app-metrics
>
>
> Abstract: In this short talk demonstrates a very simple and developer
> friendly workflow for releasing containerized services written in Go. It
> also cover some lessons the team learned, when starting to build their
> first Golang service, and provides some helpful tips and tricks for keeping
> developers happy as they work with Go.
>
>
> Time: Thursday. 29th of March, 2pm (GMT)
>
> Looking forward seeing you all there (yes, the video is going to be
> recorded)
>
> -M
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_
> QAtEhyiyryve1vn9__YoQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Dara Hayes

Associate software engineer
<https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180323/836fe93a/attachment.html 

From eshortis at redhat.com  Fri Mar 23 15:58:11 2018
From: eshortis at redhat.com (Evan Shortiss)
Date: Fri, 23 Mar 2018 12:58:11 -0700
Subject: [aerogear-dev] Community Hangout: Automated Releases of
 Containerized Golang Applications
In-Reply-To: <CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
	<CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
Message-ID: <CA+BWC0+D7=Q592MEwFMX-Ek=LbVs8UC1V+Nx6gXOgs+Z+6bX8w@mail.gmail.com>

Might be worth seeing if this can be moved a couple of mins to avoid the
4.x team standup? Looking forward to it.

On Fri, Mar 23, 2018 at 3:24 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> Hey Mathias,
>
> Could we get a calendar invite? Otherwise I'll forget to turn up and that
> would be unfortunate :)
>
> Kindest Regards,
>
> Dara
>
> On Fri, Mar 23, 2018 at 9:20 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> with the recent work on the mobile initiative around Openshift, more and
>> more repositories in AeroGear land are containing GOLANG code.
>>
>> Our own Dara Hayes is willing to give a little intro and reflect some
>> experiences from his recent work on this repo:
>> https://github.com/aerogear/aerogear-app-metrics
>>
>>
>> Abstract: In this short talk demonstrates a very simple and developer
>> friendly workflow for releasing containerized services written in Go. It
>> also cover some lessons the team learned, when starting to build their
>> first Golang service, and provides some helpful tips and tricks for keeping
>> developers happy as they work with Go.
>>
>>
>> Time: Thursday. 29th of March, 2pm (GMT)
>>
>> Looking forward seeing you all there (yes, the video is going to be
>> recorded)
>>
>> -M
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryv
>> e1vn9__YoQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 

EVAN SHORTISS

MOBILE DEVELOPER

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

Los Angeles

evan.shortiss at redhat.com    M: +1-781-354-2834     IM: @evanshortiss
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@redhatnews <https://twitter.com/redhatnews>   Red Hat
<https://www.linkedin.com/company/red-hat>   Red Hat
<https://www.facebook.com/RedHatInc>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180323/ddc8e30a/attachment.html 

From matzew at apache.org  Sat Mar 24 04:59:03 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 24 Mar 2018 09:59:03 +0100
Subject: [aerogear-dev] Community Hangout: Automated Releases of
	Containerized Golang Applications
In-Reply-To: <CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
	<CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
Message-ID: <CAAg5f2S3cWcwgV9RvS0A=OR3yTGM-DqdwDvTu2SmKJuJT=33dQ@mail.gmail.com>

It's a community event, so no 'corp. calendar invites'... the thing from
youtube has a 'reminder' feature - perhaps that's good ?

On Fri, Mar 23, 2018 at 11:24 AM, Dara Hayes <dara.hayes at redhat.com> wrote:

> Hey Mathias,
>
> Could we get a calendar invite? Otherwise I'll forget to turn up and that
> would be unfortunate :)
>
> Kindest Regards,
>
> Dara
>
> On Fri, Mar 23, 2018 at 9:20 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi,
>>
>> with the recent work on the mobile initiative around Openshift, more and
>> more repositories in AeroGear land are containing GOLANG code.
>>
>> Our own Dara Hayes is willing to give a little intro and reflect some
>> experiences from his recent work on this repo:
>> https://github.com/aerogear/aerogear-app-metrics
>>
>>
>> Abstract: In this short talk demonstrates a very simple and developer
>> friendly workflow for releasing containerized services written in Go. It
>> also cover some lessons the team learned, when starting to build their
>> first Golang service, and provides some helpful tips and tricks for keeping
>> developers happy as they work with Go.
>>
>>
>> Time: Thursday. 29th of March, 2pm (GMT)
>>
>> Looking forward seeing you all there (yes, the video is going to be
>> recorded)
>>
>> -M
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryv
>> e1vn9__YoQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>


-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180324/41671e1c/attachment-0001.html 

From matzew at apache.org  Sat Mar 24 04:59:21 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 24 Mar 2018 09:59:21 +0100
Subject: [aerogear-dev] Community Hangout: Automated Releases of
 Containerized Golang Applications
In-Reply-To: <CA+BWC0+D7=Q592MEwFMX-Ek=LbVs8UC1V+Nx6gXOgs+Z+6bX8w@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
	<CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
	<CA+BWC0+D7=Q592MEwFMX-Ek=LbVs8UC1V+Nx6gXOgs+Z+6bX8w@mail.gmail.com>
Message-ID: <CAAg5f2QvVV6MHrHiuyvN+z7YuteaCNqvVC_=LhD+DymcdmnsHw@mail.gmail.com>

sure we can move it 15 down

On Fri, Mar 23, 2018 at 8:58 PM, Evan Shortiss <eshortis at redhat.com> wrote:

> Might be worth seeing if this can be moved a couple of mins to avoid the
> 4.x team standup? Looking forward to it.
>
> On Fri, Mar 23, 2018 at 3:24 AM, Dara Hayes <dara.hayes at redhat.com> wrote:
>
>> Hey Mathias,
>>
>> Could we get a calendar invite? Otherwise I'll forget to turn up and that
>> would be unfortunate :)
>>
>> Kindest Regards,
>>
>> Dara
>>
>> On Fri, Mar 23, 2018 at 9:20 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>>> Hi,
>>>
>>> with the recent work on the mobile initiative around Openshift, more and
>>> more repositories in AeroGear land are containing GOLANG code.
>>>
>>> Our own Dara Hayes is willing to give a little intro and reflect some
>>> experiences from his recent work on this repo:
>>> https://github.com/aerogear/aerogear-app-metrics
>>>
>>>
>>> Abstract: In this short talk demonstrates a very simple and developer
>>> friendly workflow for releasing containerized services written in Go. It
>>> also cover some lessons the team learned, when starting to build their
>>> first Golang service, and provides some helpful tips and tricks for keeping
>>> developers happy as they work with Go.
>>>
>>>
>>> Time: Thursday. 29th of March, 2pm (GMT)
>>>
>>> Looking forward seeing you all there (yes, the video is going to be
>>> recorded)
>>>
>>> -M
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> github: https://github.com/matzew
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Aerogear" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to aerogear+unsubscribe at googlegroups.com.
>>> To post to this group, send email to aerogear at googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryv
>>> e1vn9__YoQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Dara Hayes
>>
>> Associate software engineer
>> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
>
> EVAN SHORTISS
>
> MOBILE DEVELOPER
>
> Red Hat NA <https://www.redhat.com/>
>
> Los Angeles
>
> evan.shortiss at redhat.com    M: +1-781-354-2834     IM: @evanshortiss
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> @redhatnews <https://twitter.com/redhatnews>   Red Hat
> <https://www.linkedin.com/company/red-hat>   Red Hat
> <https://www.facebook.com/RedHatInc>
>



-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180324/0595ea78/attachment.html 

From matzew at apache.org  Thu Mar 29 05:05:33 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 29 Mar 2018 11:05:33 +0200
Subject: [aerogear-dev] Community Hangout: Automated Releases of
 Containerized Golang Applications
In-Reply-To: <CAAg5f2QvVV6MHrHiuyvN+z7YuteaCNqvVC_=LhD+DymcdmnsHw@mail.gmail.com>
References: <CAAg5f2Qe+HJWgjJTvSQD+RUMV=RX_QAtEhyiyryve1vn9__YoQ@mail.gmail.com>
	<CABkcJC2o6F86uSnVpJub8yO-73Vb8_yMVHyExVcwTHBv2ydcXA@mail.gmail.com>
	<CA+BWC0+D7=Q592MEwFMX-Ek=LbVs8UC1V+Nx6gXOgs+Z+6bX8w@mail.gmail.com>
	<CAAg5f2QvVV6MHrHiuyvN+z7YuteaCNqvVC_=LhD+DymcdmnsHw@mail.gmail.com>
Message-ID: <CAAg5f2TjqybWPAXogtvR8qLikp-57w=Z1BSqw-jxBafm-OW-4w@mail.gmail.com>

reminder, today at 15:15 (CET)  we have our community hangout on "Golang
and the ecosystem" with Dara!

-Matthias

On Sat, Mar 24, 2018 at 9:59 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> sure we can move it 15 down
>
> On Fri, Mar 23, 2018 at 8:58 PM, Evan Shortiss <eshortis at redhat.com>
> wrote:
>
>> Might be worth seeing if this can be moved a couple of mins to avoid the
>> 4.x team standup? Looking forward to it.
>>
>> On Fri, Mar 23, 2018 at 3:24 AM, Dara Hayes <dara.hayes at redhat.com>
>> wrote:
>>
>>> Hey Mathias,
>>>
>>> Could we get a calendar invite? Otherwise I'll forget to turn up and
>>> that would be unfortunate :)
>>>
>>> Kindest Regards,
>>>
>>> Dara
>>>
>>> On Fri, Mar 23, 2018 at 9:20 AM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> with the recent work on the mobile initiative around Openshift, more
>>>> and more repositories in AeroGear land are containing GOLANG code.
>>>>
>>>> Our own Dara Hayes is willing to give a little intro and reflect some
>>>> experiences from his recent work on this repo:
>>>> https://github.com/aerogear/aerogear-app-metrics
>>>>
>>>>
>>>> Abstract: In this short talk demonstrates a very simple and developer
>>>> friendly workflow for releasing containerized services written in Go. It
>>>> also cover some lessons the team learned, when starting to build their
>>>> first Golang service, and provides some helpful tips and tricks for keeping
>>>> developers happy as they work with Go.
>>>>
>>>>
>>>> Time: Thursday. 29th of March, 2pm (GMT)
>>>>
>>>> Looking forward seeing you all there (yes, the video is going to be
>>>> recorded)
>>>>
>>>> -M
>>>>
>>>>
>>>> --
>>>> Matthias Wessendorf
>>>>
>>>> github: https://github.com/matzew
>>>> twitter: http://twitter.com/mwessendorf
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Aerogear" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to aerogear+unsubscribe at googlegroups.com.
>>>> To post to this group, send email to aerogear at googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>>> gid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryv
>>>> e1vn9__YoQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Qe%2BHJWgjJTvSQD%2BRUMV%3DRX_QAtEhyiyryve1vn9__YoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Dara Hayes
>>>
>>> Associate software engineer
>>> <https://redhat.com> TRIED. TESTED. TRUSTED.
>>> <https://redhat.com/trusted>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>>
>> EVAN SHORTISS
>>
>> MOBILE DEVELOPER
>>
>> Red Hat NA <https://www.redhat.com/>
>>
>> Los Angeles
>>
>> evan.shortiss at redhat.com    M: +1-781-354-2834     IM: @evanshortiss
>> <https://red.ht/sig>
>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>> @redhatnews <https://twitter.com/redhatnews>   Red Hat
>> <https://www.linkedin.com/company/red-hat>   Red Hat
>> <https://www.facebook.com/RedHatInc>
>>
>
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180329/1be025b7/attachment-0001.html 

From dpassos at redhat.com  Thu Mar 29 17:08:50 2018
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 29 Mar 2018 18:08:50 -0300
Subject: [aerogear-dev] Replace Spring dependency management by a single
	gradle file
Message-ID: <CADF=h2tqu_R1zY66YxPT2w6U-RdKqCJBfU+gtPihjyJEmKsmpg@mail.gmail.com>

Hi,

While working on push stuff I figure out Spring dependency management[1]
doesn?t work properly with Gradle transitive dependencies[2].

TL;DR It?s ignoring the transitive dependencies and on push, it causes some
dependency conflicts. Since Google Services plugin doesn?t found any
dependency it?s going to inject it from your on.

Android dependency 'com.google.firebase:firebase-iid' has different
version for the compile (11.4.2) and runtime (12.0.1) classpath.

I?ve sent a PR[3] to remove it for now and revisit it in the future. I have
moved all our dependencies version for a single file[4] like most of the
libraries do.

This also will make us a little more fast and flexible to do changes in our
dependencies.

Any thoughts?

[1] https://github.com/spring-gradle-plugins/dependency-management-plugin
[2]
https://docs.gradle.org/current/userguide/managing_transitive_dependencies.html
[3] https://github.com/aerogear/aerogear-android-sdk/pull/173
[4]
https://github.com/aerogear/aerogear-android-sdk/blob/master/constants.gradle
?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180329/c3a36c6b/attachment.html 

From dpassos at redhat.com  Thu Mar 29 17:30:23 2018
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 29 Mar 2018 18:30:23 -0300
Subject: [aerogear-dev] Make MobileCore Init automatically called in Android
	SDK
Message-ID: <CADF=h2vUzwb1U30O0GB9J4taBkkvAuvUdSkqHEk7jyQfDhK3Og@mail.gmail.com>

Hi,

Revisiting some Google and Firebase stuff Summers and I realized the
Firebase Android SDK doesn?t need we do any init to the lib starts/be
configured.

TL;DR what Firebase does is uses a Content Provide[1] (not really created
for this) as a trick to initialize the lib before the app starts

Why Content provider?

Because it has access to the applicationContext[2] and is called *before*
all other Android kinds of stuff in the Android lifecycle (including
Application)

I?d like to do the same for our Android SDK and initialize the lib using
the same trick so we can provide a MobileCore.getInstance() already
configured with all the things the developer needs (Logger, HttpLayer,
Mobile Services info, etc?) without need to create an application class or
call MobileCore.init(context) anywhere and kill all static methods we have
today in MobileCore

It will also allow us to send the default metrics before the Android
lifecycle starts the app and have some controls (when need) to know when
the app is in background and foreground, listeners possible crashes and
other things without the developer needs to call/configure anything.

PS: This is will probably be the first step to kill the responsibility to
the MobileCore instantiate the Service Modules[3]

Any thoughts?

[1]
https://developer.android.com/guide/topics/providers/content-providers.html
[2]
https://developer.android.com/reference/android/content/ContentProvider.html#getContext(
)
[3] https://issues.jboss.org/browse/AGDROID-796
?
-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180329/5eb8e631/attachment.html 

From mwessend at redhat.com  Thu Mar 29 17:37:54 2018
From: mwessend at redhat.com (Matthias Wessendorf)
Date: Thu, 29 Mar 2018 23:37:54 +0200
Subject: [aerogear-dev] Replace Spring dependency management by a single
	gradle file
In-Reply-To: <CADF=h2tqu_R1zY66YxPT2w6U-RdKqCJBfU+gtPihjyJEmKsmpg@mail.gmail.com>
References: <CADF=h2tqu_R1zY66YxPT2w6U-RdKqCJBfU+gtPihjyJEmKsmpg@mail.gmail.com>
Message-ID: <CAKUFdH2OK2PJcxB+fuEUHHyf3P65bHWPG8QC7vXsv6whTcQYfQ@mail.gmail.com>

sounds good to me.

TBH, I found it quite confusing, seening that spring dependency in there,
just because of BOM support

On Thu, Mar 29, 2018 at 11:08 PM, Daniel Passos <dpassos at redhat.com> wrote:

> Hi,
>
> While working on push stuff I figure out Spring dependency management[1]
> doesn?t work properly with Gradle transitive dependencies[2].
>
> TL;DR It?s ignoring the transitive dependencies and on push, it causes
> some dependency conflicts. Since Google Services plugin doesn?t found any
> dependency it?s going to inject it from your on.
>
> Android dependency 'com.google.firebase:firebase-iid' has different version for the compile (11.4.2) and runtime (12.0.1) classpath.
>
> I?ve sent a PR[3] to remove it for now and revisit it in the future. I
> have moved all our dependencies version for a single file[4] like most of
> the libraries do.
>
> This also will make us a little more fast and flexible to do changes in
> our dependencies.
>
> Any thoughts?
>
> [1] https://github.com/spring-gradle-plugins/dependency-management-plugin
> [2] https://docs.gradle.org/current/userguide/managing_
> transitive_dependencies.html
> [3] https://github.com/aerogear/aerogear-android-sdk/pull/173
> [4] https://github.com/aerogear/aerogear-android-sdk/blob/
> master/constants.gradle
> ?
> --
> -- Passos
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CADF%3Dh2tqu_R1zY66YxPT2w6U-RdKqCJBfU%
> 2BgtPihjyJEmKsmpg%40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CADF%3Dh2tqu_R1zY66YxPT2w6U-RdKqCJBfU%2BgtPihjyJEmKsmpg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Project lead AeroGear.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180329/e6727df7/attachment.html