replace slack with zulip (and a few other misc updates)

Author: TimidRobot

content/community/community-team/community-building-roles/contents.lr

@@ -6,64 +6,57 @@ title: Community Team: Community Building Roles
 ---
 description: This page serves as a guide for community building roles on CC's <a href="/community/community-team/">Community Team</a>.
 ---
-body:
+body: <!-- disregard: vim syntax highlighting fix_ -->
 
 Community building roles are for folks interested in helping grow CC's open source community by ensuring all contributors have a good experience and spreading the word about CC's projects.
 
 If you'd like to apply for one of these roles, please see the main [Community Team][communityteam] page.
 
 ## Community Collaborator
-**Who should apply:**  
-If you’ve helped anyone else in the CC open source community on GitHub, Slack, or email and you’d like to do more to help grow the community, you should apply for this role!
 
-**What does this role give you?**  
+**Who should apply:**
+If you’ve helped anyone else in the CC open source community on GitHub or Zulip and you’d like to do more to help grow the community, you should apply for this role!
+
+**What does this role give you?**
 * You’ll receive previews of upcoming changes to the Community Team program.
 * You’ll be listed as [a member of the Community Team on CC Open Source](/community/community-team/members/).
 
-**How can you engage with the community?**  
+**How can you engage with the community?**
 You can use the following channels to engage with the community:
 * [Edit access](/community/community-team/engagement-channels/#edit-access)
   on our upcoming tweets
-* Invitation to our Slack channels
-  * [Newbie channels](/community/community-team/engagement-channels/#newbie-channels)
-  * [UX design channels](/community/community-team/engagement-channels/#ux-design-channel)
-  * [Community Team channel](/community/community-team/engagement-channels/#community-team-channel)
-* Invitation to our [meetings](/community/community-team/engagement-channels/#meetings)
-* Membership in the [Community Team mailing list](/community/community-team/engagement-channels/#community-team-group)
+* Invitation to [Zulip](/community/#zulip)
 
-**Guidelines for Community Contributors**  
+**Guidelines for Community Contributors**
 If you’ve been accepted as a Community Contributor, you are encouraged to:
 * keep helping people in the CC open source community!
-  * Respond to people on Slack.
+  * Respond to people on Zulip.
   * Respond to questions or issues on GitHub.
-  * Respond to people on CC's mailing lists.
-* participate in discussions in Slack or via email.
 * contribute in other ways if you’d like, like [writing code or reviewing pull requests](/community/community-team/project-roles/).
-* suggest improvements to, and new ideas for, the tweets from the [CC Open Source Twitter account](https://twitter.com/cc_opensource).
 
 **Note:** The role of Community Contributor was deprecated in December 2020 and all members were redesignated as collaborators.
 
 ## Community Maintainer
-**Who should apply:**  
+**Who should apply:**
 If you’re a Community Collaborator who has done some meatier community building tasks and wants more responsibility, you should apply for this role. Please note that this role comes with a lot of responsibilities!
 
-**What does this role give you?**  
+**What does this role give you?**
 * Everything a Community Collaborator gets.
 * Manager permission on CC’s developer mailing list.
   * You’ll be able to approve new requests for people to join and moderate the list.
 * Creative Commons staff will write you a letter of recommendation on request.
 * You'll receive CC swag.
 
-**How can you engage with the community?**  
+**How can you engage with the community?**
 In addition to the channels afforded to a Community Collaborator, you can use the following channels to engage with the community:
 * [Publish access](/community/community-team/engagement-channels/#publish-access) on
   our upcoming tweets
 
-**Guidelines for Community Maintainers**  
+**Guidelines for Community Maintainers**
 If you’ve been accepted as a Community Maintainer, you are encouraged to:
 * do everything a Community Collaborator does.
 * respond to requests to join the CC developer mailing list.
-* be available on Slack/email or GitHub regularly.
-* ensure that people are getting the help they need on Slack and GitHub.
+* be available on Zulip/email or GitHub regularly.
+* ensure that people are getting the help they need on Zulip and GitHub.
 
 [communityteam]:/community/community-team/

content/community/community-team/contents.lr

@@ -68,7 +68,7 @@ Great contributions are those that are of a high level of quality such that a ma
 
 Your code does not necessarily need to be merged to count as a "Great Contribution".
 
-**If your question is not answered here, please ask us on Slack, or at <a href="mailto:opensource@creativecommons.org">opensource@creativecommons.org</a>!**
+**If your question is not answered here, please ask us on Zulip!**
 
 ## Evaluation Criteria
 

content/community/community-team/engagement-channels/contents.lr

@@ -8,7 +8,7 @@ description: This page serves as a guide for Community Team members on how to en
 ---
 is_long_page: true
 ---
-body:
+body: <!-- disregard: vim syntax highlighting fix_ -->
 
 You've joined the CC Community Team. Congratulations! This is a very clear
 indication of your desire to engage more deeply with the Creative Commons
@@ -22,119 +22,32 @@ access, it can be easy to not know what is expected of you and how you can make
 the most of your involvement. This guide will condense this information down to
 help you identify the best ways to engage with the team. _Let's get started!_
 
-## Meetings
+## Zulip
 
-We regularly hold meetings to discuss work and, occasionally, to play games.
-Based on your role and the project, you will be invited to some of these
-meetings. You can join the CC Engineering calendar to keep up with the schedule.
-
-### Community meeting
-
-In this meeting, all the staff and open-source community at CC meet to discuss
-work. Any major discussions and ideas that affect the projects or process take
-place in this meeting. It's also a channel to know what is happening in a
-parallel project that you don't get to interact with as much. We have a Show &
-Tell, so if you did or made something recently that you think is interesting,
-you can present that.
-
-**Frequency:** monthly
-
-### Vocabulary sprint planning
-
-In this meeting, the Vocabulary sprint planning meeting is where all members
-involved in Vocabulary meet. This is mainly held to determine reasonable
-milestones on what can be accomplished in the next two weeks and assign
-different tasks and tickets to different people. If you'd like to get involved
-with Vocabulary code you can pick up some tasks here.
-
-**Frequency:** fortnightly
-
-## Slack
-
-We communicate over text using Slack. Everyone from the community is on it,
+We communicate over text using Zulip. Everyone from the community is on it,
 including CC employees. You can find fellow developers, technical writers and
 designers all in the same place. If you are, or want to be, a part of the
-community, [join us on Slack](/community/#slack). It is one of the best ways to
+community, [join us on Zulip](/community/#zulip). It is one of the best ways to
 connect with us.
 
-Slack is organised by channels and, depending on your role, you will be invited
-to these channels to participate in discussions about certain topics.
-
-### Newbie channels
-
-There are a number of channels which budding open source developers join in
-hopes of finding like-minded developers. You should help them get started, clear
-simple doubts, introduce them to FOSS and make them feel welcome in our
-community. After all, the more the merrier!
-
-**Channel:** `#general`, `#cc-dev-workprograms`, `#cc-developers`
-
-### Community team channel
-
-This is a channel where you can connect with other members of the Community
-Team. Announcements pertaining to the Community Team and planned changes to the
-community will be announced here first.
-
-**Channel:** `#cc-dev-community-team`
-
-### Engineering channel
-
-This is a channel where the entire engineering team of CC can be reached.
-
-**Channel:** `#engineering`
-
-### UX design channels
-
-This is the channel where we discuss design and UI/UX of various CC software and
-websites. This is particularly relevant to the Vocabulary project. The Figma
-specific channel mostly posts updates from the Figma documents of all the
-various projects.
-
-**Channel:** `#ux-design`, `#ux-design-figma`
-
-## Mailing lists
-
-We also have a few mailing lists where we communicate announcements and the
-like. Join us on our [Google Group mailing lists](/community/#mailing-lists) if
-you are, or want to be, a part of the community.
-
-### Developer group
-
-This group is for all developers who are associated or related to the
-open-source community around our projects.
-
-**Address:** cc-developers@creativecommons.org
-
-### Usability Announcements group
-
-This group is for all people participating in our Usability testing sessions.
-Announcements of upcoming tests are made in this group.
-
-**Address:** usability-announce@creativecommons.org
-
-### Community Team group
-
-This group is for all CC tech staff and everyone on the Community Team.
-
-**Address:** community-team@creativecommons.org
-
 ## GitHub
 
 All our code is hosted on GitHub, we use issues to track bugs and identify
 features and pull requests to improve the software and drive it forward. All
-Community Team members with the role of
-[Project Collaborator](/community/community-team/project-roles/#project-collaborator)
-or higher are added to the
-[CC organisation](https://github.com/creativecommons/)
-on GitHub.
+Community Team members with the role of [Project Collaborator][project-collab]
+or higher are added to the [CC organisation][gh-cc] on GitHub.
 
 We use GitHub teams to manage access levels for all members of the organisation.
 Each role in a particular project corresponds to a certain access level over the
 repositories that are a part of that project. As you change your role, you will
 automatically be added to the appropriate team.
 
-The [GitHub docs](https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)
-are the best place to learn about these access levels.
+The [GitHub docs][ghdocs-perms] are the best place to learn about these access
+levels.
+
+[project-collab]: /community/community-team/project-roles/#project-collaborator
+[gh-cc]: [ghdocs-perms]
+[ghdocs-perms]: https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
 
 ### Read access
 
@@ -164,28 +77,3 @@ Maintain access grants you the privileges to manage almost all aspects of the
 repository, except any destructive action or sensitive information. You can
 modify the repositories' topics, description and social cards among other
 settings.
-
-## Twitter
-
-Twitter is our preferred social media platform. We don't have a LinkedIn or
-Facebook presence. We generally post updates from our projects, introduce newly
-published blog posts, announce new releases of our software and any other
-interested information related to both FOSS and Creative Commons.
-
-While [CC Open Source](https://twitter.com/cc_opensource) has a rather humble
-Twitter following, our tweets are often retweeted by
-[the parent Creative Commons handle](https://twitter.com/creativecommons).
-
-### Edit access
-
-You can see all the upcoming tweets from Creative Commons, suggest any
-improvements to the text or the material, suggest new topics for the tweets, and
-even write tweets that will be published, after review, from the official
-Twitter handle.
-
-### Publish access
-
-You can post or schedule the tweets to be published from the official Twitter
-handle. You can also interact with the open source community on Twitter and
-access the official Twitter stats to further improve our outreach and engagement
-metrics.

content/community/community-team/project-roles/contents.lr

@@ -6,7 +6,7 @@ title: Community Team: Project Roles
 ---
 description: This page serves as a guide for project-based roles on Creative Commons' <a href="/community/community-team/">Community Team</a>.
 ---
-body:
+body: <!-- disregard: vim syntax highlighting fix_ -->
 
 Project roles are intended for folks interested in contributing to a specific
 project or codebase. You may have roles on multiple projects, but they will
@@ -34,26 +34,15 @@ this role.
 You can use the following channels to engage with the community:
 - [Read access](/community/community-team/engagement-channels/#read-access) on
   the relevant repos on GitHub
-- Invitation to our Slack channels
-  - [Newbie
-    channels](/community/community-team/engagement-channels/#newbie-channels)
-  - [UX design
-    channels](/community/community-team/engagement-channels/#ux-design-channel)
-  - [Community Team
-    channel](/community/community-team/engagement-channels/#community-team-channel)
-- Invitation to our
-  [meetings](/community/community-team/engagement-channels/#meetings)
-- Membership in the [Community Team mailing
-  list](/community/community-team/engagement-channels/#community-team-group)
+- [Zulip](/community/#zulip)
 
 **Guidelines for Project Contributors**
 
 If you’ve been accepted as a Project Contributor, you are encouraged to:
 - keep contributing to the project as and when you can!
-- participate in discussions in Slack or via email.
-- contribute in other ways if you'd like, like [helping out newbie developers
-  or voting on our
-  tweets](/community/community-team/community-building-roles/).
+- participate in discussions in Zulip.
+- contribute in other ways if you'd like, like [helping out newbie
+  developers](/community/community-team/community-building-roles/).
 
 
 ## Project Collaborator

content/community/contents.lr

@@ -4,81 +4,43 @@ _template: page-with-toc.html
 ---
 title: Join the CC Developer Community
 ---
-description: Join our Slack to meet other developers interested in Creative
+description: Join our Zulip to meet other developers interested in Creative
 Commons (CC), get feedback on your projects, and talk with CC's full-time
 Technology team members. You can also keep up with us on the <a href="/blog">CC
 Open Source Blog</a>.
 ---
-body:
+body: <!-- disregard: vim syntax highlighting fix_ -->
 
 
-## Mailing Lists
+## Zulip
 
-**CC Developers**: For general technical discussion open to all members. Join
-[on Google Groups][group-cc-developers] or by sending an email to
-`cc-developers+subscribe@creativecommons.org`.
+Creative Commons has a large Zulip community with many sub-communities. It is
+open to the public and you can sign up with the [Creative Commons Community
+Intake Form][zulip-signup]. If you're not familiar with Zulip, please read
+[Getting started with Zulip | Zulip help center][zulip-start].
 
-**CC Usability Announcements**: Announcement-only list for users to sign up for
-usability testing. Join [on Google Groups][group-usability-announce] or by
-sending an email to `usability-announce+subscribe@creativecommons.org`.
+Once you join, please introduce yourself in the `# Open Source` channel.
 
-[group-cc-developers]: https://groups.google.com/a/creativecommons.org/forum/#!forum/cc-developers
-[group-usability-announce]: https://groups.google.com/a/creativecommons.org/forum/#!forum/usability-announce
-
-
-## Slack
-
-Creative Commons has a large Slack community with sub-communities for
-tech/developers (of course), the [CC Global Network][network], specific
-countries, open education, GLAM, and more. It is open to the public and you can
-[sign up here][slack-signup]. If you're not familiar with Slack, please read
-["Getting Started" on Slack's usage guide][slack-usage]. Information on joining
-a specific channel is on ["Join a channel"][slack-join-help].
-
-Once you join, please introduce yourself in the `#cc-developers` channel.
-
-[network]: https://network.creativecommons.org/
-[slack-signup]: http://slack-signup.creativecommons.org/
-[slack-usage]: https://get.slack.help/hc/en-us/categories/360000049043
-[slack-join-help]: https://get.slack.help/hc/en-us/articles/205239967-Join-a-channel
+[zulip-signup]: https://docs.google.com/forms/d/e/1FAIpQLSf2HY_wHq5SlgP_0U0ZWQKGXKwocNhm_vCPY34bUQrQ_hWoAQ/viewform
+[zulip-start]: https://zulip.com/help/getting-started-with-zulip
 
 The channels most relevant to CC's developer community are:
 
 | Channel | Discussion related to |
 | ------- | --------------------- |
-| `#cc-dev-legal-tools` | [cc-legal-tools-app][cc-legal-tools-app] project (CC Legal Tools formatting and translation) |
-| `#cc-dev-legaldb` | [legaldb][legaldb] project |
-| `#cc-dev-license-chooser` | [cc-chooser][cc-chooser] project (new CC license chooser) |
-| `#cc-dev-linkchecker` | [cc-link-checker][cc-link-checker] project |
-| `#cc-dev-platform-toolkit` | [mp][mp] project (CC Platform Toolkit) |
-| `#cc-dev-searchportal` | [search][search] project |
-| `#cc-dev-vocabulary` | [cc-vocabulary][cc-vocabulary] project |
-| `#cc-dev-workprograms` | **GSoC, GSoD, Outreachy, and other [work programs][workprograms] or internships** |
-| `#cc-developers` | **general technical issues, new tech blog posts, etc.** |
-| `#cc-translation` | Coordinating translation efforts |
-| `#cc-usability` | general usability issues, seeking feedback on new releases of CC products from the community, etc. |
+| `# CCOS Work Programs` | GSoC, GSoD, Outreachy, and other [work programs][workprograms] or internships |
+| `# Open Source` | CC Open Source projects |
+| `# Translation` | Translation and Transifex coordiantion |
 
-[legaldb]: https://github.com/creativecommons/legaldb
-[cc-chooser]: https://github.com/creativecommons/cc-chooser
-[cc-legal-tools-app]: https://github.com/creativecommons/cc-legal-tools-app
-[cc-link-checker]: https://github.com/creativecommons/cc-link-checker
-[mp]: https://github.com/creativecommons/mp
-[cc-vocabulary]: https://github.com/creativecommons/cc-vocabulary
-[search]: https://github.com/creativecommons/search
 [workprograms]: /programs/
 
 
-### Slack Tips
+### Zulip Tips
 
-- You will automatically join the `#general` and `#cc-announcements` channels
-  when you sign in to Slack for the first time.
-    - `#general` is for general purpose discussions relevant to CC.
-    - `#cc-announcements` is reserved for important announcements from CC
-      staff.
-- For more information about how Creative Commons uses Slack, see [the Slack
-  page on the CC public wiki][wiki-slack].
-- If you're looking to talk to someone on CC's full-time engineering staff,
-  you're most likely to find us on Slack between 11:00 and 23:00 UTC on
+- [Getting started with Zulip | Zulip help center][zulip-start]
+- If you're looking to talk to someone on CC's full-time Technology team,
+  you're most likely to find us on Zulip between 11:00 and 23:00 UTC on
   weekdays.
-
-[wiki-slack]: https://wiki.creativecommons.org/wiki/Slack
+- In addition to a web interface, Zulip has dedicated apps: [Download the Zulip
+  app for your device](https://zulip.com/apps/)
+  - Organization URL: `creativecommons.zulipchat.com`