Hi Tharindu,

I modified my project proposal[1] in google doc, as you suggested i added
function list which i am going to exposed to apis after modified the
content  i shared the doc to summer of code.
waiting for your feedback
[1]
https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing

Thanks,
Asantha

On Tue, Mar 22, 2016 at 8:16 PM, Asantha Thilina <[email protected]>
wrote:

> Hi Tharindu,
>
> thanks a lot for the feedbacks, sure i will modify the content of the
> proposal as suggested  and submit to google within today
>
> Thanks,
> Asantha
>
>
> On Wed, Mar 23, 2016 at 7:45 AM, Tharindu Edirisinghe <[email protected]>
> wrote:
>
>> Hi Asantha,
>>
>> I've added the latest proposal you've sent to google docs in [1]. As
>> Chamila suggested, can you list down the methods that you expose in the API
>> (public methods in the userstore manager) in the proposal so that it is
>> easy to understand the functionality of the userstore manager. Also it is
>> better to submit the proposal to google now and update later if any
>> modification is needed.
>>
>> [1]
>> https://docs.google.com/document/d/1xv7iB3VAUElvf1Cl3So0TSLCSjuZOS-IyT-Fy_1zl_c/edit?usp=sharing
>>
>> Thanks,
>> TharinduE
>>
>> On Mon, Mar 21, 2016 at 9:58 PM, Asantha Thilina <
>> [email protected]> wrote:
>>
>>> Hi Chamila,
>>>
>>> Thanks a lot for the feedback, sure i will update my proposal as you
>>> suggested
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Mar 21, 2016 at 9:18 AM, Chamila Wijayarathna <[email protected]>
>>> wrote:
>>>
>>>> Hi Asantha,
>>>>
>>>> Looks good, please talk with Tharindu also before submitting the
>>>> proposal. Even you submit your proposal, you can improve it until 25th.
>>>>
>>>> So if time permits, I would like to suggest you to add some details
>>>> about what are the APIs and functions you are going to expose after
>>>> developing this new user store manager, if you have already decided on
>>>> them. Since you may have went through the codes of existing user store
>>>> managers, you may already have an idea about what are the functions you
>>>> need to exposed to outside. So if can add at least few functions you are
>>>> going to expose with some details, it would make your proposal more
>>>> attractive. Also I would like to suggest you to add link of github repo
>>>> where you have started development. Also if you have written any blogs
>>>> related to the project, mongoDB, etc. please mention them also in your
>>>> proposal.
>>>>
>>>> Also I see some formatting issues and some dates has got repeated in
>>>> your timeline, hope you will correct the when submitting proposal at GSoC
>>>> site.
>>>>
>>>> Cheers!
>>>>
>>>> On Mon, Mar 21, 2016 at 9:18 PM, Asantha Thilina <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Chamila,
>>>>>
>>>>> Thanks a lot for your valuable feedback as you suggested i corrected
>>>>> my project proposal and here i attached my finalize project proposal
>>>>>
>>>>> expecting your feedback
>>>>>
>>>>> Thanks,
>>>>> Asantha
>>>>>
>>>>> On Mon, Mar 21, 2016 at 5:44 AM, Chamila Wijayarathna <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Hi Asantha,
>>>>>>
>>>>>> Thanks for sending your proposal. It seems to be in good shape, but I
>>>>>> would like to suggest few more improvements.
>>>>>>
>>>>>>    1.  You have mentioned you are implementing Custom User Store
>>>>>>    Manager by extending JDBCUserStoreManager. But actually you have to 
>>>>>> extend
>>>>>>    AbstractUserStoreManager. I think you have done this correctly in the 
>>>>>> code
>>>>>>    you sent previously. Please correct this.
>>>>>>    2. I think by custom user store manager, you have meant mongoDB
>>>>>>    user store manager you are planning to implement, in most places. Its
>>>>>>    better to mention specifically as MongoDBUserStoreManager than saying
>>>>>>    custom user store manager.
>>>>>>    3. You have mentioned about "Implement a proper encryption
>>>>>>    mechanism to overcome the security hauls in custom User store 
>>>>>> Manager.".
>>>>>>    Can you be more specific on what are the security holes you are 
>>>>>> talking
>>>>>>    about. AFAIK encryption mechanisms we are currently using are quite 
>>>>>> ok and
>>>>>>    if there are no any strong reasons, I suggest you to follow the 
>>>>>> existing
>>>>>>    mechanisms.
>>>>>>    4. It would be great if you can allocate 1-2 weeks for doing a
>>>>>>    small research on how other NoSQL databases such as CouchDB, Neo4j 
>>>>>> can be
>>>>>>    used to implement an user store in IS. By looking at your time line, I
>>>>>>    think it would be possible to allocate some time for this in the 2nd 
>>>>>> half
>>>>>>    of the programme. We can do this if time permits, but its better to 
>>>>>> mention
>>>>>>    it in your proposal as optional (I believe it would make the project 
>>>>>> more
>>>>>>    complete).
>>>>>>
>>>>>> Looking forward to see your proposal.
>>>>>>
>>>>>> Good Luck!
>>>>>>
>>>>>> On Mon, Mar 21, 2016 at 5:15 PM, Asantha Thilina <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> here  i attached my project proposal for GSOC 2016 Project 21  for
>>>>>>> your kind consideration,
>>>>>>> I kindly request your feedback and thought on it.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Asantha
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Dev mailing list
>>>>>>> [email protected]
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Chamila Dilshan Wijayarathna,*
>>>>>> Software Engineer
>>>>>> Mobile:(+94)788193620
>>>>>> WSO2 Inc., http://wso2.com/
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Chamila Dilshan Wijayarathna,*
>>>> Software Engineer
>>>> Mobile:(+94)788193620
>>>> WSO2 Inc., http://wso2.com/
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Tharindu Edirisinghe
>> Software Engineer | WSO2 Inc
>> Platform Security Team
>> Blog : tharindue.blogspot.com
>> mobile : +94 775181586
>>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to