Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Mark Phillips, Kate Wittenberg, Jefferson Bailey, John Kunze, John Chodacki, Ricc Ferrante

Goals

Discussion items

ItemWhoNotes
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
jk: as discussed in the Tech WG, the IETF has new RFC Independent Stream Editor with different requirements and/or style for the review process. WG began discussing if changes are in order to help the spec get through this new RFC process, possibly by splitting it into two specs. Timeline impact not clear at this point.
mp: in the Tech WG there was good discussion and a number of ideas proposed

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?jb: IA may send some people
mp: UNT may may also send people (reminder that it's in September)
rf: anyone going to ipres?
jb: I'll be there

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 OverviewKunzeStarted 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.
Suggestions for managing meetings/calendars/invitationsPhillips

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 though 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. 

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 on involvement. Mark to investigate.

Role of chairPhillipsDuration 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? 

...