Hi Niranjan, Have we finalized the approach on adopting the secondary user store? If so where was it discussed?
Regards, Dilshan On Wed, May 21, 2014 at 12:42 PM, Krishanthi Samarasinghe < [email protected]> wrote: > Hi all, > > We are going to escape the license agreement from BYOD as well, if user > requires. > > 1. +1 for doing these changes in next release without doing changes in > last minute. Because we have to do these changes in iOS, Android as well as > in server side too. > 2. + 1 for keeping license agreement for BYOD without letting user to > violate the company policies. > 3. + 1 for skipping license through configuration and disable it for > entire tenant itself. > 4. +1 for giving guide when entering server address. > > @Shan, > > What do you think about these changes? > > Thank you. > > > > > On Tue, May 20, 2014 at 9:23 PM, Niranjan Karunanandham <[email protected] > > wrote: > >> Hi all, >> >> I agree with Dilshan. We don't need the license screen for COPE but we >> need it for BYOD. It is a must to show the license whether the user reads >> it or not. Also having features like passing new values from the server >> requires changes and we need to consider whether we need to implement it as >> we have a lot to do. There is a most important feature that it was agreed >> to go with release which is *Secondary User Store*. This is a must if we >> need to say that we support full tenancy and I think we need to put >> resources in that. I have put that in the white board. >> >> Also if there is a change which can effect both Android and iOS like the >> text fields changing or flow change then we should stop having two people >> implement this. If a person is going to do it then that person should do it >> in iOS also and it needs to be documented as it has to be given to the >> documentation team. Last minute one person doing it, is not correct. >> Corresponding branches need to be created in the iOS and android. Only when >> both are completed and tested should it be merged to the develop. Because >> we put a lot of focus and forget to implement it in iOS. >> >> Therefore if we going forward with this please create it as a separate >> branch so that the android branch is only merged* if and only if *the >> iOS is also completed. >> >> P.S.: Please create corresponding JIRAs for everything. >> >> Regards, >> Nira >> >> >> >> On Tue, May 20, 2014 at 8:38 PM, Harshan Liyanage <[email protected]>wrote: >> >>> Hi, >>> >>> +1 for skipping license through config. >>> >>> Thanks, >>> >>> Best Regards, >>> >>> Lakshitha Harshan >>> Software Engineer >>> Mobile: *+94724423048* >>> Email: [email protected] >>> Blog : http://harshanliyanage.blogspot.com/ >>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>> lean.enterprise.middleware. >>> >>> >>> On Tue, May 20, 2014 at 8:32 PM, Dilshan Edirisuriya >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I believe license itself needs to be there for BYOD devices unless >>>> tenant admin wants to skip that through a configuration and disable it for >>>> entire tenant itself. What is the purpose of having the license if it can >>>> be skipped? That means BYOD devices can register without it and violate the >>>> company policies? >>>> >>>> Regards, >>>> >>>> Dilshan >>>> >>>> >>>> On Tue, May 20, 2014 at 8:16 PM, Harshan Liyanage <[email protected]>wrote: >>>> >>>>> Hi Chan, >>>>> >>>>> It's not about showing the license for all users. This is about >>>>> bypassing the license screen by* choosing bypass option* if the user >>>>> wants to do so. >>>>> >>>>> Thanks, >>>>> >>>>> Best Regards, >>>>> >>>>> Lakshitha Harshan >>>>> Software Engineer >>>>> Mobile: *+94724423048* >>>>> Email: [email protected] >>>>> Blog : http://harshanliyanage.blogspot.com/ >>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>>>> lean.enterprise.middleware. >>>>> >>>>> >>>>> On Tue, May 20, 2014 at 8:08 PM, Chan <[email protected]> wrote: >>>>> >>>>>> +1 for changing the text of fields for usability. A small concern on >>>>>> Kasun's comment about License agreement - I thought we all agreed that >>>>>> there is no license agreement for COPE devices. Did this change? >>>>>> >>>>>> Cheers~ >>>>>> >>>>>> >>>>>> On Tue, May 20, 2014 at 5:15 PM, Harshan Liyanage >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Please find my comments inline. >>>>>>> >>>>>>> 1. How do the user know the format to type in the domain. What if he >>>>>>> type "http://abc.com";? I think we should guide him in the screen as >>>>>>> it was before. And the title "MDM Server" does not sound right to me >>>>>>> because we all agreed on the single name "EMM" and why do we deviate >>>>>>> from >>>>>>> that in Agent? >>>>>>> >>>>>>> I think we should guide the user as before. >>>>>>> >>>>>>> 2. +1 for this change, but still I feel "Domain" sounds clear than >>>>>>> "Group". >>>>>>> >>>>>>> I think we should add a help screen to let the users to know what >>>>>>> is meant by these fields (domain/group). So then there won't be any >>>>>>> clarification issues. >>>>>>> >>>>>>> 2. -1 for this change. I think all the users should see the license >>>>>>> agreement. Otherwise this can be an issue later (Ex:If his/her phone get >>>>>>> wipes off for some reason, he might complain about it negatively). I >>>>>>> don't >>>>>>> see any complication in showing the agreement because they can simply >>>>>>> accept it and go ahead if they want. I think showing the agreement is >>>>>>> anyways better and safe in legal aspects as well. So I strongly -1 on >>>>>>> this >>>>>>> change. >>>>>>> >>>>>>> I also agree with Kasun. Users must know what the EMM client app is >>>>>>> capable of. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Best Regards, >>>>>>> >>>>>>> Lakshitha Harshan >>>>>>> Software Engineer >>>>>>> Mobile: *+94724423048* >>>>>>> Email: [email protected] >>>>>>> Blog : http://harshanliyanage.blogspot.com/ >>>>>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>>>>>> lean.enterprise.middleware. >>>>>>> >>>>>>> >>>>>>> On Tue, May 20, 2014 at 4:55 PM, Kasun Dananjaya Delgolla < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Krishanthi, >>>>>>>> >>>>>>>> Please find my comments on above options. >>>>>>>> >>>>>>>> 1. How do the user know the format to type in the domain. What if >>>>>>>> he type "http://abc.com";? I think we should guide him in the >>>>>>>> screen as it was before. And the title "MDM Server" does not sound >>>>>>>> right to >>>>>>>> me because we all agreed on the single name "EMM" and why do we deviate >>>>>>>> from that in Agent? >>>>>>>> >>>>>>>> 2. +1 for this change, but still I feel "Domain" sounds clear than >>>>>>>> "Group". >>>>>>>> >>>>>>>> Here are my comments on Improvements section: >>>>>>>> >>>>>>>> 1. +1 for this, these information should be sent be the server >>>>>>>> probably in SENDER_ID request and then we can show/bypass pin setting. >>>>>>>> >>>>>>>> 2. -1 for this change. I think all the users should see the license >>>>>>>> agreement. Otherwise this can be an issue later (Ex:If his/her phone >>>>>>>> get >>>>>>>> wipes off for some reason, he might complain about it negatively). I >>>>>>>> don't >>>>>>>> see any complication in showing the agreement because they can simply >>>>>>>> accept it and go ahead if they want. I think showing the agreement is >>>>>>>> anyways better and safe in legal aspects as well. So I strongly -1 on >>>>>>>> this >>>>>>>> change. >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> >>>>>>>> On Tue, May 20, 2014 at 4:00 PM, Krishanthi Samarasinghe < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Shan, >>>>>>>>> >>>>>>>>> As we discussed, we are going to do following changes: >>>>>>>>> >>>>>>>>> 1. Change the message in setting server IP screen. >>>>>>>>> Change from *Set your server address here to start registration, >>>>>>>>> i.e : www.abc.com <http://www.abc.com>"* to "*Set your MDM server >>>>>>>>> address"* >>>>>>>>> >>>>>>>>> 2. In login screen, currently we have inputs as following order: >>>>>>>>> i. Domain >>>>>>>>> ii. Username >>>>>>>>> iii Password >>>>>>>>> >>>>>>>>> We are going to change it as: >>>>>>>>> i. Username >>>>>>>>> ii. Password >>>>>>>>> iii. Group (We are using this for tenancy) >>>>>>>>> >>>>>>>>> *Note:* Here I have attached the server IP >>>>>>>>> screen(setServerIP.png) and the login screen(login.png). >>>>>>>>> >>>>>>>>> *Improvements:* >>>>>>>>> >>>>>>>>> 1. We should allow to add pin code, only for users who is able to >>>>>>>>> wipe the device. For that we(Android agent) need to get that >>>>>>>>> information >>>>>>>>> from the server side *after the login*, but *before completing >>>>>>>>> the registration*. Then there will be changes in both server side >>>>>>>>> and android agent. >>>>>>>>> >>>>>>>>> 2. We should allow user to do the registration even *without >>>>>>>>> seeing license agreement* if *he/she requires*. There cannot be >>>>>>>>> any screen between the registration and registration successful >>>>>>>>> screens. >>>>>>>>> For that we need to include a check box. We need to decide the screen >>>>>>>>> where >>>>>>>>> we have to add this. >>>>>>>>> >>>>>>>>> If we are going to implement this, since there are many logical >>>>>>>>> implementation based on the license agreement in Android Agent, we >>>>>>>>> have to >>>>>>>>> do a major change in Android Agent. >>>>>>>>> >>>>>>>>> Please let me know, if I have missed any point. >>>>>>>>> >>>>>>>>> Others opinions are welcome. Please give your comments to proceed >>>>>>>>> on this. >>>>>>>>> >>>>>>>>> Thank you. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best Regards, >>>>>>>>> Krishanthi Bhagya Samarasinghe >>>>>>>>> Senior Software engineer >>>>>>>>> >>>>>>>>> Mobile: +94 716028280 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Kasun Dananjaya Delgolla >>>>>>>> >>>>>>>> Software Engineer >>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>> lean.enterprise.middleware >>>>>>>> Tel: +94 11 214 5345 >>>>>>>> Fax: +94 11 2145300 >>>>>>>> Mob: + 94 777 997 850 >>>>>>>> Blog: http://kddcodingparadise.blogspot.com >>>>>>>> Linkedin: *http://lk.linkedin.com/in/kasundananjaya >>>>>>>> <http://lk.linkedin.com/in/kasundananjaya>* >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Chan (Dulitha Wijewantha) >>>>>> Software Engineer - Mobile Development >>>>>> WSO2Mobile >>>>>> Lean.Enterprise.Mobileware >>>>>> * ~Email [email protected] <[email protected]>* >>>>>> * ~Mobile +94712112165 <%2B94712112165>* >>>>>> * ~Website dulitha.me <http://dulitha.me>* >>>>>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>>>>> *~Github @dulichan <https://github.com/dulichan>* >>>>>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dilshan Edirisuriya >>>> Senior Software Engineer - WSO2 >>>> Mob: + 94 777878905 >>>> http://wso2.com/ >>>> >>> >>> >> >> >> -- >> >> *Niranjan Karunanandham* >> Senior Software Engineer - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> M: +94 777 749 661 <http:///> >> > > > > -- > Best Regards, > Krishanthi Bhagya Samarasinghe > Senior Software engineer > > Mobile: +94 716028280 > > -- Dilshan Edirisuriya Senior Software Engineer - WSO2 Mob: + 94 777878905 http://wso2.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
