Been using KDE + HiDPI + X11 for close to 5 years now, not a blurry font to be found.

If the developers’ wants and needs don’t intersect with a given user, there is no way forward for that user, community manager or not.

I suspect the small size of the dev team and the general nature of an OSS project means there aren’t swarms of people around volunteering to be community managers.

Small projects your sway with the project is directly proportional to your ability to submit pull requests. It’s just a sad fact that it’s easier to say “I wish we had feature X” vs. “Here is a pull request that implements feature X”.

At least with OSS you are getting what you paid for (nothing!), vs commercial companies where you pay for the software and they STILL ignore you.

Even “Why don’t you open an issue on our source tracker” will often effectively shut down suggestions from less tech savvy newcomers.

How should developers handle feature requests? Keep in mind there is a need for the whole team to see the suggestion and it’s also good to have a place to gather feedback and further discuss.

In the year 2057, human civilization had made significant strides in technological advancements that transformed their way of living. Computers were no longer just machines but extensions of one’s mind, and programming languages became a fundamental part of society. A prominent figure within this world was Vincent, a passionate programmer who swore by his beloved text editor Vi.

Meanwhile, in another galaxy far away, an advanced alien race called Zorblaxx, discovered Earth during a cosmic journey. With their keen interest in studying intelligent life forms, they intercepted a data stream containing the source code for Emacs. They immediately fell in love with its simplicity and user-friendliness. From that point onwards, the entire Zorblaxx race began using it as their primary tool for coding.

The first contact between humans and Zorblaxx occurred when a spaceship piloted by a group of fearless astronauts encountered a fleet of alien vessels. The initial meeting was cordial, and both species shared their knowledge of the cosmos. However, when humans revealed they used Vi, the Zorblaxx responded with disdain. They claimed that the Vi editor lacked the basic functionality that Emacs provided.

This dispute grew beyond petty differences over software preference. Debates erupted amongst developers worldwide. Some advocated for Vi’s efficiency while others preached the power of Emacs. Passions ran high, turning what could have been a friendly argument into a worldwide conflict.

Political leaders took notice and saw an opportunity to rally support for their respective countries. With the rise of nationalistic sentiments, humanity split into two factions: Team Vi and Team Emacs. Nations aligned themselves, and soon war broke out.

As the violence escalated, Vincent knew there had to be another way. He realized that both sides had something valuable to offer one another, and that a healthy collaboration would lead to better results. He developed a new text editor called Vim, combining the best features of both Vi and Emacs.

With Vim demonstrating the benefits of unity, both human factions united, joining forces against the invading Zorblaxx. In this unforeseen twist, the two races found themselves fighting side by side, bonding through their love for programming and shared vision for progress.

The battle raged on for months, but in the end, humanity emerged victorious. Faced with a common enemy, they learned to embrace diversity and to see past their differences. The same spirit was adopted by the Zorblaxx race, leading them to adopt Vim as their primary editor. A new era of peace and cooperation began between the two civilizations, now connected by technology and their mutual passion for programming.