Does anyone have existing institutional policy guidelines for staff who contribute to open source software projects? A group at the California Digital Library is looking to learn from prior art in dealing appropriately with non-technical things like licensing, intellectual property, legal policy, cost/benefit issues, etc. It would be great if any of you have something like that to share. -John