Skip to content
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.

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

seeking feedback: diagnostic report tooling #301

Closed
boneskull opened this issue May 15, 2019 · 9 comments
Closed

seeking feedback: diagnostic report tooling #301

boneskull opened this issue May 15, 2019 · 9 comments

Comments

@boneskull
Copy link

I’m working on a toolkit (still unreleased) to help inspect and process diagnostic reports (generated via process.report).

I’m hoping to drop in to an upcoming meeting and get some feedback about the current state of the project, and how it can better serve various use-cases.

Tentative plan:

I’d want to present a couple slides with an overview of the tool’s functionality and goals, then perhaps a quick demo (2-3 minutes). I’d open it up for questions and general feedback, then ask a few specific questions. What do you think?

@mhdawson
Copy link
Member

I think this is a good idea, given the collaborator summit conflicts with the next meeting I'd suggest we think about doing it in the meetin gon June 12th.

@boneskull
Copy link
Author

Sounds good to me. I am also available to meet about it during the summit!

@mhdawson
Copy link
Member

Tagged with diag-agenda, if there is a meeting before the 12th, we will just need to skip it on the agenda

@boneskull
Copy link
Author

@mhdawson So, the 12th then?

@mhdawson
Copy link
Member

mhdawson commented Jun 5, 2019

Will be on the agenda for the 12th.

@boneskull
Copy link
Author

errr, is that supposed to be now? maybe I have the wrong TZ.

@mhdawson
Copy link
Member

Sorry for some reason there was no entry on the Calendar (or any other data anymore). In any case too late for this week so I've re-added to the Calendar for next week.

@gireeshpunathil
Copy link
Member

I guess the purpose of this issue is resolved? if so can we close this?

@mmarchini
Copy link
Contributor

Closing, feel free to reopen if there's anything left to be discussed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants