move to uxlfoundation org (#533)

CONTRIBUTING.rst

@@ -36,12 +36,12 @@ Submit a Change
 ---------------
 
 * For questions, feature requests, or to report a bug, submit an
-  `issue <https://github.com/oneapi-src/oneAPI-spec/issues>`__.
+  `issue <https://github.com/uxlfoundation/oneAPI-spec/issues>`__.
 * For changes to the document build infrastructure or minor editing of
   the text, please submit a `pull request
-  <https://github.com/oneapi-src/oneAPI-spec/pulls>`__.
+  <https://github.com/uxlfoundation/oneAPI-spec/pulls>`__.
 * For significant changes to the specification, submit an `issue
-  <https://github.com/oneapi-src/oneAPI-spec/issues>`__. Make sure to
+  <https://github.com/uxlfoundation/oneAPI-spec/issues>`__. Make sure to
 
   * include "RFC" in the title,
   * explain your proposed change and the motivation for the change.

README.rst

@@ -6,11 +6,11 @@
 oneAPI Specifications
 =====================
 
-.. image:: https://github.com/oneapi-src/oneAPI-spec/actions/workflows/pr.yml/badge.svg
-   :target: https://github.com/oneapi-src/oneapi-spec/actions/workflows/pr.yml
+.. image:: https://github.com/uxlfoundation/oneAPI-spec/actions/workflows/pr.yml/badge.svg
+   :target: https://github.com/uxlfoundation/oneAPI-spec/actions/workflows/pr.yml
 
-.. image:: https://api.reuse.software/badge/github.com/oneapi-src/oneapi-spec
-   :target: https://api.reuse.software/info/github.com/oneapi-src/oneapi-spec
+.. image:: https://api.reuse.software/badge/github.com/uxlfoundation/oneAPI-spec
+   :target: https://api.reuse.software/info/github.com/uxlfoundation/oneAPI-spec
    :alt: REUSE status
 
 .. image:: https://www.bestpractices.dev/projects/8323/badge
@@ -150,7 +150,7 @@ Making a Release
 .. _`Read the Docs`: https://readthedocs.org/
 .. _`oneAPI Specification`: https://oneapi.io/spec
 .. _reuse: https://pypi.org/project/reuse/
-.. _HTML: https://oneapi-src.github.io/oneAPI-spec/spec/
-.. _PDF: https://oneapi-src.github.io/oneAPI-spec/spec/oneAPI-spec.pdf
+.. _HTML: https://uxlfoundation.github.io/oneAPI-spec/spec/
+.. _PDF: https://uxlfoundation.github.io/oneAPI-spec/spec/oneAPI-spec.pdf
 .. _`oneapi.io`: https://oneapi.io
 .. _roadmap: roadmap.rst

doc/governance.rst

@@ -18,10 +18,6 @@ The overall specification also has a core team and lead. The **oneAPI
 core team** is responsible for issues that involve multiple oneAPI
 elements and provides general oversight.
 
-`Technical advisory boards
-<https://github.com/oneapi-src/oneapi-tab>`__ review topics related to
-specifications and provide feedback. There may be overlap between core
-team and technical advisory board.
 
 
 Decision Making
@@ -60,12 +56,3 @@ Governance Changes
 Governance is intended to be informal and low overhead while
 encouraging broad participation from the community. oneAPI core team
 may change governance as the community evolves.
-
-
-Code of Conduct
-===============
-
-We follow `Contributor Covenant
-<https://www.contributor-covenant.org>`__. Contact a core team member
-or `oneAPI leadership <mailto:oneapi@intel.com>`__ with questions or
-to report an issue.

security.md

@@ -69,6 +69,6 @@ If you have any suggestions on how this Policy could be improved, please submit
 an issue or a pull request to this repository. Please **do not** report
 potential vulnerabilities or security flaws via a pull request.
 
-[1]: https://github.com/oneapi-src/oneapi-spec/releases/latest
-[2]: https://github.com/oneapi-src/oneapi-spec/security/advisories/new
-[3]: https://github.com/oneapi-src/oneapi-spec/security/advisories
+[1]: https://github.com/uxlfoundation/oneapi-spec/releases/latest
+[2]: https://github.com/uxlfoundation/oneapi-spec/security/advisories/new
+[3]: https://github.com/uxlfoundation/oneapi-spec/security/advisories

source/404.rst

@@ -11,5 +11,4 @@ We cannot find the page. Please try:
 - Starting the navigation from `spec.oneapi.io <https://spec.oneapi.io>`__
 - Clearing your `browser cache <https://clear-my-cache.com/>`__ and
   starting the navigation from `spec.oneapi.io <https://spec.oneapi.io>`__
-- Filing an issue in `Github <https://github.com/oneapi-src/oneapi-spec/issues>`__
-- Emailing to: `oneAPI@intel.com <mailto:oneAPI@intel.com>`__
+- Filing an issue in `Github <https://github.com/uxlfoundation/oneapi-spec/issues>`__

source/conf.py

@@ -86,7 +86,7 @@
 # documentation.
 #
 html_theme_options = {
-    'repository_url': 'https://github.com/oneapi-src/oneapi-spec',
+    'repository_url': 'https://github.com/uxlfoundation/oneapi-spec',
     'path_to_docs': 'source',
     'use_issues_button': True,
     'use_edit_page_button': True,

source/introduction.rst

@@ -79,42 +79,8 @@ and so on specified in `RFC 2119`_.
 Contribution Guidelines
 =======================
 
-This specification is a continuation of Intel’s decades-long history
-of working with standards groups and industry/academia initiatives
-such as The Khronos Group, to create and define specifications in an
-open and fair process to achieve interoperability and
-interchangeability. oneAPI is intended to be an open specification and
-we encourage you to help us make it better. Your feedback is optional,
-but to enable Intel to incorporate any feedback you may provide to
-this specification, and to further upstream your feedback to other
-standards bodies, including The Khronos Group SYCL specification,
-please submit your feedback under the terms and conditions below. Any
-contribution of your feedback to the oneAPI Specification does not
-prohibit you from also contributing your feedback directly to other
-standard bodies, including The Khronos Group under their respective
-submission policies.
-
-Contribute to the oneAPI Specification by opening issues in the oneAPI
-Specification `GitHub repository
-<https://github.com/oneapi-src/oneapi-spec>`__.
-
-Sign your work
---------------
-
-Please include a signed-off-by tag in every contribution of your
-feedback. By including a signed-off-by tag, you agree that: (a) you
-have a right to license your feedback to Intel; (b) Intel will be free
-to use, disclose, reproduce, modify, license, or otherwise distribute
-your feedback at its sole discretion without any obligations or
-restrictions of any kind, including without limitation, intellectual
-property rights or licensing obligations; and (c) your feedback will
-be public and that a record of your feedback may be maintained
-indefinitely.
-
-If you agree to the above, every contribution of your feedback must
-include the following line using your real name and email address:
-Signed-off-by: Joe Smith joe.smith@email.com
-
+See Contributing_.
 
 .. [*]: Other names and brands may be claimed as the property of others.
 .. _`RFC 2119`: https://tools.ietf.org/html/rfc2119
+.. _Contributing: https://github.com/uxlfoundation/CONTRIBUTING.rst