Browsing through the MUI-classes available with MOS1.4
and on Aminet, I came to the question of which of all those
similar classes should be choosen for any given task.

Some of them are probraly abandoned, or in the control
of devs who will never even consider supporting MorphOS.
Others are surely full of bugs which may go unnoticed by
a beginner in MUI-developing.

So how about someone sorting all available classes in certain categories:

a) The MOS-core-team has access to the sources.
This should apply to all those found in mossys:classes/MUI.

b) MOS-native version does exist.

c) only 68k but stable.

d) hostile developer

e) abandoned

f) pile of s****

Also a quick run-down of the accompining licences and
their demands would be welcomed.

@Kronos

I had asked about doing this exact same thing several times over the years, even before becomeing a MOSser myself. The most important directory one can have on MorphOS is the SYS:Classes/MUI, so there will be a "safe" place to put 68k mui libs.

Now back to your question. We have a FAQ moderator, and I am supportive of this. (I remember many system crashes because I was stuck using some beta of a betterstring.mcc, as required by YAM at the time). Let's see what we can come up with.. :)