Skip to content

Contributing patches

Tom Tucker edited this page Jan 14, 2020 · 4 revisions

Contributing source code patches or new files/features to LDMS

Licenses

Patches (bug fixes, minor refactoring) to existing files are accepted on the condition that they are provided to the project under the same license as the patched file(s).

LDMS is open source and includes a variety of 3rd party dependencies libraries under compatible licenses. Contribution of new plugins or other files are accepted on the condition that they document their open-source license and mark contributed files correspondingly.

Mechanics

Patches to the latest GA release (tag OVIS-4.3.3 as of Jan 7 2020) should be constructed as follows:

  • fork the repository.
  • create your patch branch based on branch OVIS-4.
  • push your patch to your github fork.
  • create a pull request for the OVIS-4 branch.

Patches to the development branch (master as of Jan 7 2020) should be constructed as follows:

  • fork the repository.
  • create your patch branch based on branch master(?).
  • push your patch to your github fork.
  • create a pull request.

Main

LDMSCON

Tutorials are available at the conference websites

D/SOS Documentation

LDMS v4 Documentation

Basic

Configurations

Features & Functionalities

Working Examples

Development

Reference Docs

Building

Cray Specific
RPMs
  • Coming soon!

Adding to the code base

Testing

Misc

Man Pages

  • Man pages currently not posted, but they are available in the source and build

LDMS Documentation (v3 branches)

V3 has been deprecated and will be removed soon

Basic

Reference Docs

Building

General
Cray Specific

Configuring

Running

  • Running

Tutorial

Clone this wiki locally