How Much would it Cost to make it "Free for Open Source"?

One of the _great_ ways to get adoption for _any_ service (_on GitHub_)
is to make it available for "_free_" for Open Source projects.

_Assuming_

I did a quick simulation of the ("_medium term_") cost (_per month_) using the following factors:

+ 10TB (10,000GB) of storage (_that's a **LOT** of data..._)
+ 10,000,000 (10 Million) PUT requests (_to save the data. 10M comments/updates per month_)
+ 10,000,000 (10 Million) GET requests (_to view past issue comments_)
+ 0 transfer in/out fees if we host the application on AWS see links below.

## Projected Cost: $283.86/Month

https://calculator.s3.amazonaws.com/index.html

## Considerations:

+ All S3 Costs are "Pay As You Go", so we will only spend the money if/when the service is popular.
+ In the beginning (MVP) it will be $5/month to test the idea.
+ ***Most people*** will **_not_ click** on the link to **view** the "**History**" of a given **issue/PR comment**.
+ However ***ALL*** will _see_ the "Meta Table" displaying the "stats" for the issue.
+ The people who _will_ click the link will _likely_ only view a single issue at a time.

> The way we need to _think_ about this cost is "Marketing".
> If we end up with _zero_ paying customers and we're "_burning_" $300/month on S3 costs,
> we can always email all the people using the service for "_free_" and _ask_ them to help spread the word.

## Background Reading:

+ https://blog.cloudability.com/aws-s3-understanding-cloud-storage-costs-to-save/
+ https://www.quora.com/Is-there-data-transfer-cost-between-AWS-S3-and-EC2-within-the-same-availability-zone

The issue names no repository files, tests, or implementation entry point. Start by reviewing the S3 calculator assumptions and the project's current hosting or storage setup; a concrete implementation scope and acceptance criteria are needed before completion can be defined.

Written by the indexing model from the issue text.