Skip to content

Team Structure

Version: Arctyk ITSM v0.6.0+
Last Updated: January 2026

This page outlines the Arctyk ITSM team structure, roles, and responsibilities.

Team Roles

Core Maintainers

Responsibilities:

  • Review and merge pull requests
  • Set technical direction and architecture
  • Manage releases and versioning
  • Triage issues and feature requests
  • Mentor contributors

Current Maintainers:

Contributors

Responsibilities:

  • Submit bug fixes and feature implementations
  • Improve documentation
  • Write tests
  • Participate in code reviews
  • Help answer questions from users

How to Become a Contributor:

  1. Make your first contribution
  2. Continue contributing quality pull requests
  3. Engage positively with the community
  4. Help review others' contributions

Community Members

Responsibilities:

  • Use Arctyk ITSM and provide feedback
  • Report bugs and suggest features
  • Help other users in Discord
  • Share knowledge and use cases

Decision-Making Process

Minor Changes

  • Bug fixes, documentation updates, and small improvements can be merged by any maintainer after one approval

Major Changes

  • New features, architectural changes, and breaking changes require:
  • Proposal and discussion (GitHub Issue or Discussion)
  • Technical design review
  • Approval from core maintainers
  • Comprehensive tests and documentation

Emergency Fixes

  • Critical security issues or production bugs can be merged immediately by maintainers with post-merge review

Communication Channels

GitHub

  • Issues: Bug reports and feature requests
  • Pull Requests: Code changes and reviews
  • Discussions: General questions and ideas

Discord

  • Real-time chat
  • Quick questions and help
  • Community building

Documentation

  • This site is the source of truth for technical information
  • Keep documentation up-to-date with code changes

Working Together

Code of Conduct

  • Be respectful and inclusive
  • Provide constructive feedback
  • Assume good intent
  • Help others learn and grow

Best Practices

  • Communicate early and often
  • Ask for help when stuck
  • Share knowledge through documentation
  • Celebrate team wins

Team Ceremonies

Code Reviews

  • All code changes require review before merge
  • Reviews should be timely (within 48 hours)
  • Use reviews as learning opportunities
  • Be thorough but kind

Release Planning

  • Releases follow semantic versioning
  • Release notes document all changes
  • Migration guides provided for breaking changes

Growth Paths

From Community Member to Contributor

  1. Start using Arctyk ITSM
  2. Report bugs with detailed information
  3. Submit documentation improvements
  4. Fix small bugs
  5. Implement features

From Contributor to Maintainer

  1. Consistent, quality contributions over time
  2. Deep understanding of codebase
  3. Help review others' pull requests
  4. Participate in architecture discussions
  5. Invitation from current maintainers

Resources