@icfantv I humbly offer some constructive criticism, which I hope does not come across as harsh.

TL;DR: Acknowledge that the current situation isn't ideal, revise the project status notice in the README to include a call for contributors and maintainers, and put a call for contributors and maintainers on https://angular-ui.github.io/bootstrap/ as well.

The optics of the current situation, fair or not, paint the picture that you (the current maintainers) are not terribly interested in handing off this project or seeing bugs get fixed. Giving you the benefit of the doubt, I assume that's not actually what you want, so let me explain why it looks that way.

On the one hand, you are saying that you want to be very discriminating about who you add as a contributor/maintainer. This makes sense, and I'm sure is rooted in the desire for this project to continue to succeed. You don't want quality and community support to fall off because of poor leadership. I get that, and I get why you want to be careful.

On the other hand, the result is that the project has had a long period without active leadership or progress. Plus, the community has had no way to gauge how long it will take before the someone else is allowed to take leadership and start making progress again. That's bad for the project too.

The fact that your responses here don't acknowledge the downside of having no active leadership or progress implies (whether true or not) that you don't understand that downside. It would help a lot with appearances if you simply said something like "We realize the current situation is not ideal and would very much like to see this project flourish under someone else's leadership.", especially when discussing your standards for adding someone as a contributor. For instance, it would have provided an entirely different context if you had said that and then "However," before continuing with "for us to add anyone as a contributor...".

I see the call for contributors and maintainers from back in January, but please realize that right now that issue is at the very end of page 5 out of 11 pages of open issues. Unless someone is actually looking for that or just happens to get lucky with a search term, no one will see it. Based on the dates on the subsequent open issues, that issue got bumped off page 1 over 8 months ago, so it's been out of easy sight for quite a while. Even worse, the project status notice at the top of the README says "this project is considered feature-complete and is no longer being maintained". The way that reads, it sounds like you (the current maintainers) don't think there is even a need for bug or documentation fixes, and strongly implies you are NOT in fact seeking any additional contributors/maintainers. This creates the appearance, fair or not, that you're either unaware that there is room for bugfixes and other improvements, or that you just don't care whether or not the project gets them. And that appearance is what leads to calls for project forks, like this one.

I strongly suggest someone revise the project status notice 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 that January issue so that anyone interested can easily speak up. Those things should also be added to https://angular-ui.github.io/bootstrap/, since that probably gets some visibility the github page does not. It would go a long way toward improving appearances, not to mention improving your chances of having someone step up to take over the project.

I am 100% willing to flesh out and PR the README changes I just suggested, if you think it will actually get reviewed and merged.

Anybody continuous his own branch? I can join to develop. #6658

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions