Skip to content

Personal dashboard page #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JelteF opened this issue Feb 18, 2025 · 3 comments · Fixed by #51
Closed

Personal dashboard page #36

JelteF opened this issue Feb 18, 2025 · 3 comments · Fixed by #51
Assignees

Comments

@JelteF
Copy link
Collaborator

JelteF commented Feb 18, 2025

Peter Geoghegan mentioned this on the mailinglist:

It'd be nice if there was a way to see a list of open
patches that I am associated with in any way, either as an author or
as a reviewer (or as a committer). The list of patches would ideally
be organized into two groups: those in the open CF, and those in the
next CF.

I like "Useful links that you can use and bookmark", but I'd prefer if
there was only one link that I needed to bookmark. That is, I'd like
it if "Your entries in the current commitfest", "Your entries in the
open commitfest", and "Entries that you are reviewing in current
commitfest" were all merged into one dashboard view (that also
included "Entries that you are reviewing in the open commitfest").
Essentially, "patches that you're involved in in any capacity that
haven't already been closed out", organized along the same lines as
the existing links (every patch fitting into 1 or those 4 categories),
and presented to me as a single page of patches/items.

I think a personal dashboard page makes sense, needs some design and discussion on what should be on there though. But honestly anything is better than nothing at this point.

@destrex271
Copy link
Contributor

Image

This is a very rough layout of what I am thinking but essentially it targets the following:

  • A side panel where we can get an overview of the profile and stats like number of patches that the user has to review, number of patches that were committed that the user was involved in, number of patches authored by user, number of patches authored by user and ready to be committed etc etc..
  • The main panel uses the same view that we have for the commitfest view. The only change is that we are fetching the patches where the user has been involved in any capacity(author, reviewer, past reviewer, part of mail threads etc..). We can customize the filters that we provide in the committfest page according to these here

@JelteF
Copy link
Collaborator Author

JelteF commented Mar 2, 2025

@destrex271 thanks for the rough layout. For now I went with a much simpler initial version in #51. Basically it's just showing a list of open patches you're interested in for now.

@JelteF JelteF closed this as completed in #51 Mar 2, 2025
@JelteF JelteF closed this as completed in 2e6f028 Mar 2, 2025
@destrex271
Copy link
Contributor

@destrex271 thanks for the rough layout. For now I went with a much simpler initial version in #51. Basically it's just showing a list of open patches you're interested in for now.

Cool!

Is it ok if I build on that and this layout in a separate pr for a future release?

JelteF added a commit that referenced this issue Mar 17, 2025
The homepage was not showing a lot of useful information. It had a list
of mostly ancient commitfests, a search box, and a few links to more
useful pages. This revamps the homepage with an initial version of a
personalized dashboard. The dashboard shows patches that the user is
subscribed to, either because they are marked as an author or a
reviewer. We then try to group and sort these patches in an attempt to
let the user easily find the patches that require their attention.

Many things can likely be tweaked/improved. I think this first version
is already a huge improvement over the status quo, so I think it's worth
committing deploying this mostly as is and then iterating on it based on
feedback.

This is what it looks like:
![screenshot of
homepage](https://github.com/user-attachments/assets/6f464597-30f9-4f4b-9b98-17ac90b64b60)

Fixes #36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants