Changes between Version 1 and Version 2 of GECDemoSubmission


Ignore:
Timestamp:
02/08/13 11:50:07 (7 years ago)
Author:
peter.stickney@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GECDemoSubmission

    v1 v2  
    11112. Use this URL to create a demo request ticket:
    1212
    13      http://groups.geni.net/geni/newticket?keywords=GEC13
     13     http://groups.geni.net/geni/newticket?keywords=GEC16
    1414
    15 3. Copy the request template from this URL and paste it into your request ticket:
     153. Copy the request template below and paste it into your request ticket:
    1616
    1717{{{
    1818 Template to include in your demo request ticket:
    1919
    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
    2122    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
    2224    Number of wired network connections (include required bandwidth if significant)
     25
    2326    Number of wireless network connections (include required bandwidth if significant)
     27
    2428    Number of static addresses needed (if any)
     29
    2530    Monitor (y/n, specify VGA or DVI) (Specify resolution only if your software has resolution restrictions.)
     31
    2632    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 
    2836}}}
    2937
    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.
     38We expect most demonstrations will integrate two or more projects, so please make sure you mention any other collaborating teams in the text of
     39your ticket. The tickets will help us locate collaborating teams near each other in the demo space as much as possible.
    3440
    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.
     41Posters 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.
    3842
    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.
     43You 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.
    4344
    4445Here are more detailed instructions:
    4546
    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.
     47When 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.
    5451
    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.
     52The 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.
    5753
    58 Thanks for your help on this, and please let me know if you have any
    59 suggestions for improving demo arrangements.
     54If you have any trouble creating or using a ticket, please email help-at-geni.net and we'll make sure your information is entered.