learningequality / learningequality/studio
Notifying multiple editors when a channel is published
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
Currently, only the person who publishes a channel receives a notification that a channel has been published and is ready for update in Kolibri. The only way other editors would know that a channel has been re-published would be if they go into their own instance of Kolibri and see whether there is an update from a previously published version of the channel. It would be helpful to have an option where multiple editors could be notified when a channel has publishing completed (e.g., a checkbox "[ ] Notify all editors on this channel when publishing has completed").
Category
ENHANCEMENT
Real-life consequences (anything community should be aware of, for instance how it affects end users)
Given that our users only connect to the Internet when really needed, if an editor is publishing a channel in a location with decent connectivity, but wanted to notify editors in locations with more limited connectivity, having this option would take out a middle notification step (and potentially allow for some creative uses of auto-forwarding/forwarding to WhatsApp, etc.).
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
Start by tracing the existing channel-publishing completion notification and how editors associated with a channel are represented. Define the notification preference and recipient behavior, then verify that every relevant editor is notified after publishing completes; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100