Contributor qwerty800 on Synaptic package manager
Generate Revenue for DEVELOPERS
Written by macvr the 17 May 09 at 07:19.
New
hi,
i love open source and the loads of free stuff .
But here is the problem with open source developers> developers dont get paid , and over the course loose interest over their NON-paying hobby projects , or they are not able to maintain their product due to lack of funds for the network hosting, etc.
Not to blame the developers, but DEVELOPERS NEED TO EAT, they need to have money to concentrate on the free product they are making. else they tend to take more interest towards their paying jobs eventually they loose all interest in their open source program.
there have been many examples[not to name specific softwares], where the developers have blocked the repos for lack of funds to keep the site running, devs dropping out of projects and asking for someone else to take over the project.
imagine the possibility of a free equivalent products ,which work as good as the proprietary programs or even better.
Open source CANNOT sustain itself unless devs get money.
and i hate the donate buttons[some sites are still labeled donate], it should be more appropriately labeled "contribute".
i admit, i have never donated to any open source projects, and so also the millions of other users who have not donated.
but there must be a way to generate free content for users and also get money to the devs making us happy.
once there is revenue for the devs, more might be attracted to create programs,more innovative ideas,more competition, more choices, better products.
this would give us better quality and we would have better support for the programs.
[....]
Solution #2:
Link to the project website/provide dev's e-mail
Written by
Ssdg the 18 May 09 at 14:29.
You might know that a lot of FOSS devellopers are already paid. (exemples: Bigger Kernel devs by Linux vendors like red hat, eclipse devs by IBM,...)
But in case of benevolent projects, you can't find thoses informations easily, so why not promoting the project website in package/program description?
Most FOSS projects allow people to pay via paypal already,so why adding a repository or any other method that needs the original develloper to "sign-up"? Let's use his/her favorite way of getting paid.
You might know that a lot of FOSS devellopers are already paid. (exemples: Bigger Kernel devs by Linux vendors like red hat, eclipse devs by IBM,...)
But in case of benevolent projects, you can't find thoses informations easily, so why not promoting the project website in package/program description?
Most FOSS projects allow people to pay via paypal already,so why adding a repository or any other method that needs the original develloper to "sign-up"? Let's use his/her favorite way of getting paid.
Solution #3:
Ubuntu App Store
Despite its closed nature, Apple's App Store has proven to be a tremendous success. The App Store model involves a central organization that approves and distributes commercial applications directly to users. The central organization takes a small percentage of the revenue generated on each app sold; the rest of the revenue goes directly in the pocket of the developer. The overall goal is to make it as easy as possible to connect users who want to pay for high-quality free software, to developers who want to produce that software.
It is very easy to imagine Canonical acting as the the central distributor in this model, as it currently performs this role already with software that is free-as-in-beer (much of it is free-as-in-speech as well). Additionally, much of the core technologies required for such an app store to exist are already in place: distribution, packaging and installation is all provided by apt; Synaptic provides a convenient graphical front-end for installation and package management. Perhaps, with small extensions to these existing systems, it would be possible to create an infrastructure to allow for individual payments to application developers.
Just off of the top of my head, here is what this might involve: It seems likely that this would involve the addition of a special repository for software for which the developer would like to be paid; let's call it a repository for "contribution-based" software. Apt package info may be extended to support monetary value as extra meta-information. Every apt front-end would then need to be modified to respect this extra monetary meta-information. The apt front-ends should be able to integrate with a centralized data store that tracks various payment methods, such as a credit card, or paypal credentials. Synaptic would perhaps be extended to allow the filtering of contribution-based software, perhaps with a dedicated button that include/excludes such software. Other GUI tweeks would be possible.
I can already see many problems with the above (what happens if you're using an older apt client that doesn't respect financial meta-information; the package gets downloaded for free). There are almost certainly more elegant ways to solve this problem that will be apparent to other Debian and Ubuntu developers, and I encourage you to elaborate on how this might work from a technical standpoint.
It is also important to note that while Apple's app store primarily hosts non-free software (free as in beer, and free as in speech), and uses DRM to ensure that users do not make copies of this software, I believe that neither of these features are essential to the success of an Ubuntu App Store. It is possible to imagine individual users swapping .deb's of contribution-based software via filesharing networks, or visiting the authors' websites to compile "contribution-based" software from source and package it by hand; and, according to the terms of the GPL, and most other free software licenses, they would be completely within their rights to do so. However, such methods are much less convenient than simply clicking through a graphical interface, and obtaining your packages directly from Canonical, especially with respect to the demographic of non-technical users that Canonical would like to target. Just so long as value is added to the software in some way, be it by way of convenience or by some other means, then a "contribution-based" repository will be used over other methods of obtaining and installing the software. Additionally, I feel that many Ubuntu users would like to see developers get paid, and thus would be more inclined to use such a service.
In conclusion, while putting a price on software that has otherwise been free-as-in-cost might at first seem a bit unusual, we must consider that providing a convenient, direct mechanism for developers to be paid for their software will help, not harm, the Ubuntu GNU/Linux distribution, the ecosystem of free-as-in-speech software, and the Free Software Movement in general. It will attract more users and more developers to the Ubuntu GNU/Linux platform, especially as such a mechanism does not exist on Microsoft Windows. One need only look to the success of the Apple App Store, and Sun's soon-to-be-launched Java app store, to see that there is a demand for such a distribution model.
Despite its closed nature, Apple's App Store has proven to be a tremendous success. The App Store model involves a central organization that approves and distributes commercial applications directly to users. The central organization takes a small percentage of the revenue generated on each app sold; the rest of the revenue goes directly in the pocket of the developer. The overall goal is to make it as easy as possible to connect users who want to pay for high-quality free software, to developers who want to produce that software.
It is very easy to imagine Canonical acting as the the central distributor in this model, as it currently performs this role already with software that is free-as-in-beer (much of it is free-as-in-speech as well). Additionally, much of the core technologies required for such an app store to exist are already in place: distribution, packaging and installation is all provided by apt; Synaptic provides a convenient graphical front-end for installation and package management. Perhaps, with small extensions to these existing systems, it would be possible to create an infrastructure to allow for individual payments to application developers.
Just off of the top of my head, here is what this might involve: It seems likely that this would involve the addition of a special repository for software for which the developer would like to be paid; let's call it a repository for "contribution-based" software. Apt package info may be extended to support monetary value as extra meta-information. Every apt front-end would then need to be modified to respect this extra monetary meta-information. The apt front-ends should be able to integrate with a centralized data store that tracks various payment methods, such as a credit card, or paypal credentials. Synaptic would perhaps be extended to allow the filtering of contribution-based software, perhaps with a dedicated button that include/excludes such software. Other GUI tweeks would be possible.
I can already see many problems with the above (what happens if you're using an older apt client that doesn't respect financial meta-information; the package gets downloaded for free). There are almost certainly more elegant ways to solve this problem that will be apparent to other Debian and Ubuntu developers, and I encourage you to elaborate on how this might work from a technical standpoint.
It is also important to note that while Apple's app store primarily hosts non-free software (free as in beer, and free as in speech), and uses DRM to ensure that users do not make copies of this software, I believe that neither of these features are essential to the success of an Ubuntu App Store. It is possible to imagine individual users swapping .deb's of contribution-based software via filesharing networks, or visiting the authors' websites to compile "contribution-based" software from source and package it by hand; and, according to the terms of the GPL, and most other free software licenses, they would be completely within their rights to do so. However, such methods are much less convenient than simply clicking through a graphical interface, and obtaining your packages directly from Canonical, especially with respect to the demographic of non-technical users that Canonical would like to target. Just so long as value is added to the software in some way, be it by way of convenience or by some other means, then a "contribution-based" repository will be used over other methods of obtaining and installing the software. Additionally, I feel that many Ubuntu users would like to see developers get paid, and thus would be more inclined to use such a service.
In conclusion, while putting a price on software that has otherwise been free-as-in-cost might at first seem a bit unusual, we must consider that providing a convenient, direct mechanism for developers to be paid for their software will help, not harm, the Ubuntu GNU/Linux distribution, the ecosystem of free-as-in-speech software, and the Free Software Movement in general. It will attract more users and more developers to the Ubuntu GNU/Linux platform, especially as such a mechanism does not exist on Microsoft Windows. One need only look to the success of the Apple App Store, and Sun's soon-to-be-launched Java app store, to see that there is a demand for such a distribution model.
Many applications don't have .deb packages on their download pages
Written by Clorox the 28 Jul 09 at 21:09.
New
This is very common - I show Ubuntu to my friend, he/she likes it, then tries to go to a website to install a program.
a) He/she downloads an rpm. I show them how to use Alien; they run away from Linux because you have to use the command line.
b) He/she downloads a tgz. This could be anything, such as a source tarball, Slackware package, or an archive containing files that need to be extracted somewhere. I have no idea what to do with it either; they run away from Linux because of bad package formats.
c) He/she downloads a bin file (Google Earth). I have experience with this, so I show them how to use make-googleearth-package; they run away from Linux because you have to use the command line.
d) He/she downloads a deb. Something goes right, and it installs without a hitch.
So software packaging is a huge issue, and there's sort of a war between rpm and deb, and other weird formats.
Solution #1:
Promote openSUSE Build Service
Written by
Clorox the 28 Jul 09 at 21:09.
This way, developers can make packages for the most popular Linux distributions more easily. Once a developer is ready to build packages for his/her software, he/she uses osc to automatically make packages for:
-SUSE/openSUSE
-Red Hat/Fedora/CentOS
-Debian
-Ubuntu
-Mandriva
If you're a developer, install the package "osc", and use it well!
This way, developers can make packages for the most popular Linux distributions more easily. Once a developer is ready to build packages for his/her software, he/she uses osc to automatically make packages for:
-SUSE/openSUSE
-Red Hat/Fedora/CentOS
-Debian
-Ubuntu
-Mandriva
If you're a developer, install the package "osc", and use it well!
Solution #2:
Alien GUI
Written by
yoman82 the 7 Aug 09 at 21:34.
This would make an easy process for command line users easy for people who are only accustomed to a gui.
This would make an easy process for command line users easy for people who are only accustomed to a gui.
Solution #3:
Include Alien function in gdebi-gtk package installer
Written by
kikl the 12 Aug 09 at 16:48.
Adding an alien GUI is a good idea, but I think such a GUI already exists. It's called package converter.
http://code.google.com/p/foxoman/wiki/PackageConverter
If someone downloads an rpm-package and double-clicks it under ubuntu, it is most likely that the wants to install the package. He shouldn't be forced to use a separate tool. Therefore, the package conversion functionality should be included into the package installer. If you double click the rpm-file, the package installer automatically converts and installs the package.
Adding an alien GUI is a good idea, but I think such a GUI already exists. It's called package converter.
http://code.google.com/p/foxoman/wiki/PackageConverter
If someone downloads an rpm-package and double-clicks it under ubuntu, it is most likely that the wants to install the package. He shouldn't be forced to use a separate tool. Therefore, the package conversion functionality should be included into the package installer. If you double click the rpm-file, the package installer automatically converts and installs the package.