Fix #469, Additional bundle updates for Draco open source release

[jphickey]

Describe the contribution
Remaining bundle updates for open source release

[keegan-moore]

Can you create an issue to commit this stuff under?
It's a best practice to reference an issue number in all commits.
That might actually be necessary anyway to pass our commit format pipeline check.

[dzbaker]

Can you create an issue to commit this stuff under? It's a best practice to reference an issue number in all commits. That might actually be necessary anyway to pass our commit format pipeline check.

I went ahead and updated the PR to reference our issue for repository cleanup.

[keegan-moore]

Can you create an issue to commit this stuff under? It's a best practice to reference an issue number in all commits. That might actually be necessary anyway to pass our commit format pipeline check.

I went ahead and updated the PR to reference our issue for repository cleanup.

Looks like the tools are connecting it to #469 (not our internal issues).
Not sure how to differentiate them. Perhaps we wouldn't need to if we moved our open-source update issue tracking back out to github.com. I've got some ideas about this that might help.

[dzbaker]

Can you create an issue to commit this stuff under? It's a best practice to reference an issue number in all commits. That might actually be necessary anyway to pass our commit format pipeline check.

I went ahead and updated the PR to reference our issue for repository cleanup.

Looks like the tools are connecting it to #469 (not our internal issues). Not sure how to differentiate them. Perhaps we wouldn't need to if we moved our open-source update issue tracking back out to github.com. I've got some ideas about this that might help.

Yeah, I have some ideas that I want to discuss with you about handling that long term.