Subject: [Taps] Weekly github digest (TAPS Activity Summary)

From: Repository Activity Summary Bot <[email-masked]>
Date: Sun, 24 Oct 2021 04:50:47 -0700 (PDT)

Issues
------
* ietf-tapswg/api-drafts (+4/-15/💬12)
  4 issues created:
  - We fixed ARCH lets fix Imple (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/958 
  - Impl: Pooled Connection (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/956 [Implementation] 
  - We fixed Arch - let's fix API (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/955 [API] 
  - TAPS API sits above the Transport System (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/953 [API] 

  9 issues received 12 new comments:
  - #945 Arch-Review MW: Connections introducing head-of-line blocking (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/945 [Architecture] 
  - #919 ART-ART: Send events too limiting? (2 by gorryfair, mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/919 [API] 
  - #918 ART-ART: scope vs. framer (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/918 [API] 
  - #915 ART-ART: be clearer with RFC 7556 reference (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/915 [API] 
  - #914 ART-ART: MUST NOT in section 8 paragraph 3 (2 by gorryfair, mwelzl)
    https://github.com/ietf-tapswg/api-drafts/issues/914 [API] 
  - #909 ART-ART: WithServiceName (1 by britram)
    https://github.com/ietf-tapswg/api-drafts/issues/909 [API] 
  - #901 ART-ART: Explicit context in the Send in example in 3.1.1 (2 by mwelzl, tfpauly)
    https://github.com/ietf-tapswg/api-drafts/issues/901 [API] [editorial] 
  - #879 ART-ART: Separation of architecture and interface documents (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/879 [Architecture] 
  - #184 Replace long author lists with editors (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/issues/184 [wontfix] [API] [admin stuff] 

  15 issues closed:
  - Arch-Review MW: https://github.com/ietf-tapswg/api-drafts/issues/944 [Architecture] [editorial] 
  - We fixed ARCH lets fix Imple https://github.com/ietf-tapswg/api-drafts/issues/958 [Implementation] 
  - We fixed Arch - let's fix API https://github.com/ietf-tapswg/api-drafts/issues/955 [API] 
  - ART-ART: be clearer with RFC 7556 reference https://github.com/ietf-tapswg/api-drafts/issues/915 [API] 
  - TAPS API sits above the Transport System https://github.com/ietf-tapswg/api-drafts/issues/953 [API] 
  - ART-ART: MUST NOT in section 8 paragraph 3 https://github.com/ietf-tapswg/api-drafts/issues/914 [API] 
  - ART-ART: Avoid "atop" and "underneath" https://github.com/ietf-tapswg/api-drafts/issues/895 [API] [editorial] 
  - ART-ART: Make sure that language can age well https://github.com/ietf-tapswg/api-drafts/issues/894 [API] [editorial] 
  - Add implementation text for multicast https://github.com/ietf-tapswg/api-drafts/issues/876 [Implementation] 
  - ART-ART: high vs. low priority values vs. semantics https://github.com/ietf-tapswg/api-drafts/issues/917 [API] [editorial] 
  - ART-ART: Introduce Caching https://github.com/ietf-tapswg/api-drafts/issues/883 [Architecture] [editorial] 
  - ART-ART: Tidy "cleaning up" in Arch https://github.com/ietf-tapswg/api-drafts/issues/892 [Architecture] [editorial] 
  - Are scoped IPv6 address (and zone indexes in particular) supported? https://github.com/ietf-tapswg/api-drafts/issues/864 [API] 
  - ART-ART: Explicit context in the Send in example in 3.1.1 https://github.com/ietf-tapswg/api-drafts/issues/901 [API] [editorial] 
  - what does connected mean? https://github.com/ietf-tapswg/api-drafts/issues/737 [Implementation] 

Pull requests
-------------
* ietf-tapswg/api-drafts (+10/-18/💬6)
  10 pull requests submitted:
  - And then there were five authors.... (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/960 
  - And then there were five authors.... (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/959 [Architecture] 
  - Trying to align more with ARCH draft-ietf-taps-impl.md (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/957 
  - Terms for Transport Services (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/954 
  - Minset: Fixing wrong statement about missing soft error, name cleanup (by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/952 
  - ARCH components. (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/951 
  - API: PVD  and other queriable info (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/950 [API] 
  - Remove a MUST NOT (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/949 
  - PR to address Arch-Review MW (by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/948 
  - Be careful with the results of Preconnection.Resolve() (by britram)
    https://github.com/ietf-tapswg/api-drafts/pull/947 

  6 pull requests received 6 new comments:
  - #952 Minset: Fixing wrong statement about missing soft error, name cleanup (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/952 [API] 
  - #951 ARCH components. (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/951 
  - #950 API: PVD  and other queriable info (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/950 [API] 
  - #949 Remove a MUST NOT (1 by gorryfair)
    https://github.com/ietf-tapswg/api-drafts/pull/949 [API] [editorial] 
  - #935 s/MUST/SHOULD because else we don't even eat our own dog food  :) (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/935 [Architecture] 
  - #934 Explicit context in example (1 by mwelzl)
    https://github.com/ietf-tapswg/api-drafts/pull/934 [API] [editorial] 

  18 pull requests merged:
  - Minset: Fixing wrong statement about missing soft error, name cleanup
    https://github.com/ietf-tapswg/api-drafts/pull/952 [API] 
  - PR to address Arch-Review MW
    https://github.com/ietf-tapswg/api-drafts/pull/948 
  - Trying to align more with ARCH draft-ietf-taps-impl.md
    https://github.com/ietf-tapswg/api-drafts/pull/957 [Architecture] 
  - Terms for Transport Services
    https://github.com/ietf-tapswg/api-drafts/pull/954 [API] [Implementation] 
  - And then there were five authors....
    https://github.com/ietf-tapswg/api-drafts/pull/960 [Implementation] 
  - And then there were five authors....
    https://github.com/ietf-tapswg/api-drafts/pull/959 [Architecture] 
  - API: PVD  and other queriable info
    https://github.com/ietf-tapswg/api-drafts/pull/950 [API] 
  - ARCH components.
    https://github.com/ietf-tapswg/api-drafts/pull/951 [API] 
  - Remove a MUST NOT
    https://github.com/ietf-tapswg/api-drafts/pull/949 [API] [editorial] 
  - s/MUST/SHOULD because else we don't even eat our own dog food  :)
    https://github.com/ietf-tapswg/api-drafts/pull/935 [Architecture] 
  - Ensure language can age well, avoid atop and underneath
    https://github.com/ietf-tapswg/api-drafts/pull/929 [API] [editorial] 
  - Multicast reuse draft-ietf-taps-impl.md
    https://github.com/ietf-tapswg/api-drafts/pull/877 [Implementation] 
  - Priority values: higher = higher.
    https://github.com/ietf-tapswg/api-drafts/pull/928 [API] 
  - Small fixes to Gorry's latest arch update.
    https://github.com/ietf-tapswg/api-drafts/pull/940 [Architecture] 
  - Caching and racing in implementation intro
    https://github.com/ietf-tapswg/api-drafts/pull/942 [Architecture] 
  - clean up cleaning up
    https://github.com/ietf-tapswg/api-drafts/pull/943 
  - Scoped IPv6 addresses
    https://github.com/ietf-tapswg/api-drafts/pull/946 
  - #737 "connected" doesn't mean send a packet to draft-ietf-taps-impl.md
    https://github.com/ietf-tapswg/api-drafts/pull/878 [Implementation] 

Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-tapswg/api-drafts