Official v1 release plans

[kzndotsh]

Let us discuss what is required for our first "official" v1 release.

It's important we get to an official starting release so that we can start a proper workflow/release cycle moving forward and not fall into a never ending roadmap of feature creep.

• [ ] What will our official change log/roadmap consist of?
• [ ] What will be required infrastructure/CI CD/systems wise?
• [ ] What will be required branding wise?
• [ ] What will be required code standard wise?
• [ ] What will be required database wise?
• [ ] What will be our main offering list/commands/etc so to speak?

Etcetera, etcetera. All ideas and considerations are welcome.

[kzndotsh]

Proposed command groups/commands list

Admin

• [ ] Sync
• [ ] Clear
• [ ] Load
• [ ] Unload
• [ ] Reload

Moderation

• [ ] Ban
• [ ] Unban
• [ ] Kick
• [ ] Timeout
• [ ] Warn
• [ ] Note
• [ ] Purge
• [ ] Jail
• [ ] Slowmode
• [ ] Report

Utility

• .

Fun

• .

[kzndotsh]

Key features/integrations/services

• .

[electron271]

i dont think we really need anything or much branding wise that i can think of

[kzndotsh]

i dont think we really need anything or much branding wise that i can think of

Maybe a proper final run through reading README and other docs if that counts as branding lol.

Also any "language" / phrases / etc used.

[HikariNee]

IMO, getting a nice looking help command should be the first priority.

And two, a generic error handler for any command (which we still don't have iirc)

[electron271]

we need hybrid commands as the first priority imo

[HikariNee]

To be honest, prefix commands are good enough It only becomes a problem when you get added in too many servers.

[electron271]

decided in #525 if this is incorrect feel free to reopen