Description is
Actually I prefer to keep the LICENSE field in the recipe list, which is important for users to select recipes. For example, if users selected some commercial license recipes (e.x., ffmeg), they do need to have the information that the recipe is not for free license.
The question we asked ourselves when it came to select the table headings was: will sorting by the heading help developers find what they are looking for? Our assumption was that sorting by license will not particularly help developers find a certain recipe or package, at least it won't be as useful as sorting by name or group. You probably don't remember the license of the recipe you are looking for, but you might remember the name or which function it's related to (i.e. the group). Having said that, as long as there is enough space in the table, I am not opposed to displaying the license information. However, if adding the license column cuts the name or group values in the table, the license column will have to go. It's a question of establishing priorities when it comes to displaying information within the space we have available. Belen
The current layout in recipe selection is enough for displaying the name/license/group/included information.
Without cropping the cell values?
Yes, I think so. You can have a check at the recipe selection page.
Great, thanks!
Mark it as WONTFIX
Done