The Origin of Community
35
1 the origin of community (@ penn libraries)
-
Upload
michael-winkler -
Category
Education
-
view
195 -
download
0
Transcript of The Origin of Community
1
the origin of community(@ penn libraries)
2
a brief timeline of how the pennlibraries are moving to a strategy that
leverages community source software & community participation to achieve its
goals …
3
… you know how to set this up, right? you’re a computer guy …
4
… and so, a short review of what we’ve learned, how we’ve evolved, and what
we’ve left along the side of the road
5
project shopping
6
physically & administratively separate developers, system administrators & IT
support staff, who respond to expressed needs within their own
capabilities & capacities …
7
… produce diverse solutions using a range of technologies to deliver applications & services that are
minimally integrated …
8
… 1 problem + 1 developer + 1 server= 1 solution …
9
… exhaustion of development capacities as support & enhancement
demands overwhelm developers & system administrators …
10
… so, project shoppingled to…
11
project lists
12
library managers create project lists to try & understand development
capacity & priorities …
13
… allowed team-based approaches to projects that would have been out of
scope for a single developer …
14
… while increasing transparency, project lists did little to discern
priorities or provide governance for management or on-boarding new
projects …
15
… “one is the loneliest number that you’ll ever do
two can be as sad as one, it’s the loneliest number since the number
one” …
16
… and so, project listsled to…
17
consolidation
18
bring most developers together with systems & support staff under unified
administration …
19
… provides internal methods for selecting technologies, protocols &
methods …
20
… and a deeper set of resources to deploy for development, operation &
support …
21
… better coordination of diverse sets of vertical applications built on a diverse technical architecture …
22
… and so, consolidationled to…
23
portfolios
24
develop service layers that are horizontally arrayed, addressed
directly, & orchestrated to provide composed functionality …
25
… built on standard infrastructure for virtualization, for enterprise level
development & integration, and for open source release …
26
… but, still a ‘go-it-alone’ strategy …
27
… and so, portfolios arepreparing us for…
28
community
29
a rich community
30
… and in september 2008, the pennlibraries joined the mellon-funded
ole design project & will soon become a founding partner in the
kuali ole build project …
31
… to gain benefits for penn libraries that includes …
32
organize software around workflow, not the reverse
gain format neutrality to improve staff deployment based on function rather than format
deploy more staff to service roles rather than processing roles
assimilate enterprise project management techniques, adopt best-practice from partners
aggregate collection metadata from local and external sources
integrate with university infrastructure for IdM, procurement, data warehouse, teaching & learning
automate manual processes
increase the skills & experiences of staff
raise library IT to the enterprise level
put a tiger in our tank
be a leader in software development on campus & in the community
participate in setting the direction & priorities of solutions
sustain our efforts
opportunities & engagement with other community-based projects
leverage diversity of effort & collective intelligence
control our destiny in true partnership with other libraries, other campus agencies, & with vendors
… some of these benefits accrue directly from the technology, but
most are consequences of participation in the Kuali OLE
community …
33
… and so, community becomes our strategy.
34
and a last thought
