diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100644 index 0000000..e2dae09 --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1,2 @@ +# Existing visible maintainer team with repository maintain access. +* @uxlfoundation/sig-leaders diff --git a/.github/ISSUE_TEMPLATE/work-item.yml b/.github/ISSUE_TEMPLATE/work-item.yml new file mode 100644 index 0000000..f406e77 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/work-item.yml @@ -0,0 +1,29 @@ +name: Work item or documentation issue +description: Track a concrete foundation or Working Group task. +labels: [needs-triage] +body: + - type: textarea + id: problem + attributes: + label: Problem and affected area + description: Include the affected project, page or work package. + validations: + required: true + - type: textarea + id: evidence + attributes: + label: Evidence or reproduction steps + description: Link existing work, decisions or affected pages. + validations: + required: true + - type: textarea + id: completion + attributes: + label: Completion criteria + validations: + required: true + - type: input + id: owner + attributes: + label: Agreed owner or team to consult + description: Do not assign an owner without their agreement. diff --git a/.github/meeting-notes-template.rst b/.github/meeting-notes-template.rst new file mode 100644 index 0000000..4cc1998 --- /dev/null +++ b/.github/meeting-notes-template.rst @@ -0,0 +1,28 @@ +Meeting title +============= + +Date: YYYY-MM-DD + +Attendees +--------- + +Agenda +------ + +Discussion +---------- + +Decisions +--------- + +Record approved decisions separately from proposals and open questions. + +Actions +------- + +For each action, record the agreed owner, next step and target date or issue. + +Materials and recording +---------------------- + +Add presentation links and recording access details. Update the meeting index. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..ad526c8 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,13 @@ +## Change + +Describe the problem and resulting behavior. Link related issues or decisions. + +## Validation + +- [ ] Local documentation links checked. +- [ ] Meeting/SIG index updated where applicable. +- [ ] Relevant chair or maintainer identified for content review. + +## Decisions or follow-up + +Separate proposed decisions from approved ones; note any remaining owner action. diff --git a/.github/scripts/check_local_links.py b/.github/scripts/check_local_links.py new file mode 100644 index 0000000..00c3a78 --- /dev/null +++ b/.github/scripts/check_local_links.py @@ -0,0 +1,60 @@ +"""Check local file targets in Markdown and reStructuredText (not URL/anchors).""" + +from pathlib import Path +import posixpath +import re +import sys +from urllib.parse import unquote, urlsplit + +TARGETS = re.compile( + r"(?m)^\.\. _[^\n]+?:[ \t]+([^\n]+)$" + r"|<([^<>\n]+)>`_{1,2}" + r'|\]\((<[^>]+>|[^)\n]+)\)' + r"|(?m:^\[[^\]\n]+\]:[ \t]+([^\n]+)$)" +) + + +def check(root): + root = root.resolve() + entries = [p for p in root.rglob('*') if '.git' not in p.relative_to(root).parts] + paths = {p.relative_to(root).as_posix() for p in entries} + errors = [] + for source in entries: + if source.suffix.lower() not in {'.md', '.rst'} or not source.is_file(): + continue + content = source.read_text(encoding='utf-8') + for match in TARGETS.finditer(content): + target = next(g for g in match.groups() if g is not None).strip() + if target.startswith('<'): + target = target[1:target.index('>')] + else: + target = re.split(r'\s+[\"\']', target, maxsplit=1)[0] + if not target or target.startswith(('#', '//')): + continue + parsed = urlsplit(target) + if parsed.scheme: + continue + local = unquote(parsed.path) + if not local: + continue + base = root if local.startswith('/') else source.parent + candidate = (base / local.lstrip('/')).resolve() + try: + candidate.relative_to(root) + # Keep the written case: Windows resolve() can canonicalize it. + prefix = '' if local.startswith('/') else source.parent.relative_to(root).as_posix() + normalized = posixpath.normpath(posixpath.join(prefix, local.lstrip('/'))) + except ValueError: + normalized = None + if normalized not in paths and candidate != root: + line = content.count('\n', 0, match.start()) + 1 + errors.append(f'{source.relative_to(root).as_posix()}:{line}: missing local target: {target}') + return errors + + +if __name__ == '__main__': + errors = check(Path.cwd()) + for error in errors: + print(error) + print(f'Local documentation links: {len(errors)} error(s). External URLs and anchors are not checked.') + sys.exit(bool(errors)) diff --git a/.github/scripts/test_local_links.py b/.github/scripts/test_local_links.py new file mode 100644 index 0000000..dc9c8aa --- /dev/null +++ b/.github/scripts/test_local_links.py @@ -0,0 +1,35 @@ +from pathlib import Path +import tempfile +import unittest +from check_local_links import check + + +class LocalLinkTests(unittest.TestCase): + def test_local_targets_and_external_links(self): + with tempfile.TemporaryDirectory() as directory: + root = Path(directory) + (root / 'docs').mkdir() + (root / 'slides with spaces.pdf').touch() + (root / 'docs' / 'notes.rst').write_text( + '.. _slides: ../slides%20with%20spaces.pdf\n' + '`slides <../slides with spaces.pdf>`__\n' + '.. _site: https://example.org/missing\n', encoding='utf-8') + (root / 'README.md').write_text( + '[multi\nline](docs/notes.rst#agenda)\n' + '[slides]()\n' + '[root](/docs/notes.rst)\n' + '[anchor](#agenda)\n[mail](mailto:test@example.org)\n', encoding='utf-8') + self.assertEqual(check(root), []) + + def test_missing_case_mismatch_and_escape(self): + with tempfile.TemporaryDirectory() as directory: + root = Path(directory) + (root / 'note.rst').touch() + (root / 'README.md').write_text( + '[missing](missing.pdf)\n[case](NOTE.rst)\n' + '[outside](../outside.md)\n[reference]: missing.rst\n', encoding='utf-8') + self.assertEqual(len(check(root)), 4) + + +if __name__ == '__main__': + unittest.main() diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml new file mode 100644 index 0000000..6051795 --- /dev/null +++ b/.github/workflows/docs.yml @@ -0,0 +1,20 @@ +name: Documentation +on: + pull_request: + push: + branches: [main] +permissions: + contents: read +jobs: + local-links: + name: Local documentation links + runs-on: ubuntu-latest + timeout-minutes: 5 + steps: + - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4 + with: + persist-credentials: false + - name: Test link checker + run: python3 -m unittest discover -s .github/scripts -p 'test_*.py' + - name: Check local links + run: python3 .github/scripts/check_local_links.py diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..c18dd8d --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +__pycache__/ diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..1b83213 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,44 @@ +# Contributing + +Use this repository for foundation governance, SIG documentation and community infrastructure. +Use the [Working Group](https://github.com/uxlfoundation/open-source-working-group) +for cross-project work packages, and the relevant library repository for implementation bugs. + +## Issues and work packages + +Use an issue template to describe the problem, affected area, evidence and +completion criteria. Identify an owner when one has agreed to take the work. +Maintainers use `needs-triage` for items awaiting a decision and area labels for +routing. An old issue is not automatically obsolete: close it only with evidence +of completion, a duplicate reference or an explicit decision not to pursue it. +Reassign an open issue out of a closed milestone when agreeing its next target. + +## Documentation and meeting notes + +Make focused pull requests and explain what changed and how it was checked. +Use the [meeting-notes template](.github/meeting-notes-template.rst) for new notes. +Use YYYY-MM-DD in new filenames, update the relevant index, and check relative +links and presentation attachments. Preserve existing filenames and historical +decisions; correct broken links without rewriting the meeting's conclusions. +Link new large recordings from an approved stable host rather than adding video +binaries. State any membership requirement for recording access. + +Run `python .github/scripts/check_local_links.py` from the repository root. +The check validates local file targets in Markdown and reStructuredText; it does +not check external websites or section anchors. Public links and meeting content +also need a human review. + +## Review and repository maintenance + +The existing `@uxlfoundation/sig-leaders` team routes repository reviews through +CODEOWNERS. Changes to meeting decisions or leadership need the relevant chairs' +confirmation. Prefer one approving review and passing documentation checks before +merging; keep proposed changes separate from approved decisions. Administrators +retain an exception path for urgent maintenance and should document any exception +in the PR. Do not treat an automated link check as approval of meeting content. + +Use the existing foundation and project policies. This guide does not introduce +a new license or change governance or contribution terms. Ask foundation +operations to confirm applicable terms before importing third-party material. +Report security vulnerabilities through the affected project's private reporting +channel or security policy, rather than posting details in a public issue. diff --git a/README.md b/README.md index 552e0ac..96d662f 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ The Unified Acceleration (UXL) Foundation exists to define a standards-based, cross-architecture open specification for accelerated computing and to foster the open-source implementations of the specification. -More information can be found at http://www.uxlfoundation.org. +More information can be found at https://uxlfoundation.org. You can also find out more about our mission, projects and how to contribute in the [UXL Foundation Charter](/doc/uxl-foundation-charter.rst). @@ -15,13 +15,13 @@ projects that implement the oneAPI Specification. The community is invited to join the meetings, review the [oneAPI Specification](https://spec.oneapi.io), and read the information in this -repo. Contributions can be made by joining the Working Groups, Special +repo. Contributions can be made by joining the Working Group, Special Interest Groups (SIGs) or posting comments or questions as GitHub issues. General questions can go to this repo, and issues specific to parts of the specification can go to the [Specification -repo](https://github.com/oneapi-src/oneapi-spec). +repo](https://github.com/uxlfoundation/oneAPI-spec). -Sign up to the mailing lists for the Working Groups and Special Interest +Sign up to the mailing lists for the Working Group and Special Interest Groups (SIGs) [here](https://lists.uxlfoundation.org/groups). Join the [Slack @@ -42,12 +42,10 @@ Working Group The Working Group meets regularly to organize community proposals and contributions to the specification and open source projects. This group -defines work packages for areas of development and collaboration. Each group -has a GitHub repository linked below. +defines work packages for areas of development and collaboration. Its repository is linked below. * [Working Group](https://github.com/uxlfoundation/open-source-working-group) - This - group focuses on development of the open source projects that form part of - the foundation. + group coordinates the foundation's specifications and open source projects. Special Interest Groups (SIGs) ------------------------------ @@ -67,6 +65,11 @@ minutes can be found in the relevant folder in this repository. * [Hardware](/hardware) - This group covers topics related to the integration of hardware and how this is defined in the oneAPI specification. +Contributing +------------ + +See [CONTRIBUTING.md](CONTRIBUTING.md) for issue routing, meeting notes and review expectations. + Upcoming Events ------------- @@ -76,7 +79,7 @@ Calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/oneapi?view=lis Stay Informed ------------- -[Join the relevant mailing list to receive an invite for the Working Groups +[Join the relevant mailing list to receive an invite for the Working Group and SIGs](https://lists.uxlfoundation.org/g/main) [Contact us](mailto:membership@uxlfoundation.org) with any questions about membership. diff --git a/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst b/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst index 97f4b44..7be2fbe 100644 --- a/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2024-03-14-UXL-AI-SIG.rst @@ -49,7 +49,7 @@ Attendees Agenda - * Enabling oneDAL on ARM target Chandan Sharma (`slides `__) -* oneDNN overview and update Mourad Gouicem (`slides `__) +* oneDNN overview and update Mourad Gouicem (`slides `__) * Discussion (motivation, expectation, future topics) Question: Fujitsu extended oneDAL to use OpenBLAS library to enable ARM target. oneDAL uses private MKL interface. Will oneDAL use public MKL interface? @@ -69,4 +69,4 @@ Answer: Yes. oneDNN Graph is an official feature of oneDNN. oneDNN Graph API is Question: What does it take to optimize oneDNN to other targets? -Answer: There are three levels. The first approach is to map the API to external library (e.g. ARM backend relies on ACL, Nvidia backend relies on cuDNN/cuBLAS, ...), the second one is to add C++/SYCL implementations with targeted optimizations (e.g. RISC-V RVV optimized Matmul), and the third one is to add jitting capabilites and jit kernel generators (e.g. x64 support contributed by Intel and SVE support contributed by Fujitsu). +Answer: There are three levels. The first approach is to map the API to external library (e.g. ARM backend relies on ACL, Nvidia backend relies on cuDNN/cuBLAS, ...), the second one is to add C++/SYCL implementations with targeted optimizations (e.g. RISC-V RVV optimized Matmul), and the third one is to add jitting capabilites and jit kernel generators (e.g. x64 support contributed by Intel and SVE support contributed by Fujitsu). diff --git a/ai-and-scientific-computing/2024-10-24-UXL-AI-SIG.rst b/ai-and-scientific-computing/2024-10-24-UXL-AI-SIG.rst index e9d7bbc..20a78f4 100644 --- a/ai-and-scientific-computing/2024-10-24-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2024-10-24-UXL-AI-SIG.rst @@ -32,9 +32,9 @@ Attendees Agenda -“oneDNN vision” Mourad Gouicem, Intel (`slides `__) +“oneDNN vision” Mourad Gouicem, Intel (`slides `__) -“Adding Scikit-learn Intel extension to UXL” Nikolay Petrov, Intel (`slides `__) +“Adding Scikit-learn Intel extension to UXL” Nikolay Petrov, Intel (`slides `__) Question: As the uKernel API has specific block sizes, how should we write kernel for matrices that don’t fit these block dimensions, especially with fringe areas? Do we need new primitives for these cases? @@ -81,4 +81,4 @@ Question: Has there been any effort to work with scikit-learn developers to simplify plugin usage, perhaps by automatically loading plugins similar to TensorFlow’s approach? Answer: -Yes, discussions are ongoing with scikit-learn maintainers to explore backend integration for estimator acceleration. Though not yet implemented, there’s interest in creating a plugin API that could automatically load extensions. +Yes, discussions are ongoing with scikit-learn maintainers to explore backend integration for estimator acceleration. Though not yet implemented, there’s interest in creating a plugin API that could automatically load extensions. diff --git a/ai-and-scientific-computing/2025-3-6-UXL-AI-SIG.rst b/ai-and-scientific-computing/2025-3-6-UXL-AI-SIG.rst index d7f9d25..5d06a81 100644 --- a/ai-and-scientific-computing/2025-3-6-UXL-AI-SIG.rst +++ b/ai-and-scientific-computing/2025-3-6-UXL-AI-SIG.rst @@ -31,7 +31,7 @@ Attendees Agenda ====== -Extend OneDNN Operators/APIs for AI Chips Leping Wang, En Saho, (`slides `__) +Extend OneDNN Operators/APIs for AI Chips Leping Wang, En Saho, (`slides `__) AI use cases with oneDNN on Arm Ashok Bhat, (`slides `__) diff --git a/ai-and-scientific-computing/2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst b/ai-and-scientific-computing/2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst index 2aa6575..dbc3f2d 100644 --- a/ai-and-scientific-computing/2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst +++ b/ai-and-scientific-computing/2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst @@ -61,7 +61,7 @@ Summary ======= Overview ------------------ +-------- - This meeting featured two technical presentations on oneDNN optimizations and acceleration of scientific computing. - First session by Fujitsu team presented their work on AI for drug discovery using protein folding optimization with the oneDNN stack. @@ -70,40 +70,40 @@ Overview - The discussion included questions about integration approaches, performance implications for different architectures, and potential impacts on downstream frameworks like PyTorch and TensorFlow. Accelerating Scientific AI for Drug Discovery - Talk by Rakshith G B and Shreyas Shankar, Fujitsu ------------------ +------------------------------------------------------------------------------------------------- Title: Accelerating Scientific AI for Drug Discovery: OpenFold Optimization with oneDNN Abstract ------------------ +-------- - Protein structure prediction is transforming modern AI-driven drug discovery by enabling rapid understanding of protein folding functions and therapeutic targets. - This talk introduces OpenFold AI Surrogate Model and presents benchmark results with recent oneDNN-based optimizations, including JIT BRGEMM kernel enhancements. Discussion Highlights ------------------ +--------------------- - Rakshith explained how protein folding simulation has been accelerated from days or months to hours using modern AI models like AlphaFold and OpenFold, which predict 3D protein structures from 2D amino acid sequences. -- Fujitsu team conducted enablement, tuning and benchmark testing on ARM CPU, achieving execution time of 7.3 seconds for a 76-residue protein with 0.24 Å (Angstrom) accuracy, and achieved ~4x performance boost after optimizing OpenFold with nneDNN JIT BRGEMM kernel implementation in PyTorch. +- Fujitsu team conducted enablement, tuning and benchmark testing on ARM CPU, achieving execution time of 7.3 seconds for a 76-residue protein with 0.24 Å (Angstrom) accuracy, and achieved ~4x performance boost after optimizing OpenFold with oneDNN JIT BRGEMM kernel implementation in PyTorch. - Shreyas presented on the JIT BRGEMM kernel, explaining how just-in-time compilation using xbyak_aarch64 provides advantages over ahead-of-time compilation by enabling specialized code generation based on runtime conditions, dead code elimination, and better register allocation. - He detailed the BRGEMM (Batch Reduced GEMM) kernel implementation for ARM architecture, which performs batch reduced general matrix multiplication without storing intermediate results, resulting in approximately ~4x speedup for large matrices compared to the default implementation. - The work was conducted as part of AI Frameworks OSS Development, and Fujitsu continues to develop these low-level kernels for their upcoming FUJITSU-MONAKA 2nm ARM CPU processor launch in FY2027. oneDNN Stack Simplification on AArch64 using KleidiAI - Talk by Jonathan Deakin, Arm ------------------ +------------------------------------------------------------------------------------ Title: oneDNN Stack Simplification on AArch64 using KleidiAI Abstract ------------------ +-------- - We will discuss our active oneDNN RFC (`#5145 `__) which proposes replacing Compute Library (ACL) with Arm® KleidiAI™ for AArch64. - This change is proposed to simplify stack, bringing development and performance benefits. This session will cover a brief history of oneDNN on AArch64, explain our motivation for the change, and discuss questions and feedback. Discussion Highlights ------------------ +--------------------- - Jonathan presented on replacing ACL with KleidiAI in oneDNN for AArch64, explaining that this change would simplify the stack ad provide better framework integration. - The proposed approach involves integrating KleidiAI kernels directly into oneDNN rather than maintaining them as a separate library, which would eliminate the need for additional build steps and reduce complexity. diff --git a/ai-and-scientific-computing/README.rst b/ai-and-scientific-computing/README.rst index 10826dc..e7a6d0a 100644 --- a/ai-and-scientific-computing/README.rst +++ b/ai-and-scientific-computing/README.rst @@ -18,3 +18,19 @@ Archived meeting notes from oneAPI AI Tab meetings held under the oneAPI Community Forum can be found `here`_ .. _here: https://github.com/oneapi-src/oneAPI-tab/tree/main/ai + +Meeting notes +============= + +* `2026-06-25 <2026-6-25-UXL-AI-and-Scientific-Computing-SIG.rst>`__ +* `2026-04-23 <2026-4-23-UXL-AI-and-Scientific-Computing-SIG.rst>`__ +* `2026-03-05 <2026-3-5-UXL-AI-SIG.rst>`__ +* `2025-12-19 <2025-12-19-UXL-AI-SIG.rst>`__ +* `2025-09-04 <2025-9-4-UXL-AI-SIG.rst>`__ +* `2025-06-26 <2025-6-26-UXL-AI-SIG.rst>`__ +* `2025-03-06 <2025-3-6-UXL-AI-SIG.rst>`__ +* `2024-10-24 <2024-10-24-UXL-AI-SIG.rst>`__ +* `2024-09-12 <2024-09-12-UXL-AI-SIG.rst>`__ +* `2024-06-06 <2024-06-06-UXL-AI-SIG.rst>`__ +* `2024-03-14 <2024-03-14-UXL-AI-SIG.rst>`__ +* `2023-10-25 <2023-10-25-UXL-AI-SIG.rst>`__ diff --git a/doc/Meetings.rst b/doc/Meetings.rst index 60c273a..0a4f443 100644 --- a/doc/Meetings.rst +++ b/doc/Meetings.rst @@ -38,7 +38,9 @@ several reasons: * People can decide if they want to attend the meeting and potentially invite others -To send an agenda, ... +Send the agenda to the group mailing list linked from its repository page. +Include the meeting date, time zone, agenda topics and the calendar link. +Coordinate calendar or host changes with the group chairs or foundation operations. Recording a Meeting ------------------- @@ -53,8 +55,10 @@ There are many benefits to recording a meeting There are also tools for summarizing meeting transcripts. This is useful for the note taker as well as attendees. -Keep in mind that the recording will be available to everyone. If you have -private information, you should not record the meeting. +Check the recording access settings with the host before the meeting and tell +attendees that it is being recorded. Recordings may require membership and an +openprofile account; do not assume that every recording is publicly accessible. +Do not include private information in a public meeting record. There are two ways to record a meeting: @@ -77,6 +81,14 @@ There are two ways to record a meeting: Publishing Meeting Minutes -------------------------- +Use the meeting-notes template linked from CONTRIBUTING.md. Save new notes with +a YYYY-MM-DD filename in the relevant group directory and add them to its index. +Include decisions, action owners, presentation links and recording access details. +Submit a pull request for review by the relevant group chairs before publication. +Preserve existing filenames and historical records when correcting links. +For new large recordings, link to an approved stable video host rather than +committing the video file to Git. + .. _`UXL Groups`: https://lists.uxlfoundation.org/groups .. _`Open Source WG Calendar`: https://lists.uxlfoundation.org/g/open-source-wg/calendar# .. _`My Meetings`: https://openprofile.dev/my-meetings diff --git a/doc/README.rst b/doc/README.rst index 1496735..d66807a 100644 --- a/doc/README.rst +++ b/doc/README.rst @@ -7,13 +7,15 @@ Documentation related to infrastructure for UXL. `UXL Foundation Charter`_ Outlines the foundation projects and how to contribute `UXL Goals 2025`_ - The goals set for the UXL Foundation in 2025 + Historical goals for 2025; not a statement of current-year commitments `UXL GitHub`_ GitHub Actions, repositories and organizations `UXL Slack`_ Managing Slack channels `Web Hosting`_ Hosting project web sites +`Meetings`_ + Attending, hosting and publishing meeting records `Get Started`_ How to get started with the UXL Foundation projects @@ -23,3 +25,5 @@ Documentation related to infrastructure for UXL. .. _`UXL Slack`: uxl-slack.rst .. _`Web Hosting`: web-hosting.rst .. _`Get Started`: get-started.rst + +.. _`Meetings`: Meetings.rst diff --git a/doc/uxl-slack.rst b/doc/uxl-slack.rst index 5376d16..94a5a02 100644 --- a/doc/uxl-slack.rst +++ b/doc/uxl-slack.rst @@ -24,4 +24,4 @@ Getting the Token The token is connected with a slack app. You need to be signed in to uxlfoundation workspace to see it, otherwise you will not see the app. -.. _`Slack Action`: https://github.com/uxlfoundation/spec-working-group/blob/main/.github/workflows/slack-pr.yaml +.. _`Slack Action`: https://github.com/uxlfoundation/open-source-working-group/blob/main/.github/workflows/slack-pr.yaml diff --git a/language/README.rst b/language/README.rst index c2c73db..08fe676 100644 --- a/language/README.rst +++ b/language/README.rst @@ -82,13 +82,13 @@ Hereafter, you will find slides, recordings, and additional materials from the m :2023-11-07: | SYCL-Graphs: A Progress Update | Ewan Crawford, Ben Tracy, Maxime France-Pillois (Codeplay Software), Pablo Reble, Julian Miller (Intel) - | `slides `__ - `demo video `__ + | `slides `__ + `demo video `__ :2023-09-19: | SYCL Extension Proposal for PIM/PNM | Hyesun Hong (Samsung) - | `slides `__ + | `slides `__ Archived meeting notes from meetings held under the oneAPI diff --git a/steering-committee/README.rst b/steering-committee/README.rst index b5b99bc..41828e5 100644 --- a/steering-committee/README.rst +++ b/steering-committee/README.rst @@ -10,6 +10,8 @@ outputs from the Working Groups. Minutes from the Steering Committee meetings are made available in this folder. +`23rd October 2025 <2025-10-23-UXL-Steering-Committee.rst>`_ + `11th September 2025 <2025-09-11-UXL-Steering-Committee.rst>`_ `28th August 2025 <2025-08-28-UXL-Steering-Committee.rst>`_ @@ -62,9 +64,9 @@ Minutes from the Steering Committee meetings are made available in this folder. `27th June 2024 <2024-06-27-UXL-Steering-Committee.rst>`_ -`13th June 2024 <2024-06-13-Steering-Committee.rst>`_ +`13th June 2024 <2024-06-13-UXL-Steering-Committee.rst>`_ -`30th May 2024 <2024-05-30-Steering-Committee.rst>`_ +`30th May 2024 <2024-05-30-UXL-Steering-Committee.rst>`_ `23rd May 2024 <2024-05-23-UXL-Steering-Committee.rst>`_