| Summary: | Marketplace integration with flattr Social Micropayment platform | ||
|---|---|---|---|
| Product: | Community | Reporter: | Lars Ködderitzsch <lars> |
| Component: | Marketplace | Assignee: | Christopher Guindon <chris.guindon> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, eclipse, ian.skerrett, loskutov, mail.eclipse.org, remy.suen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Lars Ködderitzsch
PayPal (http://paypal.com) which is used for example to donate at SourceForge is an alternative to Flattr. Although Paypal also allows for donations to plugin (or more generically content) vendors, the concept behind is completely different. With social micropayment platforms like flattr or kachingle (http://www.kachingle.com/) a consumer usually assigns a fixed monthly rate to his flattr/kachingle account. This monthly contribution is then divided among all the content vendors (e.g. website, blogs, software providers) which the consumer decides to flattr/kachingle in a month. The process of flatt(e)ring something is as simple as it gets - just a click on a certain flattr/kachingle button on the content vendors website. This lowers the hurdle for donating something (usually a very small share) to an offering of his liking greatly. A dedicated donation via Paypal is rather complicated in comparison and speaking from my experience as eclipse plugin provider (http://eclipse-cs.sf.net) rarely someone does it. Integration of flattr for instance would also be rather simple for the Eclipse Marketplace - it would just require having an extra attribute in the plugin registration data with marketplace, and of course the display of said flattr buttons (if such flattr id is provided by a plugin vendor). I agree it would be nice to have some type of payment model available. I think the easiest would be to allow for plug-in providers to charge for a version of their product, ie some for of micropayment. Maybe this can be done via paypal? One concern I have with flatr is that it is too new and people aren't use to it yet. (In reply to comment #3) > One concern I have with flatr is that it is too new and people aren't use to it > yet. Even if Flattr is new it is already very popular in the Eclipse universe: https://flattr.com/search/eclipse In my view this feature request is only about a donate link/button or multiple links/buttons which can be configured by the person who register the solution at the Marketplace and which will then shown at http://marketplace.eclipse.org/ and in the client. To donate further steps have to perform at the website of the payment service. (In reply to comment #3) > One concern I have with flatr is that it is too new and people aren't use to it > yet. Agreed, services like flattr/kachingle are relatively new, but Eclipse is all about being cutting edge, no? ;-) (In reply to comment #5) > (In reply to comment #3) > > One concern I have with flatr is that it is too new and people aren't use to it > > yet. > > Agreed, services like flattr/kachingle are relatively new, but Eclipse is all > about being cutting edge, no? ;-) Very good point. :-) Any chance to see some light here? I would also like to see some kind of Paypal "donate" button as it is widely used. If it is hard to create some default button/form - can I simply embed my custom Paypal form into the Marketplace page or it must first be approved by somebody from *.eclipse.org? Regards, Andrei Your idea is good, but: If you are working in a big company, it is nearly impossible to flattr (probably blocked by admins) or to pay anything directly. You have to fill out a number of forms and you have to search for someone who will be able to support you with a budget. And I don't see, that I should privatly pay for things the company needs. But I have no solution for it. The best thing would be, if there is a company flatr account. But who should have access? Same thing with PayPal. The company needs at least a printable bill. But I think that Eclipse.org should handle this in some years... This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |