You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/scripts/first_time_greeting
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -160,22 +160,22 @@ make benchmark BENCHMARKS_FILTER=\".*/@stdlib/math/base/special/sin/.*\"
160
160
161
161
If you haven't heard back from us within two weeks, please ping us by tagging the \"reviewers\" team in a comment on this PR.
162
162
163
-
If you have any further questions while waiting for a response, please join our [Gitter channel][stdlib-gitter] to chat with project maintainers and other community members.
163
+
If you have any further questions while waiting for a response, please join our [Zulip community][stdlib-zulip] to chat with project maintainers and other community members.
164
164
165
165
We appreciate your contribution!
166
166
167
167
## Documentation Links
168
168
169
169
- [Contributing Guidelines][stdlib-contributing]
170
170
- [Development Guide][stdlib-development]
171
-
- [Gitter channel][stdlib-gitter]
171
+
- [Zulip Chat][stdlib-zulip]
172
172
- [make rules for running examples][make-docs-examples]
173
173
- [make rules for running unit tests][make-docs-test]
174
174
- [make rules for running benchmarks][make-docs-benchmark]
@@ -200,9 +200,9 @@ We appreciate your contribution!
200
200
201
201
And thank you for opening your first issue! We will get back to you shortly. :runner: :dash:
202
202
203
-
If you have any further questions while waiting for a response, please join our [Gitter channel][stdlib-gitter] to chat with project maintainers and other community members.
203
+
If you have any further questions while waiting for a response, please join our [Zulip community][stdlib-zulip] to chat with project maintainers and other community members.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Woot woot! If you are new to stdlib, welcome! And thanks for your interest! Whil
34
34
35
35
### Issues
36
36
37
-
When filing new [issues][stdlib-issues] and commenting on existing [issues][stdlib-issues] on this repository, please ensure that discussions are related to concrete technical issues. For general questions and help, consult the [FAQ][stdlib-faq] and visit the [Gitter][stdlib-gitter] channel.
37
+
When filing new [issues][stdlib-issues] and commenting on existing [issues][stdlib-issues] on this repository, please ensure that discussions are related to concrete technical issues. For general questions and help, consult the [FAQ][stdlib-faq] and visit the [Zulip][stdlib-zulip] chat.
38
38
39
39
**Before** filing a potential bug report,
40
40
@@ -87,7 +87,7 @@ If you have found a bug that you would like to fix,
87
87
88
88
If you want to contribute a new feature or a breaking change to stdlib, be sure to
89
89
90
-
- consult the [Gitter][stdlib-gitter] channel to discuss ideas and to gather feedback as to whether a feature would be better developed as an external package. Discussing the design upfront helps ensure that we're ready to accept your work.
90
+
- consult the [Zulip][stdlib-zulip] chat to discuss ideas and to gather feedback as to whether a feature would be better developed as an external package. Discussing the design upfront helps ensure that we're ready to accept your work.
91
91
- write an RFC (request for comments) detailing the proposed change and submit as an issue on the project GitHub issue tracker.
92
92
- wait for RFC approval.
93
93
- submit a [pull request][stdlib-pull-requests], making sure to adhere to the guidance set forth in the RFC.
@@ -449,7 +449,7 @@ Phew. While the above may be a lot to remember, even for what seem like minor ch
Copy file name to clipboardExpand all lines: FAQ.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ This project
114
114
115
115
1.**Speed**: JavaScript is fast for a dynamically compiled language. This is largely due to the need for browser vendors to run web applications as fast as possible, thus forcing vendors to make continuous performance improvements and create highly optimized runtime environments.
116
116
2.**Rendering Engine**: web browsers are performant, highly optimized view engines, supporting a range of rendering modes ([DOM][dom], [canvas][canvas], [WebGL][webgl]). The web browser has become the preferred medium for interactive graphics, with most major numerical computing platforms supporting some form of web browser rendering ([R][shiny], [Python][bokeh], [MATLAB][plotly]). Accordingly, if JavaScript is already being used to render data as a plot, supporting numerical manipulation of that data without requiring language context switching and the additional complexity of establishing bridges between different languages and platforms also makes sense.
117
-
3.**Community**: JavaScript has one of the [largest][stackoverflow-developer-survey] and most diverse developer [communities][stackoverflow-developer-survey]. Giving that community access to better and more intermediate tools for numerical computing enables more potential creative applications and use cases. And further, numerical computing has traditionally been the purview of companies selling expensive software only accessible to industry and large academic institutions. By creating free and open numerical computing tools in JavaScript, numerical computing is democratized and made accessible to a [community][module-counts] which has typically not had access to such tools.
117
+
3.**Community**: JavaScript has one of the [largest][stackoverflow-developer-survey] and most diverse developer [communities][stackoverflow-developer-survey]. Giving that community access to better and more intermediate tools for numerical computing enables more potential creative applications and use cases. And further, numerical computing has traditionally been the purview of companies selling expensive software only accessible to industry and large academic institutions. By creating free and open numerical computing tools in JavaScript, numerical computing is democratized and made accessible to a [community][libraries-io] which has typically not had access to such tools.
118
118
4.**Ubiquity**: JavaScript is [ubiquitous][javascript-ubiquity], being supported on nearly any device with a web browser and, now, being pushed as a preferred scripting language in the Internet of Things (IoT) ([Cylon.js][cylon-js], [iot.js][iot-js], [JerryScript][jerryscript], [Johnny-Five][johnny-five]). Thus, if a numerical compute application can run in JavaScript, the broader the potential reach of that application.
119
119
5.**Distribution**: distributing a numerical compute application is considerably easier when compared to traditional numerical computation platforms. Because JavaScript is ubiquitous, the need for installing additional languages and tooling is often unnecessary. A web browser is frequently all that is required.
120
120
6.**Package Management**: Node.js package management is superior to anything available in other numerical computing environments. As developers who must manage Python [virtual environments][virtualenvs] or implement odd workarounds to support multiple versions of the same dependency can attest, the Node.js strategy makes dependency management trivial. And further, tight integration with [npm][npm] makes distribution even more frictionless. Frictionless is not a common adjective used in describing package management in other numerical computing environments.
@@ -794,7 +794,7 @@ See the [contributing guide][contributing-guide].
Copy file name to clipboardExpand all lines: SUPPORT.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Please seek support in the following ways:
32
32
33
33
-**Bugs**: if you have found a bug or would like to make a specific feature request, please file an issue on the stdlib [issue tracker][stdlib-issues].
34
34
-**Security vulnerabilities**: if you would like to report a security vulnerability, please consult the stdlib [security policy][stdlib-security] and follow requested steps for responsible [disclosure][stdlib-security].
35
-
-**Questions**: for general questions (i.e., concerns which are **not** bug reports or explicit feature requests), please ask on either [GitHub discussions][stdlib-discussions] or on [Gitter][stdlib-gitter].
35
+
-**Questions**: for general questions (i.e., concerns which are **not** bug reports or explicit feature requests), please ask on either [GitHub discussions][stdlib-discussions] or on [Zulip][stdlib-zulip].
36
36
37
37
Please do **not** file issues on the issue tracker seeking help or support debugging your application or open-source project when the encountered issues are specific to your project. You will have better luck in such instances seeking help from other users of stdlib via Stack Overflow or other non-stdlib affiliated public forums.
Copy file name to clipboardExpand all lines: docs/contributing/FAQ.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,7 +137,7 @@ Consider whether the number of parameters can be reduced. If reduction is not po
137
137
138
138
## I have opened a pull request, where can I seek feedback?
139
139
140
-
Consider joining our [Gitter channel][stdlib-gitter]! We are proud to have a very active community where members help each other by asking and answering questions. A maintainer will review your pull request soon and provide feedback. You can also discuss it during our [weekly office hours meeting][stdlib-office-hours]!
140
+
Consider joining our [Zulip community][stdlib-zulip]! We are proud to have a very active community where members help each other by asking and answering questions. A maintainer will review your pull request soon and provide feedback. You can also discuss it during our [weekly office hours meeting][stdlib-office-hours]!
141
141
142
142
<aname="generate-fixtures"></a>
143
143
@@ -425,7 +425,7 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
Copy file name to clipboardExpand all lines: docs/contributing/git_cheatsheet.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -482,7 +482,7 @@ Assuming you've already cloned the repository and set up your identity:
482
482
483
483
Congratulations! You now have all the essential Git commands to navigate your workflow smoothly while contributing to `stdlib`. Whether you're fixing a bug, adding a feature, or just getting started, this cheatsheet will help you stay organized and avoid common pitfalls. Keep practicing, stay curious, and enjoy the process. Happy coding!
484
484
485
-
To get started with your first contribution, check out the [Contributing Guide][stdlib-contributing] and [Development Guide][stdlib-development]. If you have any further questions, feel free to join our [Gitter][stdlib-gitter] channel to connect with the community and get support.
485
+
To get started with your first contribution, check out the [Contributing Guide][stdlib-contributing] and [Development Guide][stdlib-development]. If you have any further questions, feel free to join our [Zulip][stdlib-zulip] chat to connect with the community and get support.
486
486
487
487
## Other Links
488
488
@@ -495,7 +495,7 @@ To get started with your first contribution, check out the [Contributing Guide][
0 commit comments