Doodle is paid with a free trial, so we would only be able to use it for scheduling the first meeting. After that, the trial would expire and we could no longer easily use it.
I was thinking about using it as token for all meetings. I don't think we should do this dance for every meeting. It's best to settle on a week day and time and stick to it. Sorry if that wasn't clear. Also, we can use any other free/open source tool for that, if it exists. Maybe this forum itself has some form of poll where users can vote?
If we can narrow it down sufficiently on this thread, it may be easier to just voice our needs with comments instead of moving to another platform. For starters, we could narrow it down to weekends. Monday-Friday is already going to have more scheduling conflicts than weekends. It has a narrower window of time for most people (late afternoon - evening) which stretches thin across all world time zones. While with weekends, we have all day. Secondly, we could make a window of time based on our geographical base to include as many people as possible. For example, we could fit a time that's early in the morning for the US West Coast and late in the evening for India.
If we agreed on the two points above, then the possible meeting times would be in a narrow enough range to decide on this thread. Alternatively, we could use Google Sheets to present all possible times to meet and collectively narrow it down. Although then, it's a security risk because anyone on the internet can edit the document and mess with it. If you have to sign up or be invited to edit, that creates a barrier to entry for someone wishing to edit it.
Edit: even commenting on a Google Doc or similar could still introduce an opportunity for spamming.
Has any meeting occurred? If not should we follow through with next Saturday?
No meeting has occurred. I think Saturday, June 4 at 9 AM PDT would be the best time for our meeting. I'm just waiting to see what @aj_ortiz says.
I'll make the official declaration for clarity and formality. To everybody on this thread, @aj_ortiz plans to host a virtual meeting on Saturday, June 4 at 9 AM PDT. We will discuss using Swift for numerical computing and machine learning. All of you are invited.
- It's been 14 months since we started the "post"-S4TF chatter and asked for a real working group. Congratulations to ourselves for finally pulling it off.
6 Likes
What video link do we plan on using for tomorrow?
1 Like
I cant make it today unfortunately. Will there be notes posted afterwards? Hope to see you guys next edition in any case!
It's 5 minutes in and it still says "Waiting for the host to start this meeting". Just want to make sure the meeting is still on today.
Yes, I'm waiting too
Same here.
I'll start a new meeting Launch Meeting - Zoom
@rex-remind you just posted a link to download the Zoom app.
nevermind it works now
I've joined @rex-remind's Zoom link. I'm going to wait a few more minutes before starting so that everybody who wants to join can.
Thank you to everyone who attended the first meeting of the Numerical/ML Working Group!
In our initial meeting we performed some brainstorming and established consensus of our initial focus towards expanding Swift's matrix capabilities. Additionally, we established consensus on communication channels (Slack and Swift Forums), project management tooling (GitHub), and a unified commitment towards making tangible progress.
5 Likes
For reference, here is the link to tomorrow’s meeting at 9am PT https://meet.google.com/gci-boyn-dma
All further meetings will be coordinated solely through the previously posted slack channel.
Hi,
I am very much interested in collaborating and joining the Numerical/ML WG. I am thinking about working on a DL framework called swiftograd, inspired by tinygrad, after I saw that S4TF was archived. This is intended to be a very small DL library like tinygrad. I would love to see the community opinion on this and whether there should be a larger project for a DL library to replace S4TF.
Also @rex-remind could you please post an updated invitation link of the slack channel, as the one posted here expired.
Hi @KhalidAl-otaibi, unfortunately moment died in September and work stopped. However, the long term success of AI/ML on Swift is still very important to me so maybe we can get things going again.
Here is a permanent invite link Slack for anyone who sees this going forward.
For posterity, if things ever seem quiet in there feel free to tag me in a message. Volunteer work can ebb and flow a times.
To reply to your other question, we were working on a fresh Numerics/ShapedArray lib pulling pieces from S4TF that made sense without pulling in too much of the complexity, and building out from there. This may align with what you're trying to achieve. Let's discuss in slack.