Skip to content

wasi-preview2 article - #83

Merged
disquisitioner merged 2 commits into
gh-pagesfrom
2024-01-25-WASI-Preview2
Feb 7, 2024
Merged

wasi-preview2 article#83
disquisitioner merged 2 commits into
gh-pagesfrom
2024-01-25-WASI-Preview2

Conversation

@ricochet

Copy link
Copy Markdown
Collaborator

Cross-posting from Dan's personal blog with his permission.

https://blog.sunfishcode.online/wasi-preview2/

Cross-posting with Dan's permission from personal blog
detailing the WASI P2 milestone.
@disquisitioner

Copy link
Copy Markdown
Collaborator

Great to have an article that highlights approval of WASI Preview 2, and I like the idea of cross-posting from Dan's blog. (Thanks, @sunfishcode!). Two questions:

  1. Is there anything we can link to that represents the official approval vote outcome from the WASI Subgroup?
  2. Is there an announcement (or something comparable to Dan's blog) about having completed the Component Model work? (That seems worth celebrating/announcing too, and though I wouldn't hold up this post for a post there I do think it'd be good to highlight that too if possible and link to it).

@disquisitioner

disquisitioner commented Jan 30, 2024

Copy link
Copy Markdown
Collaborator

Also, per our conversation this morning @ricochet, if you want to control how the article excerpt gets generated and included in the overall News page you can add the following to the post's markup file:

excerpt_separator: <!--end_excerpt-->
---
This is the excerpt paragraph, generally the very first one in the post, which serves both as the
introductory paragraph in the post and will be pulled out and used to preview/tease the article
in the overall News page at https://bytecodealliance.org/articles/ along with title, posted date,
and the author's avatar.
<!--end_excerpt-->

@pchickey

Copy link
Copy Markdown
Collaborator

WebAssembly/WASI#577 can be used as a place where the "official" approval was recorded

@disquisitioner disquisitioner left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest a tweak to the intro part of this so it looks like the following:

 ---
title: WASI Preview 2 Launched
author: "Dan Gohman"
github_name: sunfishcode
excerpt_separator: <!--end_excerpt-->
---
The WASI Subgroup voted on January 25, 2024 to launch WASI Preview 2!
This blog post is a brief look at the present, past, and future of WASI,
and a repost of an original article shared
[here]( https://blog.sunfishcode.online/wasi-preview2/).
<!--end_excerpt-->

## The present

This yields a reasonable intro that can also serve as the teaser "excerpt" to show on the overall News page of Bytecode Alliance website and also links to Dan's original blog post.

Everything else looks fine!

@sunfishcode

Copy link
Copy Markdown
Member

Sounds good to me!

@sunfishcode sunfishcode left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've heard feedback that calling it "WASI 0.2" instead of "WASI Preview 2" is easier to understand. If y'all agree, I've made these edits as review suggestions here. Either way, this looks good to me!

Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
@@ -0,0 +1,206 @@
---
title: WASI Preview 2 Launched

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: WASI Preview 2 Launched
title: WASI 0.2 Launched

@disquisitioner disquisitioner Feb 6, 2024

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK with "WASI 0.2", especially as we consistently used that terminology during last week's Plumber's Summit. I do want to make sure we let people know early on in the post that what we are calling "WASI 0.2" here used to be widely referred to "WASI Preview 2" and is still going to be encountered using that previous nomenclature. (E.g. the repo is WASI/preview2.)

So I'm fine with WASI 0.2 in the title but think we should make that point as early in the document as possible to minimize confusion.

Also, Eric Gregory has just staged a PR with his write-ups from both days of last week's Plumber's Summit and he uses the "Preview 2" and "Preview 3" nomenclature there. Should we ask him to change that??

Lastly, you aren't modifying your blog post to be "0.2" instead of "Preview 2" are you @sunfishcode ??

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I'm fine with WASI 0.2 in the title but think we should make that point as early in the document as possible.

Yes, on line 13 here I have added a mention that "WASI 0.2" is also known as "WASI Preview 2".

Also, Eric Gregory has just staged a PR with his write-ups from both days of last week's Plumber's Summit and he uses the "Preview 2" and "Preview 3" nomenclature there. Should we ask him to change that??

Yeah. It's not absolutely necessary, but it would be good if he could change that.

Lastly, you aren't modifying your blog post to be "0.2" instead of "Preview 2" are you @sunfishcode ??

I have now modified the post to be "0.2".

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I relayed word to @ericgregory so he can look at changing things in his posts.

Also, will the URL to your post still be https://blog.sunfishcode.online/wasi-preview2/?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll keep that URL live, but I'll add a new URL based on WASI 0.2 as soon as I can figure out how to do that in my blog software here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
Comment thread _posts/2024-01-25-WASI-Preview2.md Outdated
@sunfishcode

Copy link
Copy Markdown
Member

I could also submit a PR to this branch if you'd like, if that'd be easier than all these suggested changes.

@disquisitioner

Copy link
Copy Markdown
Collaborator

An updated PR in this branch with all these changes would be great, @sunfishcode -- thanks! That way I can wear the reviewer hat plus also still test the branch stand-alone on my development machine to check URLs, etc.

@ricochet

ricochet commented Feb 6, 2024

Copy link
Copy Markdown
Collaborator Author

Hey I welcome someone taking this over. I should have time to pull in edits this weekend but I'm spread a little too thin for the next few days.

@sunfishcode

Copy link
Copy Markdown
Member

@disquisitioner I've now posted #85 with a branch with the WASI 0.2 changes.

* Say "WASI 0.2" instead of "WASI Preview 2".

* Tidy up the beginning.
@disquisitioner

Copy link
Copy Markdown
Collaborator

Merging into gh-pages now that we've incorporated additional updates from @sunfishcode's branch.

@disquisitioner
disquisitioner merged commit 82eed94 into gh-pages Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants