docs: replace Element references with Zulip

Author: batpigandme

.github/ISSUE_TEMPLATE/config.yml

@@ -18,5 +18,5 @@
 
 contact_links:
   - name: 💬 Question
-    url:  https://gitter.im/stdlib-js/stdlib
-    about: Got a question we haven't already answered? Ask us on Element! 🤗
+    url:  https://stdlib.zulipchat.com
+    about: Got a question we haven't already answered? Ask us on Zulip! 🤗

.github/ISSUE_TEMPLATE/idea.yml

@@ -30,7 +30,7 @@ body:
 
         1.  Before submitting your idea, please be sure to look through the [list of existing ideas](https://github.com/stdlib-js/google-summer-of-code/issues?q=label%3Aidea+) to ensure that your idea has not already been discussed.
 
-        1.  Also, before submitting your idea, please be sure to reach out over the stdlib [Element channel](https://gitter.im/stdlib-js/stdlib) to discuss it with us first. We'll inform you whether the idea has already been implemented, if the idea will entail enough work to last the duration of the GSoC program, if the idea requires too much work to be meaningfully pursued during GSoC, and if the idea is within the scope of stdlib.
+        1.  Also, before submitting your idea, please be sure to reach out over the stdlib [Zulip chat](https://stdlib.zulipchat.com) to discuss it with us first. We'll inform you whether the idea has already been implemented, if the idea will entail enough work to last the duration of the GSoC program, if the idea requires too much work to be meaningfully pursued during GSoC, and if the idea is within the scope of stdlib.
 
         1.  Understand that submitting an idea is **not** sufficient to participate in GSoC. To be considered, a GSoC application **must** have a written proposal submitted to <https://summerofcode.withgoogle.com/>. To begin working on a GSoC application, we **strongly** recommend using the stdlib [application template](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=rfc%2C2023&template=application.yml&title=%5BRFC%5D%3A+).
 

.github/workflows/scripts/update_ideas_list.js

@@ -45,23 +45,23 @@ var HEADING = [
 	'',
 	'Before working on your GSoC application, please review our list of ideas to see if you find a project which excites you. The list of existing ideas is provided to serve as inspiration and to indicate which directions may be good for stdlib.',
 	'',
-	'If you do find an existing idea that you\'d like to pursue, please be sure to contact us in our [Element](https://gitter.im/stdlib-js/stdlib) channel to discuss it first! **Always be sure to ask about these ideas prior to working on application in order to get the latest information about what is already implemented and what exactly must be done.**',
+	'If you do find an existing idea that you\'d like to pursue, please be sure to contact us in the [GSoC Questions](https://stdlib.zulipchat.com/#narrow/channel/546969-gsoc-questions) channel of our [Zulip chat](https://stdlib.zulipchat.com) to discuss it first! **Always be sure to ask about these ideas prior to working on application in order to get the latest information about what is already implemented and what exactly must be done.**',
 	'',
 	'Priority, difficulty, technology, and topic area have no bearing on the chances of an idea being accepted. All ideas are equally good, and your chances of being accepted depend solely on the **quality of your application**.',
 	'',
 	'**Project Length**',
 	'',
 	'GSoC allows three different project lengths: **90** hours, **175** hours, and **350** hours. Each idea must indicate whether the idea is a better fit for 90, 175, or 350 hours.',
 	'',
-	'In some cases, we may be able to extend a 175 hour project to a 350 hour project by extending the ideas of what can be done. Similarly, in some cases, a 350 hour project can be shortened to a 175 hour project by only implementing part of an idea and leaving the rest for a future project. In either case, if you want to adjust the project length, please be sure to contact us in our [Element](https://gitter.im/stdlib-js/stdlib) channel to discuss it first!',
+	'In some cases, we may be able to extend a 175 hour project to a 350 hour project by extending the ideas of what can be done. Similarly, in some cases, a 350 hour project can be shortened to a 175 hour project by only implementing part of an idea and leaving the rest for a future project. In either case, if you want to adjust the project length, please be sure to contact us in our [GSoC Questions](https://stdlib.zulipchat.com/#narrow/channel/546969-gsoc-questions) channel to discuss it first!',
 	'',
 	'## Your Own Idea',
 	'',
 	'If you\'d like to submit your own idea, that is also welcome; just be sure to propose your idea to stdlib mentors first! After reaching out, we\'ll inform you whether the idea has already been implemented, if the idea will entail enough work to last the duration of the GSoC program, if the idea requires too much work to be meaningfully pursued during GSoC, and if the idea is within the scope of stdlib. **Unsolicited, undiscussed ideas are less likely to get accepted.**',
 	'',
 	'The best project for you is the one you are most interested in and knowledgeable about. Excitement and aptitude are two key ingredients of a successful project and help ensure your commitment and ability to see a project through to completion. So if there is something you are especially passionate about and that you believe aligns with the scope and goals of stdlib, we\'d be happy to hear your pitch!',
 	'',
-	'After discussing with us in our [Element](https://gitter.im/stdlib-js/stdlib) channel and receiving approval to submit your idea, please open an [issue](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+) which describes your idea using the [**idea issue template**](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+).',
+	'After discussing with us in our [Zulip](https://stdlib.zulipchat.com) chat and receiving approval to submit your idea, please open an [issue](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+) which describes your idea using the [**idea issue template**](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+).',
 	'',
 	'## Mentors',
 	'',

FAQ.md

@@ -20,10 +20,10 @@ In short, given that the intent of GSoC is offering new contributors a pathway i
 
 In general, we prefer open and public communication. However, we recognize that you may have legitimate concerns regarding the sharing of personal information, especially in public forums. If you need to communicate privately, you can e-mail one of the [mentors](https://github.com/stdlib-js/google-summer-of-code/blob/main/mentors.md) directly.
 
-If you do reach out directly to a mentor, please be **respectful** of their time. If your e-mail is not for confidential purposes (e.g., you're e-mailing to ask if you can do idea X or something similar), mentors are likely to refer you to our public [Element](https://gitter.im/stdlib-js/stdlib) channel.
+If you do reach out directly to a mentor, please be **respectful** of their time. If your e-mail is not for confidential purposes (e.g., you're e-mailing to ask if you can do idea X or something similar), mentors are likely to refer you to our public [Zulip](https://stdlib.zulipchat.com) community.
 
 ## Why are idea issues locked?
 
 Idea issues are **not** our desired forum for initial project inquiries and are intended to be a lightweight means for core stdlib developers to write down potential GSoC project ideas. Our aim is to keep idea issues as clear and succinct as possible and to avoid long drawn out discussions which are better suited for chat.
 
-If you have questions or are interested in pursuing a particular idea, you should reach out in our [Element](https://gitter.im/stdlib-js/stdlib) channel. 
+If you have questions or are interested in pursuing a particular idea, you should reach out in the [GSoC Questions](https://stdlib.zulipchat.com/#narrow/channel/546969-gsoc-questions) channel of the stdlib [Zulip chat](https://stdlib.zulipchat.com). 

ideas.md

@@ -4,23 +4,23 @@
 
 Before working on your GSoC application, please review our list of ideas to see if you find a project which excites you. The list of existing ideas is provided to serve as inspiration and to indicate which directions may be good for stdlib.
 
-If you do find an existing idea that you'd like to pursue, please be sure to contact us in our [Element](https://gitter.im/stdlib-js/stdlib) channel to discuss it first! **Always be sure to ask about these ideas prior to working on application in order to get the latest information about what is already implemented and what exactly must be done.**
+If you do find an existing idea that you'd like to pursue, please be sure to contact us in the [GSoC Questions](https://stdlib.zulipchat.com/#narrow/channel/546969-gsoc-questions) channel of our [Zulip chat](https://stdlib.zulipchat.com) to discuss it first! **Always be sure to ask about these ideas prior to working on application in order to get the latest information about what is already implemented and what exactly must be done.**
 
 Priority, difficulty, technology, and topic area have no bearing on the chances of an idea being accepted. All ideas are equally good, and your chances of being accepted depend solely on the **quality of your application**.
 
 **Project Length**
 
 GSoC allows three different project lengths: **90** hours, **175** hours, and **350** hours. Each idea must indicate whether the idea is a better fit for 90, 175, or 350 hours.
 
-In some cases, we may be able to extend a 175 hour project to a 350 hour project by extending the ideas of what can be done. Similarly, in some cases, a 350 hour project can be shortened to a 175 hour project by only implementing part of an idea and leaving the rest for a future project. In either case, if you want to adjust the project length, please be sure to contact us in our [Element](https://gitter.im/stdlib-js/stdlib) channel to discuss it first!
+In some cases, we may be able to extend a 175 hour project to a 350 hour project by extending the ideas of what can be done. Similarly, in some cases, a 350 hour project can be shortened to a 175 hour project by only implementing part of an idea and leaving the rest for a future project. In either case, if you want to adjust the project length, please be sure to contact us in our [GSoC Questions](https://stdlib.zulipchat.com/#narrow/channel/546969-gsoc-questions) channel to discuss it first!
 
 ## Your Own Idea
 
 If you'd like to submit your own idea, that is also welcome; just be sure to propose your idea to stdlib mentors first! After reaching out, we'll inform you whether the idea has already been implemented, if the idea will entail enough work to last the duration of the GSoC program, if the idea requires too much work to be meaningfully pursued during GSoC, and if the idea is within the scope of stdlib. **Unsolicited, undiscussed ideas are less likely to get accepted.**
 
 The best project for you is the one you are most interested in and knowledgeable about. Excitement and aptitude are two key ingredients of a successful project and help ensure your commitment and ability to see a project through to completion. So if there is something you are especially passionate about and that you believe aligns with the scope and goals of stdlib, we'd be happy to hear your pitch!
 
-After discussing with us in our [Element](https://gitter.im/stdlib-js/stdlib) channel and receiving approval to submit your idea, please open an [issue](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+) which describes your idea using the [**idea issue template**](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+).
+After discussing with us in our [Zulip](https://stdlib.zulipchat.com) chat and receiving approval to submit your idea, please open an [issue](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+) which describes your idea using the [**idea issue template**](https://github.com/stdlib-js/google-summer-of-code/issues/new?assignees=&labels=idea&template=idea.yml&title=%5BIdea%5D%3A+).
 
 ## Mentors
 

organization/slot_announcement_checklist.md

@@ -41,7 +41,7 @@ After Google has publicly announced slot allocations, we need to do the followin
 > [!NOTE]
 > Currently, sending out acceptance e-mails is done manually. We should investigate doing this directly from Google Sheets by creating a [mail merge](https://developers.google.com/apps-script/samples/automations/mail-merge).
 
--   [ ] Post the drafted announcement to Gitter.
+-   [ ] Post the drafted announcement to Zulip.
 -   [ ] Sent acceptance e-mails to all accepted GSoC contributors.
 -   [ ] Send rejection e-mails to all rejected GSoC contributors.
 -   [ ] Invite accepted GSoC contributors to the stdlib Slack.