Skip to content

Propose moving alab_control into alab_one #84

@mattmcdermott

Description

@mattmcdermott

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions