...
Erin - FSU said their goal was reducing complexity and for that reason, they are using AWS. But that doesn't make sense for organizations outside the US
...
Erin - I don't think they have the support to be a the main competitor to a community product. The Fedora software didn't solve their problem so they created something that does and that's something to expect.
Este - we're part of the Islandroa collaboration group and it support supports ISLE. We talked about Archepeligo and said the community isn't there and we want to go with the community. We are looking at how to work with AWSS to simplify things. Our org is saying "we want you in the cloud" and it's a good reason to move. I also think the service provider question is important. The expertise we have with Born Digital is part of how we are able to do this. We need to keep the eggs in the Fedora 6.0 basket and we need there to be a community of users in that community.
...
Sayeed - we're being asked to move to the cloud too. But using the cloud and be dependent on AWS and microsoft Microsoft infrastructure and it would be hard to take them out. If you use Fedora 6 in the cloud it gives you some insulation to those hooks. Is that part of the value or values? It can be framed as insurance
...
What will your community do if you need to change directions.?
Scott - some schools might not have options to not move to the cloud.
Sayeed - one of my colleagues has gone to town on researching the terms and conditions of cloud services. ACTION - Sayeed will ask his collegues colleagues to share the info he is compiling in a shareable format.
...
Tim - if you're not worried about lock-in, AWS will save you money. But if you protect yourself, if will not save you money. Sayeed, you should write a breif brief statement we can elaborate on ACTION -
Mark - executive roundatble roundtable at recent CNI (spring) was about this. We could cite that. Lots of similar themes. ACTION - get those.
Tim - this is similar to the publishing use case. It's easy for people to see themselves in. The customer is the product. We should draw these parallels. Even provosts see this and understand it.
Erin - protection is a counterbalance to reducing complexity in our messaging.
Scott - storage people are worried about where things should be stored. Storage and repository people can structure it differently.
Sayeed - we shouldn't cast this as complexity. It's insurance. It's protection from lock-in
Tim - Privacy and autonomy taxes - it is worth the resources for the organization to have these things? But tax is negative. I like insurance or protection better. What is our portability worth to us?
Recommendations - what is missing and what do we do with them.