OpenTimelineIO AAF Adapter Removal Tasks

[markreidvfx]

The following tasks need to be resolved before AAF Adapter can safely be removed from OpenTimelineIO.
Please let me know if there are any other blocking issues to add to this task list.

The pull request to remove the AAF Adapter from OTIO is here
AcademySoftwareFoundation/OpenTimelineIO#1348

Blocking Tasks

• Fix test coverage lost in OTIO due to the AAF adapter AcademySoftwareFoundation/OpenTimelineIO@913f540
• Enable EasyCLA enforcement if possible
• Enable Developer Certificate of Origin (DCO) enforcement
• Enable pull request reviews settings in repository
• Enable CodeCov CI and pull request reports
• Enable Dependabot
• Create / Verify PyPi package publishing works
• Create PyPi package alias for OTIO Rearrange PyPI projects, break out adapters AcademySoftwareFoundation/OpenTimelineIO#1386
• Linking docs to OTIO strategy and publishing
• Add Code of Conduct and Contributing docs
• Fix CI pip install OTIO URL
• Fix Badge path in Readme
• Add issue and pull request templates

Possible Blocking Tasks

• Migrate OTIO AAF Adapter Issues or link
• Migrate OTIO AAF Adapter Pull Requests?
• What OTIO version do we test against? multiple?
• Any additional docs need to move/remove from OTIO?
• Improve front page README

[JeanChristopheMorinPerso]

Regarding CLA and DCO, none of the repositories in the OpenTimelineIO organization have them enabled. I personally think it's fine, but obviously I'm not a member of the TSC so that's just my personal opinion.

CodeCov and Dependabot are really easy to enable. See https://docs.codecov.com/docs/github-2-getting-a-codecov-account-and-uploading-coverage and https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates (I think you might have to actually enable Dependabot in the repo settings).

I can help with some of these and the packaging/build side of things too.

[markreidvfx]

@jminor said he was going to look into the CLA stuff.
Thanks @JeanChristopheMorinPerso , I have DCO and CodeCov working in my fork.

The annoying thing with CodeCov at the moment is pytest is running against a installed wheel and CodeCov doesn't like the file paths if you do that. Trying to think of the best approach to deal with this. pip install -e . works fine, but I like the idea of running the test against the wheels like you helped me do in my repos. pytest-cov doesn't seem have many options help do that.

[JeanChristopheMorinPerso]

Maybe https://docs.codecov.com/docs/fixing-paths?

[markreidvfx]

That looks like it might work, I'll give it a try!

[timlehr]

I think this can be closed, no? @markreidvfx