Community#

Glasgow Interface Explorer is a community-driven project that coordinates via GitHub issues and real-time chat channels on multiple platforms:

All of our chat channels are bridged together; regardless of which one you choose, your messages reach everyone on all of the platforms. Note that what you say will be logged in a public archive indexed by search engines.

Fediverse#

Many of the community members involved with the project have Fediverse pages; @esden@chaos.social has been writing a lot about the process of mass manufacturing the hardware.

You, too, can join the conversation via the #GlasgowInterfaceExplorer hashtag. Please avoid using #Glasgow; we are not talking about the city. (Unless you live there, in which case both are appropriate!)

Weekly meetings#

Every week we conduct an informal developer meeting on our chat channels, discussing the progress over the last week, outstanding issues, and any other matters that need attention. At the moment the meeting is scheduled every Saturday at 22:00 UTC, and the typical duration is one hour. Anyone is free to attend, and we publish our past meeting minutes.

When conducting a meeting, we first discuss nominated issues, and then anything else that is brought up. Once discussed, the nominated tag is removed.

Acknowledgements#

The Glasgow project has been built by its many contributors, including some without whom the project would not have been possible:

  • @whitequark originated the overall design, coordinates the project and implements most of gateware and software

  • @awygle designed the power/analog port circuitry and helped with layout of revB

  • @marcan improved almost every aspect of hardware for revC

  • @esden is handling batch manufacturing

  • @smunaut provided advice crucial for stability and performance of USB communication

  • @electroniceel improved the hardware for revC2, designed the test jig and is working on advanced protection circuitry

  • @Attie improved and refactored many applets, hardware photos

  • @mwkmwkmwk does important maintenance work to keep the codebase in good shape