Dynamic Runtime Community Meeting - Revision history

imported>WilliamFeiereisen at 22:26, May 22, 2017

2017-05-22T22:26:14Z

← Older revision		Revision as of 22:26, May 22, 2017
Line 4:		Line 4:

	We foresee a 2-day agenda in four parts		We foresee a 2-day agenda in four parts

			Agenda:

	'''1) Retrospectives from several projects on what we		'''1) Retrospectives from several projects on what we

imported>WilliamFeiereisen at 21:54, May 22, 2017

2017-05-22T21:54:21Z

← Older revision		Revision as of 21:54, May 22, 2017
Line 1:		Line 1:
	Join us July 25-26, 2017 in the Washington DC Area		'''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		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

imported>WilliamFeiereisen at 21:54, May 22, 2017

2017-05-22T21:54:03Z

← Older revision		Revision as of 21:54, May 22, 2017
Line 8:		Line 8:
	learned and how it applies to each application domain. Focus on application experience: 1/2 day'''		learned and how it applies to each application domain. Focus on application experience: 1/2 day'''

	9:00am - 12:00pm		July 25, 9:00am - 12:00pm

	'''2) Talks on the common elements that have been learned among the projects: 1/2 day'''		'''2) Talks on the common elements that have been learned among the projects: 1/2 day'''

	1:00pm - 5:00pm		July 25, 1:00pm - 5:00pm

	'''3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours'''		'''3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours'''

	9:00am - 11:am		July 26, 9:00am - 11:am

	'''4) an open session that defines a list of topics for		'''4) an open session that defines a list of topics for
Line 22:		Line 22:
	blueprint for federal managers to use as RFP material.: 1/2 day'''		blueprint for federal managers to use as RFP material.: 1/2 day'''

	11:00am - 4:00pm with a beak for lunch		July 26, 11:00am - 4:00pm with a beak for lunch

imported>WilliamFeiereisen at 21:53, May 22, 2017

2017-05-22T21:53:20Z

← Older revision		Revision as of 21:53, May 22, 2017
Line 5:		Line 5:
	We foresee a 2-day agenda in four parts		We foresee a 2-day agenda in four parts

	1) Retrospectives from several projects on what we		'''1) Retrospectives from several projects on what we
	learned and how it applies to each application domain. Focus on application experience: 1/2 day		learned and how it applies to each application domain. Focus on application experience: 1/2 day'''

	9:00am - 12:00pm		9:00am - 12:00pm

	2) Talks on the common elements that have been learned among the projects: 1/2 day		'''2) Talks on the common elements that have been learned among the projects: 1/2 day'''

	1:00pm - 5:00pm		1:00pm - 5:00pm

	3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours		'''3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours'''

	9:00am - 11:am		9:00am - 11:am

	4) an open session that defines a list of topics for		'''4) an open session that defines a list of topics for
	common community work for the next year or two. This can also be a		common community work for the next year or two. This can also be a
	blueprint for federal managers to use as RFP material.: 1/2 day		blueprint for federal managers to use as RFP material.: 1/2 day'''

	11:00am - 4:00pm with a beak for lunch		11:00am - 4:00pm with a beak for lunch

imported>WilliamFeiereisen at 21:45, May 22, 2017

2017-05-22T21:45:03Z

← Older revision		Revision as of 21:45, May 22, 2017
Line 3:		Line 3:
	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		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		We foresee a 2-day agenda in four parts

	1) Retrospectives from several projects on what we		1) Retrospectives from several projects on what we
	learned and how it applies to each application domain. 1/2 day:		learned and how it applies to each application domain. Focus on application experience: 1/2 day

	~~2)talks on the common elements that have been learned among the projects~~		9:00am - 12:00pm
	~~and 1/2 day~~

	3) an open session that defines a list of topics for		2) Talks on the common elements that have been learned among the projects: 1/2 day

			1:00pm - 5:00pm

			3) A short session on the characteristics of prospective hardware that will need to be managed: 2 hours

			9:00am - 11:am

			4) an open session that defines a list of topics for
	common community work for the next year or two. This can also be a		common community work for the next year or two. This can also be a
	blueprint for federal managers to use as RFP material.		blueprint for federal managers to use as RFP material.: 1/2 day

			11:00am - 4:00pm with a beak for lunch

imported>WilliamFeiereisen at 20:51, May 22, 2017

2017-05-22T20:51:22Z

← Older revision		Revision as of 20:51, May 22, 2017
Line 1:		Line 1:
	Join us July 25-26, 2017 in the ~~San Francisco Bay~~ Area		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.

imported>WilliamFeiereisen at 10:56, May 11, 2017

2017-05-11T10:56:56Z

← Older revision		Revision as of 10:56, May 11, 2017
Line 1:		Line 1:
	Join us July 25-26, 2017 in the San Francisco Bay Area		Join us July 25-26, 2017 in the San Francisco Bay 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 common		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.

imported>WilliamFeiereisen at 10:55, May 11, 2017

2017-05-11T10:55:51Z

← Older revision		Revision as of 10:55, May 11, 2017
Line 1:		Line 1:
	~~Dynamic Runtime Community Meeting~~		Join us July 25-26, 2017 in the San Francisco Bay Area

	~~Join us July 25-26~~, ~~2017~~ in ~~the San Francisco Bay 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 common

imported>WilliamFeiereisen at 10:52, May 11, 2017

2017-05-11T10:52:54Z

← Older revision		Revision as of 10:52, May 11, 2017
Line 1:		Line 1:
	Dynamic ~~Runtimes~~ Community Meeting		Dynamic Runtime Community Meeting

	Join us July 25-26, 2017 in the San Francisco Bay Area		Join us July 25-26, 2017 in the San Francisco Bay Area

imported>WilliamFeiereisen: Created page with "Dynamic Runtimes Community Meeting Join us July 25-26, 2017 in the San Francisco Bay Area"

2017-05-11T10:50:57Z

Created page with "Dynamic Runtimes Community Meeting Join us July 25-26, 2017 in the San Francisco Bay Area"

New page

Dynamic Runtimes Community Meeting

Join us July 25-26, 2017 in the San Francisco Bay Area