Hi, One of the new features of the upcoming aurweb release is a dashboard which will be displayed in place of the regular home page after login. Right now, it includes * a list of flagged packages the logged in user (co-)maintains, * a list of package requests affecting the logged in user, * the list of packages the logged in user maintains and * the list of packages the logged in user co-maintains. You can already test the new feature under [1]. Note that you will need to ignore the warning your browser might show because the aur-dev subdomain is not part of our SSL/TLS certificate (and least with Firefox, this is not easily possible, because of HSTS; Chromium seems to work, though). What are your thoughts on this? Are there any other suggestions for useful things to display on that page? Regards and have a nice Sunday, Lukas [1] https://aur-dev.archlinux.org/
On 02/12/2017 09:56 AM, Lukas Fleischer wrote:
Hi,
One of the new features of the upcoming aurweb release is a dashboard which will be displayed in place of the regular home page after login. Right now, it includes
* a list of flagged packages the logged in user (co-)maintains, * a list of package requests affecting the logged in user, * the list of packages the logged in user maintains and * the list of packages the logged in user co-maintains.
You can already test the new feature under [1]. Note that you will need to ignore the warning your browser might show because the aur-dev subdomain is not part of our SSL/TLS certificate (and least with Firefox, this is not easily possible, because of HSTS; Chromium seems to work, though).
That is sorta problematic, and I am actually a bit frightened that Chrome still hasn't fixed this policy bug. HSTS pretty much exists as a red flag that something is deeply wrong on a website that purports to hold to high standards; allowing users to simply click through the warning kind of defeats the "strict" in STS. Since the aur-dev subdomain does apparently get used on occasion, can you see about getting that added to the certificate? (I have just mentioned it on #archlinux-devops.)
What are your thoughts on this? Are there any other suggestions for useful things to display on that page?
I'll be happy to trial it (I was waiting for this release eagerly) just as soon as I can access it... -- Eli Schwartz
Hi Lukas, the dashboard looks really useful. Only one question: Are old requests dismissed? Or will they stay forever? To me, it looks unnecessary to keep them, and I would really appreciate if they were dismissed after they were accepted some time ago (like 6 months) to keep the list clean. Regards Janne On 02/12/2017 03:56 PM, Lukas Fleischer wrote:
Hi,
One of the new features of the upcoming aurweb release is a dashboard which will be displayed in place of the regular home page after login. Right now, it includes
* a list of flagged packages the logged in user (co-)maintains, * a list of package requests affecting the logged in user, * the list of packages the logged in user maintains and * the list of packages the logged in user co-maintains.
You can already test the new feature under [1]. Note that you will need to ignore the warning your browser might show because the aur-dev subdomain is not part of our SSL/TLS certificate (and least with Firefox, this is not easily possible, because of HSTS; Chromium seems to work, though).
What are your thoughts on this? Are there any other suggestions for useful things to display on that page?
Regards and have a nice Sunday, Lukas
On 02/12/2017 10:17 AM, Eli Schwartz wrote:
On 02/12/2017 09:56 AM, Lukas Fleischer wrote:
Hi,
One of the new features of the upcoming aurweb release is a dashboard which will be displayed in place of the regular home page after login. Right now, it includes
* a list of flagged packages the logged in user (co-)maintains, * a list of package requests affecting the logged in user, * the list of packages the logged in user maintains and * the list of packages the logged in user co-maintains.
You can already test the new feature under [1]. Note that you will need to ignore the warning your browser might show because the aur-dev subdomain is not part of our SSL/TLS certificate (and least with Firefox, this is not easily possible, because of HSTS; Chromium seems to work, though).
That is sorta problematic, and I am actually a bit frightened that Chrome still hasn't fixed this policy bug. HSTS pretty much exists as a red flag that something is deeply wrong on a website that purports to hold to high standards; allowing users to simply click through the warning kind of defeats the "strict" in STS.
Okay, Bluewind just fixed the cert and I am on... -- Eli Schwartz
On Sun, 12 Feb 2017 at 16:26:55, Janne Heß via aur-dev wrote:
Only one question: Are old requests dismissed? Or will they stay forever? To me, it looks unnecessary to keep them, and I would really appreciate if they were dismissed after they were accepted some time ago (like 6 months) to keep the list clean.
Currently, requests stay on the list forever. I agree that it would be useful to hide requests once closed for a while, though. Unfortunately, we do not store a time stamp of the date/time a request was closed which leaves us with two options: 1. Hide a requests if it has been closed *and* was created a certain amount of time ago. 2. Add a time stamp when the request status changes (i.e. a request is closed). Hide all closed requests where this new time stamp either dates back a certain number of days or is unset. Regards, Lukas
On Sun, 2017-02-12 at 17:02 +0100, Lukas Fleischer wrote:
On Sun, 12 Feb 2017 at 16:26:55, Janne Heß via aur-dev wrote:
Only one question: Are old requests dismissed? Or will they stay forever? To me, it looks unnecessary to keep them, and I would really appreciate if they were dismissed after they were accepted some time ago (like 6 months) to keep the list clean.
Currently, requests stay on the list forever. I agree that it would be useful to hide requests once closed for a while, though. Unfortunately, we do not store a time stamp of the date/time a request was closed which leaves us with two options:
1. Hide a requests if it has been closed *and* was created a certain amount of time ago.
2. Add a time stamp when the request status changes (i.e. a request is closed). Hide all closed requests where this new time stamp either dates back a certain number of days or is unset.
Regards, Lukas
I would be in favor of #1 simply because it would require less code and no added information to the database. It wouldn't be likely that there are any open requests that would be affected by a change like this (or that anyone would even care). Mark Weiman
On 02/12/2017 11:02 AM, Lukas Fleischer wrote:
On Sun, 12 Feb 2017 at 16:26:55, Janne Heß via aur-dev wrote:
Only one question: Are old requests dismissed? Or will they stay forever? To me, it looks unnecessary to keep them, and I would really appreciate if they were dismissed after they were accepted some time ago (like 6 months) to keep the list clean.
Currently, requests stay on the list forever. I agree that it would be useful to hide requests once closed for a while, though. Unfortunately, we do not store a time stamp of the date/time a request was closed which leaves us with two options:
1. Hide a requests if it has been closed *and* was created a certain amount of time ago.
2. Add a time stamp when the request status changes (i.e. a request is closed). Hide all closed requests where this new time stamp either dates back a certain number of days or is unset.
Regards, Lukas
So I saw the patches in pu to hide 6-month-old requests that have been resolved, and looking at the dashboard some old requests have disappeared. However, I also cannot see the recently-closed deletion request for firefox-dev (PRQ #7448, filed 2/07/2017), which was accepted, but then restored by the maintainer -- could that be confusing things? Also, two other requests that were accepted today, still list themselves as "pending". Is this supposed to happen??? -- Eli Schwartz
On Wed, 15 Feb 2017 at 21:58:28, Eli Schwartz via aur-dev wrote:
So I saw the patches in pu to hide 6-month-old requests that have been resolved, and looking at the dashboard some old requests have disappeared.
However, I also cannot see the recently-closed deletion request for firefox-dev (PRQ #7448, filed 2/07/2017), which was accepted, but then restored by the maintainer -- could that be confusing things? Also, two other requests that were accepted today, still list themselves as "pending".
Is this supposed to happen???
The setup at aur-dev.archlinux.org currently uses a separate database which I synced with the official one a couple of days ago. Regards, Lukas
participants (4)
-
Eli Schwartz
-
Janne Heß
-
Lukas Fleischer
-
Mark Weiman