Date: Thu, 28 Mar 2024 17:02:56 +0000 (UTC) Message-ID: <2091676789.15.1711645376195@eb16dacead9f> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14_1464628829.1711645376194" ------=_Part_14_1464628829.1711645376194 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The ArchivesSpace Slack is intended to facilitate conversation among tho= se actively working on teams or projects related to development of the Arch= ivesSpace application and its community. The ArchivesSpace slack is n= ot intended to be a member support channel, to replace the ArchivesSpace user group listserv for= community discussion, or to replace the Archi= vesSpace wiki for meeting notes and documentation.
The slack workspace ArchivesSpace.slack.com is intended to = facilitate communication between ArchivesSpace users, including members of = the Advisory Councils, working groups, teams like the Core Committers and T= raining Corps and those spearheading community development projects. Anyone= actively working on teams or projects related to ArchivesSpace development= or its community may request access to the ArchivesSpace slack workplace a= nd communicate on public channels. Invitation to join private channel= s will be extended at the request of the team leader for that channel. = ;
Channels within the ArchivesSpace slack can be either private or public.= Any ArchivesSpace sub-team, working group or team may request a slac= k channel to facilitate communication among team members or a community led= development project.
ArchivesSpace program staff may or may not join these channels as approp= riate and communication in an ArchivesSpace slack channel does not guarante= e a response from the ArchivesSpace program team. If you would like a= direct response from any member of the ArchivesSpace slack, including memb= ers of the program staff, you should tag that individual in the channel com= munication. Sending email to ArchivesSpaceHome@lyrasis.or= g will continue to be the best way to reach program team members fo= r needs unrelated to specific collaborative activities.
In addition to private and public channels, members of the ArchivesSpace= slack workplace may use the space to message each other individually. = ;
Slack channels and messages are not intended to replace standing team me= etings, meeting agendas, team documentation or email.
At any time, an ArchivesSpace team may elect to archive their slack chan= nel and discontinue use if the channel is not currently in use or a helpful= tool in the team=E2=80=99s workflow. The team may elect to reactivat= e the channel at a later date. Requests to create, archive and activa= te channels need to be made by a working group or team leader after getting= consensus from the rest of the team
If at any time you feel another member of the ArchivesSpace slack workpl= ace is creating an unsafe or uncomfortable environment or violating the ArchivesSpace Code of Conduct = contact ArchivesSpaceHome@lyrasis.org or foll= ow the reporting guidelines in the Code of Conduct.