Welcome to infrastructure Discussions for Noisebridge

[mcint]

👋 Welcome!

We're using Discussions to capture ideas and wishes of the Noisebridge community, and address them coherently, seriously, and collaboratively:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

This repo defines configuration for Noisebridge's live infrastructure, which is discussed by the meetup group but is owned by, is the responsibility of, the #rack guild. Find other discussions in Discord (and Zulip).

So that we might support a larger base of contributors, include a little about your background, interests, or other projects in the intros thread.

[jetpham]

Should we have this be in discussions or Zulip? I'm partial to using zulip more for this

[SuperQ]

I'd rather stick to a publicly accessible platform. But I'm also not sure if this is needed when we already have the issues system for discussing in public.

[mcint]

Zulip has support for publicly (logged-out) readable channels. We could promote, externally link to, some threads for public visibility. Zulip also has open signup with email or "Social"s OIDC, in fact, I've had to ban a user.

[mcint]

If you feel like you've had the same conversation more than once, twice, thrice—maybe within a week, and people are clamoring for solutions, information, a way to help, how else best to turn on the spigot?

[SuperQ]

I don't see Zulip as a useful platform. It's yet another random thing that needs to be used and maintained.

I would much prefer the minimum number of platforms.

We need at a minimum:

• A git repo
• An issue tracker

Currently we do this on GitHub. It's a common enough platform that requires zero effort from Noisebridge to maintain. There are other hosted Git platforms that we can easily switch to.

I don't mind having an infra discussion forum, but I don't want additional fragmented platforms. So we can use GitHub discussions, wiki, etc. But I want to be intentional about reducing information fragmentation.

Today, Zulip is not a solution.

[jetpham]

Loren was quoting the ghostty repository's policy on having discussions before issues are opened to assure that the majority of issues are resolved before they even have to turn into issues if that makes any sense, but it could also be argued to say that the scale of our repository is much lower and the dynamic of our maintainers is very different aswell.

…

On March 12, 2026 11:48:22 PM PDT, Ben Kochie ***@***.***> wrote: I'd rather stick to a publicly accessible platform. But I'm also not sure if this is needed when we already have the issues system for discussing in public. -- Reply to this email directly or view it on GitHub: #441 (reply in thread) You are receiving this because you commented. Message ID: ***@***.***>

[mcint]

I'm specifically responding to conversations about the infrastructure repo, nb infrastructure more broadly, getting a lot more attention—due to website downtime, and a broadening base of interest in contributions.

For folks who are newer still that jet (there are a few people active after meetups) I want a place that is

• public—still tied to the repo
  • consensus building, in public
  • a shared written understanding of the range of opinions advocated for
    • We don't have policies in the README, pinned issues are a GitHub-feature rather than a git feature (and @ElanHR is mirroring repos to other forges)
• Topics don't need to be strictly "an issue" on "this repo".
  • Because of narrow acceptability criteria
  • And issues age out, aren't checked

Maybe I could pin some issues, and that would satisfy for reachable discussions.

---

Plausible alternatives excluded include:

• wiki (no culture of discussion thread there),
• Discord (excludes some users, Zaccahe entirely, afaik SuperQ and Jof in practice, different pacing)
• Zulip - has most of the right audience, sign up is open. I do call it a "chat forum". Conclusions don't make it back to the repo
• Discourse - discuss.nb.net is not up. Same for mailing list