corefx-standup
corefx-standup copied to clipboard
dotnet
CoreFX Contributors standups - dates, topics voting, etc.
Talking points: * Great contribution experience (natural workflow which works) - [#20570](https://github.com/dotnet/corefx/issues/20570) * Great contribution docs - in progress on [CoreFX wiki](https://github.com/dotnet/corefx/wiki/New-contributor-Docs) (RW for everyone) * Marking issues (or announcing...
Talking points: * Automation: * CI (Jenkins, eventually migrating to Helix) * Helix (eventually to have public access) * Goal to stay clean.
Talking points: * See [#20902](https://github.com/dotnet/corefx/issues/20902) (CoreFxExtensions repo) for current list * We consider only 'core' types to be part of CoreFX. Incl. types which we need to use ourselves. *...
During the last standup we mentioned *remote almost-internships* and a possibility of contributors becoming mentors. * What kinds of projects could be done this way? Would it be solving issues...
See details (with links) on [ApiCompat wiki page](https://github.com/dotnet/corefx/wiki/ApiCompat) Note: We are striking balance between easy-of-use in .NET Standard vs. being perfect and failing as early as possible for 'missing' APIs...
* [Triage rules](https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/issue-guide.md#triage-rules---simplified) * Notification tooling we use internally (v2 version slowly in progress - https://github.com/karelz/GitHubIssues/issues/9) Both captured in talk [Challenges of Managing CoreFX Repo](https://www.youtube.com/watch?v=Kcm0ns1pzm0&list=PLwZVRWVJepJtK6UZD-m2VLU2k2V-O5OrG&index=31) at 8:03. Questions - bug...
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...
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...