oneMKL use of Slack channel

[rodburns]

• Link to the UXL Foundation Slack workspace and channel from the project README
• Assign team member(s) to monitor the Slack channel
• Set up notifications in the oneMKL Slack channel when new RFCs are added to the project repo for community review and comment

Acceptance Criteria:

• Link to Slack available on README
• Named team member(s) monitoring channel
• Notifications appearing on the Slack channel when new RFCs are added to the project

[sknepper]

@rodburns - Looking at the free vs paid Slack plans here: https://slack.com/pricing/paid-vs-free , it appears that people on the free plan see only a 90 day history of conversations.
Will the use of Slack for certain discussions/decisions cause the history to be hidden to users who are using a free Slack plan? In that case, it seems like keeping the main discussions on the Github project itself would be more appropriate.
If this concern should be raised elsewhere, please move the discussion there. Thanks!

[rodburns]

The general guidance would be that decision making is made on the GitHub repo itself rather than in Slack. That is more transparent in any case. But general discussions on things can be had on Slack where conversations and threads are easier to have than on GitHub. This way losing old conversations shouldn't matter too much, but if it is a problem we can talk about how to solve that.

[vbm23]

uxlfoundation/oneMath#481 created by @rscohn2

[vbm23]

Awaiting uxlfoundation/oneMath#481 to be merged by @vpirogov / @mkrainiuk post 2 approvals

[vbm23]

@sknepper @mkrainiuk Kindly help notify when the slack token as a secret for the repo is worked out from PR by Alexey.

In order to meet the other acceptance criterias, can one help update links to UXL Foundation Slack Workspace and oneMKL channel in Contributing Guidelines and if applicable also to Support section of README.

So also Team members involved into working with external contributors would need to monitor the channel.

[mkrainiuk]

"Named team member(s) monitoring channel" will be covered by #8 when we define the list of maintainers.

[vbm23]

The secret has been created by Alexey & @rscohn2 confirmed that it works here

[vbm23]

Named team member(s) monitoring channel to be taken up in #8

[mkrainiuk]

List of Intel team member monitoring channel was defined and approved. We are waiting for some reps from Codeplay as well.