| Line 22: | Line 22: | ||
===A rough timeline for your progress=== | ===A rough timeline for your progress=== | ||
* **21 April - 1 May**: Read the code of shumgrepper and datagrepper. (Maybe fix some small bug in passing) | |||
* **1 May - 10 May**: Make the blueprint (such as which way to use to get the connect between shumgrepper , the name of the method to use …) of the project. | |||
* **1 May - 15 June**: Code, finish the basic function of the project. (user can get json information of md5sum, sha1sum and sha512sum) | |||
* **16 June - 25 June**: Review the code , find bug and write a mid-term evaluations. | |||
* **25 June - 30 July**: Imporve the function of the project, fix the bug and enhance performance. | |||
* **30 July - 18 August**: Make some test and finish the documents of the project. | |||
===Any other details you feel we should consider=== | ===Any other details you feel we should consider=== | ||
===Have you communicated with a potential mentor? If so, who?=== | ===Have you communicated with a potential mentor? If so, who?=== | ||
Revision as of 16:24, 16 March 2014
Proposal
Please describe your proposal in detail. Include:
An overview of your proposal
The need you believe it fulfills
Any relevant experience you have
How you intend to implement your proposal
Shumgrepper is a new project that is similar with datagrepper. So it could fork from Datagrepper. Shumgrepper is a project based on Flask, SQLAlchemy and summershum. Datagrepper is a project based on Flask, SQLAlchemy and fedmsg.
I think the view of datagrepper and shumgrepper is similar, so I think the modify for view is easy, just change the word that returned.
Summershum and shumgrepper can be connected with each other in database and Python data. For the query that has been generated, it’s okay just to return the database query from the database. As for the old data, shumgrepper should use summershum modules and datagrepper to download the packages. Then calculate md5sum, sha1sum and sha512sum of the file, return to user in json and store it in database.
I looked carefully at the code of summershum. There has been a model of database in summershum. I could use this model in shumgrepper which will make the connection between summershum and shumgrepper smooth.
A rough timeline for your progress
- **21 April - 1 May**: Read the code of shumgrepper and datagrepper. (Maybe fix some small bug in passing)
- **1 May - 10 May**: Make the blueprint (such as which way to use to get the connect between shumgrepper , the name of the method to use …) of the project.
- **1 May - 15 June**: Code, finish the basic function of the project. (user can get json information of md5sum, sha1sum and sha512sum)
- **16 June - 25 June**: Review the code , find bug and write a mid-term evaluations.
- **25 June - 30 July**: Imporve the function of the project, fix the bug and enhance performance.
- **30 July - 18 August**: Make some test and finish the documents of the project.