Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Propose moving alab_control into alab_one #84

Open
mattmcdermott opened this issue Mar 12, 2024 · 0 comments
Open

Propose moving alab_control into alab_one #84

mattmcdermott opened this issue Mar 12, 2024 · 0 comments

Comments

@mattmcdermott
Copy link
Collaborator

mattmcdermott commented Mar 12, 2024 •
edited
Loading

We should discuss moving alab_control as a folder or package within alab_one, as it would simplify management of our code.

It's not clear that alab_control is used by any other labs/groups than ours, so I don't think this would take the code away from anyone.

The only downside I see is not having a way to publicly show what we work on, but IMO that is only a small con.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mattmcdermott