Spec group / committee

[ahmadnassri]

between my humble suggestions for v1.3 and @andydude's pull requests (#2, #3) there is certainly enough to discuss in addition to the spec.

this is however challenging for the following reasons:

1. this repo does not represent the official spec
2. collaboration with the extended community (especially the browser vendors) is critical
3. ideas & contributions in silos are ineffective

Which is why I'd much rather see a core group of committed users / creators that leverage the spec be involved in leading those changes, including the original authors.

some notes:

1. Github is a great format for facilitating issues, pull requests and contributions
2. Github is not a good enough discussion / community center
3. Making this repo official, will require more collaboration and an organization (of people) to come together around it.

next steps / suggestions:

• ensure original author (@janodvarko) has buy-in and help facilitate forming of this group.
• identify key individuals of interest to improve on the spec.
• message the extended community, and solicit feedback to identify where the spec is in most need of improvement
• identify key tooling providers (most listed here) and work together on establishing a pipeline for future updates

suggestions welcome :)

[ericduran]

@ahmadnassri Curious where this was left off?

I'm extremely interested in pursuing this. Since the current HAR spec is really being left behind. Curious what happened with buy-in from @janodvarko? and http-archive-specification google group?

[ahmadnassri]

@ericduran I did not get any interest or buy-in ... well not even a response ... happy to take further suggestions or actions to further this along!

[andydude]

I am also interested, but I don't want to be the only one!

[rbtcollins]

TBH the current stalled situation is worse than you publishing a spec based on the discord and google groups discussions.