Catalog the current flows
Open
Scheduling tool
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
The purpose of the work here is to look at all the flows we have. Track which ones are on/off and the capabilities of each one.
With this information, we need to communicate with our meeting admins and confirm the behavior they want and the status of the flow (on/off)
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by locating all existing flows and recording whether each is on or off and what capabilities it has; then confirm the desired behavior and status with the meeting admins. Done means the complete catalog and those confirmations are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100