Status: Draft/Planning

Features

Parser

Infer and Write in BNF Cython's Grammar

1-4 days

|| Create Cython's Parser Actions: Python has ~50 action methods of about ~15 lines of code I takes something like 1.5 h to test and implement a new action I assume that will be ~40/30 rules: 60 h of work, that is working for 6h a day ...

best:7.5 worst:10 days

AST

Generate AST tree structure

1 days

Extend basic python AST with CDefs

3 days

Match AST tree structure with the existing Expr Tree

4-10 days

FlowGraph

Create FlowGraph Structure

1 days

Create Modifiers

1 days

Schedule

May

Week 1

Stories

Effort

May 26

Students begin coding for their GSoC projects

June

2 - 7 Week 2

Parser

9 - 14 Week 3

Parser / AST

16 - 21 Week 4

AST

23 - 28 Week 5

AST

June 12

Parser working

July

30 - 5 Week 6

AST

7 - 12 Week 7

AST/ Flow Graph / MidTerm Evaluation

14 - 19 Week 8

Flow Graph

21 - 26 Week 9

Flow Graph

28 - 2 Week 10

Flow Graph

July 7

Mentors and students can begin submitting mid-term evaluations

July 14

Mid-term evaluations deadline

August

4 - 9 Week 11

Flow Graph

11 - 16 Week 12

Write Documentation

11

Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc

18

Firm 'pencils down' date. Mentors, students and organization administrators can being submitting final evaluations to Google.

Summary

FabrizioM/soc2008/Schedule (last edited 2009-03-01 01:02:24 by localhost)