The person who keeps the tool: reviews and merges (27 passages, no note) the pull requests (31 passages, no note), cuts the releases, holds the licence inventory (4 passages, no note) and the security contact, and decides on a design (4 passages, no note) change after the discussion it starts with. A maintainer's own small change may be merged by its author (note: Author) once the pipeline (note: Pipeline) is green; a story is always reviewed by someone else.
Maintainer
Properties3
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapMaintainer
Neighbourhood map Maintainer
Distance1 hop
27 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ReleaseProcessis assigned to6
- ReleaseTermis related to6
- PipelineTermis related to2
- AuthorRoleis related to4
- Contract import scope reviewMeetingis documented by1
- Twin resources reviewMeetingis documented by1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.