starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Forms of communication between developers?(Discord/Teams/Slack/Email) #972

New Issue
Closed
opened 2026-01-30 22:12:45 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 22:12:45 +00:00
Owner
Copy Link

Originally created by @Puthranps on GitHub (May 11, 2019).

Will, there be a teams/slack/discord or email listing that where we can collaborate in real time? If this proposal can get approved for a discord server I can submit a pr on the Readme with a permalink. I would like there to be a way to communicate with the developers without having to post new issues.

Originally created by @Puthranps on GitHub (May 11, 2019). Will, there be a teams/slack/discord or email listing that where we can collaborate in real time? If this proposal can get approved for a discord server I can submit a pr on the Readme with a permalink. I would like there to be a way to communicate with the developers without having to post new issues.
claunia added the Issue-QuestionNeeds-Tag-FixProduct-MetaArea-Build labels 2026-01-30 22:12:45 +00:00
claunia commented 2026-01-30 22:12:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 12, 2019):

I believe this is a question for @DHowett-MSFT or @bitcrazed

@zadjii-msft commented on GitHub (May 12, 2019): I believe this is a question for @DHowett-MSFT or @bitcrazed
claunia commented 2026-01-30 22:12:46 +00:00
Author
Owner
Copy Link

@Puthranps commented on GitHub (May 13, 2019):

That would be great I think it would be more convenient than doing Twitter dm',s and some non Microsoft maintainers may get the chance to communicate with each other on one platform

@Puthranps commented on GitHub (May 13, 2019): That would be great I think it would be more convenient than doing Twitter dm',s and some non Microsoft maintainers may get the chance to communicate with each other on one platform
claunia commented 2026-01-30 22:12:46 +00:00
Author
Owner
Copy Link

@Puthranps commented on GitHub (May 13, 2019):

For preference I think we should discord because slack can erase message history and doesn't scale too well and teams I think would be more accessible than teams and email.

@Puthranps commented on GitHub (May 13, 2019): For preference I think we should discord because slack can erase message history and doesn't scale too well and teams I think would be more accessible than teams and email.
claunia commented 2026-01-30 22:12:46 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (May 14, 2019):

We are definitely looking into options re. discussions & chat. Please bear-with us while we figure out a plan here.

@bitcrazed commented on GitHub (May 14, 2019): We are definitely looking into options re. discussions & chat. Please bear-with us while we figure out a plan here.
claunia commented 2026-01-30 22:12:46 +00:00
Author
Owner
Copy Link

@Puthranps commented on GitHub (May 14, 2019):

@bitcrazed no rush at all I just wanted to make this suggestion thanks for taking this issue into consideration.

@Puthranps commented on GitHub (May 14, 2019): @bitcrazed no rush at all I just wanted to make this suggestion thanks for taking this issue into consideration.
claunia commented 2026-01-30 22:12:47 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 24, 2019):

This is not the official team Discord. There is no official team Discord.

@DHowett-MSFT commented on GitHub (May 24, 2019): This is not the official team Discord. There is no official team Discord.
claunia commented 2026-01-30 22:12:47 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 24, 2019):

@MooseA Please don't post unrelated social links to unrelated communities. Thanks!

@DHowett-MSFT commented on GitHub (May 24, 2019): @MooseA Please don't post unrelated social links to unrelated communities. Thanks!
claunia commented 2026-01-30 22:12:47 +00:00
Author
Owner
Copy Link

@jj10133 commented on GitHub (Sep 10, 2019):

Please could we have some means of communicating ?? rather than the issues??

@jj10133 commented on GitHub (Sep 10, 2019): Please could we have some means of communicating ?? rather than the issues??
claunia commented 2026-01-30 22:12:47 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Sep 12, 2019):

Update 2019-09-11 - We have begun discussions with a team that's working on a generalized solution in this space, but it's going to be a few months until its viable.

In the meantime, please continue to post issues here: The Terminal dev team are constantly monitoring and responding to issues in this repo, ensuring a good likelihood of a response.

If you want to ping us elsewhere, you'll likely have some luck by pinging us on Twitter: Rich or Kayla

@bitcrazed commented on GitHub (Sep 12, 2019): Update 2019-09-11 - We have begun discussions with a team that's working on a generalized solution in this space, but it's going to be a few months until its viable. In the meantime, please continue to post issues here: The Terminal dev team are constantly monitoring and responding to issues in this repo, ensuring a good likelihood of a response. If you want to ping us elsewhere, you'll likely have some luck by pinging us on Twitter: [Rich](https://twitter.com/richturn_ms) or [Kayla](https://twitter.com/cinnamon_msft)
claunia commented 2026-01-30 22:12:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 22, 2021):

You know, it's been a could years, and IMO we've had a pretty good flow here on GitHub alone. I'd rather not fragment our communication into multiple platforms. Discussing features and bug fixes here on github has been a reliable way of communicating with our external contributors, so I think we'll just stick with that. Thanks for the suggestion!

@zadjii-msft commented on GitHub (Nov 22, 2021): You know, it's been a could years, and IMO we've had a pretty good flow here on GitHub alone. I'd rather not fragment our communication into multiple platforms. Discussing features and bug fixes here on github has been a reliable way of communicating with our external contributors, so I think we'll just stick with that. Thanks for the suggestion!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Build Issue-Question Needs-Tag-Fix Product-Meta
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#972
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?