[FOLIO-413] Create communication channels for Resource Access Created: 09/Dec/16  Updated: 12/Nov/18  Resolved: 10/Jan/17

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Peter Murray Assignee: Peter Murray
Resolution: Done Votes: 0
Labels: sig-ra
Remaining Estimate: Not Specified
Time Spent: 30 minutes
Original estimate: Not Specified

Sprint:

 Description   

See SIG Participants List, Resource Access tab for details.



 Comments   
Comment by Peter Murray [ 14/Dec/16 ]

SIG communication channels created:

Andrea Loigman - let me know if you want me to create a Slack channel. Details need to be filled in for the WebEx connection information (Michael Winkler or maybe Holly Mistlebauer can add that information). Note that I set up a template for meeting agendas, notes, and tasks based on what the Forum Facilitators do; it makes use of some Confluence macros that make setting up agendas/notes and keeping track of tasks easier. We don't have any documentation on this (yet), so let me know if you have any questions.

Comment by Andrea Loigman [ 14/Dec/16 ]

Thanks Peter. I'll reach out to Mike and /or Holly and see if I can get the Webex info from them (probably as soon as the SIG agrees on a regular time to convene).

Is there a lot of overhead for creating a Slack channel. I actually like Slack and would like to use it. But, I'd hate to have you do the work and then have my group decide not to go there.

Thanks for the meeting template. - One of the first things we'll be doing is picking a secretary. I'll likely have that person reach out to you if they need help.

Comment by Peter Murray [ 15/Dec/16 ]

Ah – Slack channels are by far the easiest thing to set up. I've done that and sent you an invitation to the channel. Let me know if there is anything else I can do to help you get started.

Comment by Peter Murray [ 10/Jan/17 ]

I think this is all set, so I'm going to close it out. If you need anything else, please let me know.

Generated at Thu Feb 08 23:05:35 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.