This was originally posted on the Project Bamboo wiki, at https://wiki.projectbamboo.org/display/BPUB/W3-+Implementation+Proposal (https://wiki.projectbamboo.org/x/qARL) by Quinn Dombrowski, last edited Jan 23, 2009.
Straw Proposal Outline
- Midway through an 18-month planning project
- Expecting to submit implementation proposal in October
- Big goals: consortium of institutions/organizations to develop what's of most value to support evolution of research using digital technologies & submit proposal at end
- 2010: begin implementation (if proposal works)
- Keep at a forefront what Bamboo does to move forward teaching and research
- Seen very important modifications/additions from where we started
- Community itself defines levels of community responsibility
- When you hear about consortial model, tell us if we're getting that right
- Firmly respecting the "we" - different kinds of constituencies, audiences, etc brought to the table
- We're working on building a common language
- From what we've heard from workshop 1, there's a lot of interest in what we're trying to do here
- This could be 7-10+ year effort
- Framing it as something that could end is important
- Moving in dimensions that pull at each other--services infrastructure, exploring/demonstrating/learning how technology can inform and shape teaching/research
- Important to not have it get too big
- We want implementation proposal on 3-year timeframe-- right level of concreteness, ability to deliver
- Proposal will be more compelling if we tell that larger story
- Focus bulk of work on what happens in 3-year timeframe
- Major areas of work we can imagine submitting as part of this proposal
- Infrastructure of shared tech services for arts/humanities/interpretive social science
Could be in a "cloud" model
- Scholarly network for people/projects/tools/services
Driving it from the people side first is important
- Exploration and Demonstration "Labs": Sandbox and Support
- Exploration of interoperability possibilities between tools/content sources/infrastructure
- Give faculty and others a chance to learn how to use these tools to build mashups, share hands-on training materials and projects
- Stories/Educational Opportunities/Best Practices Hub
- Build and Sustain Bamboo Consortium
- These areas may be reconfigured/resized in the proposal (see chart)
- "What is Bamboo" poster (1a) - many of same themes as mentioned above
- Workshop 2 - series of working groups
- Relationship between major areas of implementaiton proposal and working groups:
- informed by stories, shared services, tools and content
- scholarly networking
- exploration and demonstration: tools and content, education, institutional support
- stories/educational/best practices: stories, educational, tool and content partners
- build and sustain - institutional support
- We said we'd publish a number of documents - these will be folded into the proposal
- We want to use the proposal as a major driver for this work
- Services roadmap: important for how we can map it out, based on stories/activities, a series of services
- Consortium discussion will feed into smaller document
- Ecosystem of partnerships- many of you are the leaders of these efforts
- Tie into, build, reinforce, leverage, support these efforts
- As we make things more concrete, we'll be able to put actual figures on this
- Re: financial crisis- is this the time to do this? Do we huddle back into our institutions, or is this proposal more compelling-- working together
- Scale back, phase over longer periods of time
- Value proposition becomes important (institutional support group) - what is the institution getting? what's the value to whom?
- Build, plan, explore - important to keep in mind vis a vis roles for consortial model
Q & A
Q: We've had to take feedback to our institutions and tell them this is an iterative process, this is what the idea is, this is the plan, at the end of the 5 workshops there'll be implementation
At the last meeting, if I take back a plan saying that in the next 3 years there'll be an infrastructure of shared services, we'd have a response from the chancellery who'd been involved in every stage of national projects, and we'd be pushed to actually say "tell us more specifics"
We've taken all this info from the wiki exercises and had meetings, so what would be good in discussing the implementation proposal and consortium model would be what was suggested by support group: some really strong statement from leadership council that would back up the info we bring home
We're with you - we're convinced there's a lot there
But our institutions need more info to commit resources in all the ways Chad mentioned, we need something really concrete and coherent
- Different ways to explain/discuss value proposition
- Paper ways of doing that, and video stories too
- Services piece requires a lot of work still. Say how that's been driven and informed by the whole process
- Need to push on materials used to tell the stories in different ways
Q: This is just a heuristic exercise
"Technological sublimity" - it can be everything
Have you articulated what Bamboo will NOT be?
Are there borders? Important to say where boundary lines are
- This came from W2 - while I talk about standards, we decided it won't be a standards organization
- Needs to adopt standards as part of its community, select some specs, could select a profile (here's 10 if you're going to launch an X)
- Portfolio of guidelines
- Bamboo should draw attention to activities in that scope
- Vis a vis 'build' part - PB should build as little as possible
- Reuse what's out there - there's a rich set of things that already exist
- Only develop things when something else just isn't available
- You could say that Sourceforge garage projects may or may not count
- Should use technologies we have been using in the community, being developed by community
- Another area of focus - related to Euro projects- notion of in these large infrastructure projects (outside US) - where does PB fit in? Is it doing what DARIAH is doing?
- How do we advance through shared tech services - advanced != make content, make tool
- Enabling possibilities, connections - how do you hook things together and tackle those problems
- It's not sexy - it's trench work that a handful of IT people in this room might really enjoy
- But there's other things we could do that aren't being done elsewhere that we should pick up
- DAG: In W1, Bamboo should build "The Ultimate X" - this is not what we're trying to do
- Would be a very difficult thing to do
- In W1 discussions (also W2) - this is something that comes up in discussions, but PB isn't trying to solve tenure problem or what gets recognized
- It's important, but it's not our primary focus
- Strong proposal would talk about not only what we;re going to do, but also what we're not and why
- Help with scope definition (short term 3 years, long term 7+)
- Walking into an airplane, and the pilot says "where do you want to go today?"
Q: Might have misunderstood, but we just heard you say you're not going to be building things...
- CJK: We're gonna build as little as possible - different than not building things
- Q: Wasn't one of your goals a "cloud-based environment?"
- DAG: More on this tomorrow, but idea that we're making a distinction between tools/applications and services that tools/content sources could draw upon
- Part of our ongoing discussion, part of our value proposition is that there's valuable tools out there, can't we help invest - moving from lowest to highest level of value - to create shared services that could be used by different people
- Cloud model - is one way of building out that
- Build up a language to explain what we mean
- If we can enable reuse and connection and understanding and ease around existing applications - we're trying to help with that
Q: You're going to build as few tools as possible, could you talk about intent for offering particular services? where's that going?
- Is there intent for PB as a consortium to offer particular services or, do it as little as possible
- DAG: With services, there's strong arguments for offering a set of services ("web services" to general community, cloud model = so each institution doesn't have to run a set of things on their own)
- Available and guaranteed services to participating members of that community - that might be a more sustainable way to handle these challenges
- CJK: This gets into why consortial model talks about what resources an institution could contribute
- An institution could say "we're already working on this, might as well"
- Multiple institutions could offer storage - this benefits institution that doesn't have that resource
- Someone received funding for a project, then realized they had no infrastructure to make it happen - how can we help with that?
- We need to explore those opportunities, figure out what things we shouldn't do
- This is different from Building Software
Q: Distinction between facilitating services and availability vs. actually providing them
In your model, if Bamboo provides services, you'll need an operations level
Implications of getting into service provisioning business, ramifications not just for organization but for whole landscape of people who might be interested/collaborators
Q: For PB being successful in the long term, participant institutions are at an advantage because their faculty are in a position to embark on research efforts and teaching efforts that they wouldn't be able to otherwise
Another way of framing the success - speaks to people like provosts who are allocating resources, strengthens institution, its ability to attract/maintain the best faculty
Don't overlook that formulation
Going back to wise statement about needing to build as little as possible, would urge PB to think in build/not portfolio set of activities around evaluating and recommending
One of the problems right now is there are too may choices, none of which have reached critical mass, most of which don't interoperate
What's needed (nasty position to be in) is to pick winners and losers, or coordinate community activity to do that
Urge you to include that in your toolkit of infrastructure building activities
Role and appearance of the people who are contributing, and the services/tools/etc layered on top
Layers allowing those of us who aren't from resource-plentiful universities
My institution's economy relies on high price of oil - we don't have much money at all right now
I like the ability for institutions to commit different kinds of investments, allows my smaller university to stay in the game
Details of Straw Proposal Outline
- Some of the major sections of the proposal:
- "Value proposition" - statement of need and opportunity, what's the story that can be told to institutions?
- Investments we're already making in humanities scholarship, how that can be leveraged
- Important to have a case statement or value proposition as soon as possible after this workshop
- What do partner institutions look like? What are their roles?
- Work plan and budget
- Series of documents that may overlap with parts of the proposal
- Current work from working groups - inst. support talked about key questions around value proposition
- Exploration/labs is a new way of framing this - there's multiple working groups pushing towards this
- What the future working groups will be towards workshop 4?
- Stories working group is trying to generate scholar stories so we can derive activities
- Tools/content and services/interaction are important
- Trying to figure out the right kind of alignment
- Does there need to be reconfiguring the charters of working groups?
- Other kinds of discussions that have to happen
- Value proposition- so leadership council is trying to shape that
- Long-term vision: trying to talk to other community leaders
- Shared services - need to have series of discussions with other technical leaders in SOA and other areas
- Balance between enterprise and other approaches
- Importance of connecting w/ other tech consortia, info led by digital humanities centers
- Important to begin discussions w/ institutions, might be valuable to talk with institutions at higher level
- Map of where we might put focus between 3 and 4 - not focusing on everything in detail
- Value proposition is important, long-term vision
- Major areas of work: lots we want to push towards; if we're still framing work that way at the end of this workshop
- Begin discussion w/ other institutions about how they see their roles
- Workplan/budget: post-workshop 4
- We need info before we can write that out
- We haven't fleshed out between 4 and 5 - taking info to then revise the work plan
- After this workshop, a quick reflection on what we've heard/learned, and send out an update
- Slide with pink boxes: these resonate with different people based on institutional interests
- Could start by talking about exploration labs - ways to build and invest in centers of local campuses
- Shared services:
- What is meant by "services"? In W2 we tried to do a more narrow definition - building discrete modular reusable web service,s used to discover and consume (from tool and data sources)
- Not broader definition of all services and applications
- Idea of cloud-based approach: we think we're going to derive services of high value to community
- If there's 10-20-50 members of community who are going to want to use those services, what's the best way to provide them?
- Does each institution do local instantiations? One or two institutions to whole community?
- Could be corporate or other partners brokered by Bamboo?
- Services could range from a whole set of things, could look like common services available to developers, or services that deal with storage, authentication, etc
- Complex topic: any group in the business of providing services people are relying on, have to think carefully about how one does that
- By banding together, we can provide some common services/efforts that many people need, rather than local instantiations
- Still in the process of figuring on based on analysis of scholarly practice what the services should be
- By the time proposal is written, going from what could be done to what PB will do
- Defining, then mining/grouping scholarly activities
- Finding key candidates, then figuring out business model
- Some comes from the model we have - defining and mining comes from W1 + stories group to derive set of activities that we think are particularly important to build services around
- Partnership and interplay with tools/content projects is fundamental
- Discussion with existing developers: what would be of value to you, so you don't have to build that into your future roadmap of software development
- Services roadmap: can draw a picture of what's needed/possible, what are areas of high value?
- What are we going to get by investing in them?
- What's the business model for how we provide that?
- Fair amount of work that has to happen related to working groups and program staff
- Scholarly networking - thanks to John for yesterday's presentation
- Yesterday: validating that this is important
- Heard this strongly in W1 - something fundamental that needs to be done; but what is the "it" and how is it done?
- Importance of people finding people they can collaborate with
- Relatedly - finding and discovering other kinds of tools/projects/content/services
- Trying to think of a model where we can weave this together to allow discovery and sharing across a broad community
- The "pub problem" - I find out about the best things when having a drink with someone after a workshop
- Connected across places/spaces w/o being face-to-face
- Existing tools and platforms that are out there for scholarly networking: can we use some of those, what will that get us?
- Connections to what's happening elsewhere that provide platforms for higher education
- Good opportunity for alignment between PB and Sakai - high value to communities
- Connections to how scholarly networking derived from and adds value to scholarly communication/societies
- Conversations with more people leading those efforts
- Exploration labs:
- Opportunity for this group to help figure out if this is the right thing to focus on/conceptualize
- Number of different ideas layered here
- What PB is finally trying to do - at each of our campuses/people we support, within 3-5 years, when a faculty member/student are looking for some way to learn about digital tech, scholarly practice, figuring out which tools to use - should be substantially easier/better to do that at local institutions
- Centers libraries, IT where you can go, be able to learn/explore/build
- Should be easier to use the tech so you spend most of your time on the teaching/research, less time mastering tech problems
- Help with some of those issues, the way the rich set of tools/applications/content sources can be interconnected
- Guidance around narrower set of infrastructure we provide to the community
- Going from interoperability to how research is changing
- Is this the right way to conceptualize this? Or that every institution would do? Or groups of institutions?
- Stories/education op/best practices
- Could be manifest across whole PB community
- Gathering, documenting, sharing these
- These materials serve a number of purposes: growing body of materials that can be shaped in different ways
- Discussion about interconnection of these stories and how to look at practices that cut across disciplines
- Things that can benefit students and faculty
- Stories as a way to help us derive a sense of the best investments around services
- Ways that can help institutions make a more compelling case of the value of doing this work
- Stories/education materials are service particular ends in some cases, from improving research to building infrastructure
Q: Exp labs - centers and activity centers, does the money go to the centers for projects, or service helping provide things?
- Want to figure out how people who are doing that investment, what they need
- If someone is trying to lead that across multiple institutions, that might be a better place to distribute money than giving it to each individual institutions
- This is preliminary, based on shape of proposal/total resources
Table Discussions of Proposal
- Hard to respond to the proposal; we were intrigued
- A lot was about political organization; our natural response was trying to imagine what such a group could do
- Where between a completely social consortium that does no building, and one that's just a development
- Somewhere in the middle
- Tension between focus of small group of builders and the rest of the consortium
- How do we make sure we don't come apart with builders doing building, and losing connection w/ connection with scholars
- Focusing on point 3 - keeping phase 1 in mind
- Most important things, building on value proposition of what's in it for my institution
- Looked at shared services, scholarly network
- Needs to be creative link between form of services created and how we need to build the network because there's so much work needed to be done nationally
- Bringing together groups of people working in their institutions w/o knowing larger context
- Added an item related to value proposition - is this the time and place to add measures of success? Evlaution/assessment piece
- When we're selling it, we can say "here's how to know it was a worthwhile investment
- Building on idea of broadening reach of project, possibility of making query to various institutions with idea of asking what they'd be willing to contribute
- Not just what do you want, but what are you wiling to contribute
- What do you want from other members of the project?
- Outreach to companies (commercial) as well as our "safety zone" of academic community given realities of financial situation
- companies might have more resources available
- Would like to see a pie chart added to wiki - what sort of representation by disciplines at these workshops
- success of project going to depend on faculty vehicle - better idea of who's showing up, where they're coming from
- Kept coming back to issues of scope
- Hard to evaluate proposal w/o agreement on scope, what scope of consortium would be
- We have ideas, things like "wouldn't want to provide services, S3 Amazon Cloud Provider" but understanding statement made yesterday that we want to reuse rather than build wherever possible
- From tech point of view, might be more possible to provide services that people compose into tools rather than a bunch of tools
- Those expectations need to be set so people coming to community need to understand where their needs fit in
- Ties into value proposition and long-term vision
- Focused in on scholarly networks and exploration labs
- Discussion around whether arrows between areas was scholarly network - is it on its own, or does it connect other areas?
- Thinking not just discovering info/resources, but what happens through use, networks become smarter
- Do scholarly networks lack spaces for collaboration?
- Scholarly networking developed via the exploratory labs, or parallel thing?
- Could there be a help desk that scholars could go to to find things quicker and faster than a discussion list?
- Exploratory labs - discussion about whether these, based on our own experiences, research labs - spaces where scholars can get together, and also pedagogical labs
- Should those be separate or unified?
- Are exploratory labs a tension between integrating IT into existing pedagogical forms (lectures, seminars) or developing new pedagogical forms?
- MIT moving way from giant lectures to smaller spaces (whiteboards, small tables, clickers)
- Exploratory labs are physical spaces at universities, or virtual and allowing universities to connect
- What's happened to standards and best practices area that existed in W2?
- Need to coordinate and agree on interfaces
- If we need to link data, we have to recommend ways to do it
- This cross-cuts a lot of the areas, but hasn't been explicitly mentioned in any way
- Need to articulate how that fits in
- Two principle areas - stories, interested where this fits in
- What's meant by that?
- Consider a variety of views
- One consensus: collection of use case scenarios and people's needs and pieces of stories should continue to feed into the processes of design and build
- Important to articulate that in the proposal - not just gathering the stories, and then building, but a constant iterative revisiting and collection of new inputs from users too
- Second area: value proposition(s) - identified 3
- Reaffirmation of original project goal of reversing amount of time spent on building tools vs doing research
- Second: enabling and supporting the 95% of scholara who don't normally work on DHum to be able to access and work with these tools/services in the normal course of their work
- More speculative - potential to open up transformations for ways of working in the Humanities
- Not just enable them to do what they're doing on a computer, but work with much more diverse range of materials. Produce new sorts of outputs, be assessed in new ways
- How the evaluation is to be determined
- Focused on value proposition
- Really needs to start saying what it is
- Need to be more specific concrete things on the table
- Need data - can't do computation w/o it
- One of the corporations that exist, challenges they pose - what sort of opportunities do those challenges represent?
- References to certain kinds of tools that we can agree on have general utility across disciplines
- Lots of things involving text processing For this to have clearly perceived value - need to start saying what those things are
- Also some consensus that just from social perspective, begins to be important to go back home after receiving funding to go to these things, "here's what we're going to do"
- There is no art without constraint
- Haven't yet found the constraints on what could be done here
- All has a blue-sky feel to it
- Never been involved in a proposal w/o fairly concrete sense of finiteness of resources
- This forced us to make hard choices about what we're going to do
- Lack of that is impeding our ability to push forward
- As far as stories, we want to encourage you to include stories about success but also failure and frustration
- Out of these can come your value proposition
- Where are you getting your stories from?
- Other communities outside the humanities that have faced these issues, had successes and failures
- Would be useful to learn from their stories, not repeat their failures
- Exploration labs - useful to think concretely
- Think hard about where are the labs now for exploration, how can they be pulled together, work most efficiently, convergence of humanities centers i-schools, libraries, dig hum centers
- Should be drawn together, lab should be spaces where different generations of scholars work together on projects
- Finiteness of resources, and realities of what have to be accomplished
- Have to tel stories about people who could put resources in
- Need more finite sense of what is involved
- A little concerned that we haven't had that focusing-in phase
- Need to iterate - if Bamboo is ambitious, will fail over and over
- Will succeed only if there' a sustainability model that will allow for tweaking and redesigning
- A lot is learned when things blow up
- 'Prototyping' = 'blowing up'
- Fleshing out things that you've said, these are important issues
- This is why it's a straw proposal
- All of your comments have been captured