-
Notifications
You must be signed in to change notification settings - Fork 4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #61751 from jmarolf/infra/add-design-meeting-docum…
…entation
- Loading branch information
Showing
2 changed files
with
58 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
name: IDE Feature suggestion | ||
about: Propose a new IDE feature | ||
title: '' | ||
labels: [Feature Request, Area-IDE] | ||
assignees: '' | ||
--- | ||
|
||
<!-- | ||
We welcome feature suggestions! We have a process to discuss and evaluate new feature suggestions. Here is an overview of our process [here](https://github.com/dotnet/roslyn/blob/main/docs/contributing/ide_design_process.md). This template will help us gather the information we need to start the review process. | ||
--> | ||
|
||
## Summary | ||
|
||
<!-- | ||
Brief summary of what this proposal is about. | ||
--> | ||
|
||
## Background and Motivation | ||
|
||
<!-- | ||
What is the problem we are solving and in what context did you encounter it? | ||
--> | ||
|
||
## Proposed Feature | ||
|
||
<!-- | ||
Please provide a sketch of the feature you are proposing. Be as specific as you can: the more specific the proposal, the easier the process will be. Including screenshots of some of the existing problems can also help a lot here. | ||
--> | ||
|
||
## Alternative Designs | ||
|
||
<!-- | ||
Were there other options you considered? | ||
How does this compare to features in other editors? | ||
--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# IDE Team Design Process | ||
|
||
## Discussions / Issues | ||
|
||
The goal is that contributors can create and discuss feature suggestions without needing to have everything fully figured out. Feel free to file a new [Github issue](https://github.com/dotnet/roslyn/issues/new?assignees=&labels=Area-IDE%2CFeature+Request&template=feature-suggestion.md) or start a [discussion](https://github.com/dotnet/roslyn/discussions/new). These conversations can continue at their own pace until contributors feel ready to make a more formal proposal. | ||
|
||
## Proposals | ||
|
||
### Adding a proposal | ||
|
||
For a feature proposal to be reviewed, a Github issue needs to be created that has the following items in its description. If these aren't there to start they eventually need to be appended as a comment to the issue before its brought up for discussion. | ||
|
||
- **Summary**: Brief summary of what this proposal is about. | ||
- **Background and Motivation**: What is the problem we are solving and in what context did you encounter it? | ||
- **Proposed Feature**: How the proposed solution solves the problem? | ||
- **Alternative Designs**: Were there other options you considered? How does this compare to features in other editors? | ||
|
||
Once you've added the details for your feature tag a member of the Roslyn-IDE team and they will add the "[Feature Request](https://github.com/dotnet/roslyn/issues?=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22Feature+Request%22)" label to your Github issue. | ||
|
||
### Getting the issue championed by the IDE team | ||
|
||
A member of [Roslyn-IDE](https://github.com/orgs/dotnet/teams/roslyn-ide) will need to decide to "champion" that feature proposal and bring it for discussion by adding it to the "On Deck" tab in the [IDE Design Review](https://github.com/dotnet/roslyn/projects/40) project. Behind the scenes the IDE Team generally meets once a week to discuss these issues. |