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 Todo List

From Bike Collectives Wiki
Please list task, any relevant notes, and date added.

BikeCollectives.org front page

Miscellaneous

  • https://opencollective.com/bikebike-everywhere/projects/tecnologia-tech/updates/2023-tech-news-noticias-tecnologicas-de-2023 -Angel York (she/her) (talk) 05:49, 12 January 2024 (UTC)
    • Yay, it is up. --Jonathan Jan 15
  • have a tech meeting --Angel York (she/her) (talk) 04:51, 13 January 2024 (UTC)
    • I am still working on a long list of todos, and correcting major issues as they arise. For instance, updating Mailman3, and hardening the software from subscription spam. I'll call a tech meeting when it becomes prudent. (Jonathan)
      • We all really appreciate all the hard work you've put in. Someone just today was saying how smoothly the tech transition seemed to have gone from an outside perspective. You do a lot of skilled work, and everyone benefits from it. April does a lot, too. I know my role is soft skills, but I do a lot, too. But I thought we were a team. Occasional meetings are a part of that, so we can all stay on the same page. An opportunity to talk about things, like google captchas. For instance, I found a potential skilled coding volunteer who said they're looking for something to do. If they pan out, I thought it might be nice to catch up first. It's been quite a while. I know you've had a lot going on in your life lately and I've been wondering how you're doing. I hope you're doing ok. --Angel York (she/her) (talk) 08:39, 16 January 2024 (UTC)

done

  • hyperkitty 10 minute project https://lists.bikecollectives.org/hyperkitty/list/thethinktank@lists.bikecollectives.org/message/UAXPYXWBNV2SPPE7SETDFXMPYK4EHSFB/ --Angel
    • Just part of what I do. I do a lot of administrative actions behind the scenes: Make sure people are properly subscribed, correct broken threads and glue them back together, expunge content that could be used by spammers (like that link to a list of email addresses which ended up on the archive - that link was removed) --Jonathan Jan 15
      • I know. We still need more tech volunteers so the bus factor isn't as much of an issue. --Angel York (she/her) (talk) 08:39, 16 January 2024 (UTC)
      • That shall come with time. Even before getting there, it's important to establish a firm base, and a critical component to that is maintaining documentation on a revision system with bug reports, and good testing protocols, etc. A wiki does not provide the best environment to accomplish this feat (even with its revision system), which is the point I am trying to make. But, it is a good temporary solution, and can be used concurrently for some tasks. However, when that component is in place, that is when meetings and training and onboarding new volunteers will become much more practical.
        • I know we decided that at a meeting a couple years ago give or take, but this comes as a surprise to me because it's a change from what we all agreed on at the meeting where we wrote the OCF tech update call for volunteers section together. Anyway it's a moot point for now, the person who made a post to mastodon saying they were looking for somewhere to donate a few hours each week to use their fluent coding skills never got back to us anyway. --Angel York (she/her) (talk) 04:56, 18 January 2024 (UTC)
          • Actually, at the last meeting we had a healthy discussion about the best way to approach code maintenance and documentation for system administrators. The most recent todo was to setup Gitea, however, the todo list on OCF predated that discussion. Currently, there are lots of docker-compose and Dockerfiles that are not part of any revision system, or adequately documented, except via the docker-compose.yml files or accompanying README files. Once Gitea is setup, there will be a lot more consistency, and it will make the whole process of introducing new people to the system many times easier, not to mention, avoiding a lot of unnecessary iteration (something software developers love to avoid). If you do not build a good foundation, the house will fall down, and often the foundation building process is the most time consuming part. I'll admit, after that last meeting I got distracted with setting up matrix (via experimentation with matrix-docker-ansible-deploy on one of my servers), but then I got busy with other volunteer commitments. However, Gitea was what I should have been working on, rather than the Matrix :) From my standpoint, this long written conversation we have been having, actually constitutes a meeting, until the next meeting when that important TODO is in place. --Jonathan 1-18-24
            • Yes, I absolutely agree, this should be a meeting. Plus then we could do small talk, too! And your cat could have come! Mind if I cut and paste all this and move it over to a meeting page so it isn't cluttering up the to do list? I don't know precisely which meeting it was, I'm pretty sure it was in June, but I know for a fact that we all worked on that tech update in a shared doc together in a tech meeting, including what we want in a volunteer. I had to push for several meetings to finally get it off the agenda and into the conversation at the meeting. It also sat in the shared doc for a long time before it got translated. We always try to do big announcements this way so that everyone has a chance to iron out the details. Anyway, I'm glad you're working on the Gitea thing now, thanks for doing that. P.S. Four tildes gets you the pretty time stamp if you want it. --Angel York (she/her) (talk) 20:07, 18 January 2024 (UTC)
              • The cat says Meowww Meowwww (Hi)! PositiveSpin (talk) 02:27, 20 January 2024 (UTC)
  • update https://github.com/bikebike/BikeBike to reflect changes made within the past 5 years, or update the link on bikebike.org to where we're keeping the updates nowadays. --Angel York (she/her) (talk) 22:37, 15 January 2024 (UTC)
  • bikebike.org is doing the thing again. --Angel York (she/her) (talk) 22:37, 15 January 2024 (UTC)
    • Corrected: browserlist hadn't been updated (I was wondering if that was a requirement when I first set this up, and now we know), this has been added to the ofelia (cron) -> `pnpm update browserlist@latest` --Jonathan Jan 15

bikebike.org

hopefully relatively small fixes?

  • update https://en.bikebike.org/humans.txt --Angel York (she/her) (talk) 08:39, 16 January 2024 (UTC)
  • update git link at bottom of bikebike.org --Angel York (she/her) (talk) 08:39, 16 January 2024 (UTC)
  • add the mastodon, instagram, and ThinkTank links at the bottom of bikebike.org next to the facebook logo --Angel York (she/her) (talk) 08:39, 16 January 2024 (UTC)
  • change "passed conferences" to "past conferences" on the conferences page --Angel York (she/her) (talk) 08:51, 16 January 2024 (UTC)
  • add mastodon and instagram to the logos in the footer, maybe some of the big communications apps people in countries outside the US use frequently, too

medium fix

wiki

  • Update MediaWiki - we're out of the support window for 1.38 as of June 2023. Rather than jump to the latest 1.41 release, which ends support in December 2024, it seems like we should probably just update to 1.39 LTS which is supported until November 2025; then we get a couple of years before we really have to upgrade again. I can do this and document the process as I go, since it seems like there will be some quirks relevant to our particular setup, but I want to check and make sure I'm doing things right. Jonathan, could you review the following? --AprilWick (talk), 19 January 2024
    • sub-tasks:
      • back up the database and files
      • Download the new release and replace the old release files
      • Update the database using mw-config/index.php
      • Check release notes for any configuration variables that have changed
      • Download and install updated extensions, and install RenameUser and PageForms because we'll need them going forward
      • Test everything
    • April's questions
      • Jonathan, it looks like you have notes on dumping the database in docker/bikecollectives/README, but they're a little sparse. Will the "docker exec mediawiki2_mariadb mysqldump..." be sufficient? And do you expect the "database not recreating" issue mentioned there to come up during the upgrade, or was that just a migration issue?
      • I know you've got containers for testing in docker/mediawiki. Seems like I should test the update in one of those first, or possibly using a... commit? of the production container so I'm testing with the latest everything?
        • That's the plan - Always perform testing/coding changes in the staging instance. The magic of docker is that you can setup a staging environment anywhere, including your home directory. This time, I'll setup a new staging instance with the current data so you can perform PageSchema tests. Once everything is good, the changes can be committed to live.
        • (PositiveSpin (talk) 07:16, 25 January 2024 (UTC)) April, you are good to go. Before you proceed:
          1. Read through the whole new README.md . You'll need to use a markup capable editor to view it. Visual Studio Code has a nice preview feature.
          2. Git is setup for both staging (push) and production (pull), the README.md covers this.
          3. Our MediaWiki database and image volumes are huge, hence the reason for having the staging environment adhering to some special rules.
          4. Login with your normal credentials. Your normal login already has permissions for bikebike. This makes who checks more logical, too.
          5. The type of administration we are doing now is almost completely version controlled based. Docker is actually a type of version control system. There are real differences with archaic LAMP administration, but obvious overlaps, too.
          6. There are some minor differences between the 1.38 and 1.39 Vector skin. Place production and staging side by side to observe the differences. I am thinking the changes are nice, and we should stick with them.
          7. Ask me questions about anything you don't understand.
          8. Yay!
  • Consider setting up PageSchemas for other info eventually, e.g. shop documentation (shop manuals, volunteer guides, instructional materials, codes of conduct, etc.) --AprilWick (talk), 19 January 2024
Retrieved from "https://bikecollectives.org/wiki/index.php?title=Tech_Todo_List&oldid=50554"