Mark Nottingham
Mark Nottingham
FWIW, I agree with David - a simple majority is appropriate here.
I agree that a separate body is not a good idea here. Still, I wonder if it's useful to have the entire body rule on everything; do we really want...
Hmm. These are already available at: https://rfc.fyi/?stream=iab I think it'd be better to add a new UX on the front page for accessing streams directly. I've created #20 for that;...
Re chairing continuity, see #310.
Makes sense. I think the goal is to align it with the vision work.
RFCs are fetched from the RFC editor, processed, and stored in `rfcs.json`; that file is fetched by your browser. Including Internet-Drafts would make that file considerably larger, so that load...
These are the two that I haven't yet found new names for - would love suggestions. I'll think more on platform. I included it because this factor does come up...
Note that HTTP provides no guarantee that chunks are preserved end-to-end; furthermore, many (most?) HTTP APIs don't guarantee that chunk delineation is exposed accurately.
Also, `pip` seems to be picking up something from the environment that specifies `x86_64` as the arch, whereas an install usually (and correctly) builds `arm64`. Still looking into this.
Yeah, `rm lib/Gemfile lib/Gemfile.lock; cp lib/docker/action/Gemfile lib/Gemfile` seems to work. Weirdly, it also seems to fix the pip problem; not sure what's going on there.