Dear all, Pete would like to have a fairly complete draft of 5_SoftwareStack by Tuesday evening (yes, tomorrow). Make sure that your components have some milestones in the Deliverables section. Don't go overboard with it; one-two milestones per year for the first three years for each component will be plenty, we mostly want them there so that the reviewers can't complain about a lack of them. Besides, Pete wants the whole part 5 trimmed down to 20 pages (it's currently at 34, and a number of things are still missing, so, short of using a font size 6, it will take a ruthless trimmer to squeeze it; any volunteers?). Speaking of missing things, here's what I noticed after a quick browse through the document: Operating System and Runtime - Linux Integration (Kamil): incomplete Deliverables - Advanced OS Functionality (Ron): missing Deliverables, Collaboration, Support - Qthreads (Ron): missing - I/O Forwarding (Kamil): missing Deliverables, Support - Simulation (Ron): missing Tools - Measurement and Analysis (John, Bronis, Al): complete? (other than the milestones) - Underlying Infrastructure (Bronis, John, Jeff): complete? (other than the milestones) - Tool Integration (Bronis, Al, John, Jeff): mostly complete Programming Models - Advanced Languages (Barb, John): complete? (the deliverables almost read like milestones) - MPI (Rajeev, Rusty): missing Deliverables, Collaboration, Support - Plum (Pavan): missing - Resilience and FT (Al): complete (it even has actual milestones -- for five years!) Data - In-Situ Analysis (Jim, Hank): complete - Checkpoint (Rob): missing Deliverables, Collaboration, Support - Hierarchical Storage (Lee): incomplete Deliverables - I/O Libraries (Gary): complete? - Low Level Storage (Galen): incomplete Deliverables - Metadata (Rob): incomplete Deliverables and Support, missing Collaboration Math (Jack, Mike) - Used a different formula than the rest (one giant component spanning over four pages, with multiple tasks), but other than the milestones, complete? Note: I made some formatting changes to the section headers in *all* component.tex files, so be sure to update your checked out SVN tree before modifying anything to avoid merging conflicts down the road... There is now a top-level Makefile in "5_SoftwareStack" that can be used to build the whole part 5. Feel free to change the order of groups/components as it's currently mostly alphabetical; the relevant files are software-stack.tex (for the top level) and group.tex in each group subdirectory. Kamil