Here is another implementation: Another Blog Resurrection, the Fediverse, and a New Comment System

By "lurking" I understand: they would be here reading and voting but not engaging otherwise. In practice, is it any different than not being here at all?

If by "lurking" you mean that they would be here posting under pseudonyms and asking me if I would be able to identify them... Then it's a more interesting question. But I don't think I would be able to identify them from their style.

Isn't that up to the person using the bot?

The post is what started the whole ADR wave in the industry (I think there was also a conference talk by him). https://adr.github.io/ has a list of resources (templates, articles, examples, tools, etc.).

We do that in a meeting. In some cases it may take several meetings before we can make a decision. But I think those are generally fruitful meetings (I don't see them as waste of time). PRs give people a chance to think about these on their own pace, but when it comes to decision making, I feel like meetings actually save time (provided that people are sufficiently informed).

It's also possible that our ADRs deal with higher level decisions and is therefore easier to establish some sort of a consensus. From your description (especially the "refactoring" bit) I thought maybe you are using ADRs at a level that is closer to code. I cannot really think of our ADRs stopping people from refactoring the code in any way :)

I see. I guess if it's accepted then you update the Status in the PR and merge it? There isn't a single ADR format; there are several ADR formats that are successfully being used by different teams. The format I had in mind was the one introduced by Nygard (linked article). In our case, we generally first discuss the topic and then write the accepted decision in an ADR. So, there isn't much room for discussion/voting afterwards.

But it's good to learn about other people using it in different ways (a learning opportunity for me). It's interesting that you mention ADRs stopping people from refactoring. Do you have any examples you could give?

We started with with ADR, but then we also started using RFCs to discuss designs. Having this sort of minimal documentation really helps us in many aspects.

That sounds like you have slightly deviated from the simple ADR format (maybe not)? How do you perform the voting?

In programming.dev you can find the following:

• https://programming.dev/c/data_engineering
• https://programming.dev/c/sql
• https://programming.dev/c/postgresql

You can also request communities in https://programming.dev/c/community_request

I did the same. I submitted the default order without realizing that it was an ordered list.

I use identity to mean "account" here. Like a Google account that can be use both in Gmail and YouTube.

Oh yes, the perfect programming language.