Page tree

Request A Hosted Project

General Information / Policy

  • DI2E Framework supports Hosted Projects that will be used either for development, sustainment or support for a C4ISR capability by a DoD or Intelligence Community organization.
  • If you are new to DI2E, you may want to visit our page that describes the tools provided when you request a "Hosted Project" space.  Click here for more details on DevTools
  • If you are interested in a Hosted Project, review the following instructions below.  Links to complete the request are at the end of the instructions.  Reviewing and following the instructions will avoid delay in processing your request.
  • Key goal of DI2E Framework is providing an open and public environment in order to promote collaboration and interaction which may result in reuse and shared best practices with other DI2E users.
  • DI2E users have the ability to control privacy and access to their tools and content.  However, all DI2E users have the ability to read general information about any project's name, description, and points of contact.  This permits DI2E users to reach out and collaborate where it makes sense.  
  • In order to promote discovery of Hosted Projects, DI2E Framework will add a general DI2E Storefront (https://storefront.di2e.net/) entry that includes the basic information listed above, namely Project Name, Description, and POCs.  At any time, the project owner can update and revise this general Storefront entry in coordination with DI2E Framework staff.  A link to the DI2E Storefront entry will be provided in the original project request.  In instances when a project has a more mature or complete product, in invitation will be made to the owner to provide a more detailed entry in the DI2E Storefront.
  • As a Hosted Project request is being processed, intermediate status will be provided.  In some cases, additional information will be requested. 

====== Option 1:  Hosted Project Request Instructions  (Quick Summary) ======

These shorter instructions are intended for experienced users who have previously set up a Hosted Project.  New users are encouraged to follow the detailed instruction listed below in "Option Two."

Part One Establish a DI2E user account.  Instructions for requesting an account posted here:  Click here to request an account

Part Two:  Key areas to focus on when submitting a Hosted Project:

  • Project Name/Description.  These are the most important sections which are typically not filled completely or clearly.  Spell out acronyms and write a Project Name and Description that anyone or most can understand.  All projects, whether public or private, are visible to entire community.  Everyone can view basic information (e.g., project name, description, and POCs), so clear titles and descriptions are helpful.
  • Hosted Project Access.  This field indicates the level of access for other DI2E users.  The three options are the following:
    1. "All DI2E Account Holders."  This is fully accessible by all DI2E users and is the default setting.  Requesting to be private is by exception.
    2. "Some Project Information is shared with all DI2E account holders."  The intent for this option is some information is public and some areas are private. The areas that are private could include new individuals who request access via the project owner.
    3. "Private."  Project is not accessible to other DI2E users.  However, like option two above, a DI2E user can still contact the project approver and request access or to engage in general collaboration.
  • Click here to Complete a Hosted Project Request:  Click here to Start Request


 ====== Option 2: Hosted Project Request Instructions (Complete and Detailed) ======

Part One:  Establish a DI2E user account.  Instructions for requesting an account posted here:  Click here to request an account

Part Two:  Review instructions and complete request form.

Step 1:  Once you have established a DI2E account, you can proceed to submit a "Hosted Project Request."  Complete the information listed in Figure 1:

  • Summary.  Replace short name or abbreviation of your project in the brackets indicated in the form.  For example, in Figure 1 below in the "Summary" field, it says "New DI2E Project request for your project name here:" (Figure 1. "Blank Form") You would replace "for your project name here:" with "CPT" and the full summary would read "New DI2E Project request for CPT."  (Figure 1, "Sample Completed Form.")
  • Project Name.  Short title of your project.  Spell out all acronyms. 
  • Project key.  No more than 10 characters, uppercase letters and numbers.  No spaces or punctuation.  Project acronyms are frequently used.
  • Project Description.  Provide a description that can be understood by most DI2E users.  All projects general information (e.g., Project Name/Description and POC info) is viewable by entire community even for private projects.  Our goal is to promote collaboration and reuse across the community. Spell out all acronyms.  Examples:
    • Example 1 (Customer using JIRA and Confluence only).  Using DI2E tools to manage our project (not good).  Using DI2E tools to manage a project focused on developing cyber planning dashboard (better).
    • Example 2 (Customer using JIRA, Confluence, and Bitbucket).  Army team is developing image processing tool that will assist analysts to rapidly label and identify geospatial targets.  
    • Example 3 (as depicted in Figure 1 below).  Project Name:  Cyber Planning Tools (CPT).  Project Description:  The Cyber Planning Tools (CPT) project will support the development and management of security tools used by the Army G-6.  The tools will include planning workflow, supporting UI, and a user dashboard.


Blank FormSample Completed Form

Figure 1. Basic Project Information

Step 2:  Complete the information listed in Figure 2:

  • Supports C4ISR.  This box must be read, understood, and checked.  By checking, the submitter acknowledges the requested project supports intelligence related work in DoD or Intelligence Community.
  • Project Owner.  Primary POC for this project.  Our staff will use this POC first for questions about the project and general coordination.
  • Project Owner phone.  Phone number of the project owner.
  • Project Owner email address.  Email of project owner.
  • GPOC.  May be same as Project Owner or different.  Include full name, email, and phone.  (e.g., Maj John Smith / jsmith@army.mil  / 
  • Organization/Agency.  Primary Service or Agency.  Select from the drop-down list.
  • Office Symbol.  Here, you can provide more granular organization information (e.g. Army G-6; SPAWAR CIO-2; DIA-ES4)
  • Contains ITAR/FOUO/CUI.  Select either "Yes" or "No."  For additional information:  Additional Information
Blank FormSample Completed Form

Figure 2. Project POC Information


Step 3:  Select the desired DevTools  Figure 3a provides an example in which the user selected JIRA, Confluence, and Bitbucket (Stash).  Other details regarding selecting DevTools:

  • For additional information about each DevTools, go here:  Additional DevTools information
  • Additional DevTools can be requested at any time.  Even after project is approved, you can go back to the original request ticket and select "Add additional DevTools."

Sample Completed Form

Figure 3a. Select DevTools
  • If JIRA is one of the selected tools, click on the "Configurations" tab and select applicable options (Including if you want Jira Service Desk).  (See 3b. below)

Step 4:  Hosted Project Privacy.  Figure 4 below shows initial and sample completed form.  Other information related to this section:

  • General Guidance.  A key goal of DI2E Framework is to provide the community an open and collaborative environment.  This is best accomplished when a project is completely open and public.  Even when a project is private or partially private, all DI2E users can view general information such as Project Name, description, and POC information.  This permits other DI2E users to reach out and collaborate when applicable.  It doesn't imply an owner has to grant full or partial access to their project tools.
  • Hosted Project Access.  This field indicates the level of access for other DI2E users.  The three options are the following:
    1. "All DI2E Account Holders."  This is fully accessible by all DI2E users and is the default setting.  Requesting to be private is by exception.
    2. "Some Project Information is shared with all DI2E account holders."  The intent for this option is some information is public and some areas are private. The areas that are private could include new individuals who request access via the project owner.
    3. "Private."  Project is not accessible to other DI2E users.  However, like option two above, a DI2E user can still contact the project approver and request access or to engage in general collaboration.
  • Hosted Project access justification.  This field is filled in when selecting "Private" is selected for "Hosted Project Access."  Provide additional information why project must be private and if a user can contact project owner for general collaboration.
  • Additional Information.  Provide any additional information that would be helpful in creating your new project.  Once the request is completed and submitted, a user can add additional information in the comments section of the request ticket.

Blank FormSample Completed Form

Figure 4. Hosted Project Privacy Information


Step 5:  Other Hosted Project Information.  Figure 5 below shows initial and sample completed form.  Other information related to this section:

  • Assignee. For internal use.  This section is left blank and not filled in by the project requestor.
  • Reporter.  This field is automatically populated by the individual making the project request.  No action required.
  • Labels.  Labels are like meta-data tags.  Labels help users discover your Hosted Project.  For example, in Figure 5 below, the Labels "cyber," "planning," and "dashboard." were added by the requestor.  In addition, DI2E Framework staff may revise and add additional tags they deem appropriate to help project discovery.
  • Priority.  User can select the desired level, but in most cases, internal DI2E staff will adjust based on the overall merits of the requested project.
  • Due Date.  A user can select a desired date of completion.  However, internal DI2E staff respond and prioritize hosted project requests based on the overall merit of the request and the given backlog at any time in the approval process.
  • Email Users.  A project requestor can list other emails of who should be included on any correspondence related to the project request.
  • Attachment.  A project requestor can attach relevant documents/files related to the project request.
  • Requestor's email address.   Include requestor's email.
  • After entering all the above information, click on "Create" to submit request.

Blank FormSample Completed Form

Figure 5. Other Hosted Project Information


Step 6:  After reading the instructions in Steps 1 through 5 above, Click here to Complete a Hosted Project Request:  Click here to Start Request




Instructional Video: