[aur-dev] Notification System Overhaul
Hello all, The current notification system for the AUR is lacking in features and isn't too pretty on the code side of things. Before I try and finalize the code I have, I wanted to lay out what I was planning for some feedback. Right now the AUR only allows for notifications when a user adds a comment. I would like users to have access to notifications for the following package actions: - New comments on packages - Package updates - Package adoption/orphaning - Package deletion/merging I think having the ability to select those 4 types of notifications brings a lot more flexibility while not being overly complicated. As for the AUR web interface changes, the package details page would feature a link to modify that specific package's notifications. The page would feature a list of all potential types of notifications the user can subscribe to with a check box next to each option. The user can then select all/some/none of the notifications for that specific package. On the backend side of things, swiftmailer seems to be a decent choice for sending the notifications. It is actively developed, has all the features the AUR would really need, and has a nice interface on the programming side of things. All the notification code mixed in with package functions and the like could be ripped out allowing for easier modification down the road. Ideally the following bugs should be closed after everything is implemented: FS#15412 - Send a notification when a package is orphaned or adopted FS#19948 - Add whether or not I'm the maintainer to the aur-notify email su FS#27687 - Merging packages does not transfer the notify list. FS#30109 - email notification upon package update FS#31850 - Send notification e-mails in preferred user language FS#31851 - Overhaul e-mail notification system FS#34843 - Make bugs/AUR messages more visible Does anyone have anything major they would like to see out of the notification system? Is there anything anyone disagrees with? Regards, Jason
On 04/24/2013 06:30 PM, canyonknight wrote:
Hello all,
The current notification system for the AUR is lacking in features and isn't too pretty on the code side of things. Before I try and finalize the code I have, I wanted to lay out what I was planning for some feedback.
Right now the AUR only allows for notifications when a user adds a comment. I would like users to have access to notifications for the following package actions: - New comments on packages - Package updates - Package adoption/orphaning - Package deletion/merging
I think having the ability to select those 4 types of notifications brings a lot more flexibility while not being overly complicated.
As for the AUR web interface changes, the package details page would feature a link to modify that specific package's notifications. The page would feature a list of all potential types of notifications the user can subscribe to with a check box next to each option. The user can then select all/some/none of the notifications for that specific package.
On the backend side of things, swiftmailer seems to be a decent choice for sending the notifications. It is actively developed, has all the features the AUR would really need, and has a nice interface on the programming side of things. All the notification code mixed in with package functions and the like could be ripped out allowing for easier modification down the road.
Ideally the following bugs should be closed after everything is implemented: FS#15412 - Send a notification when a package is orphaned or adopted FS#19948 - Add whether or not I'm the maintainer to the aur-notify email su FS#27687 - Merging packages does not transfer the notify list. FS#30109 - email notification upon package update FS#31850 - Send notification e-mails in preferred user language FS#31851 - Overhaul e-mail notification system FS#34843 - Make bugs/AUR messages more visible
Does anyone have anything major they would like to see out of the notification system? Is there anything anyone disagrees with?
Regards,
Jason Is there any reason to notify for adoptions? I don't get the benefit, and it's just more clutter from my POV.
On 04/24/2013 07:25 PM, Limao Luo wrote:
On 04/24/2013 06:30 PM, canyonknight wrote:
Hello all,
The current notification system for the AUR is lacking in features and isn't too pretty on the code side of things. Before I try and finalize the code I have, I wanted to lay out what I was planning for some feedback.
Right now the AUR only allows for notifications when a user adds a comment. I would like users to have access to notifications for the following package actions: - New comments on packages - Package updates - Package adoption/orphaning - Package deletion/merging
I think having the ability to select those 4 types of notifications brings a lot more flexibility while not being overly complicated.
As for the AUR web interface changes, the package details page would feature a link to modify that specific package's notifications. The page would feature a list of all potential types of notifications the user can subscribe to with a check box next to each option. The user can then select all/some/none of the notifications for that specific package.
On the backend side of things, swiftmailer seems to be a decent choice for sending the notifications. It is actively developed, has all the features the AUR would really need, and has a nice interface on the programming side of things. All the notification code mixed in with package functions and the like could be ripped out allowing for easier modification down the road.
Ideally the following bugs should be closed after everything is implemented: FS#15412 - Send a notification when a package is orphaned or adopted FS#19948 - Add whether or not I'm the maintainer to the aur-notify email su FS#27687 - Merging packages does not transfer the notify list. FS#30109 - email notification upon package update FS#31850 - Send notification e-mails in preferred user language FS#31851 - Overhaul e-mail notification system FS#34843 - Make bugs/AUR messages more visible
Does anyone have anything major they would like to see out of the notification system? Is there anything anyone disagrees with?
Regards,
Jason Is there any reason to notify for adoptions? I don't get the benefit, and it's just more clutter from my POV. Whoops, misread. I didn't realize you could turn it off. Ignore my noise, sorry.
On more thing, there should be a "in-reply-to" field in each message's header, these fieldes should be the same for the some message thread to make gmail like system properly thread them. 2013/4/25 Limao Luo <luolimao@gmail.com>:
On 04/24/2013 07:25 PM, Limao Luo wrote:
On 04/24/2013 06:30 PM, canyonknight wrote:
Hello all,
The current notification system for the AUR is lacking in features and isn't too pretty on the code side of things. Before I try and finalize the code I have, I wanted to lay out what I was planning for some feedback.
Right now the AUR only allows for notifications when a user adds a comment. I would like users to have access to notifications for the following package actions: - New comments on packages - Package updates - Package adoption/orphaning - Package deletion/merging
I think having the ability to select those 4 types of notifications brings a lot more flexibility while not being overly complicated.
As for the AUR web interface changes, the package details page would feature a link to modify that specific package's notifications. The page would feature a list of all potential types of notifications the user can subscribe to with a check box next to each option. The user can then select all/some/none of the notifications for that specific package.
On the backend side of things, swiftmailer seems to be a decent choice for sending the notifications. It is actively developed, has all the features the AUR would really need, and has a nice interface on the programming side of things. All the notification code mixed in with package functions and the like could be ripped out allowing for easier modification down the road.
Ideally the following bugs should be closed after everything is implemented: FS#15412 - Send a notification when a package is orphaned or adopted FS#19948 - Add whether or not I'm the maintainer to the aur-notify email su FS#27687 - Merging packages does not transfer the notify list. FS#30109 - email notification upon package update FS#31850 - Send notification e-mails in preferred user language FS#31851 - Overhaul e-mail notification system FS#34843 - Make bugs/AUR messages more visible
Does anyone have anything major they would like to see out of the notification system? Is there anything anyone disagrees with?
Regards,
Jason
Is there any reason to notify for adoptions? I don't get the benefit, and it's just more clutter from my POV.
Whoops, misread. I didn't realize you could turn it off. Ignore my noise, sorry.
On Tue, May 7, 2013 at 10:19 PM, 郑文辉(Techlive Zheng) <techlivezheng@gmail.com> wrote:
On more thing, there should be a "in-reply-to" field in each message's header, these fieldes should be the same for the some message thread to make gmail like system properly thread them.
Can you add a feature request on the bugtracker [1]? I don't want to lose track of that request. Thanks, Jason [1] https://bugs.archlinux.org/index/proj2
participants (3)
-
canyonknight
-
Limao Luo
-
郑文辉(Techlive Zheng)