Import code from DataDog/libdatadog/ruby@19ae2be64

[lloeki]

Tree: 19ae2be6459745b8c4091a18b6e822f118eb0cb3

JIRA

• APMLP-1091

[ivoanjo]

Before we move things here, can we give the same permissions, access-wise, to the repo as we have for dd-trace-rb and libdatadog? I'd like to keep the same environment of quick iteration and easy contribution as we've had so far in those

[ivoanjo]

Also, ideally since both dd-trace-rb and libdatadog are public, is there any reason not to make this one public as well?

[lloeki]

can we give the same permissions, access-wise, to the repo as we have for dd-trace-rb and libdatadog?

I could swear I did so

EDIT: GH permissions were off for DataDog/ruby-guild, fixed; I punted on the shared components team ownership for now as it's a bit more unwieldy (lots of teams) but looking at the libdatadog CODEOWNERS set up it seems it's ruby-guild that's relevant so far.

[lloeki]

Also, ideally since both dd-trace-rb and libdatadog are public, is there any reason not to make this one public as well?

Process 😭

(I asked on grounds that both were public but was denied and told to go through the whole vetting process)

[ivoanjo]

It would suck to move from public to private just for that one reason. Can I maybe suggest keeping this inside libdatadog until we can make this repo public too?

[ivoanjo]

Me && @lloeki discussed over zoom that this is only the starting step for migrating away from having this on the libdatadog repo, and that the cut-off for moving things to this repo will only happen once we have everything set up, including marking the repo as public.