Export and import to cloud storage

[Glavin001]

[Easy] Users may wish to save their threat models to a cloud service such as Google Drive or Dropbox. Implementing this would require using their API’s and connecting it to SeaSponge.

[MatKallada]

Hmm, - Is this actually useful at all? The user can already save/load from file formats.

-> What is stopping them from dragging it to Drive or DropBox themselves?

To me personally, this is feature creeping, and I'd opt not to include this feature.

[Glavin001]

That's why this is for a later version (v2?) and can be low priority.

Use case: what if I am a student on a school computer (cough ew) and they want to save this to their Dropbox/Google Drive and they, of course, do not have the folder sync setup on their school computer. They could simply login and let the web application handle that syncing.

[MatKallada]

Err - something to discuss during next meeting, but I feel that we're feature creeping here.

I understand that it is convenient but File storage/Local Storage is really all we need.

Definitely, a neato feature but something to discuss.

[Glavin001]

Definitely not a priority.

[MatKallada]

I wasn't debating the priority (which would be low). I was debating whether this feature is worth developing in the first place.

Once again - something to discuss in the future.

[Glavin001]

I was debating whether this feature is worth developing in the first place.

The advantage of having it outweighs the time it will take to implement.
If we implement #13 properly, with base classes and SeaSponge API, it should be pretty straight forward implement for any other destinations such as Google Drive and Dropbox.

Once again - something to discuss in the future.

Yep.

[MatKallada]

It is indeed trivial to implement, however we would be feature creeping. For now, this feature will be placed on hold.

[Frozenfire92]

I think this is definitely worth developing. We have it in our project proposal as a version 2 feature. Thus I think creating a version 2 label and milestone would be the best solution.

[Glavin001]

Not only would linking issues with Github ( #17 ) be awesome, but what about using GitHub's API to actually store our SeaSponge files? Using https://github.com/michael/github we could actually use GitHub as a cloud storage. Hopefully this will encourage sharing of SeaSponge generated threat models and also make it easier to get started and continue modelling threats for projects.

[shirishp]

Apologies in advance if I have misunderstood something. But I think when we create a link, you can always generate full diagram with the link. Given that, do we still need to store the files on "cloud"? I can probably just ping or store the URL in my email and generate the diagram if I want.