ROADMAP post v1.0

[seanmonstar]

This updates the ROADMAP, since much of what was previously in it was accomplished in the v1 work. For now, it archives the previous roadmap too. That does make the diff look weird, but really the previous file was just renamed, and the new one is in the original file. So, while it looks like all in ROADMAP-1.0.md is new, it's just a rename. The rendered version may be more useful to look at.

---

Uplifting the summary:

Goal

Align current hyper to the [hyper VISION][VISION].

The VISION outlines a decision-making framework, use-cases, and general shape
of hyper. This roadmap describes the focus areas to continue to improve hyper
to look more like what is in the VISION.

Focus Areas

While open source is not a company, open source can be guiding. We can focus
attention to specific areas of improvement, which are based on conversations
with users, and prioritized by frequency and impact.

To that end, the following 4 areas are current focus of the project:

1. Documentation
2. hyper-util
3. HTTP/3
4. Observability

Each area benefits from having a top level description and goal, a place to
track progress, and a champion (or two) that helps push the effort.

[LucioFranco]

Not something we need to define now but would be interesting to write up what graduate means here and the criteria for that.

[programatik29]

High level server would be a nice addition to hyper-util.

[taikulawo]

We are developing a new gateway similar to NGINX, we would like add HTTP3 to it. It needs to be complete enough and go online after development finished to accept user requests.

we also investigated https://github.com/ngtcp2/nghttp3, h3 crates is too young, nghttp3 is more active than h3 from my view, but require c to rust FFI bindings. I would like to use h3 but

The h3 crate is still very experimental. While the client and servers do work, there may still be bugs. And the API could change as we continue to explore. That said, we eagerly welcome contributions, trying it out in test environments, and using at your own risk.

We will do HTTP3 support in Q4, and shipped on 2025 Q1.
I wish h3 crates will be stable soon and be ready in production :)

[gretchenfrage]

One thing I've been wondering about is if someone's written up some sort of retrospective on how the goals of the roadmap 1.0 have gone. It looks like that document essentially hasn't been unchanged since it was created.

[seanmonstar]

Yea, a retrospective would be a nice thing to put together. I'd like to do that, maybe for the end of the year... Just got to find the time 🙈