W3C home > Mailing lists > Public > public-trace-context@w3.org > May 2020

Weekly github digest (Distributed Tracing WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 12 May 2020 17:00:45 +0000
To: public-trace-context@w3.org
Message-Id: <E1jYYGr-0007Ez-DU@uranus.w3.org>



Issues
------
* w3c/trace-context (+1/-0/šŸ’¬4)
  1 issues created:
  - Document rationale for 255 leading spaces in tracestate values or remove it (by adriancole)
    https://github.com/w3c/trace-context/issues/409 

  1 issues received 4 new comments:
  - #409 Document rationale for 255 leading spaces in tracestate values or remove it (4 by adriancole, dyladan, reyang)
    https://github.com/w3c/trace-context/issues/409 

* w3c/correlation-context (+2/-1/šŸ’¬2)
  2 issues created:
  - Add rationale for why libraries MAY propagate or otherwise change to MUST (by anuraaga)
    https://github.com/w3c/correlation-context/issues/25 
  - Document rationale for 255 leading spaces in tracestate values or remove it (by adriancole)
    https://github.com/w3c/correlation-context/issues/23 

  2 issues received 2 new comments:
  - #25 Add rationale for why libraries MAY propagate or otherwise change to MUST (1 by dyladan)
    https://github.com/w3c/correlation-context/issues/25 
  - #23 Document rationale for 255 leading spaces in tracestate values or remove it (1 by adriancole)
    https://github.com/w3c/correlation-context/issues/23 

  1 issues closed:
  - Document rationale for 255 leading spaces in tracestate values or remove it https://github.com/w3c/correlation-context/issues/23 

* w3c/distributed-tracing-wg (+0/-0/šŸ’¬3)
  1 issues received 3 new comments:
  - #36 charter: plan for getting user consent (3 by plehegar, samuelweiler, yurishkuro)
    https://github.com/w3c/distributed-tracing-wg/issues/36 [privacy-needs-resolution] 



Pull requests
-------------
* w3c/trace-context (+0/-0/šŸ’¬2)
  2 pull requests received 2 new comments:
  - #391 Switch to Level 2 (1 by SergeyKanzhelev)
    https://github.com/w3c/trace-context/pull/391 [discuss-next-meeting] [editorial] [ready-for-review] 
  - #386 Clarifies the ABNF on tracestate keys (1 by adriancole)
    https://github.com/w3c/trace-context/pull/386 [discuss-next-meeting] 

* w3c/correlation-context (+1/-0/šŸ’¬0)
  1 pull requests submitted:
  - Fix typo: are allows -> are allowed (by anuraaga)
    https://github.com/w3c/correlation-context/pull/24 

* w3c/distributed-tracing-wg (+1/-2/šŸ’¬0)
  1 pull requests submitted:
  - Proposed privacy text from #36 (by plehegar)
    https://github.com/w3c/distributed-tracing-wg/pull/38 

  2 pull requests merged:
  - Proposed privacy text from #36
    https://github.com/w3c/distributed-tracing-wg/pull/38 
  - Add clearer description for Trace Context, including on the privacy sā€¦
    https://github.com/w3c/distributed-tracing-wg/pull/37 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg
Received on Tuesday, 12 May 2020 17:00:47 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 12 May 2020 17:00:48 UTC