What is the performance issues - we need to see the problem - new GH issue. If it is then is easy for us to upgrade AWS as is, just click a few buttons to spec it up
The ‘control’ issue is really 1-2 hour job to move to a new AWS account - @lauriewayne1 when framed like this is it still a priority?
eco-friendly difficult to prioritise this right now, and is it what we want. We need a strategy around values-aligned and how much resource we put into it
Canada increasing concern about data being hosted in the USA
XX Map focus for new volunteer dev: starting a Wishlist / discussion forum re. map, to include:
Map ux improvements
Completion of OSM
OSM / Google - continued co-existence? If we build features in one / both etc?
Notes from topics covered in the session
Need to start thinking about how to onboard the product manager this week.
Thanks @Kirsten for the notes!
I now realize we haven’t discussed when we will resume StripeSCA development, ping @Rachel
StripeSCA is still the top priority and it’s likely we will decide to restart it soon. We can probably make the call when most people are back from holidays.
I believe it will land somewhere between/before point 5, 6, and 7.
It’s not a small task. There are quite a few parts to it. I am afraid we are something like 50% done only
given that we think / hope that 4. might also be almost done, that would mean bumping 5 and 6. I don’t have a good feel of the size of 5, but I don’t think I would support putting 6 behind another chunk of SCA that’s as big as the last one. I would support doing 6 first, maybe that will make it marginally easier to finish SCA, and/or to bring in more devs etc
@Kirsten we need to keep in mind that it means upgrade Rails for Stripe Connect and Stripe SCA. At least on the testing side we need to double our efforts We have no automated tests on Stripe yet… everything is manual.
Let’s also see this list as a priority list, not a list in which each dots will be released. If @luisramos0 is not working on SCA, then he can work on 5 or 6 in parallel.
I wonder with this discussion if 6 isn’t too low in our priority list. If we start T&C’s before we will to upgrade this new feature as well
@lauriewayne1 can you check the comments above re. the US server and let us know your thoughts on urgency? If there are performance problems please create a github issue and document them
If it’s mostly about migrating the services from one AWS account to another so that it’s under your / our control that’s 1-2 hours
Values-aligned providers are something we’re all interested in but aren’t in a position to prioritise at the moment. Consideration will be given to this as part of our product vision and strategy process - - commencing soon (yippeeee!) I think we think that geopoliticial considerations can be part of this discussion too.
I think the urgency is high to get a server that we have control over. Everything else can wait - I don’t have an opinion about performance/capacity because we don’t have a monitoring process in place (but we will!). I am totally fine with staying on AWS for as long as it makes sense given the global product vision and strategy.
ok so I will create an issue for the migration of the US server into an AWS account that we control . . and put it at the top of ‘all the things’ . . I think - or ‘dev ready’ so we don’t forget about it?
Thank you @Kirsten! I’m thinking about the communications/user support/testing strategy for this transition so there will be way more coordination required than with usual changes (even big ones).
no i don’t think there will @lauriewayne1 - I am assuming that the users will see nothing at all, perhaps a few moments of downtime. So basic upgrade checks should be fine. I may be wrong - dev who does it can confirm - @maikel and @Matt-Yorkley are the only ones online this week though . .
I’m not 100% sure what’s involved here (if it’s just switching accounts) but I would expect the downtime to be between 5 minutes and 1 hour and we can do it at 3am to not impact users. Pre-communication is probably not needed because we can display a maintenance message during the downtime.
When it comes to users I always err on the side of overcommunication. @lauriewayne1 you could always just use that popover banner we have on the homepage to let people know and direct them to a message on your website?
I view this as an opportunity to build good feelings among the users about OFN - letting them know ahead of time seems like just good general practice and easy enough to do (and helps people understand that it’s a planned outage, not just “the server fell over and they are trying to fix it”). Really, from my perspective it’s more about building confidence and making the users feel involved and included than anticipating it causing any problems for anyone - I view this as very important as basically everyone is new and we are building our user community now. And @maikel I also appreciate that the migration can happen at a time when it’s very unlikely anyone would be needing it anyway. So I would like to give people a few days notice and use that to also remind them that despite incredible growth and lots of updates, OFNUSA’s downtime this year has been zero (I think).
We have no automated tests on Stripe yet… everything is manual.
