-
Notifications
You must be signed in to change notification settings - Fork 39
Crowdin Integration Meeting: Tuesday, May 22 8am Pacific #87
Comments
How about Thursday May 17 at 4pm Pacific? |
🎉 Sounds good to me! 🎉 |
That would be 4:30 AM in India! |
It will be 1:00am in Poland, so it will be very difficult to join :-), but as soon this will happen then better, I hope a recording of this meeting will be available online? |
@obensource I know you said afternoons/evenings are best, but could you possibly make a morning work? 8am Pacific would be more likely to work for @lukaszewczak and @maddhruv. |
@zeke sure! The next 8am slot that works for me would be Monday the 21st. Stoked to make it work for everyone–thanks Zeke! 🙌 |
How about Tuesday the 22nd? If that doesn't fit I can move stuff around and make Monday work. |
@zeke works for me! Let's do it! 🎉🎉🎉 |
This could work fine for me! |
I think we may need to postpone this meeting as we don't yet have Crowdin connected to the org. See #77 for details on why we're blocked. |
Yes, I agree, we should postpone this meeting. |
This meeting is postponed pending consideration from the TSC on authorizing the Crowdin-GitHub integration. See nodejs/TSC#544 (comment) -- that meeting is scheduled for May 23. |
Hi @zeke, are we able to make that meeting today? Is the integration with Crowdin authorized? |
Still waiting on TSC approval. Follow nodejs/TSC#544 (comment) for updates. |
This meeting didn't happen because we didn't get TSC approval of Crowdin in time. Closing with the hope that we'll resolve this at the collaborator summit this week. |
Let's meet!
We need to schedule a time to record our process for setting up the crowdin-github integration: #77
Let's make it happen before the Collaboration Summit! I'm generally available in the afternoons/evenings PST. How about y'all?
The text was updated successfully, but these errors were encountered: