-
Notifications
You must be signed in to change notification settings - Fork 1
Proposal 1
Benjamin Allan edited this page Nov 26, 2019
·
3 revisions
This documents a process for creating change proposals. This document is not prescriptive, but intended to be helpful. Proposals are not needed for bug fixes, but are desired to document significant feature changes. This page is intended to reflect the discussion on process held at LDMSCON 2019. Errors and omissions shall be corrected as the community evolves the process.
- Create an issue in the issue tracker describing what problem needs addressing.
- Gather community input on what others may need in the same topic area and what hidden constraints may exist.
- Identify the version(s) of specific tools (e.g. ldms v5) to which the change is proposed.
- Create a wiki page (Proposal X) with the next successive proposal number X.
- Document in that page (preferably as a community activity) or in related pages
- (Background if needed; be concise and reference/create other pages for details.)
- Requirements and constraints
- Possible solutions
- The merits and demerits of the alternatives, preferably based on examples and (where needed) prototype implementations.
- When appropriate, the agreed solution, implementation team, review/test team, and expected release time/version.
- Home
- Search
- Feature Overview
- LDMS Data Facilitates Analysis
- Contributing patches
- User Group Meeting Notes - BiWeekly!
- Publications
- News - now in Discussions
- Mailing Lists
- Help
Tutorials are available at the conference websites
- Coming soon!
- Testing Overview
- Test Plans & Documentation: ldms-test
- Man pages currently not posted, but they are available in the source and build
V3 has been deprecated and will be removed soon
- Configuring
- Configuration Considerations
- Running