@bbitsch
To reach the usability of Windows or even a car, there has to be a huge community of humans using the system and reporting their experience. I doubt, we have reach that yet.
I don’t think usability has to rely on a huge community of users. There was a time when Windows did not have a large user base. Improved usability can be achieved by small changes. As an example, ipFire includes this icon:

It appears on the Pakfire Configuration is a lot smaller in the WUI, and when my old eyes first saw it, I had no idea what it meant. All of the other icons are text based, but not this one. If this graphic icon was changed to say something like “Install Updates & Addons” it’s purpose would be self explanatory and consistent with the WUI style.
Blockquote The process of feature request should not be integrated into the wiki. …
You are probably right, but any other solution is likely to require a new website, back end development and a WUI. My suggestion was based on the need to minimise development and maintenance resources to implement a simple requirements management tool based on a registered user editable spreadsheet.
There is an opportunity here for the ipFire project. I suggested adding cost (hours effort) as one of the parameters to determine the ranking or priority for developers resources. There may be more than a few users out there who would consider paying €, $USD or £ to have their requirement developed ahead of others. This approach would make it far easier for companies, Govt. agencies and individuals to justify targeted donations to ipFire. Far more effective than a general call for donations.
The other benefit is to transition from developer-led to user-led development. In order to make that transition, the developers will need a good (not complex) requirements gathering system that they can trust.
Blockquote Development of a WUI and of an OS are two different parts of software engineering. Maybe there are some users of IPFire with knowledge in the first topic, which could join the development team. This demands moderation between the two branches, also.
WUI development appears to be non-existant for ipFire.
Without at least basic knowledge of networks systems you cannot setup and administer a system like IPFire. This includes basic knowledge of the underlying OS ( the real system, not just the graphical interface! ), this includes the CLI. This is true if development can’t set standards for the HW level and the BSP as Microsoft does.
Agreed. But simple routine tasks should be simple to do via the WUI. Not always true for ipFire. The CLI should be an option for advanced users, not a necessity for a user with basic needs.