List view
To improve developer experience working with this repo, we will begin migrating our DevOps pipelines into Github Action, along with consolidating documentations and leveraging popular DevOps tools like `tox` and `flake8`.  This migration to GitHub Action will be a sequence of updates to our DevOps infrastructures: 1. Propose and draft the CI pipeline in Github Action 2. Optimize build time for unit tests 3. Enforce flake8 (coding style checks) on the build and clean up coding styles to pass flake8 checks 4. Setup self-hosted machines to run our GPU workloads 5. Run tests on the appropriate dependency subsets 6. Create feature parity with the existing CI pipelines (pr-gates & night-build) 7. Deprecate CI pipelines in ADO and switch to Github Actions
No due date•13/13 issues closedUse a small dataset, so people understand the usecase. The implementation should we scalable. Then in the notebook explain with words how this could be extended to a massive dataset
No due date- No due date
- No due date•1/2 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
Look into other open source alternatives and prioritize for development
No due date•3/4 issues closed- No due date•1/1 issues closed
- No due date•8/8 issues closed
- No due date•12/12 issues closed
- No due date•1/1 issues closed
Add xDeepFM and DKN
No due date•4/6 issues closed- No due date•11/13 issues closed