Call for contributors & maintainers

[wesleycho]

This issue is to denote the status of UI Bootstrap, outline the team’s intentions for the future, and to allow comment from the community.

Currently, the UI Bootstrap team has mostly focused on the Angular 2+ successor, ng-bootstrap, in large part due to the rapid maturation of Angular 2 as a framework and the needs of the Angular community for a robust UI framework on top of Bootstrap for Angular 2. Unfortunately, this has resulted in the thinning of resources available for continued development of UI Bootstrap, a largely mature framework, and alongside Angular Material & Ionic, amongst the most mature and widely used UI frameworks in the Angular ecosystem and in the front-end web ecosystem as a whole.

In addition, many changes have happened in the team’s lives over the past year, including @Foxandxss joining the Angular docs team for development of the Angular 2+ documentation, @icfantv joining the Spinnaker team at Netflix, and myself being promoted to a lead engineering role. All of us, as well as @deeg, are currently using Angular 2 at our jobs in some capacity. @pkozlowski-opensource is currently actively leading the ng-bootstrap development as part of his company’s work, as well as continued involvement as a core member of the Angular team.

With our current manpower, we are shifting to a maintenance mode for the framework, as we cannot manage all of our obligations along with managing the behemoth that is UI Bootstrap. This is a call for the community to step up and assist us in this period of transition, and help take on the maintenance and/or feature development of this library if the community wishes for active development to continue. Otherwise, the most I personally can guarantee is that I will assist in trying to tackle some regressions that I have caused in some major work I tackled as part of the 2.0.0 release, but I will largely shift to a mentor role for anyone who would like to take ownership of the stewardship of the library, and continue to review & merge in fixes & non-disruptive features, as well as release them.

We thank all of the users who use the library, and have found & fixed bugs, as well as helped shape the library to what it is today. The community has been pretty awesome through the past couple of years, and hopefully this continues as ng-bootstrap matures!

[RomainLK]

Thanks for your hard work on this library. I have been using for years and it has greatly helped me.

Sadly I couldn't make the jump to Angular 2 and still depends on this. Until today, I thought that it was still maintained and I don't think I'm alone in this case. Could an update to the frontpage on Github reflect the current state of this project?

[zacronos]

This issue is currently on page 5 out of 11 pages of open issues, and has been off page 1 for over 8 months. Worse, the project status notice at the top of the README currently says "this project is considered feature-complete and is no longer being maintained". The way that reads, it sounds like the current maintainers don't think there is a need for bug or documentation fixes, and strongly implies you are NOT in fact seeking any additional contributors/maintainers.

If you're serious about looking for contributors and maintainers to take over the project, I strongly suggest the following 2 changes:

• revise the project status notice in the README to state clearly that there IS a need for maintenance and bugfixes, and that you are seeking experienced OSS contributors/maintainers;
  maybe even put a link to this issue so that anyone interested can easily figure out how to speak up.
• a similar notice should be added to https://angular-ui.github.io/bootstrap/, since that probably gets some visibility the github README does not

Without at least doing those things, I think the project has about a one in a million chance of being taken over by someone.