* IS&T has a process which should be used when we need to make changes to web sites controlled by them
  * We should use the process rather than directly contacting Jared
  * We should create a project and team dedicated to the bandit site
   * this would be comprised of IS&T people, Bandit people, and marketing/content people
  * Jared says we can make any kind of changes, including changes to the wiki code (not just extensions)
  * The rollout process can be very efficient (1 to 2 days) for small changes
  * The process could take up to a week for a scenario where a completely new, unknown service we being added
  * With our current site goals, no additional hardware requirements are foreseen.
 * Bandit has different needs
  * We want a site that is informative but fairly static and contains high-level material. 
   * Audiences would be marketing people, analysts, initial investigators
   * Proposed name is bandit-project.org
   * See ticket https://woof.bandit-project.org/code/demos/ticket/67
  * We want a site that is dedicated to bandit developers and consumers. 
   * This site fills these roles:
    * Project management such as Timelines, milestones, roadmaps, tasks
    * Component/deployment delivery, documentation, repositories
   * Propose to use trac to meet above roles
   * Proposed name is code.bandit-project.org
   * See tickets https://woof.bandit-project.org/code/demos/ticket/64, https://woof.bandit-project.org/code/demos/ticket/54, https://woof.bandit-project.org/code/demos/ticket/55, https://woof.bandit-project.org/code/demos/ticket/63, 
  * We want a site that acts as a repository and issuer of Bandit identities
   * This production-level site showcases our IdP deployment
   * Accounts can be created, modified, and used to create cards
   * These identities should be usable by other bandit sites
   * Proposed name is cards.bandit-project.org
   * Ticket is https://woof.bandit-project.org/code/demos/ticket/74
  * We need various sites that we have full control over
   * These are used for demos, interop events, conferences, etc.
   * IS&T does not have a good process available where these types of sites can be backed up while giving us full access
   * IS&T does have a DMZ in the data center which we could place this class of site into such that they could be backed up, but they still want to review the software and we would have limited physical access.
    * It's possible that we could at least have root access to these machines
 * Action Items:
  * Daniel will begin the process of identifying the steps needed to meet our goals for cards.bandit-project.org
  * Jim will call a meeting to refine our ideas around using trac as a developer / project management tool
  * A team needs to be proposed which includes IS&T, Bandit, and Marketing
    * Jared will set up a mailing list to kick this off
  * Someone needs to start the process of revamping bandit-project.org.
    * Some of this depends on code.bandit-project.org being complete (such as pointers to deliverables and documentation)
    * See tickets https://woof.bandit-project.org/code/demos/ticket/67, https://woof.bandit-project.org/code/demos/ticket/59, https://woof.bandit-project.org/code/demos/ticket/56, https://woof.bandit-project.org/code/demos/ticket/52,