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

Inform users about the new repo #3098

Merged
merged 3 commits into from
Feb 23, 2023
Merged

Inform users about the new repo #3098

merged 3 commits into from
Feb 23, 2023

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Feb 23, 2023

Closes: #3097

Is that okay @tomaka?

@tomaka
Copy link
Contributor

tomaka commented Feb 23, 2023

Yeah, I had in mind to do a PR like that, just I was thinking of writing a bit more text, but also I don't know exactly what to write

@tomaka
Copy link
Contributor

tomaka commented Feb 23, 2023

The CI failure can be fixed by putting a 0.7 here:

version: 0.6

I don't know why it suddenly broke, but I had to do the same fix in the new repo.

@bkchr
Copy link
Member Author

bkchr commented Feb 23, 2023

Yeah, I had in mind to do a PR like that, just I was thinking of writing a bit more text, but also I don't know exactly what to write

Okay. I think I would move forward and if you have some better text/ideas just open a pr and we extend it! :)

@tomaka
Copy link
Contributor

tomaka commented Feb 23, 2023

Also the CI fails because the spellcheck doesn't know the word "repo"

Copy link
Contributor

@tomaka tomaka left a comment

Choose a reason for hiding this comment

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

My review doesn't count, but I guess I'll put it for the principle

@github-actions
Copy link
Contributor

github-actions bot commented Feb 23, 2023

twiggy diff report

Difference in .wasm size before and after this pull request.


 Delta Bytes │ Item
─────────────┼──────────────────
          +0 ┊ Σ [0 Total Rows]

@bkchr bkchr merged commit 938055a into main Feb 23, 2023
@bkchr bkchr deleted the bkchr-deprecation branch February 23, 2023 10:19
@forgetso
Copy link

Why did the repo move to a new org?

@tomaka
Copy link
Contributor

tomaka commented Feb 23, 2023

I'm no longer working at Parity and I'm continuing the development of smoldot through treasury proposals. Since the project doesn't "belong to Parity" "anymore" (the code written in 2022 and before obviously still belongs to Parity, but everything is under GPL 3 regardless), it makes sense for it to be in a different organization.

The reason why we didn't simply transfer the repo is complicated and uninteresting.

@forgetso
Copy link

Thanks for the explanation @tomaka and good luck!

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.

Repo migration?
3 participants