-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Extension Authors Call for March 2020 #93604
Comments
The call will be held on April 7th (tomorrow) at 9 am Pacific Time. So far we will have the following participating extension authors:
|
Thanks to @eamodio and team for hosting! It was a fun and productive conversation. Glad to be a part of it. |
Yeah, it was a great event! Looking forward the next one. |
@eamodio it would be awesome to be able to "close the loop" and be able to track the issues that were raised in this call, to be able to judge the effectiveness of the meetings and whether they were able to bring attention to the critical issues facing extension authors. |
Is there any call in May? Will be happy to participate in. |
The call was great -- don't get me wrong -- but my hope coming out of that meeting was that there would be an outcome that had more teeth than "we made a list of the issues raised." For example, if there was any discussion or activity within the vscode team about the call, and if the discussion had a positive impact on planning or prioritization, it would be great to surface that information somehow, as a positive reinforcement loop. If on the other hand the purpose of the meeting is to just create another list of issues, that's cool too -- but I guess I was hoping that something more concrete would come out of it. |
While I can't really offer any concrete "teeth" outside of tracking issues and championing them β which I am definitely doing. At the same time, I believe I can confidently say that the call has definitely had an impact on planning. For example, the following are all in-progress in one stage or another (some in spec/planning, others in implementation)
And all of the other issues have been raised up and reviewed. To be clear, I don't want "just another list of issues" β I want to create a space where we can hear/see/feel what the community really wants or needs. Hopefully, that will help foster more internal champions and influence planning and direction. I also want to put people and faces to the issues, to "feel" the pain/wants/needs more acutely than in an textual issue β to help foster a better richer community. On that point, we had other members of the VS Code team listening into the call (and I'm sure others watched it after the fact), as well as members from the marketplace team. Although, at the same time, just because the community wants or needs something doesn't make it happen (or happen quickly even if we agree), it has to align with team goals, priorities, effort, etc. But the better we understand (truly understand) the needs and wants of the community we will be much better equipped to help provide them. I would also point back to the goals of these calls outlined here: #91714. The above is one of the main goals, while the other is early feedback on proposed APIs. And this next call (#96927) will be diving into some of that. I hope that makes sense and helps. |
Refs: #91714
Here is the rough plan for our extension authors call for March. The call will be on April 7th. The theme of this first call is "ice-breaker" π
Agenda
Participants
Since we want a small set of participants to facilitate richer and more effective communication, we are asking everyone who is interested in participating to fill out the sign up link below:
Sign up to participateSign-ups are over for this month's callSign-ups will end on April 1st. After which, we will reach out and confirm the set of authors who will be participating in the call, and will update this post with the final list.
Logistics
On April 7th at 9am PT (12pm ET), via a MS Teams call. Unfortunately, for this first call, we won't have a live stream setup for the broader community to join in and comment, but we will post a link to the recorded video at the end of the call. We are definitely looking into getting a live stream setup for future calls.
The text was updated successfully, but these errors were encountered: