mirror of
https://github.com/digital-asset/daml.git
synced 2024-11-13 00:16:19 +03:00
ADD: Change most Slack references to forum references where appropriate (#6071)
* ADD: Change most Slack references to forum references where appropriate CHANGELOG_BEGIN Replace references to Slack with references to discuss.daml.com CHANGELOG_END * ADD: Change issue template support link from SO to forum * ADD: Add back Slack links
This commit is contained in:
parent
081bc60e2f
commit
0ee217cdae
2
.github/ISSUE_TEMPLATE.md
vendored
2
.github/ISSUE_TEMPLATE.md
vendored
@ -4,6 +4,6 @@ This issue tracker is only for technical issues related to the DAML SDK.
|
||||
|
||||
If you suspect that your issue has a security impact, do not use this issue tracker. In that case, please contact security@digitalasset.com and follow our responsible disclosure policy: https://digitalasset.com/security/ .
|
||||
|
||||
For general questions about DAML and/or support request you should use Stack Overflow: https://stackoverflow.com/questions/tagged/daml .
|
||||
For general questions about DAML and/or support requests you should use our forum: https://discuss.daml.com .
|
||||
|
||||
-->
|
||||
|
@ -96,7 +96,7 @@ echo ""
|
||||
|
||||
function cleanup() {
|
||||
echo "SDK 0.0.0 failed to build/install - if you need help ask on"
|
||||
echo "https://slack.daml.com or https://discuss.daml.com."
|
||||
echo "https://discuss.daml.com or https://slack.daml.com"
|
||||
echo "$(tput setaf 3)FAILED TO INSTALL! $(tput sgr 0)"
|
||||
|
||||
if [[ -n "${SDK_TEMP_DIR+x}" && -d "$SDK_TEMP_DIR" ]]; then
|
||||
|
@ -8,7 +8,7 @@ DAML REPL
|
||||
being designed and is *subject to breaking changes*.
|
||||
We welcome feedback about the DAML REPL on
|
||||
`our issue tracker <https://github.com/digital-asset/daml/issues/new>`_
|
||||
or `on Slack <https://hub.daml.com/slack/>`_.
|
||||
or `on our forum <https://discuss.daml.com>`_ or `on Slack <https://slack.daml.com>`_.
|
||||
|
||||
The DAML REPL allows you to use the :doc:`/daml-script/index` API
|
||||
interactively. This is useful for debugging and for interactively
|
||||
|
@ -1182,7 +1182,7 @@ request and response elements demonstrated below or otherwise
|
||||
implemented by the API. We welcome feedback about the API on `our issue
|
||||
tracker
|
||||
<https://github.com/digital-asset/daml/issues/new?milestone=HTTP+JSON+API+Maintenance>`_
|
||||
or `on Slack <https://hub.daml.com/slack/>`_.
|
||||
or `on our forum <https://discuss.daml.com>`_ or `on Slack <https://slack.daml.com>`_.
|
||||
|
||||
Please keep in mind that the presence of **/v1** prefix in the the
|
||||
WebSocket URLs does not mean that the endpoint interfaces are
|
||||
|
@ -321,8 +321,9 @@ language for their applications.
|
||||
The only non-backwards compatible change compared to previous
|
||||
versions is the removal of queries on lists and maps in the HTTP JSON
|
||||
API. There is no trivial migration for this. If you were relying on
|
||||
these capabilities please get in touch with us via community@daml.com
|
||||
or on Slack. We’d like to hear how you were making use of the feature
|
||||
these capabilities please get in touch with us via community@daml.com,
|
||||
`on our forum <https://discuss.daml.com>`_, or `on Slack <https://slack.daml.com>`_.
|
||||
We’d like to hear how you were making use of the feature
|
||||
so that we can replace it with something better, and we will make
|
||||
some suggestions to work around the removal.
|
||||
|
||||
|
@ -6,28 +6,28 @@ Support
|
||||
|
||||
Have questions or feedback? You're in the right place.
|
||||
|
||||
- **Questions: Stack Overflow**
|
||||
- **Questions: Forum**
|
||||
|
||||
For “how do I?”, “why does something work this way” or “I’ve got a programming problem I’m trying to solve” questions, the `daml tag on Stack Overflow <https://stackoverflow.com/questions/tagged/daml>`_ is the best place to ask.
|
||||
For “how do I?”, “why does something work this way” or “I’ve got a programming problem I’m trying to solve” questions, the ``Questions`` category `on our forum <https://discuss.daml.com>`_ is the best place to ask.
|
||||
|
||||
If you're not sure what makes a good question, take a look at `this checklist <https://codeblog.jonskeet.uk/2012/11/24/stack-overflow-question-checklist/>`_.
|
||||
- **Help and feedback: Slack**
|
||||
If you're not sure what makes a good question, take a look at `our guide on the topic <https://discuss.daml.com/t/how-to-ask-questions/304>`_.
|
||||
- **Feedback: Forum**
|
||||
|
||||
If you want to give feedback, or have questions that aren't right for Stack Overflow, you can join the DAML community on `Slack <https://hub.daml.com/slack/>`_ and talk to us in the ``#public`` channel.
|
||||
If you want to give feedback, you can make a topic in the ``General`` category `on our forum <https://discuss.daml.com>`_ or on `Slack <https://slack.daml.com>`_ in the ``#public`` channel.
|
||||
|
||||
When you're in the community Slack or on Stack Overflow, please keep to the `Code of Conduct <https://github.com/digital-asset/daml/blob/master/CODE_OF_CONDUCT.md>`__.
|
||||
When you're in the community Forum or on Stack Overflow, please keep to our `Code of Conduct <https://github.com/digital-asset/daml/blob/master/CODE_OF_CONDUCT.md>`__.
|
||||
|
||||
Support expectations
|
||||
--------------------
|
||||
|
||||
For community users (ie on Slack and Stack Overflow):
|
||||
For community users (ie on our Forum and Stack Overflow):
|
||||
|
||||
- **Timing**: You can enjoy the support of the community, which is provided for you out of their own good will and free time. On top of that, a Digital Asset employee will try to reply to unanswered questions within two business days.
|
||||
|
||||
Business days are affected by public holidays. Engineers contributing to DAML are mostly located in Zurich and New York, so please be mindful of the public holidays in those locations (`timeanddate.com <https://www.timeanddate.com>`_ maintains an unofficial list of holidays for both `Switzerland <https://www.timeanddate.com/holidays/switzerland/>`_ and the `United States <https://www.timeanddate.com/holidays/us/>`_).
|
||||
- **Public support**: We only offer public support - for example, on the ``#public`` channel in `Slack <https://hub.daml.com/slack/>`_.
|
||||
- **Public support**: We only offer public support - for example, in the ``Questions`` category `on our forum <https://discuss.daml.com>`_ or on `Slack <https://slack.daml.com>`_ in the ``#public`` channel.
|
||||
|
||||
We can't answer questions in private messages or over email, so please only ask questions in the ``#public`` channel.
|
||||
We can't answer questions in private messages or over email, so please only ask questions in public forums.
|
||||
- **Level of support**: We're happy to answer questions about error messages you're encountering, or discuss DAML design questions. However, we can't provide more extensive consultation on how to build your DAML application or the languages, frameworks, libraries and tools you may use to build it.
|
||||
|
||||
If you need private support, or want consultation from Digital Asset about how to build your DAML application, they offer paid support. Please contact Digital Asset to ask about pricing.
|
||||
|
@ -12,8 +12,8 @@ DAML Triggers - Off-Ledger Automation in DAML
|
||||
**WARNING:** DAML Triggers are an early access feature that is actively
|
||||
being designed and is *subject to breaking changes*.
|
||||
We welcome feedback about DAML triggers on
|
||||
`our issue tracker <https://github.com/digital-asset/daml/issues/new?milestone=DAML+Triggers>`_
|
||||
or `on Slack <https://hub.daml.com/slack/>`_.
|
||||
`our issue tracker <https://github.com/digital-asset/daml/issues/new?milestone=DAML+Triggers>`_,
|
||||
`our forum <https://discuss.daml.com>`_, or `on Slack <https://slack.daml.com>`_.
|
||||
|
||||
In addition to the actual DAML logic which is uploaded to the Ledger
|
||||
and the UI, DAML applications often need to automate certain
|
||||
|
Loading…
Reference in New Issue
Block a user