List view
Priority: LOW This milestone is concerned about the functionality of being able to DM a given user. Given the user key, the bot should be able to send the user a private message without being mentioned or messaged in advance. Success Criteria: +The bot should be able to message a user given the user's key, with the data provided to the messaging function.
No due datePriority: MEDIUM This milestone is concerned about finding a recent article/post about a given topic, through web-scrapping or by utilising the external API of another web service, or a mix of both. Success criteria: +The ability to locate a trending article/post or link about a given topic, by web-scrapping or using the external API of another web service - basically establishing the search engine for the desired topic. +Retrieving any available preview metadata for the link that can be used on Slack for card preview.
No due date•1/1 issues closedPriority: LOW This milestone is concerned about having the logic for understanding a schedule passed by the user, and converting it into CRON syntax. The CRON value will be used to evaluate the next time for sending an article to a given user. There also needs to be a regular NodeJS job that will fetch from the database the users who's target datetime is in the last `X` interval, and dispatch a messaging job for each user that sends them an article. Success Criteria: +Having a way of understanding the schedule passed by the user (could be natural language or through construction of a documented syntax) +Converting the passed schedule into CRON syntax, and storing that for the user in the DB +Evaluating the upcoming target datetime from the CRON syntax and storing that for the user in the DB +Creating a NodeJS job that will fetch recently due messaging jobs and dispatch them (the messaging job itself is out of the scope of this milestone)
No due datePriority: TOP This is a starting point for the application. The goal of this milestone is to have the bot able to keep track of who is subscribed to its news feed. Success Criteria: +The bot should be able to listen to a user's direct message, and propose a help command if an invalid input is added. This milestone will add the first available command: `schedule`, which will add a record for the user in the database. This milestone is not concerned about understanding a schedule or a topic to schedule a feed for - the bot simply adds the user to the database when it hears `schedule`, if the user is not in the database already. +There should be a database to keep track of scheduled users - very likely a NoSQL database. MongoDB seems like a good candidate for the project.
No due date