I filed the issue on GitHub : The “Message(s) [and/or] Inbox / conversations” is too loosely denominated
What should be the one name of this messaging page?
“Message Inbox”, tells the HTML title.
“conversations”, tells the URL.
“Messages”, tells the button’s link title.
“Inbox”, tells the page itself.
Note: This discussion was imported from Loomio. Click here to view the original discussion.
I’m fine with conversation.
‘Conversations’. Although I’m happy for the heading on the page itself to read ‘Inbox’, which is what it is displaying down the left-hand column.
I agree. conversation/conversations sounds good. Inbox could stay as a good title for the list of conversations.
I think as well that it should be universally referred as Conversations (plural).
However, I wouldn’t mind if we’d read “Inbox” on the page itself, as long as the HTML head title would display Conversations.
Since we’re all agreeing with Conversations, I think we’re ready for a proposal!
Proposal: Universally rename the Message Inbox “Conversations”
YES : You think that “Message Inbox”, “Conversations” and “Messages” should be merged into a single identity : Conversations. However, the page itself will keep the “Inbox” title.
NO : You think Conversations is a bad name or there’s no need for change.
Outcome: YES : “Message Inbox”, “Conversations” and “Messages” will be merged into a single identity : Conversations. However, the page itself will keep the “Inbox” title.
Votes:
Note: This proposal was imported from Loomio. Vote details, some comments and metadata were not imported. Click here to view the proposal with all details on Loomio.
Do you think it really is important to make the close date so distant? A whole week is quite long… and so far it seems pretty unanimous.
Yes.
Alright then!
OK, pretty much unanimous. Before I make a PR (unless someone else wants to do it), should the labels be changed (e.g. ‘message_inbox_badge’ to ‘conversations_badge’) or just the text itself?
@goob Just released the outcome.
Yes, that would be more intuitive especially for future developers.