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:
- Use
angular-split in your professional projects.
- Have experience with Angular build tools and package maintenance.
- 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.
Call for Maintainers: Keeping
angular-splitfuture-proofHi everyone,
I and @SanderElias had the privilege of maintaining
angular-splitfor 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-splitremains a stable, long-term solution for the ecosystem, we are looking for new maintainers to help steer the project forwardWe 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:
Who are we looking for?
You don't need to be the original author to be effective here. If you:
angular-splitin your professional projects....then you are exactly the kind of maintainer we need.
Interested?
If you want to help ensure
angular-splitstays a reliable resource for everyone, please leave a comment on this issue. I’m happy to discuss the current pipeline and onboarding process.