To prevent miscommunication, I think i should create a general guideline of writing the standard summary and tips on how to communicate it with users, so that things like "what does it means, where to change, where to get those and how it works" can be efficiently communicated.
As this is just a tips, maybe we should not be a little bit too elaborate? i.e too detailed that makes the engineer/contributor overwhelmed?
First step, let's not do this: Acronymizing things, too much that it starts creating a new Bahasa.
Sample: https://twitter.com/resir014/status/1548512823218565120 (Credits to @resir014)
To prevent miscommunication, I think i should create a general guideline of writing the standard summary and tips on how to communicate it with users, so that things like "what does it means, where to change, where to get those and how it works" can be efficiently communicated.
As this is just a tips, maybe we should not be a little bit too elaborate? i.e too detailed that makes the engineer/contributor overwhelmed?
First step, let's not do this: Acronymizing things, too much that it starts creating a new Bahasa.
Sample: https://twitter.com/resir014/status/1548512823218565120 (Credits to @resir014)