Openscapes / Openscapes/openscapes.cloud

AWS Usage Report: individual-level costs

Open
#39 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

usage-reporting
Dominant language
JavaScript
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

This would be helpful for planning for funding future hubs etc.

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.

Research direction

The issue does not name any files, tests, or entry points. First clarify which individual-level AWS costs should be reported and how the report will support funding plans; done should be defined by an agreed report scope and output.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.