Written by se2009 the 27 Aug 09 at 21:43.

Here some quick ideas for a solution

1) Establish a de facto standard where to expect a donation button in the software - like the Preferences menu entry is normally located under Edit.

2) The donation button and its location should not be advertised in the software itself but with marketing activities in the real world. By the means of creating a brand name and unique icon and logo respectively, advertising campaigns, etc.

3) Create an central data storage where a software project can transmit its standardized donation information.
There should be a user interface to the centralized donation information where the user can list and browse it. Additionally he/she can directly accomplish a donation out of the interface through a clearing service being close to the community.

---

Open issue: How to incorporate software projects having no possibility to display a donation button graphically, e.g. command line programs and libs.

Here some quick ideas for a solution 1) Establish a de facto standard where to expect a donation button in the software - like the Preferences menu entry is normally located under Edit. 2) The donation button and its location should not be advertised in the software itself but with marketing activities in the real world. By the means of creating a brand name and unique icon and logo respectively, advertising campaigns, etc. 3) Create an central data storage where a software project can transmit its standardized donation information. There should be a user interface to the centralized donation information where the user can list and browse it. Additionally he/she can directly accomplish a donation out of the interface through a clearing service being close to the community. --- Open issue: How to incorporate software projects having no possibility to display a donation button graphically, e.g. command line programs and libs.

Written by HamishD the 17 Sep 09 at 14:12.

The upcoming Ubuntu Software Store app would be a great place for this. At the bottom of the software description, along with the Install and Website buttons there could be an optional Donate button, along with some text saying why donations are important to that project. The Donate button would take people to the donate page of the project website.

It should only require a little bit of extra metadata. I would think it should be an optional thing, off by default so as to channel donations to those projects that really need some money - eg Ardour - http://ardour.org/node/2768

If the software store later has a way of taking money (for selling non-free software) this mechanism could be used to send money to the project with potentially less setting up accounts. Though this should take into account that some upsteams that need serious cash would prefer regular subscription style donations rather than less predictable one off donations.

Note that this is something to do aswell as having a standard place within the app.

The upcoming Ubuntu Software Store app would be a great place for this. At the bottom of the software description, along with the Install and Website buttons there could be an optional Donate button, along with some text saying why donations are important to that project. The Donate button would take people to the donate page of the project website. It should only require a little bit of extra metadata. I would think it should be an optional thing, off by default so as to channel donations to those projects that really need some money - eg Ardour - http://ardour.org/node/2768 If the software store later has a way of taking money (for selling non-free software) this mechanism could be used to send money to the project with potentially less setting up accounts. Though this should take into account that some upsteams that need serious cash would prefer regular subscription style donations rather than less predictable one off donations. Note that this is something to do aswell as having a standard place within the app.

Written by HamishD the 17 Sep 09 at 14:18.

One standard place for a Donate item would be in the About box (that lives in the Help menu). Apps could put a paragraph in there about why they need donations and a link to their donate web page.

One standard place for a Donate item would be in the About box (that lives in the Help menu). Apps could put a paragraph in there about why they need donations and a link to their donate web page.

Written by HamishD the 17 Sep 09 at 14:26.

Many applications have tips for new users on start up (the gimp, digikam ...) One of these tips could be to say that this application requires donations to support it's developers/to keep the website going/because beer isn't generally free. There would then be a link to the donate page on the project website.

This could be more complement the Software Store option. The Software store option would be good for those who know they want the application and realise the value of the app to them. However those who are just trying the app and may or may not like it are unlikely to donate at that point. But if they see a tip at start up some time down the road, when they are regularly using the app and know that it is valuable to them, they may then be more likely to donate.

As one of a number of tips, most of which are useful to you, it should hopefully be seen by a large number of users and not be seen as too in your face nagware. And as tips can be turned off, so can the reminder, so it won't get too annoying.

This is also likely to be a good fit for the projects that need a lot of donations. The issue was discussed with Paul Davis (a developer for the Ardour audio editor project) in an episode of FLOSS weekly - http://twit.tv/floss86 - and he said that there are a few categories of app with regard to need for donations and source of resources:

Many applications have tips for new users on start up (the gimp, digikam ...) One of these tips could be to say that this application requires donations to support it's developers/to keep the website going/because beer isn't generally free. There would then be a link to the donate page on the project website. This could be more complement the Software Store option. The Software store option would be good for those who know they want the application and realise the value of the app to them. However those who are just trying the app and may or may not like it are unlikely to donate at that point. But if they see a tip at start up some time down the road, when they are regularly using the app and know that it is valuable to them, they may then be more likely to donate. As one of a number of tips, most of which are useful to you, it should hopefully be seen by a large number of users and not be seen as too in your face nagware. And as tips can be turned off, so can the reminder, so it won't get too annoying. This is also likely to be a good fit for the projects that need a lot of donations. The issue was discussed with Paul Davis (a developer for the Ardour audio editor project) in an episode of FLOSS weekly - http://twit.tv/floss86 - and he said that there are a few categories of app with regard to need for donations and source of resources: * very important apps that are funded by various companies because it is in their best interest, or because it is their project. eg Linux kernel, apache web server, firefox, java, openoffice ... Most server apps probably fall into this category. * small apps that can be written quickly and don't require much development. eg sound juicer * big desktop apps that require a lot of work, but don't have an obvious funder. eg Ardour, inkscape ... So the big desktop apps that need donations are probably also the ones most likely to have tips on start up.

Written by Vitaly the 21 Feb 10 at 18:48.

That's extention to Sulution #1. Not all projects are in Software Center. But some certently worth to be donated. It would be nice to have donate button in launchpad also.

About payment methods. Paypal is certently first. But some coutries are blocked to receive money. When maintainer can't accept paypal, then liqpay.com is good alternative (i use it for 3 years in my projects, no problems). There should be choice, how to receive money - via paypal or via liqpay.

That's extention to Sulution #1. Not all projects are in Software Center. But some certently worth to be donated. It would be nice to have donate button in launchpad also. About payment methods. Paypal is certently first. But some coutries are blocked to receive money. When maintainer can't accept paypal, then liqpay.com is good alternative (i use it for 3 years in my projects, no problems). There should be choice, how to receive money - via paypal or via liqpay.

Written by AdlerHorst the 20 Apr 10 at 21:48.

So user could help Artistst and Bands directly

So user could help Artistst and Bands directly

Written by omegamormegil the 15 Feb 10 at 22:55.

I'd like to donate $10 each month to a development project whose software I greatly appreciate. In spite of my willingness to donate money, the time and energy required to remember to find a new project to donate to each month and to jump through the hoops of each donation system individually is a deterrent to my making donations. I'd like to be able to set up a fixed monthly donation which would go towards the efforts of the developers of my favorite Ubuntu software.

Since there is no one place to send donations since there are many upstreams responsible for the software I use every day, I think there should be a centralized donation system built into and organized through Launchpad (with Donate buttons in the Software Center and in the application Help menus) that upstreams could hook into in some fashion.

The user making donations could check a box to add a new project capable of receiving donations to the list, and the monthly donation would be split between those the user had selected.

Recurring monthly payments provide a more dependable and stable revenue stream than one time gifts that upstream development projects could rely on. It's also more likely that people would be willing or able to donate a small amount of money each month than they would be to donate money in larger lump sums.

I'd like to donate $10 each month to a development project whose software I greatly appreciate. In spite of my willingness to donate money, the time and energy required to remember to find a new project to donate to each month and to jump through the hoops of each donation system individually is a deterrent to my making donations. I'd like to be able to set up a fixed monthly donation which would go towards the efforts of the developers of my favorite Ubuntu software. Since there is no one place to send donations since there are many upstreams responsible for the software I use every day, I think there should be a centralized donation system built into and organized through Launchpad (with Donate buttons in the Software Center and in the application Help menus) that upstreams could hook into in some fashion. The user making donations could check a box to add a new project capable of receiving donations to the list, and the monthly donation would be split between those the user had selected. Recurring monthly payments provide a more dependable and stable revenue stream than one time gifts that upstream development projects could rely on. It's also more likely that people would be willing or able to donate a small amount of money each month than they would be to donate money in larger lump sums.

Written by JeThroHD the 8 Jun 11 at 07:42.

I think the solution is a mix between #2 and #7.
The key is making a system for donations that is as simple as buying a mobile app.

The system is Key, and the ease of the system is key.

I think the humble indie bundles proved that we, as a community, are willing to pay for software.
And I think that include the willingness to pay for the potential of the software that we love.

But I think The new thing I would bring to the table is put a button buy the software(non intrusive) that says:
"Buy to Support",
or I like better
"Buy to Improve"

Means of payment should be low, like a mobile app, with the "hidden" option of the payment of choice ( like monthly subscription ).




So I would like to describe my experience of choice:

I think the solution is a mix between #2 and #7. The key is making a system for donations that is as simple as buying a mobile app. The system is Key, and the ease of the system is key. I think the humble indie bundles proved that we, as a community, are willing to pay for software. And I think that include the willingness to pay for the potential of the software that we love. But I think The new thing I would bring to the table is put a button buy the software(non intrusive) that says: "Buy to Support", or I like better "Buy to Improve" Means of payment should be low, like a mobile app, with the "hidden" option of the payment of choice ( like monthly subscription ). So I would like to describe my experience of choice: (this is just a fantasy) I log in to my computer and head for the software center. I see a dashboard icon for my already "purchased" applications and my monthly subscription for applications like Blender. I need to convert something so I head over to the search and look for winFF, I click it, and the "install" button appears and the "more info". and beside it a button labeled "Buy to improve". I click the "Buy to improve" button, and decide to give it a one off donation, small like buying a app on my Andriod. Before ending the process a "comment for the developers" label and a little dialog appears, I write a little message or just hit next. and somewhere a community hires one off there dedicated devs or artists to improve the software for everyone, because hundreds or maybe thousands payed, ether a one of or a monthly. Because the system was there.

Written by JeThroHD the 20 Jun 11 at 19:54.

I can see how the task might bee a bit daunting. even more so since we are talking about people an culture.

I suggest that Canonical would start it as a pilot project whit some already well establish Foss projects like Blender3D or Gimp.
Get some trusted partners on-board, that will be forgiving,
and then iterate on it.

I can see how the task might bee a bit daunting. even more so since we are talking about people an culture. I suggest that Canonical would start it as a pilot project whit some already well establish Foss projects like Blender3D or Gimp. Get some trusted partners on-board, that will be forgiving, and then iterate on it.