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