| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = GEC Demo Submission = |
| | 4 | |
| | 5 | This page describes what you need to do to submit a Demo Request for Demo Night at GEC. Please pay attention to the dates mentioned in the email you received pointing you to this page, as we work with many vendors to ensure we have enough supplies as well as our gracious Campus Hosts to ensure we have enough Campus resources. |
| | 6 | |
| | 7 | Here's how to submit a Demo Request: |
| | 8 | |
| | 9 | 1. You have to log in (http://groups.geni.net/geni/wiki) using your GENI wiki user ID and password to create a ticket. If you don't remember your password, please email help-at-geni.net. |
| | 10 | |
| | 11 | 2. Use this URL to create a demo request ticket: |
| | 12 | |
| | 13 | http://groups.geni.net/geni/newticket?keywords=GEC13 |
| | 14 | |
| | 15 | 3. Copy the request template from this URL and paste it into your request ticket: |
| | 16 | |
| | 17 | {{{ |
| | 18 | Template to include in your demo request ticket: |
| | 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.) |
| | 21 | 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) |
| | 22 | Number of wired network connections (include required bandwidth if significant) |
| | 23 | Number of wireless network connections (include required bandwidth if significant) |
| | 24 | Number of static addresses needed (if any) |
| | 25 | Monitor (y/n, specify VGA or DVI) (Specify resolution only if your software has resolution restrictions.) |
| | 26 | 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.) |
| | 28 | }}} |
| | 29 | |
| | 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. |
| | 34 | |
| | 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. |
| | 38 | |
| | 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 | |
| | 44 | Here are more detailed instructions: |
| | 45 | |
| | 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. |
| | 54 | |
| | 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. |
| | 57 | |
| | 58 | Thanks for your help on this, and please let me know if you have any |
| | 59 | suggestions for improving demo arrangements. |
