Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename "(no topic)" to "general chat" #5838

Open
alya opened this issue Mar 6, 2024 · 5 comments
Open

Rename "(no topic)" to "general chat" #5838

alya opened this issue Mar 6, 2024 · 5 comments
Labels
P1 high-priority server release goal Things we should try to coordinate with a major Zulip Server release. webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.

Comments

@alya
Copy link
Collaborator

alya commented Mar 6, 2024

In zulip/zulip#23291, we plan to rename "(no topic)" to "general chat". This is expected to require some work to support on mobile, but the details of that are TBD pending design decisions that have not been finalized yet.

References

@alya alya added the webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity. label Mar 6, 2024
@mayankdhangar2408

This comment was marked as spam.

@gnprice

This comment was marked as off-topic.

@kartik-212004

This comment was marked as outdated.

@chrisbobbe

This comment was marked as outdated.

@gnprice gnprice added server release goal Things we should try to coordinate with a major Zulip Server release. P1 high-priority labels Jan 8, 2025
@gnprice
Copy link
Member

gnprice commented Jan 9, 2025

This feature appears to be landing in the upcoming Zulip Server 10, and will be one of the headline features there. So it'll be one of the few features we build for this legacy app.

I think the plan I'd like to pursue is to develop the feature first in zulip-flutter (zulip/zulip-flutter#1250), because development is more efficient in the Flutter app. Then when we've worked out all the questions there about what's involved and how the feature should work, we can port the changes over to this codebase.

This remains a task for the core team; we aren't able to spend time helping people work with the legacy codebase. For anyone interested in contributing to Zulip, see the zulip-flutter repo's README and Zulip's guide to contributing:
https://zulip.readthedocs.io/en/latest/contributing/contributing.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 high-priority server release goal Things we should try to coordinate with a major Zulip Server release. webapp parity Features that exist in the webapp that we need to port to mobile. We aren't aiming for full parity.
Projects
Status: No status
Development

No branches or pull requests

5 participants