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 <asanthathil...@gmail.com> 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 <cham...@wso2.com> > 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 < >> asanthathil...@gmail.com> 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 >>> Dev@wso2.org >>> 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/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
