-
Notifications
You must be signed in to change notification settings - Fork 74
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
Conversation
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 |
The CI failure can be fixed by putting a smoldot/.github/workflows/ci.yml Line 79 in 76994b5
I don't know why it suddenly broke, but I had to do the same fix in the new repo. |
Okay. I think I would move forward and if you have some better text/ideas just open a pr and we extend it! :) |
Also the CI fails because the spellcheck doesn't know the word "repo" |
There was a problem hiding this 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
twiggy diff reportDifference in .wasm size before and after this pull request.
|
Why did the repo move to a new org? |
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. |
Thanks for the explanation @tomaka and good luck! |
Closes: #3097
Is that okay @tomaka?