Changes between Version 1 and Version 2 of GECDemoSubmission
- Timestamp:
- 02/08/13 11:50:07 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GECDemoSubmission
v1 v2 11 11 2. Use this URL to create a demo request ticket: 12 12 13 http://groups.geni.net/geni/newticket?keywords=GEC1 313 http://groups.geni.net/geni/newticket?keywords=GEC16 14 14 15 3. Copy the request template from this URLand paste it into your request ticket:15 3. Copy the request template below and paste it into your request ticket: 16 16 17 17 {{{ 18 18 Template to include in your demo request ticket: 19 19 20 Brief demo description (A few sentences suitable for a GEC15 attendee information page. See http://groups.geni.net/geni/wiki/GEC14Agenda/EveningDemoSession for examples.) 20 Brief demo description (A few sentences suitable for a GEC attendee information page. See http://groups.geni.net/geni/wiki/GEC15Agenda/EveningDemoSession for examples.) 21 21 22 List of equipment that will need AC connections (e.g. laptop, switch hardware prototype, monitor). (Just put in the number of connections needed if your demo description already lists the equipment) 23 22 24 Number of wired network connections (include required bandwidth if significant) 25 23 26 Number of wireless network connections (include required bandwidth if significant) 27 24 28 Number of static addresses needed (if any) 29 25 30 Monitor (y/n, specify VGA or DVI) (Specify resolution only if your software has resolution restrictions.) 31 26 32 Number of posters (max size poster boards are 30" x 40") 27 Description of any special requests (include any non-commercial network connectivity needs, projects you'd like to be located near, etc.) 33 34 Description of any special requests (include any non-commercial network connectivity needs, projects you'd like to be located near, etc.) 35 28 36 }}} 29 37 30 We expect most demonstrations will integrate two or more projects, so 31 please make sure you mention any other collaborating teams in the text of 32 your ticket. The tickets will help us locate collaborating teams near each 33 other in the demo space as much as possible. 38 We expect most demonstrations will integrate two or more projects, so please make sure you mention any other collaborating teams in the text of 39 your ticket. The tickets will help us locate collaborating teams near each other in the demo space as much as possible. 34 40 35 Posters will be mounted on stands near the demo tables. The maximum poster 36 board size is 30" x 40." Half size posters (30" x 20") are encouraged if 37 the contents allow. 41 Posters will be mounted on stands near the demo tables. The maximum poster board size is 30" x 40." Half size posters (30" x 20") are encouraged if the contents allow. 38 42 39 You can request projectors, standard or large monitors for your demo as 40 needed. Due to the added expense, please request large or high-resolution 41 monitors only if your content requires it. We'll do our best to 42 accommodate your request. 43 You can, 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. 43 44 44 45 Here are more detailed instructions: 45 46 46 When you are entering data for your demo ticket, select your project name 47 from the drop-down list for the ticket "Component" field. Leave the 48 "Milestone" and "Dependencies" fields blank, which is the default. Assign 49 the ticket to Manu Gosain (agosain at bbn.com) and include anyone who 50 should get email updates on the ticket in the "Cc" field. The GPO will 51 update your ticket when we confirm that the resources you need are 52 available, and will use the ticket for any further communications about 53 your demo. 47 When you are entering data for your demo ticket: 48 * Select your Project Name from the drop-down list for the ticket "Component" field. 49 * Leave the "Milestone" and "Dependencies" fields blank, which is the default. 50 * Assign the ticket to Peter Stickney ( peter.stickney - at - bbn.com ) and include anyone who should get email updates on the ticket in the "Cc" field. 54 51 55 If you have any trouble creating or using a ticket, please email 56 help@geni.net and we'll make sure your information is entered. 52 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. 57 53 58 Thanks for your help on this, and please let me know if you have any 59 suggestions for improving demo arrangements. 54 If you have any trouble creating or using a ticket, please email help-at-geni.net and we'll make sure your information is entered.