Posted by bfroehle on February 3, 2011 at 9:00pm
Given the large number of Drupal sites at the University of California, Berkeley, it seems that there must be a lot of duplicated effort in both module and theme development.
In the realm of module development, I know that many of us have struggled with integrating CalNet Authentication (CAS) with the CalNet Directory (LDAP) and something like the RealName module. Others must have struggled with properly integrating the Berkeley Events Calendar with their site. There was a UC Berkeley starter theme floating around (based on Zen) for a while.
Would anybody like to join me in curating a selection of (custom) modules and themes which are broadly useful to the campus community?
Comments
UCBEvents
To get the discussion rolling, I'll share the source for ucbevents, a module which grabs event data from events.berkeley.edu and shares it with Views. I'd like to iron out any remaining bugs and post it on drupal.org. (One slight hiccup is that I don't have CVS access).
It's a little rough around the edges --- for example, there isn't a UI written for it --- but it's stable enough to run the Upcoming GA Events block and page on the Graduate Assembly website. I'd rate it as version "1.0-RC1."
Currently it exposes the event title, subtitle, short description, start time, and event types. (In particular, it doesn't expose the event end time or location). There are 6.x and 7.x versions of the module available.
ucbevents on d.o
Would the functionality be useful ONLY to people interacting with events.berkeley.edu, or is it general enough to be used with other calendars? If the former, would it be more appropriate to host this module on drupal.org or in UCB Berkeley's subverison repositories? I can see arguments, both ways... Probably it woud be best to host it in just one place, not multiple places.
It's utility is limited in
It's utility is limited in that it expects events to be returned in the XML format specified by events.berkeley.edu. I'm not sure if they used a canned solution or wrote their own thing from scratch.
I certainly agree with keeping it hosted in only place. The pros with hosting on d.o is that it's the first place folks will look --- I'm not sure everybody knows about Berkeley's subversion repositories. The con, of course, is that the module is likely only to be useful to the Berkeley community. Perhaps the ideal setup would be a "berkeley" project on d.o which would either contain all of the generically useful berkeley modules or a pointer to how to get access to Berkeley's subversion repositories.
Migrate to d.o
Since "The Great Git Migration" landed, I've moved this project to http://drupal.org/project/ucbevents
Great!
Bradley,
As you may know I have created a managed Drupal hosting service at UC Berkeley. The service offers a UC Berekely Drupal platform. The platform is a build of drupal core including our "supported modules" in sites/all/modules. (There is one change to Drupal core: the php input filter has been removed.) CAS and LDAP are included in these modules.
I have archived your CAS patch and I am eager to add it to a future release of the platform. I would like to add this functionality not as a patch to the CAS module, but if possible, as a separate helper module. I can't remember, but your patch might actually be related to the never-released LDAPSync module. Basically I want to implement this in such a way that we avoid having to re-patch an existing module every time a new version is released. Perhaps we could work together on releasing and maintaining a modified version of LDAPSync that works with RealName.
There is a Zen theme called UCBFlex which was done by Matt Olenick (when he was at UC Berkeley--now he's at ChapterThree.com). It could use some work and it is not currently part of our platform. I will provide access to this theme to UC Berkeley employees.
The IST Drupal platform is available to anyone with a UC Berkeley CalNet ID. If you would like access to download it (you also get access to the IST Drupal User's Manual) please email me at my ucb address (https://calnet.berkeley.edu/directory/) or via the drupal.org contact form and include this completed template: