-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compliance with xSDK v0.3 policies #172
Comments
Some comments:
|
aprokop
changed the title
Compliance with xSDK policies (as of version 0.3)
Compliance with xSDK v0.3 policies
Dec 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The xSDK draft community policies are available here.
As of draft version 0.3 (as of December 2016), these policies are:
options
users and does not require the purchase of commercial software.
communicators that are provided to it and not use directly MPI_COMM_WORLD.
standard Linux distributions, GNU, Clang, vendor compilers, and target machines 4 at ALCF, NERSC, OLCF.
team; mode of contact may be by email or a website.
regarding system resources and settings.
version number of the software.
name space.
publicly available), where the development version of the package is available.
installing, building, and linking against an outside copy of that software.
/include/ and /lib/, respectively.
default).
Bitbucket, where the development version of the package is available.
propagating/returning error conditions/exceptions and provide an API for changing the behavior.
they are no longer needed.
dependencies so that any other package or executable linking to the package knows to include these dependencies when linking.
The text was updated successfully, but these errors were encountered: