openwisp / openwisp/openwisp-radius
[feature] Allow configuring SMS backend and config for each organization
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 445
- Forks
- 234
- Avg merge
- 20h 21m
- Merged PRs (30d)
- 19
Description
This is a tricky one, we should allow configuring the SMS backend for each organization, ideally we should have a UI generated for this too.
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
The issue does not name any files, tests, or entry points. Start by locating the organization configuration and existing SMS backend integration, then determine how organization-specific settings and the proposed UI should fit together. Done should include a defined configuration flow and working organization-level SMS backend selection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100