Skip to content

Conversation

@cbaycity
Copy link
Contributor

@cbaycity cbaycity commented Oct 8, 2025

This removes a lot of Tumult Labs material and switches it to Open DP specific material. Note: This should probably happen before the next release of Tumult Core. With some of the links broken to Slack, Gitlab issues, and ect, we could easily confuse users.

@dasm, @TedTed, and @tmager, I'm not sure what can and can't be removed that is Tumult Labs related. For instance, can the 2025 copyright be removed or not yet? I've taken an ax to it in this draft PR. Let me know if I need to reduce back a bit. I think that the License update and link updates are required.

@cbaycity cbaycity self-assigned this Oct 8, 2025
@Maegereg
Copy link
Contributor

Maegereg commented Oct 8, 2025

This should probably be a few different PRs, as right now it's mixing together a few fairly different changes.

Dropping all the copyright headers seems reasonable to me (as far as I know they're not legally load-bearing), but we should probably check with the other OpenDP folks first.

Let's hold off on deleting .gitlab-ci.yml - there's a few other things that I think it makes sense to get rid of at the same time.

"""Common utility functions for benchmarking scripts."""

# SPDX-License-Identifier: Apache-2.0
# Copyright Tumult Labs 2025
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all these removals seem to leave empty lines or empty comments (like (/* */ or <!-- -->)) which should probably be removed

@Maegereg
Copy link
Contributor

This should probably be a few different PRs, as right now it's mixing together a few fairly different changes.

At a minimum, the copyright changes should probably be their own PR, and I think it would make sense to separate out the removal of old CI files (which I'm already planning to handle separately). Everything else (mostly updating old gitlab links) can probably go together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants