Hi Dmitry, Since Gayan is in support now, I will continue to work on this. The doc attached, contains the items completed by Gayan so far.
I will be able to do a demo on next Monday with the completed items. And we will be able to ship the completed feature for M6. Thanks Manisha On Fri, Aug 15, 2014 at 7:18 AM, Gayan Dhanushka <[email protected]> wrote: > Hi Dmitry, > > I have scheduled a demo o Monday. I will do a sample implementation of the > two scenarios and give a demo to you on Monday. > > GayanD > > > On Fri, Aug 15, 2014 at 1:05 AM, Dmitry Sotnikov <[email protected]> wrote: > >> Yes, some sort of PoC would be good. I am not sure what you mean by >> showing the Type B messages on the page - so would be great to see it in >> action or at least on mockups... >> On Aug 14, 2014 8:02 PM, "Dimuthu Leelarathne" <[email protected]> wrote: >> >>> Hi Dmitry, >>> >>> Please see my comments inline. >>> >>> >>> On Thu, Aug 14, 2014 at 12:17 PM, Dmitry Sotnikov <[email protected]> >>> wrote: >>> >>>> Gayan and Dimuthu, >>>> >>>> From my perspective, one-off UX exceptions are bad, because they make >>>> the UI inconsistent. >>>> >>>> There are two types of messages: >>>> A. High-level external notifications of someone taking some action >>>> (e.g. "John created a new app") and >>>> B. Low-level ongoing processes happening in AF as result of what the >>>> current user clicks ("Creating initial GIT repository", etc.) >>>> >>>> Type A are more social and shown across team, and only when something >>>> is actually successfully finished. >>>> >>>> Spinning wheels / progress indications are only relevant to type B. >>>> These messages are only related to the current particular user and show >>>> work in progress, starting immediately once the user clicks something. >>>> >>>> So from my perspective, either we show both types in one pane, or have >>>> two different panes (or other UX metaphors) for the two types. >>>> >>> >>> What I am suggesting is a different approach. Which is to show the type >>> B messages on the page itself where the information is related. For example >>> the fact that build is in progress should be on the Build & Repo page >>> itself. What if we do a POC for the same scenario >>> >>> 1 - on the wall >>> 2 - on the page >>> >>> And see which is user friendly? I agree two panes are not going to be a >>> good solution. >>> >>> thanks, >>> dimuthu >>> >>> >>>> My understanding is that the current idea is to try to re-use the same >>>> App Wall for everything, right? >>>> >>>> Dmitry >>>> >>>> >>>> >>>> On Thu, Aug 14, 2014 at 9:39 AM, Gayan Dhanushka <[email protected]> >>>> wrote: >>>> >>>>> Hi Dimuthu, >>>>> >>>>> I tried a sample implementation to show the implementation on the >>>>> application wall. This was done by looking at the content of the message. >>>>> It was successful. But this may not be ideal since for different kind of >>>>> start-inprogress-ended messages we may need to have different logic. >>>>> >>>>> Meanwhile I can share some wire frames of the approach suggested above >>>>> to show the in progress activities on the pages themselves. >>>>> >>>>> Thanks >>>>> GayanD >>>>> >>>>> >>>>> On Thu, Aug 14, 2014 at 4:43 AM, Dimuthu Leelarathne < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Gayan, >>>>>> >>>>>> >>>>>> On Wed, Aug 13, 2014 at 2:28 PM, Gayan Dhanushka <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi Dimuthu, >>>>>>> >>>>>>> Following are a set of actions that we want to give >>>>>>> "started-inprogress-ended" messages and places where we would put the >>>>>>> spinning wheel and messages. >>>>>>> >>>>>>> 1) Application Creation - User home near the application thumbnail >>>>>>> (This is already implemented) >>>>>>> 2) Application Upload - Application creation page (This is already >>>>>>> implemented. Spinning wheel is shown on the application creation page >>>>>>> until >>>>>>> the application is uploaded) >>>>>>> 3) Build - Repos Builds page near last build status >>>>>>> 4) Deployment - Repos Builds page near last deploy id >>>>>>> 5) Promote / Demote - Lifecycle page under the particular version >>>>>>> >>>>>>> I am tentative on having an in progress state for resource creation >>>>>>> since it does not take much time. >>>>>>> >>>>>>> >>>>>> It doesn't take much time in Dev setups. But takes considerable time >>>>>> in Cloud. I think for resources we need to give "started" and "ended" >>>>>> messages. >>>>>> >>>>>> @ Dmitry: What do you think about the new proposal? Giving >>>>>> progress-reporting on the page itself, rather than on the wall? >>>>>> >>>>>> We can do some wireframes and then can finalise. WDYT? >>>>>> >>>>>> thanks, >>>>>> dimuthu >>>>>> >>>>>> >>>>>> What are your thoughts? >>>>>>> >>>>>>> Regards >>>>>>> Gayan >>>>>>> >>>>>>> >>>>>>> On Wed, Aug 13, 2014 at 12:28 PM, Dimuthu Leelarathne < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Gayan, >>>>>>>> >>>>>>>> According to our offline discussion, then lets do this. >>>>>>>> >>>>>>>> 1 - Identify and list all actions that we want to give >>>>>>>> "started-inprogress-ended" messages >>>>>>>> 2 - Identify on which sections we are going to give feedback - >>>>>>>> spinning icon with messages >>>>>>>> >>>>>>>> If all of us agree, proceed. >>>>>>>> >>>>>>>> thanks, >>>>>>>> dimuthu >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Aug 13, 2014 at 11:54 AM, Gayan Dhanushka <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Dimuthu / Dmitry, >>>>>>>>> >>>>>>>>> IMHO it is not good to use the wall to show on going events. It is >>>>>>>>> more meant to show an action which is triggered by a user or an action >>>>>>>>> triggered by the app factory system. >>>>>>>>> >>>>>>>>> Currently we have build and deployment events which takes some >>>>>>>>> time to complete. While I agree the fact that the user must have some >>>>>>>>> feedback of the ongoing processes, shall we move these notifications >>>>>>>>> to the >>>>>>>>> page it self? We can have a small spinning icon on the page itself >>>>>>>>> near >>>>>>>>> last build status and deployment id. >>>>>>>>> >>>>>>>>> WDYT? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Aug 13, 2014 at 10:51 AM, Gayan Dhanushka <[email protected] >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> Hi Anuruddha / Dimuthu, >>>>>>>>>> >>>>>>>>>> The more global this ID is for all the events makes it more >>>>>>>>>> consistent. Otherwise we'll have to render these messages according >>>>>>>>>> to >>>>>>>>>> different parameters which are there in each message. Having said >>>>>>>>>> that we >>>>>>>>>> need to figure out a common way of doing this. Doing this by looking >>>>>>>>>> at the >>>>>>>>>> message content is not a good approach I guess. Need to figure out a >>>>>>>>>> better >>>>>>>>>> way of doing this. >>>>>>>>>> >>>>>>>>>> Gayan >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Aug 13, 2014 at 10:38 AM, Dimuthu Leelarathne < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> Good question. How about generating an ID that can be generated >>>>>>>>>>> equally from both sides. For example, if it is build then buildID. >>>>>>>>>>> If it is >>>>>>>>>>> deployment then md5 sum. The more unique the the ID is, then we >>>>>>>>>>> have less >>>>>>>>>>> work in identifying decoding user/event. >>>>>>>>>>> >>>>>>>>>>> thanks, >>>>>>>>>>> dimuthu >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wed, Aug 13, 2014 at 10:30 AM, Anuruddha Premalal < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi Gayan, >>>>>>>>>>>> >>>>>>>>>>>> We'll also need to consider about the failure events while >>>>>>>>>>>> tracking the progress. >>>>>>>>>>>> >>>>>>>>>>>> eg. Deployment failure should stop the progress of the >>>>>>>>>>>> deployment event. >>>>>>>>>>>> >>>>>>>>>>>> So we'll have to keep track on start, failure and stop status >>>>>>>>>>>> of a particular event. >>>>>>>>>>>> >>>>>>>>>>>> Other concern is assigning UUID's for events. These events are >>>>>>>>>>>> not fired from a central point how are we going to associate a >>>>>>>>>>>> UUID to >>>>>>>>>>>> track them? >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> Anuruddha. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Aug 13, 2014 at 5:37 AM, Dimuthu Leelarathne < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> There can be several methods, one being subscription >>>>>>>>>>>>> management. However since master branch is shared by all it would >>>>>>>>>>>>> be >>>>>>>>>>>>> interesting to know whether a build was triggered on it by all. >>>>>>>>>>>>> However >>>>>>>>>>>>> even in the first phase we must filter out activities happening >>>>>>>>>>>>> on the fork >>>>>>>>>>>>> repos. I think the approach Manjula mentioned should be applied >>>>>>>>>>>>> to forked >>>>>>>>>>>>> repos. >>>>>>>>>>>>> >>>>>>>>>>>>> Lets add all events to the doc life cycle and issue tracker >>>>>>>>>>>>> events as well. >>>>>>>>>>>>> >>>>>>>>>>>>> thanks, >>>>>>>>>>>>> dimuthu >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, Aug 12, 2014 at 8:42 PM, Gayan Dhanushka < >>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Manjula, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks for the input. I will try to utilize the above >>>>>>>>>>>>>> mentioned method in the second phase when trying to make the app >>>>>>>>>>>>>> wall more >>>>>>>>>>>>>> personalized. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards >>>>>>>>>>>>>> GayanD >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, Aug 12, 2014 at 5:56 PM, Manjula Rathnayake < >>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Personalized app-wall can be achieved by the way we publish >>>>>>>>>>>>>>> activities to social component. In current implementation, we >>>>>>>>>>>>>>> publish >>>>>>>>>>>>>>> activities to two contexts called 'foo-user' and 'bar-app' >>>>>>>>>>>>>>> which is >>>>>>>>>>>>>>> rendered in wall as 'foo user wall' and 'bar app wall'. We can >>>>>>>>>>>>>>> introduce >>>>>>>>>>>>>>> another context for personalized activities called >>>>>>>>>>>>>>> 'bar_app-foo_user' which >>>>>>>>>>>>>>> can be rendered in 'bar app wall' only for 'foo-user'. >>>>>>>>>>>>>>> In short, we define contexts for each user for getting a >>>>>>>>>>>>>>> personalized app-wall. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> thank you. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Tue, Aug 12, 2014 at 2:49 PM, Dmitry Sotnikov < >>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Gayan, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Indeed, looks like Udara and I are thinking along the same >>>>>>>>>>>>>>>> lines. :) This is more than just a build. E.g. when I am >>>>>>>>>>>>>>>> creating an >>>>>>>>>>>>>>>> application, there are a lot of things that happen (borrowing >>>>>>>>>>>>>>>> from your >>>>>>>>>>>>>>>> list): >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. application creation started >>>>>>>>>>>>>>>> 2. initial git repo creation >>>>>>>>>>>>>>>> 3. jenkins space creation >>>>>>>>>>>>>>>> 4. issue tracker space creation >>>>>>>>>>>>>>>> 5. app authorization in cloud environments >>>>>>>>>>>>>>>> 6. application creation completed >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If I am creating an app - I'd like to see them all - >>>>>>>>>>>>>>>> because this takes the mystery out of the process and makes me >>>>>>>>>>>>>>>> more >>>>>>>>>>>>>>>> comfortable with the platform. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If my team-member is creating an app - these 6 events and >>>>>>>>>>>>>>>> their progress are just noise. All I need to do is: "Jane >>>>>>>>>>>>>>>> created a new >>>>>>>>>>>>>>>> Java app HelloWorld" (if my role allows me to even know that >>>>>>>>>>>>>>>> this new app >>>>>>>>>>>>>>>> exists). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Again, obviously this all can be phase two. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Dmitry >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Aug 12, 2014 at 1:07 PM, Gayan Dhanushka < >>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Dmitry, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks for pointing things out. IMO that would be phase >>>>>>>>>>>>>>>>> two Dmitry. As soon as I complete publishing all the relevant >>>>>>>>>>>>>>>>> events I will >>>>>>>>>>>>>>>>> look to accommodate the noise-reduction filter as well. WDYT >>>>>>>>>>>>>>>>> of the >>>>>>>>>>>>>>>>> suggestion made by Udara in the above reply? I think that is >>>>>>>>>>>>>>>>> a valid >>>>>>>>>>>>>>>>> comment as well. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Udara, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The point that you are making is valid I think. With the >>>>>>>>>>>>>>>>> suggestion made by Dmitry in the above reply I think this >>>>>>>>>>>>>>>>> will come into >>>>>>>>>>>>>>>>> the picture. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>>> GayanD >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Tue, Aug 12, 2014 at 2:27 PM, Udara Rathnayake < >>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Gayan, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> See my comment in-line. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Tue, Aug 12, 2014 at 1:54 PM, Gayan Dhanushka < >>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi all, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> We have identified that the events in the doc attached >>>>>>>>>>>>>>>>>>> herewith are the events which are triggered within each >>>>>>>>>>>>>>>>>>> page. While some of >>>>>>>>>>>>>>>>>>> them are already published, some of them needs to be >>>>>>>>>>>>>>>>>>> published to the >>>>>>>>>>>>>>>>>>> social component in order to enhance the user experience >>>>>>>>>>>>>>>>>>> and collaboration. >>>>>>>>>>>>>>>>>>> While doing this we have encountered some issues and some >>>>>>>>>>>>>>>>>>> resolutions are >>>>>>>>>>>>>>>>>>> proposed to overcome those issues. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> *Problem*: There is no way to track whether a certain >>>>>>>>>>>>>>>>>>> build or a deployment instance triggered by someone is >>>>>>>>>>>>>>>>>>> completed.(No >>>>>>>>>>>>>>>>>>> association between start and finish events for a certain >>>>>>>>>>>>>>>>>>> instance). There >>>>>>>>>>>>>>>>>>> is no way to represent an ongoing process. (e.g. >>>>>>>>>>>>>>>>>>> application creation in >>>>>>>>>>>>>>>>>>> progress, build is in progress etc.) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Here we have to think about the user experience. >>>>>>>>>>>>>>>>>> IMO the user who triggered the build only interested to >>>>>>>>>>>>>>>>>> see the progress of that particular build, others may be >>>>>>>>>>>>>>>>>> interested to see >>>>>>>>>>>>>>>>>> the start and the end but not the progress. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> WDYT? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> The same problem would be applied to any scenario where >>>>>>>>>>>>>>>>>>> it takes some time for a certain event to finish and app >>>>>>>>>>>>>>>>>>> factory needs to >>>>>>>>>>>>>>>>>>> capture both start and completion events related to a >>>>>>>>>>>>>>>>>>> particular instance. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> *Solution* : Use a UUID to track events which takes >>>>>>>>>>>>>>>>>>> time to complete >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Publishing both start and complete events with the same >>>>>>>>>>>>>>>>>>> UUID as a event property would solve the problem. Then by >>>>>>>>>>>>>>>>>>> looking at the >>>>>>>>>>>>>>>>>>> event content we are able to find whether there is a >>>>>>>>>>>>>>>>>>> completion event for a >>>>>>>>>>>>>>>>>>> certain start event. This would be a global thing so the >>>>>>>>>>>>>>>>>>> notification wall >>>>>>>>>>>>>>>>>>> logic can be written in such a manner that we need to have >>>>>>>>>>>>>>>>>>> a look at only >>>>>>>>>>>>>>>>>>> the UUID. If we use different mechanisms for tracking start >>>>>>>>>>>>>>>>>>> and completion >>>>>>>>>>>>>>>>>>> events of different events the notification wall logic >>>>>>>>>>>>>>>>>>> would be more >>>>>>>>>>>>>>>>>>> complex when filtering out the events >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Your thoughts are welcome. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> [1] https://redmine.wso2.com/issues/3065 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>>>>> GayanD >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> Gayan Dhanuska >>>>>>>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>>>>>>> http://wso2.com/ >>>>>>>>>>>>>>>>>>> Lean Enterprise Middleware >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Mobile >>>>>>>>>>>>>>>>>>> 071 666 2327 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Office >>>>>>>>>>>>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>>>>>>>>>>>> Fax : 94 11 214 5300 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> *Udara Rathnayake* >>>>>>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>>>>>> WSO2 Inc. : http://wso2.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Mobile : +94 772207239 >>>>>>>>>>>>>>>>>> Twitter : http://twitter.com/udarakr >>>>>>>>>>>>>>>>>> Blog : http://udarakr.blogspot.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> Gayan Dhanuska >>>>>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>>>>> http://wso2.com/ >>>>>>>>>>>>>>>>> Lean Enterprise Middleware >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Mobile >>>>>>>>>>>>>>>>> 071 666 2327 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Office >>>>>>>>>>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>>>>>>>>>> Fax : 94 11 214 5300 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Dmitry Sotnikov >>>>>>>>>>>>>>>> VP of Cloud; WSO2, Inc.; http://wso2.com/ >>>>>>>>>>>>>>>> email: [email protected]; cell: +1.949.303.9653 >>>>>>>>>>>>>>>> ; Skype: DSotnikov >>>>>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> <http://wso2.com/events/> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Manjula Rathnayaka >>>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>>> WSO2, Inc. >>>>>>>>>>>>>>> Mobile:+94 77 743 1987 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Gayan Dhanuska >>>>>>>>>>>>>> Software Engineer >>>>>>>>>>>>>> http://wso2.com/ >>>>>>>>>>>>>> Lean Enterprise Middleware >>>>>>>>>>>>>> >>>>>>>>>>>>>> Mobile >>>>>>>>>>>>>> 071 666 2327 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Office >>>>>>>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>>>>>>> Fax : 94 11 214 5300 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>>> [email protected] >>>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Dimuthu Leelarathne >>>>>>>>>>>>> Architect & Product Lead of App Factory >>>>>>>>>>>>> >>>>>>>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>>>>>>> email: [email protected] >>>>>>>>>>>>> Mobile : 0773661935 >>>>>>>>>>>>> >>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> *Anuruddha Premalal* >>>>>>>>>>>> Software Eng. | WSO2 Inc. >>>>>>>>>>>> Mobile : +94710461070 >>>>>>>>>>>> Web site : www.regilandvalley.com >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Architecture mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Dimuthu Leelarathne >>>>>>>>>>> Architect & Product Lead of App Factory >>>>>>>>>>> >>>>>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>>>>> email: [email protected] >>>>>>>>>>> Mobile : 0773661935 >>>>>>>>>>> >>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Architecture mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Gayan Dhanuska >>>>>>>>>> Software Engineer >>>>>>>>>> http://wso2.com/ >>>>>>>>>> Lean Enterprise Middleware >>>>>>>>>> >>>>>>>>>> Mobile >>>>>>>>>> 071 666 2327 >>>>>>>>>> >>>>>>>>>> Office >>>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>>> Fax : 94 11 214 5300 >>>>>>>>>> >>>>>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Gayan Dhanuska >>>>>>>>> Software Engineer >>>>>>>>> http://wso2.com/ >>>>>>>>> Lean Enterprise Middleware >>>>>>>>> >>>>>>>>> Mobile >>>>>>>>> 071 666 2327 >>>>>>>>> >>>>>>>>> Office >>>>>>>>> Tel : 94 11 214 5345 >>>>>>>>> Fax : 94 11 214 5300 >>>>>>>>> >>>>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Architecture mailing list >>>>>>>>> [email protected] >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Dimuthu Leelarathne >>>>>>>> Architect & Product Lead of App Factory >>>>>>>> >>>>>>>> WSO2, Inc. (http://wso2.com) >>>>>>>> email: [email protected] >>>>>>>> Mobile : 0773661935 >>>>>>>> >>>>>>>> Lean . Enterprise . Middleware >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> [email protected] >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Gayan Dhanuska >>>>>>> Software Engineer >>>>>>> http://wso2.com/ >>>>>>> Lean Enterprise Middleware >>>>>>> >>>>>>> Mobile >>>>>>> 071 666 2327 >>>>>>> >>>>>>> Office >>>>>>> Tel : 94 11 214 5345 >>>>>>> Fax : 94 11 214 5300 >>>>>>> >>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Dimuthu Leelarathne >>>>>> Architect & Product Lead of App Factory >>>>>> >>>>>> WSO2, Inc. (http://wso2.com) >>>>>> email: [email protected] >>>>>> Mobile : 0773661935 >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Gayan Dhanuska >>>>> Software Engineer >>>>> http://wso2.com/ >>>>> Lean Enterprise Middleware >>>>> >>>>> Mobile >>>>> 071 666 2327 >>>>> >>>>> Office >>>>> Tel : 94 11 214 5345 >>>>> Fax : 94 11 214 5300 >>>>> >>>>> Twitter : https://twitter.com/gayanlggd >>>>> >>>> >>>> >>>> >>>> -- >>>> Dmitry Sotnikov >>>> VP of Cloud; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov >>>> Lean . Enterprise . Middleware >>>> >>>> <http://wso2.com/events/> >>>> >>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Architect & Product Lead of App Factory >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile : 0773661935 >>> >>> Lean . Enterprise . Middleware >>> >> > > > -- > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ <http://manisha-eleperuma.blogspot.com/>* *mobile: +94 71 8279777*
Events to be published to App Factory wall_Sep3.ods
Description: application/vnd.oasis.opendocument.spreadsheet
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
