related to this topic, there's an ongoing discussion about upgrading the spec (HAR 1.3 ?) and what information is lacking from its current iteration, the conversation started on the HAR Mailing List:
following up on this discussion, I've created a github repo and transfer the 1.2 spec over and created a 1.3 proposal: https://github.com/ahmadnassri/har-spec
particularly of interest are Andrew's suggestions on postData and timings improvements: https://github.com/ahmadnassri/har-spec/pulls
a github repo with markdown format makes it a lot easier for edits / suggestions and community contribution.
(I feel that github is a great medium for allowing people to add suggestions and discussions, beyond a mailing list) happy to donate that repo to the an official group / committee that can oversee collaborative work on the spec, but of course the browser vendors are key to this collaboration.
I've recently joined the Open API Initiative in forming the future of Open API Spec (formerly known as Swagger) and we're seeing some success in having an official group of committed owners from businesses directly interacting with the spec and leading its evolution.
perhaps we need something official around HAR as well to help steer the future of the spec and tooling around it.
what do you think is the appropriate channel to discuss? here, mailing list? github? elsewhere?