Skip to end of metadata
Go to start of metadata

This is the Bedework Enterprise Calendar System general-purpose wiki.

For more information about Bedework, please visit:

For general information and to download the Bedework quickstart package, please visit the Bedework Website.

  • No labels

1 Comment

  1. Dear Bedework Community,

    Jasig, and each sponsored project, is filled with talented and motivated developers, technicians and administrators all working hard, contributing energy and intellect to develop high quality enterprise systems, and in doing so, are actually supporting their local college or university and ultimately higher education globally. The results of your work benefits not only Bedework, but also our colleges and universities including our faculty, staff and students. Unfortunately many of those who benefit most from the Bedework and the Jasig community's efforts may not be aware how our projects contribute to (and even enable) their daily work, courses, academic and administrative departments, etc. Sadly, not everyone is a developer.

    However, this does not mean that non-technical individuals should not (or could not) become active contributors to either Bedework, another Jasig project or Jasig as an organization. The fundamental goal for 2-3-98 is to raise awareness and appreciation of openness among the members of the higher education community. Concerns about open source are less common today within the IT field, however are still present among our colleagues across campus. Who better to invite into the discussion (and indeed development) than those who are currently using and relying on open source projects? Unfortunately many of these folks may not even know how much they and their activities depend on Bedework or other Jasig sponsored projects. Considering this, I would ask you to look at your own project and your community, and ask two questions:

    1. How many folks on the campus who have adopted bedework are aware they are using not only Bedework, but an open source application or a Jasig sponsored project?
    2. How many folks who rely on Bedework are active participants in your project or Jasig generally?

    If understanding and growth in open source projects like Bedework—and the organizations that support them like Jasig—is going to increase, we cannot limit participation to developers, technicians and administrators. We must include the end-users who can testify to the quality and viability of our projects. If campus alumni review events in the campus calendar managed by Bedework, then your campus' Director of Alumni Affiars, should be a Jasig member, a Bedework contributor and 2-3-98 participant. If your students find out about campus events through Bedework, then I'd like to talk to your Campus Life Staff, Dean of Students and Athletics Director at the next Jasig Conference at the 2-3-98 session.

    Including our campus end-users, who are most familiar with, reliant on, and have come to trust Jasig's sponsored projects, provides us with an incredible opportunity to raise awareness and appreciation of open source, Bedework and the Jasig community. As campus end-users share their experiences with their colleagues and peers, a second level of dialogue will emerge beyond the technology (which, if we can be honest, can actual intimidate, detract and confuse our end-users), enabling campuses to discuss the affordances of open source, not as a technology or methodology, but as a solution to their business and operational needs.

    So I put forth a request—perhaps a challenge! Please seriously consider the two questions I asked above and identify specific individuals on the campuses who have adopted Bedework whose jobs, departments, duties, etc. rely on your project's continued success. Then, send me their names, contact information and a bit about how they use your project. I would like to introduce our efforts (Bedework's, 2-3-98's and Jasig's) and invite them to participate in one of the activities underway with 2-3-98, e.g. Edu2ools, The Logic Tree, etc. If your only contacts are technical leads on campus, please forward his/her name(s) — perhaps you could provide an introduction — and I will appeal to them directly with a similar message.

    I hope to hear from you soon, and remember, sadly, not everyone is a developer!

    Patrick Masson