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

New standard: Compression Streams #231

Closed
saschanaz opened this issue Apr 9, 2024 · 17 comments
Closed

New standard: Compression Streams #231

saschanaz opened this issue Apr 9, 2024 · 17 comments

Comments

@saschanaz
Copy link
Member

Following whatwg/compression#32, I propose standardizing Compression Streams API in WHATWG. It's an API that allows compressing and decompressing BufferSource types using a set of the most common compression algorithms (gzip/deflate/deflate-raw) in browsers through Stream API.

@ricea is the editor and I'm helping him for the transition.

compression sounds like a good short name, matching the current short name in WICG.

One open question that is blocking me from writing a full workstream proposal is that whether this matches in the existing Streams workstream. The current scope looks explicitly limited to low level stream API:

sg/db.json

Line 436 in ab9abf9

"scope": "Web APIs for creating, composing, and consuming streams of data that map efficiently to low-level I/O primitives.",

But @ricea is also an editor in Streams spec, so it may still make sense to have a common workstream?

@annevk annevk added the agenda On the agenda for the next SG meeting label Apr 10, 2024
@annevk
Copy link
Member

annevk commented Apr 10, 2024

Hey @saschanaz, thanks for raising this!

This is something we need the entire @whatwg/sg to chime in on. From my perspective it can reasonably be considered in scope of the Streams Workstream and thus not require a new one. Our next meeting is April 23, but I'll see if I can get everyone to comment here before then.

@annevk
Copy link
Member

annevk commented Apr 26, 2024

Apologies for the delay, the meeting got canceled as people are/have been traveling. The next meeting is scheduled for May 7. Hopefully people find some time to comment before then though as I don't really think there's anything controversial here.

@diekus
Copy link
Contributor

diekus commented Apr 26, 2024

At Microsoft we are supportive of having this work in WHATWG, if the current editors and the other SG members are ok with this.

@cwilso
Copy link
Contributor

cwilso commented Apr 27, 2024

OK with me.

@cwilso cwilso unassigned cwilso and diekus Apr 27, 2024
@tantek
Copy link
Member

tantek commented May 7, 2024

@github.com/annevk’s proposal in #231 (comment) to add Compression Streams to the Streams Workstream is OK with me.

(Originally published at: https://tantek.com/2024/128/t1/)

@tantek tantek removed the agenda On the agenda for the next SG meeting label May 7, 2024
@tantek tantek removed their assignment May 7, 2024
@annevk
Copy link
Member

annevk commented May 7, 2024

@saschanaz @ricea the SG reached agreement as you can tell.

https://github.com/whatwg/meta/blob/main/NEW-STANDARD.md has a checklist you can follow to add a new WHATWG standard. @domenic, @foolip, and I can help out as needed (@domenic or @foolip will have to help with step 1.i and 3; I'm happy to help with the remainder).

@yoavweiss
Copy link

Yay! Let me know when the old repo needs to be archived and/or have redirects put in place.

@annevk
Copy link
Member

annevk commented May 24, 2024

I think it would be ideal to move the repository wholesale into the WHATWG, via @domenic / @foolip / I as intermediary (I believe it cannot be transferred directly). Should probably wait until @saschanaz and @ricea have had a chance to go through the checklist.

@yoavweiss
Copy link

Yeah, that would work as well, but I believe we'd need someone with owner access to both orgs. Maybe @cwilso has that?

@foolip
Copy link
Member

foolip commented May 24, 2024

Transferring directly would be ideal for redirects. (I'm not sure if GitHub would simplify a A→B→C redirect to A→C.)

@annevk
Copy link
Member

annevk commented May 24, 2024

@yoavweiss the people I listed have the necessary access on the WHATWG side. As in, you transfer it to one of domenic/foolip/annevk and they transfer it again. That should work and is how we did this before.

@saschanaz
Copy link
Member Author

Alright, for https://github.com/whatwg/meta/blob/main/NEW-STANDARD.md, the shortname would be compression as it already is in WICG.

2 would be fun 😅 any idea what should it look like? I can only imagine WinZip-like icon, and adobe stock has something like this.

image

@annevk
Copy link
Member

annevk commented May 24, 2024

https://www.svgrepo.com/svg/238546/compress is under CC0 and seems reasonable enough. Up to you though. @saschanaz are you willing to PR db.json as well?

@saschanaz
Copy link
Member Author

Before having an actual repo transferred? If that's okay then yes.

@annevk
Copy link
Member

annevk commented May 24, 2024

Yeah that's fine. We won't merge until we have everything in order, but the more that's ready the easier it'll be to do the final administrative bits.

@foolip
Copy link
Member

foolip commented May 27, 2024

I now have transferred the repo using temporary WICG powers granted by @yoavweiss. I didn't give any teams access and haven't done anything else.

@annevk
Copy link
Member

annevk commented May 27, 2024

What needs to happen still:

@annevk annevk closed this as completed in ae043e2 May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants