OK, I'll work on it.

Hi @jcvicelli,

How are things going for you on this? Do you need help with something?

hi @pingou, I already have a solution, I just haven't the time to implement
it, busy week!
On Aug 12, 2015 4:04 PM, pagure@pagure.io wrote:

pingou added a new comment to an issue you are following:
``
Hi @jcvicelli,

How are things going for you on this? Do you need help with something?
``

To reply, visit the link below or just reply to this email
https://pagure.io/pagure/issue/262

Cool, thanks for the update!

Btw, in your solution we should be sure to include pagination as we're thinking about using pagure for https://pkgs.fedoraproject.org and that has ~22k projects :)

So, it's just a draft, should I continue this way?

This is looking good!

Just a few details :

• the table should be larger,
• I think we can drop the id,
• I'd put the author and date at the end
• give more space to name (not title) and description.
• I'd hide the table if there are no entries
• I still think we shouldn't list the projects twice (on your list and on the full list) but we can do this in a different pull request.

Thanks for working on this!!

Now I'll need to add more fields as suggested by Kevin, like last activity / # commits / # open issues / # forks / # pull requests / etc
And also test if the pagination is working.

The other fields will be harder as it means getting content from git, so a lot of IO and I don't know how the perfs will then look like if there are many many projects on the instance

OK @pingou I've tested and the old pagination logic still works. I'm sending the patch with all I've done.

@jcvicelli, I was wondering if we would want to have a configuration key to set the front page to table vs card (card being the current layout).

What do you think?

@jcvicelli, btw, I see your patch is 0002, is there a 0001 as well?

no there is not, 0001 was wrong...
good idea, I'll work on it.

@ryanlerch What should we do about this ticket? Is this still something interesting?

@ryanlerch What should we do about this ticket? Is this still something interesting?

I think the split between showing your repos, and the browse makes finding repos a little better now. And we also have basic sorting on the browse repos too.

@kevin is this something you still are keen to see?

cheers,
ryanlerch

The sorting on browse definitely helps, it would be nice if it had a few more options though, like 'most recently active' or something.

I'm not set on the table view, I just thought it would be a way to see more whats available if you are just browsing around to see what projects to contribute to for example.

The other fields will be harder as it means getting content from git, so a lot of IO and I don't know how the perfs will then look like if there are many many projects on the instance

@pingou any thoughts on efficiently storing and getting this data for sorting? would adding and updating some fields to the projects table be the wrong way to go? e.g. "last_commit_date" and or "last activity_date"?

Something like # of forks might also be useful to sort on as well.

The last update was 6 years ago, no further requests, updates or actionable tasks since then, I'm going to close this issue for now to reduce our backlog.