Fix container submodule

[bbartley]

The container-ontology submodule was previously taken from @rpgoldman 's private repo. This PR replaces the submodule with the public fork of the container-ontology.

[bbartley]

@rpgoldman this PR is a minor change to the project organization that doesn't affect any of the code; I added you as reviewer just in case you have other plans for how the PAML repo should be organized--I know you have actively been developing the container-api in the last few days

[rpgoldman]

How about I add a paml branch to the repo, and then you can track that branch in the submodule?

[bbartley]

Hi @rpgoldman ... that should be fine as long as I have write access to that branch. I want to be able to edit the container turtle files and submit PRs to the container ontology, even while working in the context of the large PAML project space.

[rpgoldman]

Hi @rpgoldman ... that should be fine as long as I have write access to that branch. I want to be able to edit the container turtle files and submit PRs to the container ontology, even while working in the context of the large PAML project space.

What I was trying to suggest was to give PAML users a relatively stable branch to deal with, for people who are not editing the container ontology.

I believe that’s compatible with what you want, but you should check out the sub module, cd to the directory, check out main , make your own topic branch, and work from there.

Then, when we have something we are happy with, we can update the paml branch to point to that, and Dan, Jake, etc. would all get that.

[rpgoldman]

@bbartley ping?

[danbryce]

@bbartley This is pretty old. Rebase or delete?