Skip to content
Branch: master
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
103 lines (73 sloc) 3.93 KB

2/Flux Licensing and Collaboration Guidelines

The Flux framework is a family of projects used to build site-customized resource management systems for High Performance Computing (HPC) data centers. This document specifies licensing and collaboration guidelines for Flux projects.

  • Name:

  • Editor: Jim Garlick <>

  • State: raw


The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.


A Flux project is defined as software which implements a resource manager function, or is otherwise tightly coupled to the resource manager or its communications framework. Flux projects are expected to have contributors spanning academic institutions, government laboratories, companies, and individuals.

Our licensing and collaboration guidelines must balance the following goals:

  • Encourage participation in the Flux community by all interested parties.

  • Ensure that the Flux community remains healthy and active by welcoming contributions, vetting changes in the open, collectivizing ownership, and distributing responsibility.

  • Allow Flux projects to leverage a large body of open source, including from the HPC ecosystem. [1]

  • Ensure that end users have full source code to their particular Flux system to maximize their ability to self-support and obtain help from the Flux community.

  • Ensure that successful Flux systems are fully replicatable and redistributable across platforms and sites.

  • Facilitate the use of Flux and its programming interfaces by external projects such as applications, application runtimes, and tools, that are distributed under a wide variety of open source and commercial licenses.


Collaboration Model for Flux Projects

  • Flux projects SHALL adopt the Collective Code Construction Contract (C4.1) described in Flux RFC 1.

  • It is RECOMMENDED that Flux projects be hosted under the Github flux-framework organization, including use of the Github tracker as outlined in C4.1.

  • It is RECOMMENDED that Flux projects be discussed on the Flux discussion list <>.

License for Flux Projects

  • Copyright for a particular Flux project SHALL be held jointly by the contributors to that project.

  • Flux projects SHALL NOT require a legal document such as a contributor license agreement or copyright assignment document to be signed by contributors.

  • Copyright for each source code module MAY be held by its authors.

  • All source code contributed to a Flux project SHALL include a copyright notice that declares the copyright holders and the license under which the source code may be copied, for example:

/* Copyright 2014 Lawrence Livermore National Security, LLC
 * This file is part of the Flux resource manager framework.
 * For details, see
 * SPDX-License-Identifier: LGPL-3.0
  • The SPDX license shorthand is RECOMMENDED. [2]

  • New contributors MAY add themselves to the project’s AUTHORS file, using the pull request process described in RFC 1.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.