Different streams can have different policies or shared information applicable to new people or people who just showed up.
IRC has topics for this.
Forum software lets you pin messages or discussions at the top.
It would be great if Zulip had this too.
You can specify a stream purpose in the Subscriptions page.
Could you clarify the sort of enhancement you'd want to see here?
At least in the version I'm using (hosted zulip.com) there's only stream name. Here are some examples:
Here's where we show descriptions:
Here's where descriptions can be edited:
Note that at present, only administrators for a realm can set stream descriptions.
Feel free to reopen if I'm misunderstanding your request.
I suspect @itamarst was filing this in response to my constant complaints. 😉
I would like to see these descriptions when we are viewing the actual stream itself, because that's when it's actually relevant.
Perhaps they could go in the area where the stream title & search box are now. Perhaps just beneath them? Or perhaps they could appear above the text entry box when entering a new stream message? (I think this is less good, for reasons below).
Another use case is for status information, e.g. for an engineering channel: "Build is OK | Next release 1.5.0 | General engineering discussion".
Here's an example from topic on IRC:
It's the text at the top starting with "https://twistedmatrix.com".
Note that it's always visible. This is surprisingly important, because it helps guide & focus conversation.
It's also editable in-place, which is also very important. The low barrier to changing it means that it stays up-to-date and relevant.
In summary: the stream purpose information that's already there seems a fine thing to show, but I'd like to always see it when viewing the stream and to be able to edit it directly while viewing the stream.
I'd reopen, but I don't have permission.
Add a draft roadmap doc.
@timabbott Will the major visual redesign take this issue into account or should we make some UX suggestions here with an eye towards implementation?
Our current visual redesign plans don't include this, mostly because we're not sure where to put it, so suggestions welcome!