Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Repo name is a bit misleading for iotedge scenario #33

Open
jiata opened this issue May 1, 2019 · 5 comments
Open

Repo name is a bit misleading for iotedge scenario #33

jiata opened this issue May 1, 2019 · 5 comments

Comments

@jiata
Copy link
Contributor

jiata commented May 1, 2019

No description provided.

@msalvaris
Copy link
Contributor

@danielleodean I think we should change the name, Thoughts ?

@danielleodean
Copy link

yeah it's good point - are we going to separate the IOT stuff into a separate repo though? (still using same approach but full notebooks in each?) if we're doing that in short term, maybe just keep the name, since it can go back to just being about AKS?

@msalvaris
Copy link
Contributor

@danielleodean I was more thinking of keeping the deployments together but maybe it make sense to seperate them. They can be based off the same CC since the overal is considerable. Thoughts?

@danielleodean
Copy link

Yeah was thinking same CC but maybe different repos? as there are considerations like repo name, different architecture diagrams, different performance considerations that might want to have separate readmes also? But if there are too many downsides to this, I'm good with whatever option you all decide @YanZhangADS also fyi

@msalvaris
Copy link
Contributor

Yep, that works for me :) @YanZhangADS what do you think?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants