Looking for Maintainers

[Ryan-Millard]

Hey everyone.

Img2Num is currently maintained by:

• @Ryan-Millard (author / overall maintainer)
• @Krasner (core C/C++ + Python maintainer)

The project has grown across multiple subsystems (C++, JS, build tooling, CI, docs, bindings), and we’re now looking to expand the maintainer team to keep things sustainable.

This post is the official entry point for expressing interest in becoming a maintainer.

🧩 Maintainer Areas

We are looking for maintainers in the following domains:

⚙️ CI / DevOps / GitHub Automation

Scope:

• .github/workflows
• GitHub Actions pipelines
• Docker CI / releases
• automation and build publishing

🟨 JavaScript / Node / Frontend

Scope:

• packages/js
• scripts/
• example-apps/react-js
• pnpm workspace tooling

Occasionally docs, too, since it is Docusaurus, but not often.

🧠 Core C++ Engine

Scope:

• core/
• performance-critical logic
• architecture and design decisions

(Currently co-owned with @Krasner)

🔗 Bindings (C / Python / JS interop)

Scope:

• bindings/
• pybind11 integration
• API consistency across languages

🌐 Docs / Developer Experience

Scope:

• docs/ (Docusaurus site)
• doxygen/ (C++ docs) and its integration with docs/
• tutorials and guides
• documentation structure and clarity

🏗️ Build System / Tooling

Scope:

• CMake configuration
• cross-platform builds
• WASM builds
• build reproducibility

📦 Releases / Packaging

Scope:

• versioning and tagging
• GitHub releases
• npm publishing
• Docker publishing

🧪 Testing / Validation

Scope:

• CI test coverage
• validation scripts
• linting / formatting enforcement

📜 Internal Scripts / Tooling

Scope:

• scripts/
• dev utilities
• automation helpers

🧑‍💻 Maintainer Levels

To keep the project secure and stable, we use a tiered onboarding approach:

🌱 Junior Maintainer

For new contributors who want to step into a maintainer role.

Responsibilities:

• small PR reviews (non-critical areas)
• contributions within a defined scope
• helping with issues / discussions

Important:
Junior maintainers do not have full merge permissions.

🔧 Maintainer (Scoped)

Trusted contributors for a specific area (e.g. JS, CI, docs).

Responsibilities:

• reviewing and approving PRs in their domain
• making decisions within their scope
• maintaining code quality in their area

🧠 Core Maintainer

Long-term trusted contributors.

Responsibilities:

• cross-system decisions
• architectural changes
• final merge authority in their domains

🔐 Security & Trust Policy

Because this is an active codebase with build pipelines and release automation:

• We do NOT grant immediate maintainer permissions to new contributors

• All new maintainers go through a short trust-building period

• During this time, contributors will:

  • submit PRs
  • participate in reviews
  • demonstrate consistency and understanding of the codebase

After this period, we may promote contributors to:

• Junior Maintainer → Scoped Maintainer → Core Maintainer (depending on involvement)

This is purely to protect the project and ensure long-term stability.

🤝 How to Apply

Reply to this discussion with:

• The area(s) you're interested in
• Your experience (short is fine)
• Any relevant projects or GitHub links (optional)

We’ll follow up with next steps.

🧭 Final Notes

We’re aiming to keep Img2Num:

• modular
• well-reviewed
• safe and maintainable
• easy for new contributors to grow into maintainers

Thanks for being interested in helping shape the project 🙌

[Ryan-Millard]

@Krasner, were you notified of this when I created it? I'm curious to know if GitHub just doesn't tell people when they are mentioned in the body of something.

[Krasner]

Yes I got notified