Skip to content

Usability Discussion #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
reyang opened this issue Oct 2, 2019 · 3 comments
Closed

Usability Discussion #195

reyang opened this issue Oct 2, 2019 · 3 comments
Assignees
@ocelotl @c24t
Labels
discussion Issue or PR that needs/is extended discussion. usability
Milestone
Beta

Comments

@reyang
Copy link
Member

reyang commented Oct 2, 2019 •
edited
Loading

With the alpha v0.1 release we've managed to have a hard-to-use SDK 🥇 , which has been demonstrated in #191.

This is a little bit deviated from the Zen of Python, as well as most of the collaborators' intention ❤️ .

Let's see if together we can do something to make the API/SDK more friendly to users:

  1. Be Python idiomatic.
  2. Make it work by default (this is already arguable).
  3. Make it as simple as possible, but no simpler.
  4. Make it self explanatory (stretch goal).
@reyang reyang added the discussion Issue or PR that needs/is extended discussion. label Oct 2, 2019
@reyang reyang added this to the Beta Release milestone Oct 2, 2019
@reyang reyang mentioned this issue Oct 2, 2019
Merged
@lzchen
Copy link
Contributor

lzchen commented Oct 2, 2019

The PR link does not work.

@c24t c24t modified the milestones: Beta Release, Alpha v0.3 Oct 11, 2019
@lzchen lzchen mentioned this issue Nov 4, 2019
Merged
@Oberon00 Oberon00 mentioned this issue Nov 12, 2019
Merged
@c24t c24t modified the milestones: Alpha v0.3, Alpha v0.4 Dec 5, 2019
@Oberon00 Oberon00 mentioned this issue Dec 9, 2019
Merged
@c24t c24t self-assigned this Dec 19, 2019
@c24t c24t added the usability label Jan 22, 2020
@codeboten
Copy link
Contributor

This update to the ruby implementation went in last week:
open-telemetry/opentelemetry-ruby#171

@toumorokoshi toumorokoshi modified the milestones: Alpha v0.4, Beta Feb 27, 2020
@c24t
Copy link
Member

c24t commented Mar 18, 2020

#466 went a long way to solving several usability problems in the library and #327 will make similar changes to integrations. There's still more work to do to make the library easy to use, but we'll track that work in more specific issues.

@c24t c24t closed this as completed Mar 18, 2020
srikanthccv pushed a commit to srikanthccv/opentelemetry-python that referenced this issue Nov 1, 2020
@mayurkale22
fix(basic-tracer): add timestamp for event (open-telemetry#195)
e114423 
* fix(basic-tracer): add timestamp for event

* fix: use performance.now()
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ocelotl ocelotl

@c24t c24t

Labels
discussion Issue or PR that needs/is extended discussion. usability
Projects
None yet
Milestone
Beta
Development

No branches or pull requests
6 participants
@codeboten @toumorokoshi @ocelotl @lzchen @reyang @c24t