Zulip bots and integrations agendas
This doc contains the agendas (and any notes) from Zulip bots and integrations team meetings.
Anyone should feel free to add items to this agenda; it’s just a draft.
2017-07-06 9AM PST
- Progress since last week:
- Neil:
- #5624 [open] - Test state in bots (ie. using StateHandler); tests for tictactoe bot
- Working on update_message testing; tests for incrementor bot, blocked by #5624
2017-06-29 9AM PST
- To discuss?
- Separation of bots into external repo? (discussion yesterday on #integrations)
- Future of update_message (generally? for bots? probe support?)
- PRs (from progress this last week)
- Progress since last week:
- Neil:
- Learning more about how the mocking works; split testing multiple-responses and return success out of #5502 into #5587.
- Commented/reviewed some PRs.
- Plans for next week or so:
- Neil:
- Develop more test support (state? update_message?)
- Push PR for multiple-responses (demo code for bot feature & testing)
- Research slash command supports among chat systems
- Remaining major projects for the interactive bots system:
- Build a documentation framework similar to the /integrations/ one (ideally, use the existing code with just some sort of tag/option)
- Improve our general API documentation
- Building StateHandler support for the various different interfaces
- Test suites
- Eliminating network access from the existing bot tests
- Adding tests for bots running in Travis CI
- Dependencies and packaging:
- zulip, zulip-bots, and zulip-bot-server packages?
- Nice requirements file for the zulip-bots package.
- Extensive user testing of pip install through running an existing bot and debugging the process.
- Getting extensive user testing of the sequence from pip install through having a working new bot. Might find we want a template one can copy to start, etc.
- Slash commands feature.
- Slack-style interface for outgoing webhooks (would want to test that actual Slack bots using that API work).
- [Embedded bots] Banning state not tracked through StateHandler in bots (no globals at the top of the file, etc.)
- [Embedded bots] UI for creating/activating an embedded bot user
2017-06-22 9AM PST - fifth meeting!
- Progress since last week:
- Neil:
- Minor PR to support more message keys in check_expected_responses [merged]
- Opened WIP Pollbot PR; awaiting further feedback, though depends upon alternative code being added to avoid use of update_message (#5426)
- Developed PR to clean up bot testing including adding support for testing multiple bot responses (send_*) per call, send_* success/failure, … (#5502)
- Simple Subscribe bot developed, illustrating use of multiple bot responses; cannot be tested fully pend #5502.
- Rohitt: