openedx / openedx/openedx-filters
How to implement organization-scoped filters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 28
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 8
Description
Description
Some comments I've gathered from the community survey on the challenges/suggestions section:
I think it would be interesting for organizations to be able to create their own events without committing them to the core or forking. For example, could I create a package of my own and associate a new event with an exception or a model change?
This can be applied as well to filters.
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 reading the issue description and the linked community survey feedback to understand the proposed organization-scoped filters. No files, tests, or entry points are identified, so the implementation boundary and acceptance criteria need to be established before work begins.
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