1. Problem Statement
   ----------------------------

Q - Executive summary of the user goal and expected outcome. What problem is being solved, why does this matter to the user?

A - Satellite is a content management system that provides great methods for mirroring content from a public network to an air-gapped environment. One of our use cases is using satellite to ensure we have the latest dependencies being updated at regular intervals. We are able to perform this task for regular package repositories and container registries, but we have to manually seek out the latest source code of any projects that we build from source on our air-gapped network. It would greatly enhance our process if Satellite could mirror and regularly sync a project from public GitHub and provide the mechanism to export it for import to the air-gapped environment.  

2. User Experience & Workflow
   -----------------------------------------

Q - Describe the experience/interaction/steps of this request as a workflow with expected outcomes at each step. What is the end-state and how will they be able to verify a successful outcome? Are you willing to test out the feature if implemented?

A - The expected workflow would be:
       1. Create a new product type as Git in the connected Satellite instance. 
       2. Sync the Git product to the Git project
       3. Export the Git product just like any other product
       4. Import the new Git product into the air-gapped Satellite
       5. Direct the disconnected GitLab instance to mirror the Satellite hosted Git product

3. Requirements
   --------------------

Q - A list of specific needs or objectives that a Feature must deliver to satisfy the Feature. Note: Any requirements that are not flagged as MVP, should be evaluated and considered for another feature.

A - Specific needs would be that Satellite is able to sync, export, and import a Git project.

4. Business Impact
   ------------------------

Q - What would happen if the inclusion of this feature wasn’t undertaken? 

A - System Admin workload increases as managing increased public dependencies becomes more time intensive. Risk increases that dependency updates are missed, thus increasing the probability of security patches not being applied.