NASA-IMPACT / NASA-IMPACT/veda-github-actions
[Designer]-[Objective 35]: CSDA catalog automation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 8
Description
Context
Motivation
Deliver CSDA catalog automation to support the Disasters program during this PI.
Description
Scope, milestones, and dependencies for csda catalog automation.
Examples & Concept Diagrams (If applicable)
Success Criteria
- Design reviewed and approved
- Implementation merged and deployed
Risks
- Dependency slippage; mitigate with early integration checkpoints.
LOE/FTE
| Person | Role | FTE | Notes |
|---|---|---|---|
| Jordan Kim | Designer | 0.42 | — |
| Nadia Hassan | Backend | 0.72 | — |
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, entry points, or concrete catalog behavior. Start by reviewing the repository's reusable GitHub Actions and clarifying the CSDA catalog scope, milestones, dependencies, and deployment target with the listed designer and backend contributor. Done means the design is approved and the implementation is merged and deployed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100