-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Update development policy to relax rules on committer agreements #994
Milestone
Comments
I suppose this warrants a post to rust-dev as well, to make sure everyone with commit access knows about it. |
Just a note that I pulled a commit from Haitao Li despite the development policy not being updated yet. |
Now we've pulled from a number of contributors without asking for an agreement. |
I have gone ahead and removed the requirement for committer agreements from the development policy. |
ZuseZ4
pushed a commit
to EnzymeAD/rust
that referenced
this issue
Mar 7, 2023
coastalwhite
pushed a commit
to coastalwhite/rust
that referenced
this issue
Aug 5, 2023
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
* Documentation: Updates for "Regression testing" * Add `ui` to the Kani testing suites
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There has been discussion lately about whether our development policy is too strict regarding committer agreements. Specifically, we require them for all patches, which is not the norm for Mozilla.
There seems to be agreement that the committer agreement only applies to those with commit access to the main repository and that they take on the liability for anything they push. We should update the development policy on the wiki to reflect this.
The text was updated successfully, but these errors were encountered: