feat: add environment properties as structured metadata for each environment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 318
Description
Use cases, pain points, and background
It is challenging for users to discover and identify the environments they need, this challenge will only become more difficult as the number of environments in the ecosystem rapidly grows.
Description:
We are working on defining a set of standard environment properties. We need to continue to develop these definitions, and then apply to our environments as structured metadata.
Design:
TBD
Out of scope:
TBD
Acceptance Criteria:
- TBD
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked environment properties tutorial and inspect how environments are currently defined in the repository. Define the standard properties, then apply them as structured metadata across the environments; the issue's acceptance criteria are still TBD, so completion needs clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100