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

(wip) presence: Display in the sidebar when bots start and stop. #7938

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

marco
Copy link
Member

@marco marco commented Dec 29, 2017

This allows bots to be marked as listening, and displays them in the sidebar if they are.

For example,

bot activity

For this to work, it would require zulip/python-zulip-api#271 to be merged in order to call the realm/mark_bot_listening endpoint when zulip-run-bot is called.

(Done for the "Issue zulip/python-zulip-api#151 [Feature proposal] Make bots announce their startup/shutdown." Google Code-in task.)

@marco marco force-pushed the announce-bots branch 7 times, most recently from 0afd19b to 4a63a2a Compare December 29, 2017 19:52
The listening bots are the bots that are currently active on the realm.
@marco marco force-pushed the announce-bots branch 3 times, most recently from 17bc1c0 to 638020d Compare December 29, 2017 21:16
`do_mark_bot_listening` can be called to add a bot's name to the
`listening` list. It can also be used to remove bots.

Whenever `do_mark_bot_listening` is called, it uses
`do_set_realm_property` to start a `realm`-type event.
@marco marco force-pushed the announce-bots branch 3 times, most recently from eb187e9 to 6c449a2 Compare December 29, 2017 22:28
`realm/mark_bot_listening` takes 2 options: `bot_name` and
`is_listening`.

`python-zulip-api` can use `realm/mark_bot_listening` in `zulip-run-bot`
to add a bot to the `listening` list.
Display the listening bots underneath the user presence list. Each bot
should have a green "active" dot next to it and a bot icon to the right.

Fix zulip/python-zulip-api#151
@marco marco changed the title [WIP] presence: Display in the sidebar when bots start and stop. presence: Display in the sidebar when bots start and stop. Dec 29, 2017
@showell showell changed the title presence: Display in the sidebar when bots start and stop. (wip) presence: Display in the sidebar when bots start and stop. Dec 31, 2017
@showell
Copy link
Contributor

showell commented Dec 31, 2017

I put "wip" in the title to reflect that we need a slightly different approach here.

@skunkmb You can inform your GCI mentor that I'm satisfied with this PR in terms of GCI credit, even though we'll need more work to merge it.

@marco
Copy link
Member Author

marco commented Jan 4, 2018

@showell @roberthoenig Hello! What is the current status of this? Is there anything I should be working on? I know we discussed that possibly @roberthoenig would do some work on the backend and after that I would rebase this to contain only frontend changes.

There is no rush, I just wanted to make sure that there isn't something that I should be working on. Thanks! 😃

@roberthoenig
Copy link
Contributor

@skunkmb sorry, missed your comment. So this is the next thing I'll be working on, probably rewriting the backend code to the changes we discussed, and reusing your frontend code. Will ping you in any new PRs on this.

@marco
Copy link
Member Author

marco commented Jan 17, 2018

@roberthoenig OK, great, thanks!

@zulipbot
Copy link
Member

Heads up @skunkmb, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/master branch and resolve your pull request's merge conflicts accordingly.

@alya alya removed the needs review label May 22, 2023
@timabbott timabbott force-pushed the main branch 2 times, most recently from 4ec3636 to 88b200c Compare August 18, 2023 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants