On 22 March 2012 20:53, Yauhen Klimovich <[email protected]> wrote: > Hi, everybody, students and mentors. >
Hi! > I am currently a student of Belarusian State University, department of > computer science, information management systems subdepartment, fifth year > of study. One of my yearly essays was Development of Automated language > identification tool of text. I am familiar with WordNet too. > You're familiar with WordNet? In what way? WordNet has been applied to many different domains, and I'd like to see you expand on this a little more. > I'm 22 years old, quickly adopting to new things and technologies, because I > have an experience of working in a team. I am interested in making our world > a little bit better. ;) > Tentative timeline > I know it's early, but could you consider putting part of your proposal in here? We can't help you with it if we haven't seen it. Your timeline needs a lot of work. I've left some comments to help you know how to improve the next version. > > April — May 19th > > Introduction to current state of the project, esp. ICF (including evaluating > performance) > > Comparing the current with DefaultSimilarity. Learn through coding ;) > > > May 20th - June 7th > > Learning project Voldemort, evaluating ability to use Lucene Score. > > Evaluation of all learned abilities. > I'm afraid that's not acceptable. May 20th is the start date for coding, all background learning should be completed by then. > > June 8th - June 30th > > Starting the realization of solution I and mentor expect to be the best. > > At the end of this period the solution should demonstrate first results. > > Writing java docs and to wiki, indeed. ;) > > > July 1st - July end > > Improving current state of solution. > This is not an activity, you're effectively saying '...stuff happens...' > End of write chapters of docs and wiki. At the end of the period code should > be ready to test. > > > August > > Test, get the code in order, clean it up, clear bug reports ;) > Testing is an ongoing activity, you should aim to test from the start of the project. > Merging, committing, pushing etc. > We haven't discussed how the projects will be developed, so there may be some merging involved at the end, but committing is an ongoing activity -- if your mentor hasn't seen work from you before the midterm, how can you pass? For the next draft of your timeline, you should keep in mind the GSoC timeline (http://www.google-melange.com/gsoc/events/google/gsoc2012), and try to break down your proposed activities by week. It may be acceptable to submit a fortnightly schedule, if that's more realistic, but a breakdown by month is just not informative enough. -- <Sefam> Are any of the mentors around? <jimregan> yes, they're the ones trolling you ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Dbp-spotlight-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbp-spotlight-users
