The default sort of the meetings should display most recent meetings at the top

[ilieandriuta]

STEPS TO REPRODUCE

1. Go to Meetings Pro
2. Create several meetings with different Start Dates
3. Observe the sorting of the meetings on the Meetings homepage

EXPECTED RESULTS

The meetings should be sorted starting with the most recent meetings first (at the top), as it's a common use case, indicated also in #36.

ACTUAL RESULTS

The meetings are sorted with the most recent meetings at the bottom.

Environment: Windows 10 Pro 64-bit, Chrome 70, using a local instance of XWiki 10.9 on Oracle 11.2.

[lucaa]

So, let me understand @ignatescustefan , the fix for this issue reverted partially the fix for #36 , it changed the order of meetings to ascending by startDate?

As @acotiuga explained on #36 , we need to properly define what "most recent" means, otherwise we'll do these kind of reverts all the time.
For me (#36) , "most recent" means in the past, closest to the current moment.
However, since here we have this issue that a meeting may also be in the future, if I'd have to extend this interpretation of "most recent" to the future, I would say it has to mean a reverse chronological order, regardless of whether the meeting is in the future or in the past. This is also because I expect this application to be used mainly to store notes for meetings from the past and only rarely for having lots of meetings planned and not yet finished.
For this ticket, as far I understand, the usecase that was used was with only meetings in the future, and the interpretation that was given to "most recent" is "closest to the current date". This causes an unpleasant situation on a wiki where lots of meeting notes have accumulated, in which the first page of the table will display the oldest meeting notes, which makes little sense...

Otherwise put, the main usecase for the meeting application should be: many meetings in the past and rather little meetings in the future, even if, during a test, this usecase may not be so obvious...

[lucaa]

So, I re-read the commits and the code more attentively, and now I understand better: there is a new behaviour that was invented in order to somewhat satisfy this strange understanding of "recent" as a thing in the future. Note that it's best to explain functional behviour changes on the issue rather than in the pull request. As a user, I don't read pull requests but I do read issues.

So, if I understand correctly, it now works like this:

• by default, the table does not display all meetings but only the future ones, ordered ascending by start date, which means the first one that will occur will display first in the table . Just note that "meetings available for a year" as it appears in the message on the screen is a very difficult to understand concept (what is an "available meeting"? what makes a meeting "available for a year"?)
• if one wants to see all meetings, they need to click the "see all meetings" button, in which case they will see everything, as before, in reverse chronological order.

Given this:

Otherwise put, the main usecase for the meeting application should be: many meetings in the past and rather little meetings in the future, even if, during a test, this usecase may not be so obvious...

and the fact that:

• "meetings available for a year" is strange to understand and also raises the question of "why one year? why not one month? why not all meetings in the future?" (so it may turn out not the best either),
• users don't read texts on the screen to understand what that table is displaying and, more importantly, why it's not displaying everything,
• this homepage was intended as an index of the data, not as a smart "see my meetings agenda" thing, so it should list everything. Also, as far as I can think right now, there are not many applications that have a "smart index" not displaying everything by default,

I consider this ticket to be uselessly complicating the functioning of this application.
Can we revert it? Or at least change the default display to all meetings ("index") and have the "future" ones available with a button.

[silviamacovei]

My interpretation of “most recent” was also as reverse chronological order. It’s how I initially understood the ticket, thinking the attached image was the expected behavior. (BTW, it would be useful for attached images to explain whether they describe the current or the expected state.)
But after reading the comments here and on issue 36 I see how the expected behavior was interpreted in the opposite manner.

I also agree that the application is usually used mainly to log info about past meetings. If the app were used mostly to plan and have the meetings, it would make sense to only display current and future events and archive past meetings. But the main purpose of the app is to track past events and store old notes for future reference.

• 1 to display to all meetings by default and have the "future" ones available with a button.

WDYT @ilieandriuta @ignatescustefan @acotiuga @mflorea