Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official v1 release plans #247

Closed
6 tasks
kzndotsh opened this issue Jun 2, 2024 · 8 comments
Closed
6 tasks

Official v1 release plans #247

kzndotsh opened this issue Jun 2, 2024 · 8 comments

Comments

@kzndotsh
Copy link
Contributor

kzndotsh commented Jun 2, 2024

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
Copy link
Contributor Author

kzndotsh commented Jun 2, 2024

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
Copy link
Contributor Author

kzndotsh commented Jun 2, 2024

Key features/integrations/services

  • .

@electron271
Copy link
Contributor

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

@kzndotsh
Copy link
Contributor Author

kzndotsh commented Jun 2, 2024

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
Copy link

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
Copy link
Contributor

we need hybrid commands as the first priority imo

@HikariNee
Copy link

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

@kzndotsh kzndotsh unpinned this issue Aug 21, 2024
@electron271
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants