|
Setup a new django app cookiecutter for xapi-caliper (repo name: event-routing-backends
)
edly team publishes ADRs to new repo for design and decsions already made.
edx + edly review and revise ADRs and land ADR changes.
edly team PRs basic implementation into the new repo.
edX + edly work together to deploy basic app to edx.org environments.
Configure new backends and Test against IMS test-suite in a sandbox environment.
Update code to make PII Leaking harder to do on accident.
PII leakage regression test
Add “negative” tests to ensure we do not send fields that are not in the Django-model-config “allow-list”.
Replace enterprise xAPI implementation with this new implementation.
Discovery: Which events are enterprise sending?
Access control / filtering (see #9).
Routers: Implement routers per enterprise.
Access-control/Filtering: Update code to support access control and filtering of events for different consumers.
Write an ADR to be reviewed by edX and Open edX community (publicize on Discourse)
Organizations/External Services to support
Must-have: enterprises
Super-nice-to-have: LRSes, university partners
Nice-to-have: external tool services
Configure prod to be able to test Caliper in production.
Time Frame | Updates & Actions Needed |
---|---|
|
Add action items by selecting the check box icon from the editing menu above. These actions will appear in the task table you create above. |
|
|
This section will link to all the development stories, tasks, and bugs connected to the single (or multiple) epics used to track the work on the Open edX JIRA site.