Re: [aerogear-dev] Repo Names (was: Re: Push "all inclusive" demo)

+1 on topic demo +1 for elect a new name

Matthias Wessendorf wrote: > On Thu, Jun 27, 2013 at 11:11 PM, Summers Pittman<supittma(a)redhat.com> wrote: >> On 06/27/2013 03:23 PM, Corinne Krych wrote: >>> Hello all, >>> >>> Before renaming, I suggest we choose which category we want to tag ProDoctor. From Jay proposal: >>> - showcase demo >>> - topics demos >>> - quickstart >>> - one off examples. >>> >>> Given those categories, I think ProDoctor is between topics demos and a first draft for showcase demo. >> +1 to it being a topics demo. > > I agree on topic demo. > > > >>> Do we want to keep the topics demos category ? As Pete Muir pointed out, does it make sense? >>> >>> or do we prefer to enhance our quick start/tutorials with different scenarios? Maybe working on the recipes/cookbook approach as defined by passos. >>> >>> We could recycle ProDoctor into several quickstarts (simplify code) and make difference cases: selective push, broadcast etc… >>> We could also reuse some material for showcase demo and off course make it blogpost. >>> >>> Several options. Depending on the choice we then get a name. >>> Just wondering which category does the TODO app falls in? >>> >>> ++ >>> Corinne >>> >>> >>> On Jun 27, 2013, at 7:08 PM, Matthias Wessendorf<matzew(a)apache.org> wrote: >>> >>>> On Thu, Jun 27, 2013 at 7:01 PM, Kris Borchers<kris(a)redhat.com> wrote: >>>>> On Jun 27, 2013, at 11:57 AM, Matthias Wessendorf<matzew(a)apache.org> wrote: >>>>> >>>>>> Any more thoughts on this ? >>>>>> >>>>>> Looks like right now the favorite is: >>>>>> aerogear-prodoctor-** >>>>> Definitely thought we were changing the name so probably not good to name the repo that. >>>> exactly :) >>>> >>>> name (and repo) needs to be changed :) >>>> >>>> Any "proposals" ? >>>> >>>>>> Perhaps we can find something "better" for the "prodoctor"... >>>>>> >>>>>> On Tue, Jun 25, 2013 at 11:40 AM, Matthias Wessendorf<matzew(a)apache.org> wrote: >>>>>>> >>>>>>> On Tue, Jun 25, 2013 at 10:52 AM, Corinne Krych<corinnekrych(a)gmail.com> >>>>>>> wrote: >>>>>>>> It's depend what we want to do with it. >>>>>>>> >>>>>>>> If it's to demo Push feature only I would suggest: >>>>>>>> aerogear-push-demo-backend/ios/web/android >>>>>>>> >>>>>>>> If we want to demo more features we could call it simply >>>>>>>> aerogear-prodoctor-… >>>>>>> yeah, works for me too. It's simple :) >>>>>>> >>>>>>>> ++ >>>>>>>> Corinne >>>>>>>> >>>>>>>> On Jun 25, 2013, at 9:54 AM, Matthias Wessendorf<matzew(a)apache.org> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> >>>>>>>> this is not really a quick start :) So I am asking for new names. >>>>>>>> >>>>>>>> Once have have decided on "better" repo names for this, I'll create a JIRA >>>>>>>> so that the repos will be renamed to better reflect what they actually >>>>>>>> are... >>>>>>>> >>>>>>>> >>>>>>>> Thoughts? >>>>>>>> >>>>>>>> -Matthias >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On Jun 11, 2013, at 10:45 AM, Sebastien Blanc<scm.blanc(a)gmail.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hey ! >>>>>>>>> We would like to provide, in a quite short delay (coming 2 weeks) a demo >>>>>>>>> showing all the different bits of the "push" world , meaning : >>>>>>>>> client | push server | JEE Backend App >>>>>>>>> >>>>>>>>> We already have the push server (aerogear-unified-push-server) : so we >>>>>>>>> need a client (iOS and maybe also Android) and a simple JEE backend >>>>>>>>> application. The backend app will mostly be scaffolded and will use the >>>>>>>>> aerogear-unified-push-java-client to send messages to the Push Server. >>>>>>>>> >>>>>>>>> Then of course, we need to think about an idea of the application itself. >>>>>>>>> It needs to stay really simple, show how we can send selectively and should >>>>>>>>> be a bit "business" related. >>>>>>>>> >>>>>>>>> So, I came up with an idea this morning that we can discuss here, of >>>>>>>>> course if you have any other idea don't hesitate to share it. >>>>>>>>> >>>>>>>>> Push Demo >>>>>>>>> >>>>>>>>> Introduction >>>>>>>>> >>>>>>>>> Prodoctor is a company in the health care industry, selling a >>>>>>>>> revolutionary tensiometer. Their clients are doctors. Prodoctor has several >>>>>>>>> sales agents all over the United States. At the headquarters, they have >>>>>>>>> their "first line" sales department doing cold calls all along the day. As >>>>>>>>> soon they have a concrete lead, they use their Prodoctor Admin app to filter >>>>>>>>> out available sales Agents available in the lead area. They can then send >>>>>>>>> them a push notification. >>>>>>>>> >>>>>>>>> The sales agent receives the notification on their mobile device that a >>>>>>>>> new lead is available. The agent will handle the lead by "accepting" the >>>>>>>>> notification informing the other agents that the lead has been processed. >>>>>>>>> >>>>>>>>> The client app >>>>>>>>> >>>>>>>>> The client consist of a list of leads : a lead can be "open" or "in >>>>>>>>> process", leads "in process" of other sales are not visible. >>>>>>>>> >>>>>>>>> optional : when the client tap a lead it appears on a map >>>>>>>>> >>>>>>>>> The client has a status that he can set: STANDBY | WITH_CLIENT |PTO >>>>>>>>> The client has a location >>>>>>>>> The client has an alias >>>>>>>>> >>>>>>>>> Prodoctor Admin client >>>>>>>>> >>>>>>>>> The admin client can create a new lead : >>>>>>>>> >>>>>>>>> A lead consist of a name and a location >>>>>>>>> >>>>>>>>> The admin client can query for Sales Agents based on : >>>>>>>>> >>>>>>>>> Status >>>>>>>>> Location >>>>>>>>> >>>>>>>>> The admin client can assign a lead to a selection (1..n) of sales agents, >>>>>>>>> this will send out the notifications. >>>>>>>>> >>>>>>>>> The admin client manage the Sales Agents DB. >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> >>>>>>>>> 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 >>>>>> >>>>>> -- >>>>>> 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 >> _______________________________________________ >> 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 -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev