MFOSSociety / MFOSSociety/MMMenu
Ideas
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Ideas that can be implemented
**1. Get static mess menu**
| Pros | Cons |
|-----------------|--------------------------------------------------|
| Easy to develop | Regular changes to be made a/c to change in menu |
**2. Master-child node architecture** _(one app will replay daily mess menu data to it's child nodes)_
| Pros | Cons |
|-----------------|--------------------------------------------------|
| No cost & concrete implementation | The master node should be trust-worthy, should be handled by mess authority |
**3. Using Open-CV to interpret the whiteboard and replay the data to nodes**
| Pros | Cons |
|-----------------|--------------------------------------------------|
| Automated, no man power required | Error prone, relatively costly |
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
No files, tests, or entry points are named. Compare the three proposed menu architectures against the repository's existing app structure, then document a chosen direction with concrete scope and acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, opencv
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100