...
- Mark Phillips, Kate Wittenberg, Jefferson Bailey, John Kunze, John Chodacki, Ricc Ferrante
Goals
Managing meetings, calendars, and communications.
Discussion items
Item | Who | Notes |
---|---|---|
Announcements | - rf: Smithsonian update (DAMS initiative). Tech WG: The IETF has new leader and; moving forward with open access, with general approach of assigning arks to everything | |
Calls for papers, submission deadlines, upcoming meetings: Calendar of events | jc: is anyone going to Open Repositories - John Chodacki has ; I have participated in pre-conference discussion iPres 2022, Sept - Jefferson going. Others?
| |
Any news items we should blog about? | Ideas - progress to date, planned posts on updates to spec. jk: The spec update post is in draft, ; a heads up that newsletter is scheduled for 3/16. jb: Another idea : for a blog post from IA is assigning ARKs from a shared system; Jefferson and Ricc for our respective organizations. rf: SI might be able to do a post as well | |
Onboarding Document Overview | Kunze | Started Google doc, will move to Confluence. Covers meeting invites, wiki and other platform access, group assignments, group-wide emails, etc. Will need to include offboarding, too. Noted that shared ownership for documentation needs to be confirmed. JK suggested KeyBase as a mechanism for sharing controlled access files. Need to explore a little further. Force 11 - does not require paid access. mp: my sense is this should live on the confluence wiki rf: agreed jk: my only hesitation is that we were once moving away from confluence mp: this seems to make sense administratively jc: rights management with the wiki is a little easier than with googledocs; what about password access? jk: what about keybase? jb: we use PGP encrypted files for 1 to 1 sharing, but otherwise have no special secret sauce jc: Force11 uses shared 1password vault, doesn't seem to require a paid account |
Suggestions for managing meetings/calendars/invitations | Phillips | Group discussion on different options for scheduling of recurring events (such as this meeting.) Personal Zoom account of the chair has worked but is not optimal way approach. Other platforms have ability create a standing rooms. Further thoughts and suggestions. Will consider creating a G-Suite on Google shared from where we generate meeting invites etc. and bring back ideas to the group. mp: do people have suggestions on meeting invitations? or do it the usual old-fashioned way? |
Discussion of communication strategies between ARK Groups. | Phillips | What models might we try for representation/communication between groups and from groups up to the AG. Liaison from AG sits in on other groups. Another option, WG chair sits in on AG meetings. Group agreed WG chairs invited to become AG members. How do we approach communicating between meetings. Broadcast emails to multiple working groups has a problem of replies bouncing if working group members reply. Slack or other platforms? Enables members to create their own channels around topics and breadth of involvement. mp: what about communicating to and between working groups? |
Role of chair | Phillips | Duration to run on the calendar year, two years? Succession planning would require is filled vice chair. Should participation in the AG require a commitment to serve as chair/vice chair at some point? mp: when do we look for new chairs? i'd like to suggest they run on the calendar year |