Changes between Version 32 and Version 33 of GECDemoSubmission
- Timestamp:
- 01/09/15 13:04:30 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GECDemoSubmission
v32 v33 1 1 2 = GEC Demo Submission =2 = GEC and US Ignite Demo Submission = 3 3 4 This page describes what you need to do to submit a demo request to participate in the Evening Demo Session at the GENI Engineering Conference (GEC). Please pay attention to the submission deadline date posted on the demo wiki page, as we work with many vendors as well as our gracious campus hosts in advance to ensure we have adequate equipment and resources for the demo, and we ''cannot'' accept late or incomplete requests.4 This page describes what you need to do to submit a demo request to participate in the Evening Demo Session at the joint US Ignite/GENI Engineering Conference (GEC). Please pay attention to the submission deadline date posted on the demo wiki page, as we work in advance with many vendors as well as our gracious campus hosts to provide adequate equipment and resources for the demo, and we ''cannot'' accept late or incomplete requests. 5 5 6 NOTE: We will distribute the demo description paragraph in the template below to all GENI attendees to help6 NOTE: DEMO DESCRIPTIONS ARE REQUIRED. We will distribute the demo description paragraph in the template below to all GENI attendees to help 7 7 people find the demos they are most interested in seeing, so it is important to write a compelling and 8 accurate description. If you have done demonstrations before, make sure to highlight what is different about this 9 demonstration compared to previous ones. Indicate in your description who really should see the demo 10 and why (e.g. "Network providers that support !OpenFlow should see this tool demonstration because it 11 will let them manage limited bandwidth efficiently.") 8 accurate description. Demo desriptions should start with a sentence that is understandable by laymen. Indicate in your description who really should see the demo 9 and why (e.g. "Network providers that support !OpenFlow should see this tool demonstration because it will let them manage limited bandwidth efficiently.") 12 10 13 11 … … 20 18 http://groups.geni.net/geni/newticket?keywords=GEC22&version=SPIRAL7&owner=peter.stickney@bbn.com 21 19 22 3. Copy the request template below and paste it into your request ticket: 20 This URL makes sure your request shows up on the GEC22 request list, so please use it to make sure your request isn't lost. 21 22 3. Copy the request template below and paste it into your request ticket. Please fill out all items.: 23 23 24 24 {{{ 25 25 26 26 27 Demo description paragraph (three sentence minimum): 27 Demo Title: 28 29 One-sentence layman's description: 30 Example: This demo shows a working prototype of an emergency communication service in St. Louis, Missouri. 31 32 Who should see this demo? 33 34 Example: Attendess interested in emergency preparedness and resiliant networks should see this demo. 35 36 Demo description paragraph: 28 37 29 38 List of equipment that will need AC connections (e.g. laptop, switch, monitor): … … 51 60 52 61 }}} 62 Please make sure you mention any other collaborating teams in the text of your ticket. The tickets will help us locate collaborating teams near each other in the demo space as much as possible. 53 63 54 We expect most demonstrations will integrate two or more projects, so please make sure you mention any other collaborating teams in the text of your ticket. The tickets will help us locate collaborating teams near each other in the demo space as much as possible.64 Posters will be mounted on stands near the demo tables, and shown throughout the event. The maximum poster board size is 30" x 40." Half size posters (30" x 20") are encouraged if the contents allow. 55 65 56 Posters will be mounted on stands near the demo tables, and shown during GEC in a poster display area. The maximum poster board size is 30" x 40." Half size posters (30" x 20") are encouraged if the contents allow. 57 58 You can request standard ( 32" ) or large monitors ( 42" ) for your demo as needed. Due to the added expense, please request large or high-resolution monitors only if your content requires it. We'll do our best to accommodate your request. 66 You can request standard ( 32" ) or large monitors ( 42" ) for your demo. Due to the added expense, please request large or high-resolution monitors only if your content requires it. We'll do our best to accommodate your request. 59 67 60 68 Here are more detailed instructions: … … 63 71 * Select your Project Name from the drop-down list for the ticket "Component" field. (If your project name is not in the list, skip this step and type it in the body of the ticket.) 64 72 * Leave the "Milestone" and "Dependencies" fields blank, which is the default. 65 * Include anyone besides you who should get email updates on the ticket in the "Cc" field . You will automatically get updates on the ticket.73 * Include anyone besides you who should get email updates on the ticket in the "Cc" field (for example, your advisor). You and the cc: list will automatically get ticket updates. 66 74 67 75 The GPO will update your ticket when we confirm that the resources you need are available, and will use the ticket for any further communications about your demo. We often get more demo requests than we can accommodate, and we will inform you via the ticket a few days after the deadline if your request is not selected for the event.