Skip to content

Commit

Permalink
How to contact maintainers + some clarifications (#2822)
Browse files Browse the repository at this point in the history
* adding slack link

* contacting maintainers

* Updating details on bazel tests

* Apply suggestions from code review

Co-authored-by: ethanglaser <42726565+ethanglaser@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: ethanglaser <42726565+ethanglaser@users.noreply.github.com>

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

---------

Co-authored-by: ethanglaser <42726565+ethanglaser@users.noreply.github.com>
  • Loading branch information
napetrov and ethanglaser authored Jun 21, 2024
1 parent 5101796 commit c3d61d3
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 2 deletions.
11 changes: 10 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ We welcome community contributions to Intel(R) oneAPI Data Analytics Library. Yo

Refer to our guidelines on [pull requests](#pull-requests) and [issues](#issues) before you proceed.

## Contacting maintainers
You may reach out to Intel project maintainers privately at onedal.maintainers@intel.com.
[Codeowners](https://github.com/oneapi-src/oneDAL/blob/main/.github/CODEOWNERS) configuration defines specific maintainers for corresponding code sections, however it's currently limited to Intel members. With further migration to UXL we will be changing this, but here are non-Intel contacts:

For ARM specifics you may contact: [@rakshithgb-fujitsu](https://github.com/rakshithgb-fujitsu/)

For RISC-V specifics you may contact: [@keeranroth](https://github.com/keeranroth/)

## Issues

Use [GitHub issues](https://github.com/oneapi-src/oneDAL/issues) to:
Expand All @@ -35,8 +43,9 @@ Use [GitHub issues](https://github.com/oneapi-src/oneDAL/issues) to:

To contribute your changes directly to the repository, do the following:
- Make sure you can build the product and run all the examples with your patch.
- Product uses bazel for validation and your changes should pass tests. Please add new tests as necessary. [Bazel Guide for oneDAL](https://github.com/oneapi-src/oneDAL/tree/main/dev/bazel)
- Make sure your code is in line with our [coding style](#code-style) as `clang-format` is one of the checks in our public CI.
- For a larger feature, provide a relevant example.
- For a larger feature, provide a relevant example, and tests.
- [Document](#documentation-guidelines) your code.
- [Submit](https://github.com/oneapi-src/oneDAL/pulls) a pull request into the `main` branch.

Expand Down
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,11 @@ To report a vulnerability, refer to [Intel vulnerability reporting policy](https

### Contribute <!-- omit in toc -->

We welcome community contributions. Check our [contributing guidelines](CONTRIBUTING.md) to learn more.
We welcome community contributions. Check our [contributing guidelines](CONTRIBUTING.md) to learn more. You can also contact the oneDAL team via [UXL Foundation Slack] using
[#onedal] channel.

[UXL Foundation Slack]: https://slack-invite.uxlfoundation.org/
[#onedal]: https://uxlfoundation.slack.com/channels/onedal

## License <!-- omit in toc -->

Expand Down

0 comments on commit c3d61d3

Please # to comment.