Skip to content

Consider a refactor for algorithms as packages. #40

Description

@jdaymude

Thinking about the long term sustainability of AmoebotSim development, one of the more brittle and confusing aspects of having a core, public version of AmoebotSim is the way algorithms are included. If this project gets lucky is successful, there might be many groups all over the place who want to make their algorithms available, and it wouldn't make sense for us to be the gatekeepers for what algorithms get to be included in the canonical version of AmoebotSim.

One solution could be to use a package/submodule model for algorithm development. AmoebotSim is the core project maintained in this repository while individual algorithms are published as separate submodules that can be linked in on as as-needed/as-interested basis. From the perspective of the SOPS lab, we could then just be responsible for keeping a list of community algorithm modules in our documentation that people could download.

I haven't yet completely thought through what this would take to implement, but it would certainly build on the work done in refactoring algorithm registration. Needs further investigation.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    diff-hardDifficult or time-consuming issue.docsImprovements or additions to documentation.improvementImprovement or optimization of an existing feature.need-infoNeeds further information before proceeding.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions