Tech meeting 2022.07.21: Difference between revisions

Latest revision as of 21:22, 25 July 2022

Whoops I put the 7/19 meeting minutes here.  They have been moved to the correct place, which is here, click me.

Minutes

Clarify that B!B!E! is not B!B!, it is a separate thing. It is a virtual "Bike!Bike! Everywhere!" event and an entity that supports the Bike!Bike! community. Probably a little like how "friends of the library" isn't the public library ✓

We fixed things

Sidekiq (the thing that sends emails from bikebike.org)

Shortly after opening registration, bikebike.org stopped sending emails!
Not sure why this happened; Godwin had to go log in to the gmail account for info@bikebike.org to unblock it
It continued to be broken because Godwin had to change the password to be able to log in, and that reset the application-specific password. This evening Godwin went in and got a new application specific password and put it in bikebike.org.

* email sending seems to work again!

Registration Hangups

Jonathan & Angel were both stuck at the Language selection step and couldn't go forward. I think this is because they had started registration before I altered the registration steps.
Turns out I had made a mistake when monkey patching the RegistrationSteps.available_steps method; it's important to run the .select { |step| send("#{step}_available?", registration) } on the list of steps, and that wasn't happening.

* It is now fixed!

@@ Line 1: / Line 1: @@
+ Whoops I put the 7/19 meeting minutes here.  [[Tech_meeting_2022.07.19|They have been moved to the correct place, which is here, click me.]]
-== Miscellaneous ==
-Godwin (of the original bikebike.org software coding project) can start making himself available to attend tech meetings!  He proposes Thursdays at 9pm.  This is the tentative time, to be changed if it doesn't also work for Jonathan.  A recurring one-hour meeting scheduled on a workday (pacific time) could also work.
-Minutes are based on memory because the meeting was supposed to be recorded but Jitsi LIED to us and didn't record the meeting as far as we can tell
+==Minutes==
+* Clarify that B!B!E! is not B!B!, it is a separate thing.  It is a virtual "Bike!Bike! Everywhere!" event and an entity that supports the Bike!Bike! community.  Probably a little like how "friends of the library" isn't the public library '''✓'''
+===We fixed things===
-==Attendees==
+====Sidekiq (the thing that sends emails from bikebike.org)====
-Angel, Darin, Godwin
+* Shortly after opening registration, bikebike.org stopped sending emails!
+* Not sure why this happened; Godwin had to go log in to the gmail account for info@bikebike.org to unblock it
+* It continued to be broken because Godwin had to change the password to be able to log in, and that reset the application-specific password.  This evening Godwin went in and got a new application specific password and put it in bikebike.org.
+'''* email sending seems to work again!'''
-==Angel's notes (planning and coordination)==
+====Registration Hangups====
+* Jonathan & Angel were both stuck at the Language selection step and couldn't go forward.  I think this is because they had started registration before I altered the registration steps.
-* It's hard to keep tech volunteers.  After every B!B!, they get really excited and stick around for a little while but never stick around long enough to make things happen.
+* Turns out I had made a mistake when monkey patching the RegistrationSteps.available_steps method; it's important to run the .select { |step| send("#{step}_available?", registration) } on the list of steps, and that wasn't happening.
-* What about asking for a specific length time commitment?  Then you scare off potential volunteers.
+'''* It is now fixed!'''
-* Godwin says nobody uses Ruby anymore and we might have an easier time finding volunteers if we use a trendy new codebase so that people can hop on, add their pet feature, and then wander off again.
-* bikebike.org's code is AWESOME but also is eroding more and more each year.
-* When it was built, they didn't plan for a pandemic.  They weren't imagining a virtual use case scenario.
-* Godwin is available to schedule a weekend some time to power through starting a new bikebike.org software project.  Starting a project is sometimes the hardest part; then you can chip away at it.
-* Godwin is available to spend 1-2 hours every ... week? I forget how much time.  But basically, Godwin is willing to chip away at this bit by bit, even if it takes  year or even 2 years, to build something new.
-* Darin mentioned that when we were having tech meetings post B!B!E!2021, we reviewed existing conference software.  Existing conference software isn't concerned with being multilingual.  Nobody is working on multilingualness in conference software.  They're all focused on adding support and features related to things like choosing which workshops to present,  which is an issue we may run into in the future, but it wasn't a feature we needed last year, and we'll do ok without it this year, too.
-* Frank is now 8 months old, Godwin will coordinate with Kathryn to make B!B! software meetings happen.  He has extremely-limited availability, but it's a deeply-held value that this be an usable resource for the community.
-* Someone emailed Godwin a couple years ago and pointed out that we should replace the photo at the bottom of bikecollectives.org with the white person with dreadlocks.  Probably through the contact form on bikebike.org, which is not a good way to reach anyone, because any email that gets sent through that contact form will get buried because it is also used by spambots to send hundreds or thousands of spam messages.
-* It would be nice to redo bikecollectives.org and integrate it with bikebike.org.
-* Bike!Bike! Everywhere! has a free option and it almost certainly always will.
-==Darin's notes (technical details)==
-We had a fairly productive meeting; discovered a major issue with our proposed change; I'm currently attempting to resolve it.
-* we forgot to account for the "next" button on the payment page; not sure what requirements must be met for it to appear but we didn't meet them
-* probably best to move the donation to the end of the registration process and use a conditional to eliminate unneeded registration steps, including payment
-- a good conditional to use is in app/views/conferences/_conference.html.haml (but only on the server, not on github!):
-    conference.city_name.present? && conference.city_id == 433
-    (it selects for conferences at the south pole, city 433)
-* the registration steps are (we think) determined in app/controllers/conferences_controller.rb in the required_steps() function.  UPDATE: it's not working.  they may be defined elsewhere.
-* restarting unicorn is the correct thing to do after the kinds of changes we're making
-Sent an email asking Jonathan "If there's a way for me to access your test instance, that might ease the process a little.  Right now I am troubleshooting live on bikebike.org which is suboptimal."