Leading a University Open Source Project, the fifteenth installment of the Impact of Open Source Software Series, was posted on October 17th, 2007, by Gary Schwartz who currently serves as Director of Communications & Middleware Technologies at Rensselaer Polytechnic Institute and is also serving as project manager and spokesperson for Bedework 1 , the open source, enterprise calendaring system for Higher Education. Thanks David for a great posting!
In his posting Gary starts off by providing some background on the Bedework project highlighting its roots in University of Washington's UWCalendar project. Much of the posting was flowed from the project requirements, which included:
- Implementation is consonant with our core competencies in Java/J2EE programming, XML, and web interface design and construction.
- Open source - no license or usage fees
- The ability to distribute administration and control to the event owners themselves is crucial in a university environment.
- The code must provide complete, well-defined APIs which are scrupulously honored, with no local dependencies (authentication, policies, etc.) The packaging must allow competent professionals to easily install the package and to get a demo version running with minimal confusion and frustration.
Gary treats these requirements in terms of how well they were articulated and the challenges they posed the organization. For example, he talks a bit about struggles with IP issues (letting go of concerns around commercial activity), establishing a development community, managing competing demands, and meeting release dates. Gray wraps up the posing by indicating that the Bedework team has benefited from the relationships developed with other institutions.
- 824 reads
