I like the idea of making the version that the developer is concentrating on, the front and center.
I am still a little struggling with the scenarios and who see what when. Can we create a set of mockups for the scenarios and personas? That would make things easier to understand and figure out how intuitive these are. We have a few basic stories told step-by-step, and I think we also identified two variations (several people working on small patches for the same version, and also someone working for a long time on a big change/high impact change). Can we just create a document or email that goes through these scenarios for the person step-by-step and add a mockup/screenshot of what the user sees on each step and what she clicks? If we get that, we will be able to quickly see which information/controls are missing and which are excessive. Thoughts? I am sorry to be asking for that. This is the trickiest part in App Factory, so it is hard to do it right and not get users confused. Yet, every customer will have to go through this screen - so it would be good if we have a higher percentage of people successfully "get it" - even if they are not super-experienced. Dmitry On Sun, Apr 27, 2014 at 9:16 AM, Shiroshica Kulatilake <[email protected]>wrote: > > > > On Sat, Apr 26, 2014 at 1:37 PM, Dimuthu Leelarathne <[email protected]>wrote: > >> Hi all, >> >> IMO, no need to give two filters, because at a given time a developer is >> concentrating on one version only - so he wants to see the status of master >> and fork of this particular version. There should be one filter for both >> master and fork. So, there should be one filter and if the developer >> select "2.0.0" from this filter, we have to show the status of master's >> 2.0.0 and the fork's 2.0.0. >> > > > +1 > > >> >> thanks, >> dimuthu >> >> >> On Sat, Apr 26, 2014 at 7:04 AM, Shiroshica Kulatilake <[email protected]>wrote: >> >>> Hi, >>> >>> Question based on the 3rd image >>> >>> So would a user want to see the controls for trunk version of the master >>> repo and version 1.0.0 of the forked repository ? >>> >>> Meaning should we give different filter options for master and fork >>> repos or give one filter option for both and show both the master and >>> forked repo of a selected version - if no fork exists then it will be empty. >>> >>> Thank you, >>> Shiro >>> >>> >>> On Fri, Apr 25, 2014 at 3:49 PM, Chanaka Jayasena <[email protected]>wrote: >>> >>>> Dimuthu, I captured your idea with the new images I am sending. We have >>>> to keep users selection of repository version in a cookie or local storage. >>>> Also I made the changes Harsha pointed out. >>>> >>>> thanks, >>>> Chanaka >>>> >>>> >>>> On Fri, Apr 25, 2014 at 8:29 AM, Dimuthu Leelarathne <[email protected] >>>> > wrote: >>>> >>>>> Hi all, >>>>> >>>>> +1 for Harsha's suggestions. >>>>> >>>>> In addition, I have a drastic suggestion. With a lot of branches this >>>>> UI will be cluttered. Therefore I have a proposal that I has been working >>>>> on my head. What if we show only a single version on this page? >>>>> >>>>> We give a drop down with all the versions. And the user to select a >>>>> version that he is interested in. After selecting the version the same >>>>> information will be shown. This idea came after I started thinking about >>>>> the user stories as Dmitry suggested. >>>>> >>>>> Bottom line is at any given time, a developer will only be >>>>> concentrating on one version of the application. Think of our use case as >>>>> developers. This will eliminate the information overload. >>>>> >>>>> So additional work is only a drop down for selecting the version but >>>>> rest of the things stays the same. WDYT? >>>>> >>>>> thanks, >>>>> dimuthu >>>>> >>>>> >>>>> On Fri, Apr 25, 2014 at 8:14 AM, Harsha Thirimanna >>>>> <[email protected]>wrote: >>>>> >>>>>> Hi Chanaka, >>>>>> >>>>>> 1. This git command help text should come with each and every >>>>>> personal repository version, not with master repositories. >>>>>> 2. Same style should use like "successful" to "Deployed" under >>>>>> deployment column. >>>>>> 3. Instead of using highlighted color to forked repository version >>>>>> record, keep it as same as others. But put very clear separater in >>>>>> between >>>>>> master and forked repositories. >>>>>> >>>>>> >>>>>> I feel other changes are very cool. >>>>>> >>>>>> thanks >>>>>> >>>>>> >>>>>> *Harsha Thirimanna* >>>>>> >>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>> * <http://www.apache.org/>* >>>>>> * email: **[email protected]* <[email protected]>* cell: +94 71 5186770* >>>>>> * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>* >>>>>> *harshathirimann linked-in: **http: >>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122 >>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>* >>>>>> >>>>>> *Lean . Enterprise . Middleware* >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Apr 25, 2014 at 7:56 AM, Chanaka Jayasena >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> Harsha and I was discussing about the improvements that can be done >>>>>>> to the UI base on previous Usability reviews. We came up with the >>>>>>> following >>>>>>> two screens. I am working with Harsha with the changes. >>>>>>> >>>>>>> thanks, >>>>>>> Chanaka >>>>>>> >>>>>>> -- >>>>>>> Chanaka Jayasena >>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >>>>>>> email: [email protected]; cell: +94 77 785 5565 >>>>>>> blog: http://chanaka3d.blogspot.com >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Dimuthu Leelarathne >>>>> Architect & Product Lead of App Factory >>>>> >>>>> WSO2, Inc. (http://wso2.com) >>>>> email: [email protected] >>>>> Mobile : 0773661935 >>>>> >>>>> Lean . Enterprise . Middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> Chanaka Jayasena >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >>>> email: [email protected]; cell: +94 77 785 5565 >>>> blog: http://chanaka3d.blogspot.com >>>> >>> >>> >>> >>> -- >>> Shiroshica Kulatilake >>> >>> Architect, >>> WSO2, Inc. http://wso2.com/ >>> Phone: +94 776523867 >>> >> >> >> >> -- >> Dimuthu Leelarathne >> Architect & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> > > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > -- 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
