1. Attendance - Eric Holguin - Zach Hoffman - Joshua Zenn 2. Are there parts of the project that are not in use or code duplication that could be removed? In the interest of reducing the amount of code we maintain. - legacy Dockerfiles at infrastructure/docker - these can almost certainly be removed; haven't worked in a long time, no known users remaining - grove - Grove is prod-ready, which is a high bar. Not getting rid of that at any point in the forseeable future - misc/changelog.pl - Some Release Managers still use this - Consider rewriting to Python for maintainability - misc/jira_github_issue_import.py - We can remove this, we moved from JIRA to GitHub a long time ago - misc/kickstart* - These are used by ISO generation; consider moving to a more appropriate location - misc/release.pl - This is our entire release process. Someone brave could rewrite to Python, but this will not be going away. - misc/parse_diffs.py - Used by GitHub Actions. Could be moved to a more appropriate location, but not deleted - traffic_control/clients/java/ - Not known to be used, candidate for removal - traffic_control/clients/python/ - Heavilly used, not being removed - Can't move it up to eliminate an empty directory, due to hard-coded install instructions - traffic_ops/traffic_ops_golang/swaggerdocs/ - Not correct - Not used - Has both opponents and proponents in the community; we can revisit the discussion to remove, but it has been shot down before - misc/git - Precommit hooks work and are good. So no remove. - cache-config/testing/docker/, tc-health-client/testing/docker/ - These are both extensively copied from an old version of CDN-in-a-Box and the TO API/Go client integration tests. - That means they not only duplicate each other, but also CiaB which is better maintained. - Instead, we could add an integration-test-specific docker-compose file a la TO/TP, and use the enroller of CiaB instead of duplicating TO API integration test code - traffic_stats/assert/ - Probably duplicates some of the traffic_ops/testing/api/assert/ - one or both should have the parts not specific to any given component moved to lib/go-util. - traffic_ops/bin/tests/ - Comcast apparently uses this, they would need to be asked to stop that before it can be removed - It does, however, duplicate a GitHub action (sort of - GHA does all Go unit tests at once and doesn't report per-component stats) - traffic_ops/etc/cron.d/, traffic_ops/etc/profile.d/ - Use of the former is unknown, should be brought up in a mailing list at some point - Use of the latter was useful in the Goose era of database management but no longer serves any known purpose - traffic_ops/install/bin/_postinstall.pl, traffic_ops/install/lib/ - The latter is only used by the former, which was itself deprecated in 7.x in favor of the Python version of that script. - Therefore, both can now be removed. - traffic_ops/install/bin/convert_profile - Clearly out-of-date script and supplemental info for migrating ATC Profiles and Parameters thereof from one EoL ATS version to another, also EoL version. - Evan Zelkowitz would know best if this has any practical use in the modern day. - traffic_ops/install/bin/install_goose.sh - can be removed - traffic_ops/install/bin/install_go.sh - can be removed - traffic_ops/install/bin/todb_bootstrap.sh - need to get the postinstall script(s) to stop recommending its usage before removal, but it does not serve any known purpose and so is a candidate for removal 3. What is the fate of #7167? - We'll probably need to rework it a bit, at the very least for conflict reasons, in a separate PR that incorporates these changes and obsoletes the PR.
On Tue, Jan 3, 2023 at 4:25 PM Holguin, Eric <[email protected]> wrote: > Consider discussing: > > Are there parts of the project that are not in use or code duplication > that could be removed? In the interest of reducing the amount of code we > maintain. > > > From: ocket 8888 <[email protected]> > Date: Tuesday, January 3, 2023 at 4:09 PM > To: [email protected] <[email protected]> > Subject: [EXTERNAL] 2023-01-04 TC Working Group Agenda and Meeting Notes > If you have anything you want to discuss at next week's meeting, respond to > this email and it's on the agenda. >
