NASA-IMPACT / NASA-IMPACT/veda-github-actions
[Geospatial]-[Objective 13]: Alerting pipeline
Open
Nobody has claimed this yet.
Objective
poc-loe
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 8
Description
Context
Motivation
Deliver Alerting pipeline to support the Disasters program during this PI.
Description
Scope, milestones, and dependencies for alerting pipeline.
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 |
|---|---|---|---|
| Elena Petrova | Designer | 0.68 | — |
| Liam Walsh | Data Curator | 0.68 | — |
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, or entry points; begin by locating the existing alerting and GitHub Actions pipeline work in the repository and reviewing its dependencies. Done means the design is reviewed and approved, and the implementation is merged and deployed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100