Dynamic Runtime Community Meeting: Difference between revisions
From Modelado Foundation
imported>WilliamFeiereisen No edit summary |
imported>WilliamFeiereisen No edit summary |
||
| Line 1: | Line 1: | ||
Join us July 25-26, 2017 in the | Join us July 25-26, 2017 in the Washington DC Area | ||
Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. | Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. We are going to hold a workshop in the Washington DC area in late July that will bring people together to discuss common experiences | ||
We foresee a 2-day agenda in three parts | |||
1) Retrospectives from several projects on what we | |||
learned and how it applies to each application domain. 1/2 day: | |||
2)talks on the common elements that have been learned among the projects | |||
and 1/2 day | |||
3) an open session that defines a list of topics for | |||
common community work for the next year or two. This can also be a | |||
blueprint for federal managers to use as RFP material. | |||
Revision as of 20:51, May 22, 2017
Join us July 25-26, 2017 in the Washington DC Area
Several computing communities have recognized a common need for dynamic runtimes to support our future computing infrastructure. Having arisen from common needs, but developed in separate application communities we can learn from our experiences and build a common community. We are going to hold a workshop in the Washington DC area in late July that will bring people together to discuss common experiences
We foresee a 2-day agenda in three parts
1) Retrospectives from several projects on what we learned and how it applies to each application domain. 1/2 day:
2)talks on the common elements that have been learned among the projects and 1/2 day
3) an open session that defines a list of topics for common community work for the next year or two. This can also be a blueprint for federal managers to use as RFP material.