On Tue, Jan 5, 2021 at 12:21 PM Larry Masinter <LMM@xxxxxxx> wrote:
It may be a fine way for a group to develop a publicly available specification that group membersimplement in an interoperable way, but why should the IETF have anything to do with it, if the
group process doesn’t admit the typical IETF cross-area industry-wide review by those who are
not so intimately familiar with the detailed vocabulary of the group’s specification to be in a positionto be able & willing to couch their questions in terms of a “Pull Request”?
There are still two separate last calls for all WG documents: WGLC and IETF LC. Even if you never followed the issues or performed periodic reviews of document revisions prior to those checkpoints, you can always do it then. Again, no one in any WG is required to interact with GitHub to contribute. That contribution is easier for those who *do* use GitHub is not a justification for prohibiting use of those tools. Equality of contribution across the board has never been an explicit goal, and indeed contributions to a document have always been dominated by one or a few authors who put in a lot more work than everyone else.
Without referencing GitHub, what objective standard for access are you advocating for, and how does the use of GitHub uniquely impact that negatively?
Kyle
