search

dotnet / corefx-standup

CoreFX Contributors standups - dates, topics voting, etc.
https://github.com/dotnet/corefx
16 stars 3 forks source link

2017/6 standup - Topics #3

Closed karelz closed 7 years ago

karelz commented 7 years ago

Please vote on topics you are interested in (👍) or you really want to avoid (👎). Feel free to suggest new topics as well.

We will try to order topics by popularity, to make sure we get to the most important ones first.

karelz commented 7 years ago

Product plans -- 2.0 vs. UWP6.0 vs. 2.1 vs. Future

Note: We can't discuss dates beyond official ship dates.

karelz commented 7 years ago

Plan to start releasing monthly alpha versions of vNext (2.1) - see details in https://github.com/dotnet/corefx/issues/20911

Note: UWP6.0 = .NET Native 2.0 likely won't have developer previews (details to be released publicly soon on CoreFX repo)

karelz commented 7 years ago

Discussion: General communication from CoreFX / .NET team: How can we be more open? (what works well, what doesn't, suggestions)

karelz commented 7 years ago

About CoreFX repo team(s) - team structure, inner workings, etc. (e.g. Core vs. Desktop vs. UWP vs. Mono/Xamarin)

Note: Somewhat captured in talk Challenges of Managing CoreFX Repo at 1:30

karelz commented 7 years ago

Larger technology design review: How we plan to roll out design plans for larger technology changes in the repo? How do we solicit feedback? (e.g. new Networking stack - info to be released publicly soon in designs repo)

karelz commented 7 years ago

Larger community contributions:

karelz commented 7 years ago

Bug management

Both captured in talk Challenges of Managing CoreFX Repo at 8:03.

Questions - bug monitoring:

  1. What do you use beside Twitter feeds @dotnetissues and @corefxissues?
  2. Would email notifications be interesting to you? (we have a few externals already)
  3. Would better notification system be useful to you? e.g. https://github.com/karelz/GitHubIssues/issues/9

Questions - bug triage:

  1. How to set up escalation route for 'hot' issues? (e.g. System.Net.Http - https://github.com/dotnet/corefx/issues/11100)
karelz commented 7 years ago

Test runs:

karelz commented 7 years ago

API review process & meetings

karelz commented 7 years ago

Which APIs belong to CoreFX vs. not? - see https://github.com/dotnet/corefx/issues/20902 (CoreFxExtensions repo)

Questions:

  1. How to deal with APIs that are off-topic, we don't think are good idea? Close more aggressively?
karelz commented 7 years ago

Involving and growing contributors community

karelz commented 7 years ago

API compat across platforms (PlatformNotSupported) & Obsolete APIs - see details (with links) on ApiCompat wiki page

Note: We are striking balance between easy-of-use in .NET Standard vs. being perfect and failing as early as possible for 'missing' APIs on certain platforms.

karelz commented 7 years ago

Random ideas:

  1. More hackatons (incl. world-wide?) like Dutch .NET Core 2.0 Hackaton (3 mins video)
  2. Release some internal .NET Foundations talks on youtube (we use these weekly sessions as deep dive into technologies for new team members - we have notes since 2008 & A/V since 2011)
  3. Host regular-ish .NET Core technology Q&A sessions (starting with GC session from Maoni Stephens) - likely in late August
  4. Shared Source CLI Essentials book for .NET Core - initiated from community, will be created in the open (everyone can contribute)
  5. .NET MeetUps roadshow in Europe this summer (Amsterdam, NL - 7/11, Prague, CZ - 7/19, Brno, CZ - 8/TBD)
  6. Under discussion: Remote almost-internships - Help grow engineers who are not eligible for classic internship. Smaller/mid-size projects with mentoring from Microsoft employees.
    • Would some experienced contributors be interested in becoming mentors?
  7. Recent idea: Meet-the-team interviews - short in-the-office chats about various parts of the technology
    • Would that be interesting?
jmezach commented 7 years ago

That's a lot of topics :). I think they are all interesting, but I'm guessing we won't have time to cover them all, so I just voted on the things that I thought would be most relevant short term.

hughbe commented 7 years ago

Recent idea: Meet-the-team interviews - short in-the-office chats about various parts of the technology Would that be interesting?

Yes yes yes! As someone who's collaborated with members of the team many times (recently on almost a daily basis for all my sins) it'd be so interesting to hear their perspectives and learning a bit more about what they're working on and how it fits in to .NET Core. I'd also be interested as part of this to understand the team structure a little better - e.g. who works on .NET core full time, who works on netfx/UAP as well

karelz commented 7 years ago

I'd also be interested as part of this to understand the team structure a little better - e.g. who works on .NET core full time, who works on netfx/UAP as well

Good point. I called it out explicitly here: https://github.com/dotnet/corefx-standup-temp/issues/3#issuecomment-308635252

Short answer: Our teams own all 3 runtimes - Desktop (incl. servicing), Core and UWP. Who works on what shifts based on business need at the moment (some people hyper-focus at times like now with UWP6.0). Area experts are typically responsible for everything. Mono/Xamarin is owned and handled by Xamarin team, but we try to remove duplication by porting code (HttpListener, Drawing) and by Mono reusing our CoreFX libraries (work in progress).

karelz commented 7 years ago

I have ordered top topics logically (taking upvotes into account) and created detailed talking points for our standup tomorrow: https://github.com/dotnet/corefx-standup-temp/blob/master/Standups/2017-06.md#finalized-content--topics

karelz commented 7 years ago

I will turn the topics into separate issues for future standups voting.