42 |
Short term |
Short term |
43 |
---------- |
---------- |
44 |
|
|
45 |
2003-06-05 - |
2003-06-17 - |
46 |
|
|
47 |
- write a PEG about GISP "killer" |
- write a PEG about implemented overlays |
48 |
- started looking GISP code |
which are implemented |
49 |
- possibly implement the "killer" based |
- important aspects: in addition to "standard" requirements, level of |
50 |
on native GISP's simulation code |
development process and the license are important |
51 |
|
|
52 |
|
|
53 |
============= |
============= |
54 |
Past: |
Past: |
55 |
============= |
============= |
56 |
|
|
57 |
|
2003-06-23 |
58 |
|
|
59 |
|
- Comments on Mikko's publication |
60 |
|
|
61 |
|
2003-06-05 - 2003-06-17 |
62 |
|
|
63 |
|
- write a PEG about GISP "killer" |
64 |
|
- started looking GISP code |
65 |
|
- possibly implement the "killer" based |
66 |
|
on native GISP's simulation code |
67 |
|
- POSTPONED |
68 |
|
- reason: too many (obvious) exploits |
69 |
|
|
70 |
2003-06-02 - 2003-06-05 |
2003-06-02 - 2003-06-05 |
71 |
- write a PEG about Storm/GISP simulation |
- write a PEG about Storm/GISP simulation |
72 |
- hypothesis and research problems/issues |
- hypothesis and research problems/issues |
73 |
- postponed |
- POSTPONED |
74 |
|
- reason: first we want to test GISP's level of development process, |
75 |
|
i.e., "maturity of the code" |
76 |
|
|
77 |
|
|
78 |
|
|
79 |
2003-05-30 |
2003-05-30 |
80 |
|
|