nusmodifications / nusmodifications/nusmods
More Robust Venue Updates
Open
Nobody has claimed this yet.
feature request
pending requirements
venue data
- Dominant language
- JavaScript
- Stars
- 689
- Forks
- 364
- Avg merge
- 7h 5m
- Merged PRs (30d)
- 14
Description
Currently the venue update request uses GitHub API to create a new GitHub issue. we should try something more crowdsource. Open for discussion but off the top of my head some ideas I had:
- Community approvals
- Median of requests (dedup by timing)
- Weighted by recency + median of requests
Contributor guide
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 or tests are named. Start by tracing the existing venue update request and its GitHub API issue-creation flow; the issue needs a decided crowdsource model and acceptance criteria before a newcomer can know what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100