Per 1EdTech

Upcoming Change to IMS Domain
Effective April 1, 2024
This is an important notice for organizations that are referencing hardcoded imsglobal.org XSDs in your software.
Effective April 1, 2024, 1EdTech will automatically redirect all traffic from its previous domain, http://www.imsglobal.org/, to https://www.imsglobal.org/.
Starting on April 1, we will redirect all files located on www.imsglobal.org to the new secure website—they will no longer be available via HTTP. This change will impact XSDs as well as other files.
The imsglobal.org will eventually be deprecated and go away completely.
Please check any URLs currently resolving to www.imsglobal.org and change them accordingly. XSDs are already located at the secure location so that testing can begin immediately.
We are implementing this change to ensure that we follow best practices. You should not have any issues if you properly respect the 301 redirect protocol by W3C.
1EdTech’s technical staff are available to help with questions.

Update http to https accordingly.

Add coverage tracking to the CI pipeline

Since Python 2.7 will no longer be supported soon (https://pythonclock.org/), we need to do the update to Python 3.

Some of the work was done pre-open source, but we need to finish it.

Need to set our session cookies to specify SameSite=None; Secure

https://blog.chromium.org/2019/10/developers-get-ready-for-new.html

When we hosted this project internally, we used GitLab CI. Now that we're open source on GitHub, we should move to a new CI platform like Travis.

Travis is dead to us. (See ucfopen/canvasapi#445 (comment))

Replace with GitHub Actions

Describe the bug

We previously had issues with the production version of Flask-Testing, where it was incompatible with Werkzeug>=1.0.0, and pinned a specific branch from their GitHub repo. That branch has since been deleted, but the production package has been updated with the new code.

Update our requirements file to pin Flask-Testing to at least 0.8.0.

Add a .github directory including cool features like:

• a CODEOWNERS file that we can use to automatically assign the team to new PRs
• issue templates
• PR templates

Implement a way to handle order of tools based on whitelist and settings file.

Describe the bug

Multiple installs of the same tool, appear to use the same launch links, despite having different launch info.

To Reproduce

Steps to reproduce the behavior:

1. Install a tool with one set of configs
2. Install the same tool with slightly different config
3. Launch Faculty Tools and observe that there are two cards for the instances, but they both link to the same instance.

Expected behavior

Each card should link to a different instance.

Environment information

• Python version (python --version) 3.7.6

Additional context

Discovered this due to an old instance of our internal proctoring software being installed at the course level (with old key/secret), alongside the new instance being installed at the account level.

Add black check as a required test.

Dockerizing the application.