Some Firefox users may need to log in more than once to log in. It's a known Firefox bug. Check "keep me logged in," it might help.

Es posible que algunxs usuarixs de Firefox tengan que conectarse más de una vez para iniciar sesión. Es un error conocido de Firefox. Marca "keep me logged in" (mantenerme conectado), puede ayudar.


Tech meeting 2022.07.21: Difference between revisions

From Bike Collectives Wiki
 
(6 intermediate revisions by 2 users not shown)
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.]]
  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.]]
[[Category:Meetings_and_minutes]]


==Agenda==
==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
* 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 '''✓'''
* Assess tech priorities
===We fixed things===
===some possible priorities===


====bikecollectives.org====
====Sidekiq (the thing that sends emails from bikebike.org)====
* replace background image at bottom of bikecollectives.org
* Shortly after opening registration, bikebike.org stopped sending emails!
* integrate with bikebike.org
* 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!'''


====wiki====
====Registration Hangups====
* get the wiki running at a usable speed (where it doesn't sometimes take several tries to save edits)
* 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. 
* make it so people can use the visual editor.
* 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.
* Make it easy to add an org
'''* It is now fixed!'''
 
====bikebike.org
* replace bikebike.org software
* contact form

Latest revision as of 05:07, 22 November 2024

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!