Roadmap

[VincentRPS]

This is a non-timed roadmap of our progress. While multiple items could be worked on at once, it would be best to work on one at a time to make both development and management easier. For example, we'd implement guilds without their member attributes or functions first and then implement those during the member implementation.

The roadmap here is meant to be done one by one, meaning the lower it goes the farther in time it will be set.

Map

• Gateway Implementation^[1?]
• Polish HTTP Implementation
• Extremely Basic Model Implementation
  Implementing all of Discord's models and types only with attributes directly given by Discord.
  Along with no implementation of functions. This is done to make future state integration easier.
• Client/Bot Implementation
• Implementation of the Commands System
• Application Command Implementation
• Component Implementation
• Gear (Cog) Implementation
• CDN Implementation
• File Implementation
• User and ClientUser Implementation
• Permissions Implementation
• Guild Implementation
• Member Implementation
• Role Implementation
• Guild & DM Channel Implementation
• Message Implementation
• Webhook Implementation
• Partial Voice Channel Implementation
• Emoji Implementation
• Stage Instance Implementation
• Thread Implementation
• Sticker Implementation
• Guild Template Implementation
• Guild Scheduled Event Implementation
• Audit Log Implementation
• Polish implementations and look for incomplete features
• Application Implementation
• Team Implementation
• (Special) Possibly allow some big bot developers to test v3's code
• OAuth2 Implementation
• Starting talking about v3 publicly
• Interactions Implementation
• (Special) Starting allowing helpers to develop using v3 so when publicized they can help users
• Multiprocess Sharding
  This is quite a hard idea to wrap your head on, but in basic terms:
  sharding across processes using multiprocessing or sharding the shard manager.
• Stabilize Unstable sections of code
• Publicize Code
• Full Voice Implementation^[1]
• (Kind of out of scope but) Hold a public vote on whether to rename pycord-development to just pycord.
• Release

Rust Components

Pycord v3's purpose has always been and always will be to be the fastest Python library for Discord. We made it because the competition was either overwhelmingly using old code bases or slow.

One of the things we're going to be doing to speed up our internals and give users the fastest experience possible is writing some of our intensive code in Rust. Such as our Voice Implementation and possibly our Gateway Implementation.
Rust gives us the power to write blazingly fast memory-efficient code while still delivering to users on Python, and it will help us deliver our speed goal.

[VincentRPS]

For now, I'm gonna pause for a bit on implementations. What I want to make sure is that the current codebase works smoothly and is stable, along with getting stuff like tests finished.
The biggest part of development for our past versions and this version specifically will be the documentation. We're the only folks who understand our own code, so writing documentation explaining it and especially giving a detailed assessment of changes is quintessentially justified and needed.