I attended Workshop 3 of Project Bamboo in Tucson Arizona this week. I think I’m beginning to understand it, though understanding what Bamboo is was one of the favorite subjects of conversation of the meeting (so I’m conscious that . There is a deliberate ambiguity to the project since they are trying to listen to the community in order to become what we want rather than what we suspect. Some of my takeaway thoughts:
- It is being structured as a consortium. Thus the long term sustainability model is that universities (and possibly associations and individuals) will contribute resources into the consortium and get back services for their faculty. This seems the right way to get to a level of broad support.
- One thing Bamboo will do is develop shared services that participating universities can use to deliver research support.
- One of the challenges is figuring out how to listen to the community. The stories are the mechanism being used for this. Scholars are contributing stories of what they do and what they want to do. In some cases the stories are being contributed by people who talk to faculty.
- Recipes (like those we developed for TAPoR) will be a key way to connect stories to the shared services. A recipe is a way of abstracting from a lot of stories something that can be used to identify the tools and content needed by researchers to do useful work.
- Bamboo probably won’t build tools, but they will build and run services with which others can build tools. Bamboo may be the project that runs SEASR as a service for the rest of us, for example. We can then build tools with SEASR for our research projects.
- Bamboo is talking about running the shared services in a cloud. I’m not sure what that means yet.