-
Notifications
You must be signed in to change notification settings - Fork 38
onboard @aandis #465
Comments
Sure! #3872 looks interesting. I was also going through #835. There is some interesting read here. +1 @rohitpaulk for that. Will go ahead with one of these! ;) |
@aandis Awesome! If you have any general questions feel free to ask them here. :-) |
👍 |
For reference - Second PR is at gratipay/gratipay.com#3893 :) |
@aandis I've sent an invite to join the Gratipay team on our GitHub org. Note that our normal pattern is to make PRs from branches in the main repo (rather than in personal forks), so that we can all collaborate on the PR as needed. Thanks for joining us! 💃 |
👍 |
We're almost done with changing the emails schema to use id instead of username (part of gratipay/gratipay.com#835). Latest PR is gratipay/gratipay.com#3896 @aandis - Once we've got this out the door, I think you'd find it more fun to hack on other tickets rather than sticking to completing #835. i.e. If writing the same migrations for every table starts to get boring, move on to something else - you could help out a newbie next time and we'll eventually get #835 done. :) Tickets that I think you'll find interesting - gratipay/gratipay.com#3894, gratipay/gratipay.com#3460 Issues filed under milestones are a great way to find work that is high-impact and mostly ready to work on - https://github.com/gratipay/gratipay.com/milestones (Team Basics, and Pivot - in particular) |
Awesome! Thanks for the tip. Will check them out! 😃 |
!m @aandis @rohitpaulk I'm following along silently, loving what you're doing! 💃 |
You feelin' onboarded, @aandis? Anything else you wanna say here? |
Nope. All good, I'll close this. :) |
Welcome. :)
|
!m @aandis 💃 |
Thanks for gratipay/gratipay.com#3888 and gratipay/gratipay.com#3891! May I add you as a collaborator on our GitHub organization? What do you want to work on next? 😄
The text was updated successfully, but these errors were encountered: