Update CONTRIBUTING.md

CONTRIBUTING.md

@@ -5,25 +5,27 @@ This guide helps to find the most efficient way to contribute, ask questions, an
 Code of conduct
 -----
 
-Please review our [code of conduct](code-of-conduct.md).
+Please review our [Code of Conduct](https://orkes.io/orkes-conductor-community-code-of-conduct)
 
 I have a question!
 -----
 
-We have a dedicated [discussion forum](https://github.com/Netflix/conductor/discussions) for asking "how to" questions and to discuss ideas. The discussion forum is a great place to start if you're considering creating a feature request or work on a Pull Request.
+We have a dedicated [discussion forum](https://github.com/conductor-oss/conductor/discussions) for asking "how to" questions and to discuss ideas. The discussion forum is a great place to start if you're considering creating a feature request or work on a Pull Request.
 *Please do not create issues to ask questions.*
 
+Conductor users hangout in the [Slack channel](https://join.slack.com/t/orkes-conductor/shared_invite/zt-xyxqyseb-YZ3hwwAgHJH97bsrYRnSZg).  Join the channel for more real-time communication!
+
 I want to contribute!
 ------
 
 We welcome Pull Requests and already had many outstanding community contributions!
 Creating and reviewing Pull Requests take considerable time. This section helps you to set up a smooth Pull Request experience.
 
-The stable branch is [main](https://github.com/Netflix/conductor/tree/main).
+The stable branch is [main](https://github.com/conductor-oss/conductor/tree/main).
 
-Please create pull requests for your contributions against [main](https://github.com/Netflix/conductor/tree/main) only.
+Please create pull requests for your contributions against [main](https://github.com/conductor-oss/conductor/tree/main) only.
 
-It's a great idea to discuss the new feature you're considering on the [discussion forum](https://github.com/Netflix/conductor/discussions) before writing any code. There are often different ways you can implement a feature. Getting some discussion about different options helps shape the best solution. When starting directly with a Pull Request, there is the risk of having to make considerable changes. Sometimes that is the best approach, though! Showing an idea with code can be very helpful; be aware that it might be throw-away work. Some of our best Pull Requests came out of multiple competing implementations, which helped shape it to perfection.
+It's a great idea to discuss the new feature you're considering on the [discussion forum](https://github.com/conductor-oss/conductor/discussions) before writing any code. There are often different ways you can implement a feature. Getting some discussion about different options helps shape the best solution. When starting directly with a Pull Request, there is the risk of having to make considerable changes. Sometimes that is the best approach, though! Showing an idea with code can be very helpful; be aware that it might be throw-away work. Some of our best Pull Requests came out of multiple competing implementations, which helped shape it to perfection.
 
 Also, consider that not every feature is a good fit for Conductor. A few things to consider are:
 
@@ -32,6 +34,7 @@ Also, consider that not every feature is a good fit for Conductor. A few things
 * Does it require new dependencies (this is rarely acceptable for core modules)
 * Should the feature be opt-in or enabled by default. For integration with a new Queuing recipe or persistence module, a separate module which can be optionally enabled is the right choice.
 * Should the feature be implemented in the main Conductor repository, or would it be better to set up a separate repository? Especially for integration with other systems, a separate repository is often the right choice because the life-cycle of it will be different.
+* Is it part of the Conductor project roadmap?
 
 Of course, for more minor bug fixes and improvements, the process can be more light-weight.
 
@@ -44,7 +47,7 @@ If you found a bug, it is much appreciated if you create an issue. Please includ
 
 I have a great idea for a new feature
 ----
-Many features in Conductor have come from ideas from the community. If you think something is missing or certain use cases could be supported better, let us know! You can do so by opening a discussion on the [discussion forum](https://github.com/Netflix/conductor/discussions). Provide as much relevant context to why and when the feature would be helpful. Providing context is especially important for "Support XYZ" issues since we might not be familiar with what "XYZ" is and why it's useful. If you have an idea of how to implement the feature, include that as well.
+Many features in Conductor have come from ideas from the community. If you think something is missing or certain use cases could be supported better, let us know! You can do so by opening a discussion on the [discussion forum](https://github.com/conductor-oss/conductor/discussions). Provide as much relevant context to why and when the feature would be helpful. Providing context is especially important for "Support XYZ" issues since we might not be familiar with what "XYZ" is and why it's useful. If you have an idea of how to implement the feature, include that as well.
 
 Once we have decided on a direction, it's time to summarize the idea by creating a new issue.