Closed caharding closed 7 years ago
@caharding @rjmackay @jshorland
- All bots go through APP review, this is likely to take a significant amount of time even if they "help" us so should be accounted for/talked about up front. This is probably the main reason features would have to be reduced
Enumerate Usecases and User flow
1. Simple Bot
2. Report Bot
3. Register Bot
4. Polling Bot
@willdoran @jshorland @rjmackay I updated the user story into 4 stages up above.
@caharding Cool, looks good, I would be happy to help @Angamanga get setup next week to start making the basic bot if that fits with @jshorland scheduling?
@jshorland does that timing work for you?
@charlie @willdoran @angamanga I'm starting to get concerned about the amount of work piling up in platform. Especially with this non negotiable tech debt we need to fix, minimal devs, and we are almost through April. I'm scheduling a planning meeting with @willdoran @angamanga this week (EDIT: TODAY) to figure out how we are going to manage this.
On Apr 25, 2017, at 8:07 PM, Charlie notifications@github.com wrote:
@jshorland does that timing work for you?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I might be missing something but the "Simple bot" spec seems a little vague:
User is alerted they can report on violations
I assume this is: a user can send a message to the bot and it responds letting them know they can report violations?
We can take response to questions and rich data, this can be passed by to the platform
I have no idea what this really means?
User is linked to Uchaguzi
When? Based on what?
FYI there are a few possible PHP modules around for powering bots: https://github.com/setkyar/laravel-messenger-bot-management https://github.com/christophrumpel/chatbot-php-boilerplate
I'm sure there are more. That was just initial google results. But definitely worth seeing if there is existing code to speed us along
@jshorland @caharding @willdoran An update on the bot: It is still not finished to send to review so it will not be ready and reviewed for the 28th of May. Hopefully I will be able to send it to review by the end of this week. After discussion with @rjmackay yesterday we concluded that for this first version, I'll focus on being able to report to a single facebook-survey, consisting of Title, Description, Photo and Location(if the user want to share that). After that and after input from testers, we can add more functionality. Any thoughts / comments about that? Please ping me with more questions if you have any!
All good. After catching up yesterday it is clear that this is just the 1st iteration and we will deal with the more complex issues of survey mapping (required fields etc.) in the next iteration.
These are the features currently available:
@Angamanga Uchaguzi logo for the bot is here:
let me know if you need anything else.
@justinscherer Thanks! Nothing else right now...
logo with transparent background:
@Angamanga Could you create any follow up issues for this and assign them to the bot theme/milestone? Then we should close this one out.
I have moved remaining bot-issues to the lesson-learned document for now and closing this: https://docs.google.com/document/d/190KdcA_DcikAzBP31am6xdRxe4jaaqC07atnWJnceZ8/edit
Facebook is partenred with Ushahidi to help create a FB bot data source for the Kenyan election. Most people are on FB messenger, we should be there too.
Use cases and User flow
Simple Bot
Report Bot
Sharing & Language
OUT OF SCOPE
4. Register Bot- User can get vote registration information- User is reminded to registerSTRETCH GOAL