Comments (28)
I want to schedule the next telco for next Tuesday 11:30 p.m. CET
from trace-context.
I can provide Zoom with recording
from trace-context.
works for me
from trace-context.
I'd like to attend, thanks!
from trace-context.
works for me.
from trace-context.
from trace-context.
Great. Agenda as follows:
Charter - Speak now, or forever hold your peace (at least the next years) (Alois)
Trace-Context - Next steps for spec definition and open issues (Sergey?)
Interoperability Testbed - Next steps.
from trace-context.
Can't be online (always the network policy issue), but look forward the results.
from trace-context.
from trace-context.
We can also use dynatrace.zoom.us/my/alois
from trace-context.
I suggest we also create a youtube channel to store the recordings, e.g. all OpenTracing monthly calls are recorded. Transparency is important. Afaik Zoom only stores videos for 1 month.
from trace-context.
Here's the meeting ID: https://zoom.us/j/767754672
from trace-context.
I’ll be there!
from trace-context.
from trace-context.
Notes are quite important for transparency as is who attended. Not everyone
will watch the video and english is easier to translate from notes vs video.
+1, and understanding English notes are much easier than video, from my perspective.
from trace-context.
I can take the meeting notes.
from trace-context.
from trace-context.
Thank you Victor. We can have them in markdown in the github repo.
from trace-context.
I assume we use Yuri's Zoom?
from trace-context.
Subscribing
from trace-context.
Recording https://zoom.us/recording/play/lYNM3N7OWaEa8hAmSpojXD-V9KN0RfefnM_rfneaBwgDKhgmCBvlcDDPqPe3b3eP
from trace-context.
Everybody OK with the next Telco Tuesday, March 12th? Time Again 11:30 p.m. Topics:
- Open issues on Trace Context
from trace-context.
from trace-context.
from trace-context.
supposing it was for tomorrow but anyway let's also please give notice on gitter when there will be a meeting as it is nice and keeps people who are working more on code vs talking a heads up https://gitter.im/TraceContext/Lobby
from trace-context.
Sorry Adrian mixed up the dates. The day was right but but the date was wrong. Yes, we can move this to Gitter if helpful. Going forward we will have a bi-weekly cadence of meetings anyways and this should not happen again.
I am just hesitant to have information distributed everywhere. There is information on GitHub, GoogleDoc and Gitter. etc. People should have one central point to get their information from.
With the W3C group we can also get a mailing list. While it is old school it will serve the purpose.
from trace-context.
from trace-context.
Let us skip today as people were confused about dates. We can use the mailing list [email protected] for further sync. Will close the issue now.
from trace-context.
Related Issues (20)
- Inconsistent text style HOT 2
- Update wording on "response headers" in privacy section to disambiguate from traceresponse headers. HOT 1
- Start Wide Review for Trace Context Level 2 Spec HOT 6
- Need to publish latest draft of trace-context-2 HOT 3
- Self-Review Questionnaire for Trace Context Level 2: Security and Privacy HOT 1
- Trace Context Level 2: Self review for i18n HOT 1
- Trace Context Level 2: Self-review for accessibility
- Enable automatic publishing for Level 2 branch
- Request to republish level-1 spec (to publish a recent editorial change)
- Trace Context: Apache Kafka protocol specification HOT 5
- specification of lowercase is incomplete HOT 4
- Version number relationship to ASCII and UTF-8 HOT 1
- Why should keys be restricted to lowercase ASCII? HOT 7
- Adopt either span-id or parent-id for section headings HOT 4
- When headers should be propagated in browsers should be made more clear HOT 2
- Change the defining document for HTTP from RFC7230 to RFC9110 HOT 2
- Update tests to test Trace Context level 2 by default
- Incorporate Level 2 changes (random trace id flag) into traceresponse header in Level 3
- Add more normative text for flags processing in traceresponse
- Level 3 spec: Update privacy section to include information about traceresponse headers.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from trace-context.