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

Guidance for external contributors on how to get large contributions into OpenSSL #174

Open
mattcaswell opened this issue Aug 22, 2023 · 3 comments

Comments

@mattcaswell
Copy link
Member

From the OTC meeting minutes (otc/meeting-minutes/2023/minutes-2023-08-22.txt)

AI: Matt to write a first draft of a guide for feature contributors

@nicowilliams
Copy link

Sometimes a contributor might start a contribution, run out of steam, and come back a year later when the upstream has merged a few thousand commits and some number of those cause conflicts for the contributor. There are tools meant to help with this, as git rebase and git merge can both be a nightmare in such cases. I linked four useful tools for this in a comment on #73.

I recommend picking and recommending one of these, though also listing the others (they all do roughly the same sort of find-and-rebase-onto-the-oldest-conflict-causing-upstream-commit-then-repeat-from-there thing).

@mattcaswell
Copy link
Member Author

Thanks @nicowilliams - I'll take a look.

@arapov
Copy link
Member

arapov commented Jan 8, 2024

from: #347

Write up some of the work practices I pioneered when developing QUIC MVP for 3.2
Compare with the project's historical work practices
Ideally talk to some of the others before I do this to understand historical work practices and the context of how I approached QUIC MVP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

3 participants