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

js-ipfs deprecation - replaced by Helia #585

Merged
merged 1 commit into from
May 26, 2023

Conversation

BigLep
Copy link
Contributor

@BigLep BigLep commented May 26, 2023

This is a blog post accompanying the js-ipfs deprecation work that is active at ipfs/js-ipfs#4336

Why now?

We were originally going to do a discuss.ipfs.tech post (proposed text). Doing this as a blog entry will cause the discuss.ipfs.tech post to be generated while getting broader reach for the message.

Switching from a discuss.ipfs.tech post to a blog entry came to mind when thinking about the next IPFS Newsletter. I know we can manually submit newsletter additions, but this should get it scooped up by default.

(With deprecations, the more expansive the communication the better to avoid surprises.)

Shouldn't we add more text about Helia?

Ideally yes, but I'm just taking the discuss.ipfs.tech text we had drafted. We will followup with an "announcing Helia" post where we can give more info about Helia.

Do we need to act quickly?

If folks aren't comfortable with this blog entry and more work is required, we can park it and should just fall back to a discuss.ipfs.tech post.

Open items

This is a blog post accompanying the js-ipfs deprecation work
that is active at ipfs/js-ipfs#4336
@BigLep
Copy link
Contributor Author

BigLep commented May 26, 2023

I added some more justification for this PR in its current form above. Feel free to critique. I am trying to let best not be the enemy of better. This seems better to me than simply doing a discuss.ipfs.tech post even if it isn't ideal. I am using the messaging we have drafted so we can move quickly on getting the broader message out about js-ipfs deprecation. If people don't like the blog post, we can just fallback to a discuss.ipfs.tech post.

@BigLep
Copy link
Contributor Author

BigLep commented May 26, 2023

@damedoteth : any concern with this going out 2023-05-26? It looks like you're out of the office. I'm wanting to move quickly here so we can more broadly get the js-ipfs deprecation notice out.

@BigLep BigLep self-assigned this May 26, 2023
@BigLep
Copy link
Contributor Author

BigLep commented May 26, 2023

@achingbrain : if we don't hear any objections from @damedoteth when you wake up and you don't see any issues in the preview, lets go ahead and merge. If you just want to go discuss.ipfs.tech post, that is fine too.

@achingbrain achingbrain merged commit 20b2d48 into main May 26, 2023
@achingbrain achingbrain deleted the post/202306-js-ipfs-deprecation-for-helia branch May 26, 2023 11:35
@BigLep
Copy link
Contributor Author

BigLep commented May 26, 2023

So a discuss post was made before this was merged: https://discuss.ipfs.tech/t/js-ipfs-deprecation-replaced-by-helia/16478

Once this is published, we'll have two discuss posts. I guess we'll live with that and link them.

BigLep added a commit that referenced this pull request May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants