Initial import, plus http status code updates

[ahobson]

Create a new otelhttp repo.

We aren't importing the entirety of go-opentelemetry-contrib because we want to enforce go linting rules and don't want to have to update the entire repository.

This PR includes changes from open-telemetry/opentelemetry-go-contrib#771

[felipe-lee]

I noticed that in the original repo they have a go.mod and go.sum in the test directory that aren't in ours. Should those be included too? If not, maybe a comment in the README indicating that they shouldn't and a reason would be good for future us when we try updating this with any changes they've made.

[felipe-lee]

This is pretty cool, I didn't realize this was a thing. Should we have something in the README to showcase using it, or a script (or Makefile, though I know there's plenty of issues with those) that will run it for us?

[ahobson]

I added something to the README

[felipe-lee]

Can you add setup instructions? Especially for non-nix users since they'll have to make sure go and pre-commit are set up correctly. Well even nix users will need to install pre-commit hooks.

[ahobson]

I added a blurb to the README

[felipe-lee]

Oh also, I don't really know much about licenses. I know we pulled this into it's own repo because of the license difference and that several of the files have the license blurb at the top of the file, but do we also need to include a repo-level license?

[ahobson]

Oh also, I don't really know much about licenses. I know we pulled this into it's own repo because of the license difference and that several of the files have the license blurb at the top of the file, but do we also need to include a repo-level license?

Thank you. I copied the LICENSE from the original repo

[ahobson]

I noticed that in the original repo they have a go.mod and go.sum in the test directory that aren't in ours. Should those be included too? If not, maybe a comment in the README indicating that they shouldn't and a reason would be good for future us when we try updating this with any changes they've made.

README updated!

[felipe-lee]

Awesome, thanks for making those updates. LGTM!

[gidjin]

LGTM. One question this repo doesn't look like a fork of the original, is there a reason we couldn't have done that?

[felipe-lee]

LGTM. One question this repo doesn't look like a fork of the original, is there a reason we couldn't have done that?

@gidjin I think that's what @ahobson was mentioning with this:

We aren't importing the entirety of go-opentelemetry-contrib because we want to enforce go linting rules and don't want to have to update the entire repository.

So I think the goal is by only keeping up with a single package it can make it easier to maintain. Though I guess one question is, how we plan on keeping up to date. Though hopefully we won't need to for too long

[ahobson]

LGTM. One question this repo doesn't look like a fork of the original, is there a reason we couldn't have done that?

@gidjin I think that's what @ahobson was mentioning with this:

We aren't importing the entirety of go-opentelemetry-contrib because we want to enforce go linting rules and don't want to have to update the entire repository.

So I think the goal is by only keeping up with a single package it can make it easier to maintain. Though I guess one question is, how we plan on keeping up to date. Though hopefully we won't need to for too long

I mean, the reason for the fork is that the folks are not updating the original with PRs we need. It seems to me like we'll have one of two outcomes:

1. They start accepting PRs and so we can stop using this fork
2. The original is basically abandonware and so we never have to worry about keeping up to date