Last month BuddyPress lead developer Mathieu Viet@imath quit WordPress . He no longer uses WordPress for his personal or commercial sites. [ https://imathi.eu/ ]. imath had been working on WordPress and BuddyPress for 12 years with a commit (code push to core) almost on a daily basis.
The reason he has mentioned is the ethics around WPEngine – Automatic saga, which left him demotivated. BuddyPress is a community driven project which run solely on motivation of its contributors. The contributors are not paid for contribution so ethics issue can become a major demotivation factor. Many contributors have now started an open letter against the proceeding : https://www.therepository.email/wordpress-contributors-and-community-leaders-call-for-governance-reform-in-rare-open-letter
Here is what RAY another co-founding BuddyPress member had to say on it :
The departure of a BuddyPress lead developer from the WordPress ecosystem could have significant implications for both the BuddyPress plugin itself and the broader WordPress community.
For BuddyPress which took a major directional shift last year with BP 12.0 update, the BP removed decade old code of loading templates which caused major issues with plugins. This visionary shift was supposed to be backed-up by new plugin implementation and ideas.
While the actual impact would depend on various factors, here are some of the potential consequences:
1. Slowdown in BuddyPress Development
- Feature Development and Bug Fixes: iMath was the only active developer in BuddyPress who was aware of all the bugs and fixes to the system. His leaving will cause delays or stagnation in terms of new feature development, bug fixes, and general maintenance.
- Leadership Gap: imath had a vision for BuddyPress and his departure would leave the project in a void. As the lead developer typically sets the direction for a project, their departure could leave a leadership void, which might make it harder for contributors to coordinate efforts, set priorities, and guide new features or changes.
- Community Trust: For users and developers who rely on BuddyPress for building online communities, this could lead to uncertainty about the future of the plugin. If the project loses momentum, it could affect the confidence in BuddyPress as a long-term solution.
2. Impact on BuddyPress Users
- Uncertainty for Active Users: Many WordPress site owners, particularly those with large, active community websites, rely heavily on BuddyPress for member management, profiles, groups, and social interaction features. If the plugin’s development slows, users may be concerned about its ongoing compatibility with new versions of WordPress.
- Security Risks: Without active development, the plugin might fall behind in addressing security vulnerabilities. WordPress and plugins are frequently targeted by hackers, and a delay in patching vulnerabilities could put sites at risk.
3. Shift in the WordPress Ecosystem
- Impact on WordPress Community Plugins: Since BuddyPress is a widely used plugin within the WordPress ecosystem, the departure of its lead developer might lead to greater fragmentation within the WordPress community, particularly in the social networking and community-building segment. Other community-driven projects like bbPress (forum software) might also be impacted as users and developers may reconsider their choice of tools for community sites.
- Rise of Alternatives: If BuddyPress stagnates, it opens the door for competitors or alternative solutions.
4. Effect on WordPress Itself
- Social Features on WordPress: BuddyPress provides a critical set of features for building social networks and community-focused websites. Without continued improvements or active maintenance of BuddyPress, users who need those capabilities may turn to other platforms or self-hosted solutions. WordPress may lose some ground in the social networking space.
- Impact on WordPress’s Reputation for Extensibility: WordPress is known for its wide array of plugins, including BuddyPress, which is integral to social networking features. A decline in BuddyPress development could affect WordPress’s reputation as a highly extensible platform for various use cases, especially community-focused websites.
6. Effect on the BuddyPress and WordPress Communities
- Community Impact: BuddyPress is not just a plugin but also a community-driven project. Its development has long been shaped by a collaborative open-source community. The departure of a lead developer could also affect the morale of contributors and volunteers, especially if the individual had been a key figure in fostering the community around BuddyPress.
- Reputation and Trust Issues: For many developers, the leadership of a project is a key factor in determining whether they will contribute to or rely on it. If the lead developer’s departure is not handled transparently, it could lead to a loss of trust in the project’s sustainability and direction.
7. Impact on WordPress Agencies and Freelancers
- Disruption for Agencies: Agencies and freelancers that specialize in building BuddyPress-based communities could see a drop in demand for new projects if clients perceive BuddyPress as an unstable or outdated solution. They might be forced to shift toward other technologies or platforms, requiring new skillsets and expertise.
- Reputation Concerns: Agencies that have heavily invested in BuddyPress-based solutions may need to find ways to reassure clients about the long-term stability of their projects. They may also need to find new ways to support and maintain existing BuddyPress-powered sites.
8. What Could Happen Next?
- Forking or New Leadership: BuddyPress could either be forked by other developers, or a new leadership team could emerge within the community to keep the project alive. A new development roadmap could potentially be laid out by the new maintainers.
- Integration with WordPress Core: There might be more pressure to integrate community-building features directly into WordPress Core, or to focus on making the WordPress platform itself better for community-driven sites.
The future is not rosy
The departure of the BuddyPress lead developer could create both challenges and opportunities for the project and the broader WordPress ecosystem. It could lead to stagnation in the development of BuddyPress, causing uncertainty for users and developers. However, it could also provide an opportunity for new leadership to emerge, potentially leading to new features, improvements, or better alternatives for community-driven WordPress sites.
In either case, it’s crucial for the WordPress community, the BuddyPress project, and its contributors to come together to navigate this transition effectively. Users and developers alike will need to stay informed about the future of BuddyPress and be prepared for potential changes.
How are other WordPress Community plugins ?
Talking about the other community plugins, BuddyBoss which is already a fork of BuddyPress was sold this year to Awesome Motive possibly due to declining business. Peepso decided to remove itself from WordPress.org as a retaliation to WordPress practices against WP Engine. UserPro the most popular community plugin is listed on sale since last year. Ultimate member is the only plugin in WordPress which seems to be doing well but often complaints about slowness.
What are we planning to do ?
We are already working on our SAAS project for over 1 year now as an alternate to BuddyPress. We expect it to be ready next year in January. This move will propel us to focus more resources towards SAAS as the future of BuddyPress and educational sites. If you are interested for a trial before release, please get in touch [email protected] / [email protected]