> In proper tools that are designed to solve a specific need, not try to do everything: badly.

And when you want to search for that one thing that you know got documented somewhere, but can't remember where, how many systems do you have to search?

That's one of the reasons I like the code, issues, docs (code or wiki depending), and discussions all in the same repo.

Not to be confused with Chat, which is more ephemeral, and is, for us, in Slack. But we have to be mindful of chat discussions that turn substantive and make sure we copy that info to a Discussion in the repo (which can be annoying to do and annoying when it's not done).

> And when you want to search for that one thing that you know got documented somewhere, but can't remember where, how many systems do you have to search?

Not GP, but is that actually a real problem? Take a project like OpenBSD where the code, the bug tracking , and the design discussion happens in different place?

Even in reality, you don’t put the workshop in the conference room.