Skip to content

Latest commit

 

History

History
43 lines (25 loc) · 1.37 KB

CONTRIBUTING.md

File metadata and controls

43 lines (25 loc) · 1.37 KB

How to contribute to HTTP/1.2

Basically:

  1. Clone repository
  2. Create branch (local or remote)
  3. Create pull request (PR)
  4. Reviewers will merge or decline

Clean Code

I am a big fan of the clean code paradigm. So you should:

  1. Blame non-clean-code
  2. Code with the clean code paradigm in mind

Signing Key / pkcs11

It is adviced to add a public signing key to GitHub and use Smartcards with openssh / ssh-agent.

Details about configuration see: GitHub Documentation.

Questions / Feature Requests / Improvements

Send questions regarding HTTP/1.2 to [email protected]

Bugs / Issues

  • Ensure the bug was not already reported by searching on GitHub under Issues.
  • If not already reported, open a new issue addressing the problem New Issue. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior.

Issue templates follow.

Cosmetical Fixing

Cosmetical changes (whitespace, indentation, etc.) are welcome.

Happy Hacking

Feel free to contribute.

HTTP/1.2 Lead Developer "Claus Prüfer"