-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Discussion] Upstream? #71
Comments
Hi @Civil! Would you be interested in scheduling a meeting so that we can further discuss this? |
Sure. My timezone is CEST and usually my evenings are free (or flexible) with exception of Wednesday. Weekends work as well, but I guess you won't work to discuss work-related stuff outside of working hours. If you can't do evenings, I can try during my day, but that's likely would be Fridays and Mondays. Though I'll need to have a look at a calendar. |
Hi @Civil, would Wednesday, August 31st at 6:00 pm CEST work for you? |
Unfortunately Wednesday is the only day a week that I can't do any meetings in the evening. In general 6 PM CEST works for me any other day. |
Would Thursday, September 1st at 6 pm CEST work for you? |
Yup, that would work for me. |
Awesome. What is your email address, so I can send you a Zoom invite? |
Great, I sent you the Zoom link |
Thanks, got an email with invitation. So see you this Thursday (1st Sep, 6 PM CEST)! |
Closing this. We have already sent our changes to the upstream 🎉 and we plan we remain updated by sending regular PRs and/or working directly on the upstream whenever we can. |
Just wanted to open an issue as I've been asked, to track discussions about overall life with upstream.
By that I mean that we definitely should discuss how we pick features from each other, maybe have a discussion about overall directions of the project (I don't actively maintain things myself, however that doesn't mean that I don't plan to implement anything, and there are some active contributors as well).
And I think if we do that early enough we might save ourself from a lot of TOIL in the future.
The text was updated successfully, but these errors were encountered: