So finally after long discussion with some senior guys in silverstripe (thanks to them) now its clear in my mind that what actually I have to do during my project. somehow I have distracted in my first week of coding and went in wrong direction. Hopefully you have read my last blog "Problems with composer" actually those prediction were almost wrong and Andrew shown me right picture about Composer. So what I did in first 2 weeks could be very easily done by using Composer itself.
      But unfortunate thing is that I have lost almost 3 weeks before realizing facts and now I have to finish my job in only 4 weeks before mid-term evaluation dead-line.
      In my Gsoc proposal I have planned to finish following tasks before mid-term evaluation.

➢ Redesign Search page of module.
➢ Redesign detailed modules/widgets download page.
➢ Write/improve algorithm & code for
   (1) Integration of ss.org system with module repositories.
   (2) Automatic creation of detailed module download pages.
   (3) Improving modules packaging ability.
   (4) Handling data of subversion.
   (5) Cron jobs (For automatic updates).
➢ Test with some dummy data.
➢ Document the work.

Now due to lack of time I will focus only on following task.

Pahse-1 : Integration of ss.org system with module repositories and creating cron job for automatic updates (6 Jun to 17 Jun).

1. This task consist integration of silverstripe with module repository, fetching module information using composer class and storing them in database for future use. 
2. For implementing this we will take URL of repository as input from users using simple silverstripe Form. This URL will be pass to one of composer class "VcsRepository" and then we will be able to fetch all the package information from module repository. 
3. For cron job we will create sub-class of build-task and so it will update our database Hourly or Daily basis .
4. write Unit-Test for all these tasks.

Phase-2 : Creating Detailed pages of module (18 Jun to 27 Jun). 

1. Most probably It will be an automated task which will create unpublished pages of modules with information stored in database and a link for download master branch.
2.  writing tests for above.

Phase-3 : Handling data of subversions, creating their packages and integrating with module pages, creating a simple module search page (28 Jun to 9 July)

1. Every module may have different versions available for download handling them and providing a download link on module pages will be primary task for this phase . 
2. composer package has a "getDistType" and "getDistUrl" methods which returns url of packages according to type of branch and creates archives for us so we can get help from composer itself for implementing above task.
3. writing tests for above .

 Documentation of work done in all above phases (10 & 11 July ).

I hope this post will help you to watch my progress. for any query or suggestion please comment on this post or mail me personally.
  
Thanks for your time .