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.


Manual: Difference between revisions

From Bike Collectives Wiki
No edit summary
m (→‎2021: spelling)
Line 35: Line 35:


===2021===  
===2021===  
* Main people involved were Kime (formerly angé), Étienne, Angel, and Darin.
* Main people involved were Kema (formerly angé), Étienne, Angel, and Darin.
* Ifny, Cweth, and Jonathan Rosenbaum did some meetings about tech after the event.
* Ifny, Cweth, and Jonathan Rosenbaum did some meetings about tech after the event.



Revision as of 05:21, 14 July 2022

So you've got access to some of the resources in the "who has access to what" document and you're wondering what to do with them.  Here's what they're for.

Communication Tools

This Google Doc: https://docs.google.com/document/d/1xC8BxX0Qliy1_7Ei_jA-4579o2H_z3Xb5ToUS7SBkH0/edit?usp=sharing contains information about various communication tools related to Bike!Bike! & bike collectives. If you need to send an announcement, ask a question, or otherwise get in touch with large groups of people, check it out. The document should probably be converted to a section on this wiki page.

Bike!Bike! Everywhere! and bikebike.org

bikebike.org interface

  • It's amazing. It was built by Godwin for managing in-person Bike!Bike! events and is very good at that. It is too rickety and custom to change, but its limitations for virtual conferences are obvious. It asks you what kind of food you eat and whether you'll need a bike and there's no way to change that really. Godwin thinks it should be rebuilt from scratch. Jonathan Rosenbaum thinks it's a beautiful work of legacy software and we should work with what we have. We don't have anyone clamoring to rebuild it anyway. Angel York (she/her) (talk) 11:02, 7 July 2022 (PDT)
  • It has a contact form. The email the contact form is associated with gets a LOT of spam. So nobody checks it, it just goes to Godwin. This is a problem because people think they can reach us using the contact form, but they can't. But spammers haven't found the real gmail address, which is also posted on the website. I'm afraid to ask anyone to remove the contact form because maybe then the spambots will keep looking until they find the real deal. We should deal with this at some point. Angel York (she/her) (talk) 11:38, 7 July 2022 (PDT)

Cryptpad (not google)

Has a variety of historical documents from Bike!Bike!_Everywhere!_2021.

Google

Gmail account

Drive contents

  • "who has access to what" document
  • Language justice tips for virtual events; language justice checklist
  • and more!

Meetings and minutes

Information aboutMeetings_and_minutes are hosted on this wiki. Identify someone at each meeting who will take notes, post the minutes, and update the wiki to include the minutes and post the information about the next meeting.

Miro

Used for Bike!Bike! Everywhere planning timeline (as of 2022)

Planning teams

The goal is for the planning team to rotate every year, with a three year term for any role.

  • Year 1 - Group A runs the event.
  • Year 2 - Group B runs the event with support and heavy involvement from Group A.
  • Year 3 - Group C runs the event with heavy involvement from Group B. Group A sits on their hands, bites their tongue, and answers questions as needed.

2021

  • Main people involved were Kema (formerly angé), Étienne, Angel, and Darin.
  • Ifny, Cweth, and Jonathan Rosenbaum did some meetings about tech after the event.

2022

Open Collective Foundation (OCF) (fiscal sponsor)

https://opencollective.com/bikebike-everywhere

They handle the money for us. Technically speaking, they are our fiscal sponsor. In 2021, Bike Farm did this as a favor, but they're just a community bike shop and fiscal sponsorship isn't really what they do. OCF does this professionally. They're really supportive and very much in line with the ethos of the Bike!Bike! community.

Zoom (video conferencing for the event)

Darin had a connection and got a free Zoom pro account or something for 3 years. It was used for 2021 and will be used for 2022 and will probably expire before the 2023 event and need to be re-donated or something else figured out. We chose Zoom for its interpretation and captioning abilities, but the field is rapidly changing and can be revisited if there's continued interest. Angel York (she/her) (talk) 11:02, 7 July 2022 (PDT)

Bikecollectives.org

Hosting

Dreamhost

Has been the host for a while. Still the host as of 2022 but I think the downtime is too high.Angel York (she/her) (talk) 11:02, 7 July 2022 (PDT)

Email

  • info@bikecollectives.org if I remember correctly, nobody checks it, it gets a lot of spam. We should deal with this at some point. Angel York (she/her) (talk) 11:38, 7 July 2022 (PDT)

Domain name registration

History

Bikecollectives.org was originally started by Jonathan Morrison, former Executive Director of the Salt Lake City Bicycle Collective. After he was no longer involved with this community, the Utah Bicycle Collective continued to pay for the website, while having nothing to do with the maintenance and running of it. Godwin has been doing that for many years, but is now very busy with a family, house, and full-time employment. Angel York (she/her) (talk) 11:02, 7 July 2022 (PDT)

In late 2021 they changed where it points, effectively vanishing the website from the internet. They thought nobody was using it. We got in touch, and they gave it to us. It is now a community-owned resource. That means the community is now responsible for paying for registration. 🚲 Donate to the tech fund here 🚲.

Porkbun (now)

The Utah Bicycle Collective kept bikecollectives.org at GoDaddy, but when we got ahold of it, we moved it over to Porkbun. They have a cute pig, a good sense of humor, they work great, and they're not GoDaddy.

Wiki

This wiki is a media wiki. If you don't know how to do something, you can go to mediawiki.org and it will tell you how to do the thing you want to do. It has a lot of resources because it's the same software they use to run Wikipedia.