Replies: 1 comment
-
Thanks, @huwdp we have an open issue: #461. I have downgraded the likelihood of issues around copyright assignment from a 5 down to a 3 since the announcement. Though personally, I just want to let the dust settle for a while before changing anything with our contributing guidelines, so I would expect that this risk will be changed/removed from my reports soon. Also thanks for reading my status reports, I put a lot of work into them to be open and transparent as I can be about the development process. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, long time follower here.
Don't know if you know this but I just wanted to let you know that GCC has dropped assigned copyright-assignment so integrating Rust-GCC into GCC should be easier. Link here to article (https://lwn.net/Articles/857791/).
Says here (Rust-GCC/Reporting@8c2c1a0) that "Be up front on all PRs that the code is destined to be upstreamed to FSF" under Copyright assignments section.
This is one big hurdle out of the way :)
Beta Was this translation helpful? Give feedback.
All reactions