-
Notifications
You must be signed in to change notification settings - Fork 2
Broken link about meeting-notes #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For the array API standard, as per data-apis/array-api#853, there are now public fortnightly community meetings, the meeting notes for which are at https://hackmd.io/zn5bvdZTQIeJmb3RW1B-8g?view. As far as I am aware, development of the dataframe API standard has been inactive for about a year. |
Thank you very much for the response @lucascolley Should the governance page be updated with this information? |
yep!
Yes, I think @rgommers or @kgryte might be able to help you there.
Some sort of update to remove the outdated information is definitely in order, yes. I guess we should try to not replace it with similarly temporary information, though :) |
@raulcd This issue data-apis/array-api#853 points to the HackMD document which includes the time and date of upcoming meetings. We should work to create a more public calendar, however, so that folks can more readily add to their existing calendars. |
Thanks for pointing that out! |
There is a meeting today btw @raulcd, in case you hadn't clocked |
Hi,
There is a link about meeting notes on the consortium governance page:
https://github.com/data-apis/governance/blob/40674d7b8a963c8d10f8dab974b884e2a9b22d24/consortium_governance.md#meetings
Which points to a non-existent repository:
https://github.com/data-apis/workgroup/tree/main/meeting_minutes
Some of us at the Arrow project are trying to understand the status of the initiative and were Arrow stands and we are trying to reconnect with the developments.
Would it be possible for some of us to get information about the latest meeting notes and / or whether these meetings are still occurring?
CC @AlenkaF @rok
Thanks,
Raúl
The text was updated successfully, but these errors were encountered: