Open iteles opened 7 years ago
linked to https://github.com/dwyl/dwylbot/issues/59#issuecomment-308034858 (How to notify errors) We also need to classify our list of errors/warning: "we should have a "scale" of words to describe the degrees of "errors" in our workflow" I've started to split comments in two categories error (starting with :stop_sign: in the comment) and warning (start with :warning: ) but it's very basic and we should create a hierarchy of our rules
The full-stop followed by 'Thanks! ❤️' reads as passive aggressive to me
I think for now we should make comments short, simple and informative of the error and we should revisit this discussion when we receive feedback from testing or when we begin to discuss dwylbot as a brand 👍
@simonlab have moved your comment here to a separate issue https://github.com/dwyl/dwylbot/issues/93
After receiving user feedback (#143), I've revised that messages will be "dwyl-style" - friendly, supportive, helpful and full of emojis 👐 🤗 ✋ 😄 🤖
Next step:
What should dwylbot's voice and tone be?
dwyl already has a playful style, with an informal tone and love for emojis. Our conversational style has been called out as setting us apart and being easy to jive with.
Which route shall we go down for dwylbot? Do we want to keep to this or make it less so?
For example:
versus
Or an amalgamation of the two? i.e. the first option but a bit more explanatory (with context), like the second option?