Bug 492379 - Request for Donation Improvements
Summary: Request for Donation Improvements
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Donation notification (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-29 18:58 UTC by Aaron Bockelie
Modified: 2024-08-30 22:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Bockelie 2024-08-29 18:58:01 UTC
### SUMMARY
Improvements for annual donation popup

To enhance the yearly donation notification feature, I propose the following possible refinements and additional configurations to make it more engaging and transparent for users. The goal is to foster a stronger connection between users and KDE, encouraging contributions by clearly demonstrating the results of their personal contribution.

### Proposed Feature Enhancements:

#### 1. **Additional Notification Options:**
   - **"What Do My Donations Do?" link**
     - **Functionality**: This button would provide users with an overview recent tangible features that have been released. This could be as simple as reading the RSS for kde.org/announcements or more. Clicking it would open a default web browser page detailing recent projects and initiatives funded by donations, such as new features in KDE Plasma, improvements in KDE applications, or community outreach efforts. This transparency helps reassure users that their contributions are making a tangible difference.
     - **Content Example**: "Your donations have recently helped us to develop [Feature X], improve [Application Y]."

   - **"Track My Donations" Button:**
     - **Functionality**: This feature allows users to connect their give.donorbox.org account directly within KDE. Once linked, instead of receiving a generic annual donation reminder, users would get a personalized notification. This notification would thank them for their previous donations and highlight the specific advancements their contributions helped achieve.
     - **Content Example**: "Thank you for your continued support! Your contributions for this quarter have helped us release [Feature Z], which was actively under development during your contribution!"

#### 2. **User Engagement Through Contribution Awareness:**
   - **Personalized Contribution Impact**: By linking their donorbox account, users could receive regular updates or a quarterly summary of how their donations are being used. This could include detailed reports, videos, or blogs about ongoing projects, further enhancing their connection to KDE.
   - **Monetary Contributions vs Technical**: For users who cannot code or contribute in technical ways, this system is a way to blend existing messaging on other ways to get involved, such as what is messaged at https://community.kde.org/Get_Involved. This is an excellent positive community message and it is valuable to equate the monetary donations with the hard technical work that the core KDE development team contributes.

#### 3. **Encouraging Donations with Positive Reinforcement:**
   - **Thank You Notifications**: Rather than just a yearly reminder to donate, users who have donated in the past would receive thank you notifications periodically, based on their notification settings, possibly somehow synced with their donor account. These notifications would include updates on what KDE has accomplished thanks to their support, as described above. This approach shifts the narrative from asking for donations to celebrating the impact of contributions.
   - **Community Recognition**: Consider adding a subtle, opt-in recognition feature where users who donate can choose to have their names listed on a public contributors page (https://kde.org/community/donations/previousdonations.php). This adds a social reward aspect to donating, making contributors feel more valued.

#### 4. **Enhanced Customization and Dismissal Options:**
   - **Customizable Notification Frequency**: Users could choose how often they receive updates about KDE’s progress and their donations’ impact, ranging from monthly to yearly, or opt-out entirely. This respects user preferences while keeping engaged users informed.
   - **Snooze or Remind Me Later**: If a user isn't ready to engage with the donation notification immediately, they could snooze it for a custom period (e.g., 1 month, 3 months) instead of just dismissing it for a year.

### Implementation Considerations:

- **Privacy and Security**: Ensure that connecting to donorbox.org and tracking donations is secure, with clear privacy policies in place to protect user data. If there is a way to store their donorbox.org identity abstracted, that would be helpful. I have not investigated how that platform functions.
- **User Interface Integration**: The additional buttons and options should be seamlessly integrated into the existing notification UI, maintaining KDE’s aesthetic and usability standards.
- **Backend Requirements**: Implementing features like donation tracking and personalized notifications will require backend support to fetch and display user-specific donation data.

### Conclusion:

These enhancement suggestions are intended to connect the yearly donation notification from a simple reminder into a tool for deeper user engagement, which KDE is already doing. By linking the concepts that already exist for transparency, personalized feedback, and multiple ways to contribute, KDE can build stronger relationships with its user base, encouraging ongoing support and involvement. This approach not only drives donations but also reinforces the value of every user’s contribution to the KDE ecosystem.
Comment 1 Nate Graham 2024-08-30 16:01:12 UTC
There are some great ideas here. I think some of them are feasible to implement. Will look into it.
Comment 2 Aaron Bockelie 2024-08-30 22:16:23 UTC
(In reply to Nate Graham from comment #1)
> There are some great ideas here. I think some of them are feasible to
> implement. Will look into it.

Great to hear! I'm not much of a real developer (I play one on "TV") so I'm one of those people that just set up a recurring donation. Given some limited instruction I'm happy to test changes out.