Components

Revision as of 11:57, 18 December 2015 by Hinerm (talk | contribs) (Add development template)

Template:Development

A software component is a program, such as a plugin, or a library of reusable functions. Components are typically designed to work together, and combined to form a software application such as ImageJ.

This web site documents lots of software components—and in particular, many ImageJ plugins. Each component's page features an informational sidebar. This page describes the meaning and purpose behind the sections of that sidebar.

Development status

Development status conveys what to expect regarding a component's future.

Unstable Project is under heavy development, with unstable API undergoing iterations of refinement. Typically, these components are either unreleased, or versioned at 0.x.
Active New features are being actively developed. API breakages are kept as limited as possible.
Stable No new features are under development. API is stable.
Obsolete The project is discontinued.

Support status

Support status indicates the level to which the team responds to questions and issue reports.

Active Someone will respond to questions on community channels, and addresses issue reports in the project's issue tracker. A best effort is made to fix reported bugs within a reasonable time frame.
Partial Someone will respond to questions on community channels, as well as to issue reports in the project's issue tracker. But reported bugs may not be addressed in a timely manner.
Minimal There is at least one person pledged to the project in some capacity, but not all roles are filled. Response time to questions and issue reports may be protracted.
None No one is pledged to support the project. Questions and issue reports may be ignored.

Team

The team is the group of people with responsibility for the component. The roles below describe the different ways people are pledged to help. Individuals may fill more than one role.

Founder Created the project. Does not imply any current participation or responsibility.
Lead Has decision-making authority: timing of releases, inclusion of features, etc.
Developer Adds new features or enhancements.
Debugger Fixes bugs. Can be assigned open issues to solve.
Reviewer Reviews patch submissions.
Support Responds to questions and issue reports. Keeps the issue tracker organized.
Maintainer Merges patch submissions. Cuts releases.
Contributor Contributed code to the project. Does not imply any current participation or responsibility.