| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Quick updates/questions Anything from slack to discuss? | Do we open SILS News listserv to subscribers outside UC Libraries? Pros/Cons? Document decision for future reference. Cons: more subscribers to manage. There is overhead in managing error reports, adding and deleting people, etc. Reminder to use the Com Leads, PM Leads or Ops Leads slack channels whenever possible rather than threads with individuals. Revisit turning off Comments decision.
| 10 | All | Re: opening SILS News listserv: No, point people to public-facing wiki. Re: Comments On? Whose responsibility is it to answer comments? We turned off comments because we wanted the footer to be higher up. What’s the best way for someone to provide feedback on decision pages? Leave Comments off. Revisit if needed later.
| SILS News will remain available to UC subscribers only. Other interested parties can follow SILS progress on Confluence and the website. | |
| 2 | (Com) https://uc-sils.atlassian.net/wiki/spaces/SP4/pages/517210559/UC+Libraries+SILS+Project+-+Phase+4+Draft+page | Discuss Confluence site Information on Confluence may be unintentionally inaccurate or misleading or confusing or controversial at times. This could cause problems when the content is read/interpreted by campus viewers. How can we address this? Will be a case-by-case basis. Come up with principles, best practices. | 15 | Ben, Adrian | Just in from Slack: “Elizabeth, our chair for Fulfillment FG, was wondering if the decision pages that are not yet "ready for primetime" are able to stay locked down vs. being made public when the whole site goes live to the public? This is just for things where a final decision has not yet been made. Trying to prevent "too many cooks in the kitchen"“ Confluence shows SILS work in progress by design. Open and transparency is a foremost goal! We agreed not to restrict any content on Confluence. We want staff to see the sausage-making so they are following the progress of SILS decisions, but we don’t want to confuse or mislead them with the status of the content, i.e., it’s not done, not verified, etc. Best practices and principles: Err on the side of sharing as much as possible. Use Google shared drive for content that you are not prepared to share yet. Call out content that’s not final/not verified as specifically as possible. For example, if a page has one fact that needs verification, call out that one fact as “in the process of verifying” or similar statement.
| | - Ben Alkaly (Unlicensed) will draft some principles/best practices for sharing Confluence content and annotating where content needs verification.
|
| 3 | Project Communication Matrix | Review draft of Communication Matrix Anything missing? Where will this live? For now, it’s being used as a reference for the communication flow diagram. | 5 | Adrian, Ben | | | - Review and edit Project Communication Matrix by 5/28 Ops Leads meeting.
|
| 4 | (COM Leads) Ongoing checkin | Is anything blocked or behind schedule? What deliverables are coming in the next week? Any decisions, consultations or approvals needed in the next week? Do you need anything?
| 10 | Ben, Adrian | Nothing blocked or to report other than what’s already been covered on this agenda. | | |
| 5 | (Com) SILS FAQ | Melvyl and Related Services in SILS Lena and Christine answered some of the FAQ questions. | 10 | Ben, Adrian | Hold for Tuesday 5/26 | | |
| 6 | (Com) Slack channel for cohort members to thank each other | Purpose: encourage members to recognize each other’s efforts showcase the good work that’s happening facilitate team bonding. Mine this channel for possible SILS News, townhalls, project updates, etc.
If we agree to add this channel, add to Communications plan and name the channel | 5 | Ben, Adrian | | SILS-Kudos is the name of the channel. | |
| 7 | (COM) SILS News Communications Phase 4 Editorial Calendar | Awareness of upcoming communications and anything needed | 5 | | | | |
| 8 | Parking Lot | | | | | | |
| 9 | | Total | 60/60 | | | | |