Paulo F. Oliveira

@jj1bdx, `libncurses[^w]*dev` was adopted as the solution in the linked pr.

For reference (this is rebar3.org): http://rebar3.org/docs/package_management/hex_package_management/#config (I assume that's what you're talking about). Here's a comparison between the two: rebar3.org | Hex.pm -- | -- username | key | api_url...

> I believe for this to work effectively a k/v will have to be placed into the parent repo and applied to all it's children. . I don't understand this....

[Erlang.SE](http://www.erlang.se/doc/programming_rules.shtml) is dead. A (currently functioning) alternative: https://docs.jj1bdx.tokyo/Erlang_Programming_Rules.html

Should we consider Open Telemetry for this? I wouldn't mind working on it, but: 1. I need to know what timings we're interested in (all of them?) 2. if I...

@lpil, a bit late to the party, but... is that repo. enough for what you envisioned? (I know you're busy with other stuff) I was just wondering if there's the...

Not at this moment, I don't think. It shouldn't be complex to implement, as a hook on `cowboy_swagger:to_json/1`, but I'm not sure we'll want that. @elbrujohalcon?

👍 then I propose a behaviour with a single function `cowboy_swagger_json_exporter:export/1` where the input is the generated `swagger.json`. Then with an application config. key like e.g. `json_exporter_mod`, you can add...

For semantics purposes, a `forbidden` keyword might make sense... but then you'd always have to have an order in evaluation: if you accept and negate a given string, which one...

> with the default for `forbidden` being `none`. It could even be `undefined` :-)