Looks good! On 16 May 2013 18:38, Kris Borchers <kris(a)redhat.com&gt; wrote: > Hey all, > > Please take a look at https://issues.jboss.org/browse/AGPUSH-11 and let > me know if you would add/change/remove any suggested components I have > suggested there. > > Thanks! > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Not sure what's the main idea, but for security we can do something like: AGPUSH-your-favorite-component-here, security If we start to create new components for security per project, it will add more confusion. At least to me. Matthias Wessendorf wrote: > Howdy, > > added a few comments > > > On Fri, May 17, 2013 at 8:52 AM, Daniel Bevenius > <daniel.bevenius(a)gmail.com <mailto:daniel.bevenius@gmail.com>> wrote: > > Looks good! > > > On 16 May 2013 18:38, Kris Borchers <kris(a)redhat.com > <mailto:kris@redhat.com>> wrote: > > Hey all, > > Please take a look at > https://issues.jboss.org/browse/AGPUSH-11 and let me know if you > would add/change/remove any suggested components I have > suggested there. > > Thanks! > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

What about the following Specific Components The following are very specific to a certain part of the "work": UnifiedPush-server UnifiedPush-ios UnifiedPush-android UnifiedPush-javascript UnifiedPush-admin UnifiedPush-java(-sender) UnifiedPush-aps

UnifiedPush-gcm UnifiedPush-simplePush (=== connection TO (various) SP networks) SimplePush-server SimplePush-javascript (=== client, I think there is only a JS client) Now, various of the above "component" have similar concerns, like security or documentation. Generic components (e.g. used like a tag) security Documentation Examples PushNetwork (e.g. when investigating for adding new supported ones...) OpenShift (support for UP / SP) Tooling (== Tooling / RAD ) Perhaps these are really more tags, but I am fine in "abusing" these components as tags.

On Mon, May 20, 2013 at 9:37 PM, Jay Balunas <jbalunas(a)redhat.com&gt; wrote: +1 - I added a comment related to this. Also, I'm not sure if Jira has "Component Themes" like it has other things, but there will be a lot of shared components between the various AG Jira's. I think it will be important to be consistent where possible (capitalization, abbreviations, naming, etc...). On May 20, 2013, at 3:23 PM, Bruno Oliveira wrote: > Not sure what's the main idea, but for security we can do something like: > > AGPUSH-your-favorite-component-here, security > > If we start to create new components for security per project, it will > add more confusion. At least to me. > > Matthias Wessendorf wrote: >> Howdy, >> >> added a few comments >> >> >> On Fri, May 17, 2013 at 8:52 AM, Daniel Bevenius >> <daniel.bevenius(a)gmail.com <mailto:daniel.bevenius@gmail.com>> wrote: >> >> Looks good! >> >> >> On 16 May 2013 18:38, Kris Borchers <kris(a)redhat.com >> <mailto:kris@redhat.com>> wrote: >> >> Hey all, >> >> Please take a look at >> https://issues.jboss.org/browse/AGPUSH-11 and let me know if you >> would add/change/remove any suggested components I have >> suggested there. >> >> Thanks! >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

apns - whoops :) On Tue, May 21, 2013 at 3:13 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: > > On May 21, 2013, at 8:09 AM, Matthias Wessendorf <matzew(a)apache.org&gt; > wrote: > > What about the following > > > Specific Components > > The following are very specific to a certain part of the "work": > > - UnifiedPush-server > - UnifiedPush-ios > - UnifiedPush-android > - UnifiedPush-javascript > - UnifiedPush-admin > - UnifiedPush-java(-sender) > - UnifiedPush-aps > > aps or apns? > > > - UnifiedPush-gcm > - UnifiedPush-simplePush (=== connection TO (various) SP networks) > - SimplePush-server > - SimplePush-javascript (=== client, I think there is only a JS > client) > > > Now, various of the above "component" have similar concerns, like * > security* or *documentation*. > <https://gist.github.com/matzew/90c9f6837eee6cb074cc#generic-components-eg... > components (e.g. used like a tag) > > - security > - Documentation > - Examples > - PushNetwork (e.g. when investigating for adding new supported > ones...) > - OpenShift (support for UP / SP) > - Tooling (== Tooling / RAD ) > > Perhaps these are really more *tags*, but I am fine in "abusing" these > components as tags. > > This looks great! GO GO GO GO! > > > > On Mon, May 20, 2013 at 9:37 PM, Jay Balunas <jbalunas(a)redhat.com&gt; wrote: > >> +1 - I added a comment related to this. >> >> Also, I'm not sure if Jira has "Component Themes" like it has other >> things, but there will be a lot of shared components between the various AG >> Jira's. I think it will be important to be consistent where possible >> (capitalization, abbreviations, naming, etc...). >> >> On May 20, 2013, at 3:23 PM, Bruno Oliveira wrote: >> >> > Not sure what's the main idea, but for security we can do something >> like: >> > >> > AGPUSH-your-favorite-component-here, security >> > >> > If we start to create new components for security per project, it will >> > add more confusion. At least to me. >> > >> > Matthias Wessendorf wrote: >> >> Howdy, >> >> >> >> added a few comments >> >> >> >> >> >> On Fri, May 17, 2013 at 8:52 AM, Daniel Bevenius >> >> <daniel.bevenius(a)gmail.com <mailto:daniel.bevenius@gmail.com>> wrote: >> >> >> >> Looks good! >> >> >> >> >> >> On 16 May 2013 18:38, Kris Borchers <kris(a)redhat.com >> >> <mailto:kris@redhat.com>> wrote: >> >> >> >> Hey all, >> >> >> >> Please take a look at >> >> https://issues.jboss.org/browse/AGPUSH-11 and let me know if >> you >> >> would add/change/remove any suggested components I have >> >> suggested there. >> >> >> >> Thanks! >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev(a)lists.jboss.org <mailto: >> aerogear-dev(a)lists.jboss.org&gt; >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> >> >> >> >> >> -- >> >> Matthias Wessendorf >> >> >> >> blog: http://matthiaswessendorf.wordpress.com/ >> >> sessions: http://www.slideshare.net/mwessendorf >> >> twitter: http://twitter.com/mwessendorf >> >> >> >> _______________________________________________ >> >> aerogear-dev mailing list >> >> aerogear-dev(a)lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > _______________________________________________ >> > aerogear-dev mailing list >> > aerogear-dev(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Ok, I will move forward with these components On Tue, May 21, 2013 at 3:16 PM, Daniel Bevenius < daniel.bevenius(a)gmail.com&gt; wrote: > +1 Look good! > > > On 21 May 2013 15:14, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> apns - whoops :) >> >> >> On Tue, May 21, 2013 at 3:13 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >> >>> >>> On May 21, 2013, at 8:09 AM, Matthias Wessendorf <matzew(a)apache.org&gt; >>> wrote: >>> >>> What about the following >>> >>> >>> Specific Components >>> >>> The following are very specific to a certain part of the "work": >>> >>> - UnifiedPush-server >>> - UnifiedPush-ios >>> - UnifiedPush-android >>> - UnifiedPush-javascript >>> - UnifiedPush-admin >>> - UnifiedPush-java(-sender) >>> - UnifiedPush-aps >>> >>> aps or apns? >>> >>> >>> - UnifiedPush-gcm >>> - UnifiedPush-simplePush (=== connection TO (various) SP networks) >>> - SimplePush-server >>> - SimplePush-javascript (=== client, I think there is only a JS >>> client) >>> >>> >>> Now, various of the above "component" have similar concerns, like * >>> security* or *documentation*. >>> <https://gist.github.com/matzew/90c9f6837eee6cb074cc#generic-components-eg... >>> components (e.g. used like a tag) >>> >>> - security >>> - Documentation >>> - Examples >>> - PushNetwork (e.g. when investigating for adding new supported >>> ones...) >>> - OpenShift (support for UP / SP) >>> - Tooling (== Tooling / RAD ) >>> >>> Perhaps these are really more *tags*, but I am fine in "abusing" these >>> components as tags. >>> >>> This looks great! GO GO GO GO! >>> >>> >>> >>> On Mon, May 20, 2013 at 9:37 PM, Jay Balunas <jbalunas(a)redhat.com&gt;wrote: >>> >>>> +1 - I added a comment related to this. >>>> >>>> Also, I'm not sure if Jira has "Component Themes" like it has other >>>> things, but there will be a lot of shared components between the various AG >>>> Jira's. I think it will be important to be consistent where possible >>>> (capitalization, abbreviations, naming, etc...). >>>> >>>> On May 20, 2013, at 3:23 PM, Bruno Oliveira wrote: >>>> >>>> > Not sure what's the main idea, but for security we can do something >>>> like: >>>> > >>>> > AGPUSH-your-favorite-component-here, security >>>> > >>>> > If we start to create new components for security per project, it >>>> will >>>> > add more confusion. At least to me. >>>> > >>>> > Matthias Wessendorf wrote: >>>> >> Howdy, >>>> >> >>>> >> added a few comments >>>> >> >>>> >> >>>> >> On Fri, May 17, 2013 at 8:52 AM, Daniel Bevenius >>>> >> <daniel.bevenius(a)gmail.com <mailto:daniel.bevenius@gmail.com>> >>>> wrote: >>>> >> >>>> >> Looks good! >>>> >> >>>> >> >>>> >> On 16 May 2013 18:38, Kris Borchers <kris(a)redhat.com >>>> >> <mailto:kris@redhat.com>> wrote: >>>> >> >>>> >> Hey all, >>>> >> >>>> >> Please take a look at >>>> >> https://issues.jboss.org/browse/AGPUSH-11 and let me know >>>> if you >>>> >> would add/change/remove any suggested components I have >>>> >> suggested there. >>>> >> >>>> >> Thanks! >>>> >> >>>> >> _______________________________________________ >>>> >> aerogear-dev mailing list >>>> >> aerogear-dev(a)lists.jboss.org <mailto: >>>> aerogear-dev(a)lists.jboss.org&gt; >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >> >>>> >> >>>> >> >>>> >> _______________________________________________ >>>> >> aerogear-dev mailing list >>>> >> aerogear-dev(a)lists.jboss.org <mailto: >>>> aerogear-dev(a)lists.jboss.org&gt; >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Matthias Wessendorf >>>> >> >>>> >> blog: http://matthiaswessendorf.wordpress.com/ >>>> >> sessions: http://www.slideshare.net/mwessendorf >>>> >> twitter: http://twitter.com/mwessendorf >>>> >> >>>> >> _______________________________________________ >>>> >> aerogear-dev mailing list >>>> >> aerogear-dev(a)lists.jboss.org >>>> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> > _______________________________________________ >>>> > aerogear-dev mailing list >>>> > aerogear-dev(a)lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>> >>> >>> >>> -- >>> Matthias Wessendorf >>> >>> blog: http://matthiaswessendorf.wordpress.com/ >>> sessions: http://www.slideshare.net/mwessendorf >>> twitter: http://twitter.com/mwessendorf >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf