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

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws
Domain
cloud

Research direction

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.

Description

discuss question

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
image

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:

Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.