| 22 | | ||Community bounding period || Get GRASS GIS and PDAL to build from source. || || |
| 23 | | ||'''Let the summer begin''' || || || |
| 24 | | ||MAY 30 - JUNE 2 || || || |
| 25 | | ||JUNE 5 - JUNE 9 || || || |
| 26 | | ||JUNE 12 - 16 || || || |
| 27 | | ||JUNE 19 - 23 || || || |
| 28 | | ||JUNE 26 - 30 || || || |
| 29 | | ||'''First evaluations''' || || || |
| 30 | | ||JULY 3 - 14 || || || |
| 31 | | ||JULY 17 - 21 || || || |
| 32 | | ||JULY 24 - 28 || || || |
| | 22 | ||Community bonding period || Get GRASS GIS and PDAL to build from source. || || |
| | 23 | ||MAY 30 - JUNE 2 || Begin development of v.in.pdal, including Unit Test coverage. Unit test development will be parallel to software development. || || |
| | 24 | ||JUNE 5 - JUNE 9 || Complete basic functionality of v.in.pdal at the command line. Begin development of GUI support. Basic functionality entails import and export of .las files to and from GRASS vector maps. || || |
| | 25 | ||JUNE 12 - 16 || Complete GUI development for v.in.pdal. Identify edge and corner cases, add them to the testing data, and handle them in code. Begin vacation 15 June. || || |
| | 26 | ||JUNE 19 - 23 || Vacation. Unavailable all week. || || |
| | 27 | ||JUNE 26 - 30 || Vacation until 26 June. Complete First Evaluation. || || |
| | 28 | ||'''First evaluations''' || || || |
| | 29 | ||JULY 3 - 14 || || || |
| | 30 | ||JULY 17 - 21 || || || |
| | 31 | ||JULY 24 - 28 || || || |
