We need to define an MVP

[k-e-l-p]

For a while, paprika has just been meandering in development without a clearly set and defined goal. We need to figure out what is needed to be done EXACTLY in order to make a first release of the bot.

At what point can we consider that the bot is ready to be deployed to replace taigabot? Are there any core features missing? If so, we need to properly define them and get to work implementing them. Are there any glaring problems with the bot at it's current state? More testing might be required, I can make a temporary deployment to #homescreen for testing.

Once we decide that the bot is ready, I'll prepare and convert the current taigabot database (if there are any changes that are required, that is) and deploy the bot.

[ghost]

I want booru search

[hihiyes]

Once it has 100% of Taiga functionality as well as it's full database it should be good to deploy.

[ghost]

yes that includes booru search

[k-e-l-p]

See, here's the problem though: do we really need every single taigabot plugin to consider paprika ready to deploy, a lot of uguubot's plugins aren't used or are too buggy and broken to be properly usable. Also, the question here is: what needs to be done SPECIFICALLY in order to consider paprika to be on par with taigabot.

So far we got boorusearch and that's it.

[ghost]

yes we need every single plugin including booru search

[k-e-l-p]

Alright, since the closest i got to a complete awnser is "everything that taigabot has", I'm gonna outline the things that need to be done:

• Implement booru search
• Implement everything that is missing in TODO.org
• fix all current technical issues
• fix any new technical issues that arise during new plugin development
• copy over taiga's db to new db
• deploy

For now, i want to run a 'indev' version on paprika for people to use so that they could test it out and find any problems that arise

[ghost]

i'll make a lol equivalent