Open Info - FOI requests
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
## Description:
- Short Description of the needed Epic in the below format
* As a (who/ person)
* I want (what/ goal)
* so that (why/ benefit proposal)
* What are the most critical features being built as part of this Epic
* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.
----
**Sizing**
* T-shirt size:
[ ] S
[ ] M
[ ] L
[ ] XL
(S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints).
* *Risks and Assumptions**
1. [ ] What are assumptions?
2. [ ] What are the risks?
3. [ ] Have we done an RFC on a technical approach?
4. [ ] Are the dependencies (technical, business, regulatory/policy) known?
5. [ ] Has work on this Epic been prioritized with key stakeholders?
Contributor guide
Research direction
This issue contains only an unfilled Epic template and does not identify files, tests, or an entry point. Clarify the requested FOI-request outcome, scope, dependencies, and acceptance criteria before locating implementation work; the current text does not define what done looks like.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100