OpenJS Foundation OpenJS Foundation Collaborator Summit, Berlin, May 2019, 5 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Proposal to drive Node js diagnostics initiatives through user journeys

Description

OpenJS Foundation Collaborator Summit, Berlin, 2019

More details: https://github.com/nodejs/diagnostics/issues/295

A

So the agenda for this session is first time that we sat on the context that why.

A

For the instance, then I would like to show producer out there and I see. There is some open questions which I hope we can add a line. Man for this collection, feedback and syncing them together.

A

Doing the contacts setup I will share some pain points currently, but I believe.

A

It's more focus where we are using over and basically today, I see. One nice thing is that we don't have so I think everyone has in their mind. What does it mean language thing? Not just access file.

A

I can have a memory, my consciousness and French for different reasons, but we are one privatizing, those use cases which our company or our cell wasting and you don't really have a collection and the diagram is what actual Majesco surface and we don't really have time and and privately on what we are planning to for work to make easier for these users.

A

It also means that we are not just not really knowing those pieces, but we also don't know how users trying to handle that so I think we can all agree that not only is, for example, one of the use cases which probably many many Jesuses, and today you can diagnose an immunity. Many many ways you can use the chrome keep snapshot, you can use the 70 profiler you can use Chico to get than bright streets are empty. My way to explain it.

A

There are many many ways and I made sure I or the Beast.

A

It will be also nice just learning what our users doing today and instead of that kind of coming.

A

A

From where we are.

A

And then they already mentioned that some of the tools only works in some of my events.

A

Use cases to leave either.

A

Of them, especially since one of them only works so I believe we have some problems and I hope that being more focused and capturing these things and research at least, we can be more focused around what we are buying.

A

So I would like to do.

A

One thing is I think this is to say, oh definitely, kind of collecting what abuse but have just any beliefs of what the user is trying to do when we are talking about diagnosing EHS process and that's like identify which are the really important ones which we have I'm, pretty sure that I use cases like we were talking about. The embedded systems environment was introduced in nutrient burglars and epi. But probably you should go up to one step in the.

B

First round.

A

Most yes, I think it would be also connected to the me how find to after the use cases today and creating the ideal user journeys really being able to identify the gap between what we have today and what you want to achieve in the future. Let's believe me in the natural where the action items.

A

Yes and the final step is I believe this is something which we are kind of today, kind of thinking about what taste and purpose I'm not talking about two links here, so I strongly believe that it should kind of stop seeking the world, like noodles /, for example, has to be supported for all yes to services, which is really suitable by, for example, we wanna have a way to diagnose naked frames between all the various pieces, a meaning of that I believe we should shift the focus to lean more the use cases and user journeys and basically start to document.

A

The discrepancy is talking about. You know what you just signed, what wins.

A

So here I'd like to give some opportunities like someone who has true or contra opinion, but stop people sleeping use physics and do such a mess. I.

A

Am sufficiently money.

A

So basically, I started to work on kind of the document where I started to call that, obviously this is just in my head. So I think this is complete.

A

So you can find this document in either in the proposal that we or.

A

A

So basically, these documentaries I really hope that we can move better to the majestic people and basically.

B

A

To do bigger sections, one is kind of collecting these cases. Another one is collecting the current tools that are available, I'm, pretty sure I missed a bunch of them. So really it was more focused in my head and, let's see the spectral cases like I was mentioned, family connection.

A

Basically, all of the use case is follow the structure that you have kind of seen on section. So as a user, what you are maybe you're serving when it's suspicious that you're a student, because this show some of them has a side effect, because it's sometimes not that obvious that why you are seeing the symptoms so that can give you a picture as user that what we are facing I believe the election. Can we really.

A

Use figure out what we are facing, then there is a debugging section, and this is a section which is quite complete, so it has to section ID, user Germany and the current researcher matrix idle idle user journeys. We feel it. Some of them is not even possible cordially and and then there is a little table which is more about what tools today recognized in time can be used for this use case and what are the existing gaps assume on a stone? We have the same for.

A

Each to has kind of little explanation what it is: very confinement and kind of what are the pros and cons when you are using this tool.

A

So that's the business sector that I started to think about I asked some folks opinion was a structure in the thank you for the feedback, but obviously I will be happy if I could get the feedback from more people and I'll talk to extend those pieces, and that's really when we could start to think about prioritizing. So first first I think it would better just capture as much information as we can.

A

Is there any question would supplement.

A

Information, no ok, then this is the more called Rayleigh path. I hope we can have good conversations. So there are some questions you want to know.

A

So chairs can be used in so many environments they and and not obvious- which one can we have the biggest impact so I look to the majestic and looks like that. Most people use this port very high standard but service. Basically, the only sauce.

A

So the focus on is basically start with those use cases, and basically one question is how we can collect more information and how frequently should.

C

My question was: the annual survey already have.

A

If I remember correctly, the annual survey questions basically.

B

C

Don't think I've ever seen like an in-depth discussion, but it has come up with certain times. I could somehow get that very quickly becomes the conversation people are concerned and, like I, don't think a lot of people I think even earlier this week,.

C

Yes, so that was something that yesterday with dr. vegetation, simply gathering numbers.

A

Like usage, so we had some ideas for how we could actually do some count, which is like integrating that into testing frameworks in code coverage frameworks.

C

And just yesterday, it'll appear that as a internal omics, poetry function that will emit you reasonably using a new node in the best lemon tree category off the default. Obviously they're tracing additional stuff. It's a lot more noise in there, but all of those simply just a tracing.

B

That we can just count how many times I think it's squirt along that direction.

B

I'm just curious inflate the node project is like a critical level at this point were like like by not having this like ability to collect this information in the wild like we're, shooting ourselves in the foot. You know, even though it's something that needs to be on that really responsibly. You know. Data collection, like this I mean I'm like hashtag, like stop trying.

B

Curious if the partitions are actually worth revisiting and like at the very end, Michael is the MVP like what would that look like, and you know, and.

C

Do you know of anyone times languages that do do that right, like that.

C

C

It'd be great to get the data and I know.

B

C

Why I said I get.

B

To buy MVP and like what is like the minimal piece of information that looks like so like not an issue right and it's like anything. It's like nothing to tell a pattern. You know about like what you're doing it's really just like metrics on, like where you're doing it, you know and so, and drew me like I'm, Mac, OS right, because.

B

It's you scale. The scale is so large, I think there's a case to be made here: okay, users of node like if you really know this project that really want this data, and it's you.

A

B

No, no, no inference that. Can you make your other than.

C

I'm, just thinking I think it's actually not a bad thing, but I don't know that it's actually critical to a survey.

B

Or something wait.

C

I should get.

C

That's just choose what we pick the best ones are and forward, rather than worrying and I would like that you get the absolute.

A

A

A

Who is using notes for rendering, like we're, pandering website.

A

Who is using more kind of a time, saver or item on mean my life consume me a message? Curves.

A

Okay looks like a pH the most and all of the rest is pretty much the same amount. I would say very many.

C

Editing to is like is: are these really that different like if you have a best practice for.

A

Running in server environment are looking from another angle, usually.

B

A

Kind of cities are not that blatantly to meet the ice from the water started, doing more destructive, maybe even because sure you just flip back to the cube I mean that's it, but that's a very good question: okay, I'm.

B

Actually, some application pruning.

B

A

I have which is more more about having a long term support, but not on specific to us more on uses like you can be always provide a way to you know: I, don't remember you.

A

A

So be the loss of conversation on the last couple of diversity means that when we started to work on these support years, I think identified four years. One of them is that every Comicon master should pass the second one is.

A

Yes, but you can get the idea. I don't have any support ears and we starting to put tools kind of what we expected to like I. Don't know.

A

In which tier show me so this is ongoing progress, but now I was thinking about that. Maybe he sees us to lean it's fine in the tooling. These changes I mean it's not because higher level features most definitely not be fair, but maybe it's a better approach. If we say that we will always give you a way to deal with your diagnostic use case. Maybe changes between baby will be different tools, and let me give some historical reason why I started to be more lenient using.

A

Variables- and there were lots of pushback on the community on this tool, because it's not really what everyone uses. It's clearly, not the high priority of people who are working and middle, putting a lot of people how we could replace or cordon based processes to you to kind of not having this have requirements in your environment and basically, if you start to log what date on, if you start now, we have not 12. This new kind of exception is logging of the property, so I feel there are other ways yeah.

A

Can be least make that commitment that you can always use no, and you will always give you documentation of respect, is recommended even if it changes between different realists. So the open question to the group is basically who believes we should still stick to tools.

A

Please raise your hand if you believe that we should talk about long term, support I, don't see hands. Then let me twist the question little bit to have some conversation around it, who believes that we shouldn't focus at the long term, support against a.

A

Smaller one one hand.

B

C

A

Absolutely agreement and I see the really hot restroom will be there that when the test Buster brain then, should we fix a tool or should be fine and.

C

Not seem like the right way to make inflexible about this table. You know.

C

B

B

You know, and so I.

C

Verify format or you.

C

Know those are things we build for and these point we are thanks. Lunging recent format course change. We would not expect.

C

If the outlet changes.

B

C

B

You on, like army contracting and the.

A

Slicing this, what James settles a bit leads back to the original conversation that should be saved on the use cases of because, as you mentioned, we can remediate the North core can really block on something which doesn't even necessary.

A

For me, leads back to the Sikh temple has to be shredded. There's always a way to do. Want the user to.

C

Remember major change.

C

That might still be a case where you say: well, it's still possible.

C

Yes, you could try and say, but.

A

I'm saying I think it's not good if you have a gap in Diagnostics even for specific amount of time, so I will definitely blow up on actually 90s release if there is no way to what what is not necessary same to over, but it has to be a way.

B

A

C

C

That one thing going back to the thing with regards to supporting Diagnostics, one of the reason that the trace that API is experimental, no path yet or c'mon experiment. If we do not have use cases that can point to it, they'll describe how it is always goes work right. We have some traces that were.

C

A

B

I guess we beat.

A

Start to say what we expect to the beginning of the presentation that we need to document what degree, what support, what we expect, how they are used, provided best practices, and then we can start a suitable. What it means diagnostic. First us for no event.

A

Okay, um so it looks like this specific question is a dependency.

A

So the rest of the sign slides basically about just drawing some unique on future, basically having always supported, use cases between releases always having best practices, and we are working towards the ideal, Germany and minimizes moving gaps and.

A

Basically, there are other questions which we can dig some of them, because we have like 50 minutes which are militant in this initiative.

A

Basically, one of them is how do we influence those design, the user journeys? This is a question more we discussed is that not every diagnostic tool is basically in the node people or kind of maintained by notable person. So how can influence something and have the contract for testing, for example, when it's owned by the community there? Any idea comment around.

B

But the reality is like theirs.

B

And so I think, if you're, if you're, if you're used to kind of like hearing a lot about them, please um cat like Chantry. They don't have the same weight like they're. Never gonna have the same weight user base. It's so ultimately laying the threshold should be much lower and I. Guess I need references Diagnostics, because.

B

Everyone is gonna use, but it's very important.

A

Yes, that's a very good point and kind of leads back to the question that kind of onboarding, more Enterprise companies for not yes, I, believe.

A

Least, when you're reaching out to other enterprises.

B

So the other reason why the nose, the noise factor might be.

A

Low this is a lot of energizes.

B

The companies are, it's called full source. There's a culture I mean.

A

It sounds like you're advocating no more the contract kind of rather than owning.

A

We have good diagnostic api's and it provides the data and the community can always feel.

C

Between me, there's wider community rules. You don't want to give away about if there's no fuel, but it's really critical to know that, then you project, not, although we lose a few things in wear that make sense, but how many some projects under the.

C

A

We make that decision.

C

A

C

Don't roll it there's any like you're gonna be able to stay here. The rules I think it's more like somebody says. Well this one I think.

C

It needs more support.

A

So it sounds like you're more on Bobby. There's one push I, don't maybe this under-resourced. So maybe then, when foundation can lift it off because it's the important part of Instagram okay be reasonable.

A

That was about and just to recognize this fall. The one way to move forward would be so. First of all, we should call that the use cases which I have no better idea than please to put into the document and let's see which one is me even plus one. So we need to find some way how to how to identify these cases.

A

You know what not good just ones now, just let's call that what we haven't privatized later then after the accusation- and we should have kind of deep dives- we are doing them before the diagraph. You kind of the usual I weekly so having. We have to do surviving these things when we are going through the in progress action items, but sometimes we do deep dives and they are picking one specific topics.

A

People who are interesting showing so we could have a deep dive term use case is kind of discussing what would be the ideal world actually use case to try what we are missing today. So definitely one way forward having one deep dive like months two weeks, but it will be a longer at fault but I think, even if we make progress and want to use a system that could be a good initial.

A

Besides, and this is where I have this unique on slice forget everything is close to the ideal and always supported, and everything is prospect from accessible and if increase is not yes use, it I really hope we can. With this one day.

A

We have 10 minutes so I finished earlier, which we can either give it back to the brain or someone has questioned and please.

A

There's no breaks.