After the merge of this PR: open-telemetry/opentelemetry-dotnet#1548

We should create more unit tests just like open-telemetry/opentelemetry-dotnet#1537 to validate the full behavior.

Consolidating thread on all open plugin requests.

All issues need help if you'd like to contribute to the project 😃

The documentation on writing a plugin can be found here.

• Umami DavidWells/analytics#149
• Firebase DavidWells/analytics#133
• Plausible https://gith

The current getting started guide assumes the user will be starting using the SDK building block packages like tracing, node, and metrics. In the future, it is expected most users will use the SDK package as a starting point and it would be better for the getting started guide to reflect that.

For some uses cases it would be useful to have an option in the gr_satellites command line tool that skips the demodulator and sends the input the directly to the deframer.

as mentioned in the UPDATING file, there are some domains in the list that represent the same domain but differ by a commonly confused character (like dashes, em dashes, and en dashes). Theres also a few that look like two characters smushed together (I think there's one like that for fi in a couple places). These are likely due to copy-paste errors or from parsing the PDF, however I want to be

See open-telemetry/opentelemetry-specification#1636 and open-telemetry/opentelemetry-specification#1612

As discussed here:

• HttpClient::CreateSession method should support passing full URL as an argument instead of host and port (or perhaps support bot