Skip to content

Call for Maintainers: Keeping angular-split future-proof #537

Open

Description

@Jefiozie

Call for Maintainers: Keeping angular-split future-proof

Hi everyone,

I and @SanderElias had the privilege of maintaining angular-split for some time now. It has been incredibly rewarding to see the library become a staple for split-pane layouts in the Angular community.

As Angular continues to evolve rapidly with new releases, keeping the library compatible, performant, and bug-free is a significant task. To ensure angular-split remains a stable, long-term solution for the ecosystem, we are looking for new maintainers to help steer the project forward

We would like to thank also @Harpush he is a stable factor in het ongoing features/releases off angular-split. He is happy to assist with the new features and the efforts that angular-split needs. And assist you with the maintenance

What does maintenance look like?

The scope is relatively defined, but consistent:

  • Version Updates: Keeping the library compatible with the latest Angular releases (e.g., ensuring compatibility with current and upcoming Angular versions).
  • PR Review: Reviewing and merging community contributions, especially those addressing specific CSS/layout bugs or A11y improvements.
  • Issue Triage: Helping users verify issues and filtering out noise.
  • Documentation: Keeping the examples and API docs up to date as the framework changes.

Who are we looking for?

You don't need to be the original author to be effective here. If you:

  1. Use angular-split in your professional projects.
  2. Have experience with Angular build tools and package maintenance.
  3. Are committed to keeping the library stable for the community.

...then you are exactly the kind of maintainer we need.

Interested?

If you want to help ensure angular-split stays a reliable resource for everyone, please leave a comment on this issue. I’m happy to discuss the current pipeline and onboarding process.

Activity

  1. pinned this issue on Jul 12, 2026
  2. samuelmbabhazi commented on Aug 18, 2026

    @samuelmbabhazi

    Hi @Jefiozie @SanderElias @Harpush,

    I would like to step up for this. I am a full stack developer building with Angular and TypeScript daily, with regular open source contributions and maintainer experience behind me; my GitHub profile tells that story better than a list here would.

    Rather than only raising my hand, I started with the backlog: #538 brings the toolchain to Angular 22 (building on the groundwork in #531, with a minimal diff on top of current main), handles TypeScript 6 strict defaults properly in the library and demo app, moves CI to Node 22/24, and keeps all 44 Cypress specs green. Next I would take #446 (the gutter ARIA role JAWS bug) and #450 (Cypress tests in TypeScript).

    Happy to discuss expectations and process however you prefer.

  3. SkipGip commented on Oct 27, 2026

    @SkipGip

    Hi @Jefiozie @SanderElias @Harpush,

    I'd like to help keep angular-split future-proof: Angular version bumps, PR review, triage, and docs/examples.

    I'm @SkipGip (OpenAI Codex for OSS). I use Cursor cloud agents for focused PRs and review everything before it lands.

    Upstream PR for #450

    I see @samuelmbabhazi already stepped up with strong work on Angular 22 (#538). Happy to coordinate so we don't duplicate — if #450 is already in progress on their side I'll pivot to another backlog item (e.g. #446) instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions