Version 5 (modified by 3 years ago) ( diff ) | ,
---|
Attendees
- TomG, Zach, Eric, Elaine, TomF, Scooter, Greg
January 12, 2023
Agenda
- ChimeraX 1.6 roadmap
- Deprecating Chimera, license support
- Retirement plans
- NIAID new statement of work
- New hardware
- New hire requirements
- Review Action Items listed below
Discussion Notes
- Email filtering with ProofPoint
- Security audit wants CGL email to use ProofPoint
- Currently it silently discards Python attachments
- Other UCSF ProofPoint users (e.g. Dave Agard) has had trouble with mail going to spam folder.
- ChimeraX 1.6 roadmap
- Next release planned for May 2023, with release candidates in April.
- R01 annual report due 6 weeks before award date which is Sept 20, so early August.
- Developer meeting will trim down current 1.6 roadmap goals to manageable set.
- Deprecating Chimera, license support
- Decided to continue selling Chimera licenses but add language saying there is no support, no development, no future releases planned, possible loss of web services.
- Add banner to Chimera web page saying to use ChimeraX.
- Retirement plans
- R01 grant funded for 4 years, Sept 20, 2022 - 2026
- Elaine, Eric, Greg, Tom G, Zach all plan to work that full period.
- Scooter plans to retire in 2 years.
- Tom Ferrin plans to reduce work from current 3 days to 1 day per week.
- RBVI future plans
- Should we pursue finding another PI to take over RBVI projects?
- Would need support of majority of Pharm Chem faculty.
- Other option for RBVI continuing beyond current 4 year R01 would be to see if Altos Labs (Tristan Croll) or CZI Imaging Institute wants to host future development.
- Tom and Scooter will talk to dept chair Michelle Arkin about lab future plans.
- Computer security audit
- 52 security actions identified over past year, all but 3 completed.
- Has taken more than a year and a lot of Scooter and Tom Ferrin's time.
Action Items
- Clean up VirtualHosts on our web servers -- Greg/Scooter
- Document new vpn setup on Linux -- Scooter
- Audit followup -- Scooter
Note:
See TracWiki
for help on using the wiki.