E4S-Project / E4S-Project/E4S-Project.github.io

Intel OneAPI licensing

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
6
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Hi,

I see E4S is redistributing Intel OneAPI compilers in containers:

https://hub.docker.com/layers/ecpe4s/e4s-oneapi/22.11/images/sha256-a3be067a792a948ddd4e45be7f29abb665eb61b2b9df2fcc68d73d74bd6954ea?context=explore

We would like to do the same (https://github.com/ACCESS-NRI/model_builder/issues/7) but I'm having trouble interpreting the Intel EULA. Does it allow this?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the Intel EULA and the referenced E4S OneAPI Docker Hub image, then compare the redistribution question with ACCESS-NRI/model_builder#7. Done means documenting a supported interpretation of whether these compilers may be redistributed in containers; no repository files or tests are identified in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.