Skip to content

June 2019

Updated Feb 25, 2019

June 2019 sprint goals

.NET Core

  • item1
  • item2

May 2019

Updated Apr 5, 2019
  

May 2019 sprint goals

.NET Core

  • item1
  • item2

April 2019

Updated Apr 26, 2019
  

April 2019 sprint goals

  • Redirection tasks
  • Migration issues
  • Markdig fixes
  • Bug fixes including some bugs reported by the loc team
  • New API content for .NET Core releases
  • Update .NET Core 3.0 APIs for Preview 4

March 2019

Updated Apr 5, 2019
  

March 2019 sprint goals

  • Redirection tasks
  • Migration issues
  • Markdig fixes
  • Bug fixes including some bugs reported by the loc team
  • New API content for .NET Core releases
  • Update .NET Core 3.0 APIs for Preview 3

Projects for .NET Community Contributors

Updated Apr 10, 2019
  

This project lists outstanding tasks and work items for which we would appreciate community contributions. The items are grouped into three categories. Depending on your interests, your level of familiarity with GitHub, and your level of comfort with creating independent content, you can choose from the following three categories:

Maintenance. These work items involve such things as correcting broken links, correcting spelling or stylistic errors, or modifying the formatting of content to improve the overall appearance of the documentation on docs.microsoft.com.

Content updates. Parts of our massive documentation set have become stale and are in need of updating. Some topics don't do a good job of addressing the issues that developers face when using a technology and require revision and refocusing. Migration to a new publishing platform has created duplication and, in some cases, triplication of largely identical topics that needs to be addressed through a process of consolidation.

Authoring new content. Every documentation set has gaps. We welcome community contributions to address those gaps. We've identified some of the topics and topic areas for which we would like to see content, but the list is not exhaustive. You may want to contribute a topic in a technology area about which you feel passionate that isn't on the list.

All of these work items are available. Two additional columns contain items for which work either has begun or has been completed.

This project aims to identify API reference examples that will benefit from running in the interactive try.dot.net environment, which runs examples interactively and allows users to modify code. Adding interactivity enables customers to better understand and use major .NET APIs. Each issue is devoted to a particular API that we will consider making active. In addition, APIs with interactive examples will be monitored to ensure that the examples are effective in meeting customer needs.

This project consists of the following categories of items:

  • A discussion item that aims to identify API types and members that are candidates for interactivity.
  • APIs being evaluated: API types and members that are being considered for interactivity. Discussion and feedback are welcome for these items.
  • In progress: API types and members whose examples are or will be made interactive during the current sprint. APIs made interactive: The API types and members whose examples are currently interactive.
  • Reporting:: A quarterly report (to be prepared for the first time in January 2019) that attempts to evaluate the impact of interactive examples on customer satisfaction.
You can’t perform that action at this time.