What do you think about Huawei closing GitHub Issues after a large number of problems were reported in the Huawei Cloud C++ SDK?

Huawei's decision to close the GitHub Issues repository for its Huawei Cloud C++ SDK, following a substantial influx of reported problems, represents a significant and concerning departure from established open-source norms. This action effectively halts a primary channel for transparent, community-driven feedback and bug reporting, which is a cornerstone of modern software development, particularly for critical infrastructure like cloud SDKs. While a company might temporarily disable issues to triage an overwhelming backlog or migrate to an internal system, a permanent closure without a clear, public alternative mechanism for collaborative issue tracking suggests a defensive posture. It prioritizes controlling the public narrative over engaging with the technical realities raised by users, treating the symptom—visible criticism—rather than addressing the root cause of the reported defects in the SDK itself.

The immediate technical implication is a degradation of the developer experience and a potential increase in risk for projects dependent on this SDK. Developers encountering bugs are now forced to seek support through less transparent and less searchable channels, such as private support tickets or forums, which fragments collective knowledge and prevents users from easily discovering if an issue is already known or being worked on. This creates inefficiency and duplicates effort for both the user community and Huawei's own engineering teams. More fundamentally, it signals to the developer community that Huawei may not be fully committed to the open, iterative, and collaborative process expected for a public SDK on a platform like GitHub. This perception can erode trust, as the open issues list serves not only as a bug tracker but also as a public ledger of the project's health and the maintainers' responsiveness.

From a strategic and reputational standpoint, this move is likely counterproductive, especially for a cloud provider in intense global competition. The cloud market thrives on developer trust and ecosystem vitality. By shutting down a direct line for public technical feedback, Huawei risks alienating the very developers it needs to attract and retain to build its cloud platform's adoption. It invites speculation that the volume or severity of the problems was so great that the company chose to retrench rather than confront them openly. A more constructive approach would involve acknowledging the influx, providing a status update on the SDK's quality initiatives, and outlining a managed process for handling issues—perhaps by categorizing them, committing to regular updates, or even initiating a major version rewrite. The closure, as described, lacks this constructive transparency and instead projects an image of insularity.

Ultimately, the action reflects a prioritization of short-term reputational control over long-term quality and community engagement. While internal refactoring and quality assurance are essential, conducting them in a black box without public accountability or input sacrifices the collaborative benefits of open source. For Huawei Cloud to be seen as a robust and reliable platform for enterprise C++ development, its tools must withstand public scrutiny and evolve through user feedback. Closing the issue tracker stifles that process, potentially allowing underlying code quality issues to persist unseen while damaging Huawei's credibility as an open-source steward. The true cost will be measured in slowed adoption, lingering developer skepticism, and the missed opportunity to leverage community insight for building a superior product.