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
@@ -8,17 +9,59 @@ API standard for arrays (or tensors).
8
9
9
10
These are relevant documents related to the content in this repository:
10
11
11
-
-[Rendered html docs for latest version](https://data-apis.github.io/array-api/latest)
12
+
-[Rendered HTML docs for latest version](https://data-apis.github.io/array-api/latest)
12
13
-[Consortium announcement blog post](https://data-apis.org/blog/announcing_the_consortium/)
13
14
-[Blog post on first release of draft array API standard](https://data-apis.org/blog/array_api_standard_release/)
14
15
15
16
See [CONTRIBUTING.md](CONTRIBUTING.md) for how to go about contributing to
16
17
this array API standard.
17
18
19
+
## Workgroup Meetings
20
+
21
+
To coordinate activities and facilitate discussion across the Python ecosystem, the Consortium for Python Data API Standards holds an open meeting every other week on Thursdays throughout the year.
22
+
23
+
This meeting is open to the public. So if you have questions about the array API standard, pain points, feature requests, or are just wanting to listen in, we encourage you to join the public call to connect with Consortium members, stay updated on the latest Consortium activities, and chat with others in the community.
24
+
25
+
Everyone is welcome—drop in and say hello!
26
+
27
+
### Time
28
+
29
+
**UTC 17:00 (05:00 PM)** every other Thursday:
30
+
31
+
| Timezone | Date/Time |
32
+
| ---------- | ---------- |
33
+
| US / Pacific | Thu 10:00 (10:00 AM) |
34
+
| US / Mountain | Thu 11:00 (11:00 AM) |
35
+
| US / Central | Thu 12:00 (12:00 AM) |
36
+
| US / Eastern | Thu 13:00 (01:00 PM) |
37
+
| EU / Western | Thu 18:00 (06:00 PM) |
38
+
| EU / Central | Thu 19:00 (07:00 PM) |
39
+
| EU / Eastern | Thu 20:00 (08:00 PM) |
40
+
| Moscow | Thu 20:00 (08:00 PM) |
41
+
| Chennai | Thu 22:30 (10:30 PM) |
42
+
| Hangzhou | Fri 01:00 (01:00 AM) |
43
+
| Tokyo | Fri 02:00 (02:00 AM) |
44
+
| Sydney | Fri 03:00 (03:00 AM) |
45
+
46
+
### Links
47
+
48
+
- Public calendar: <https://calendar.google.com/calendar/embed?src=8fe9013a2cb5d3409bb236d04eca73fa5227eac01c02ea8f6bc4a6a3cf982fa3%40group.calendar.google.com>
49
+
50
+
### Joining the meeting
51
+
52
+
- See the public calendar for information on how to join!
53
+
54
+
### Agenda
55
+
56
+
- Have specific things to discuss? Feel free to comment on <https://github.com/data-apis/array-api/issues/853> or the linked agenda document!
57
+
58
+
* * *
59
+
60
+
## Development
18
61
19
-
## Building docs locally
62
+
###Building docs locally
20
63
21
-
### Quickstart
64
+
####Quickstart
22
65
23
66
To install the local stubs and additional dependencies of the Sphinx docs, you
24
67
can use `pip install -r doc-requirements.txt`. Then just running `make` at the
@@ -31,7 +74,7 @@ $ ls _site/
31
74
2021.12/ draft/ index.html latest/ versions.json
32
75
```
33
76
34
-
### The nitty-gritty
77
+
####The nitty-gritty
35
78
36
79
The spec website is comprised of multiple Sphinx docs (one for each spec version),
37
80
all of which exist in `spec/` and rely on the modules found in `src/` (most
@@ -56,7 +99,7 @@ To build the whole website, which includes every version of the spec, you can
56
99
utilize `make spec`.
57
100
58
101
59
-
## Making a spec release
102
+
###Making a spec release
60
103
61
104
The Sphinx doc at `spec/draft/` should be where the in-development spec resides,
62
105
with `src/array_api_stubs/_draft/` containing its respective stubs. A spec
@@ -142,6 +185,7 @@ for more background on the approach we use.
142
185
143
186
<!-- TODO: write a script to automate/standardise spec releases -->
0 commit comments