<div class="gmail_quote"><br><div class="gmail_quote"><div class="im">On Sat, Oct 8, 2011 at 11:05 AM, Frank Karlitschek <span dir="ltr"><<a href="mailto:karlitschek@kde.org" target="_blank">karlitschek@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Michael,<br>
<br>
in general itīs a good idea to collect donations of course. But this has some important implications.<br>
<br>
- We need an organization who is the owner of this flattr account. Itīs now a good idea that this account is owned by me, you or any other individual<br></blockquote></div><div>I agree it should be owned by the community, but why not start with it owned individually, till we have a foundation? As I said: Keep the money in the flattr account till ownCloud can use it.<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- We need a democratic elected organization who decided how this money is spent.<br></blockquote></div><div>I agree, but we first need enough money to be spent. So in my opinion: Start now. Leave it on Flattr. Think about how to spent it, when it is reasonable. If we start collecting money after getting an organization, we miss a lot of opportunities. <br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- We need a shared bank account to hold this money.<br></blockquote></div><div>Why not see the flattr account as shared bank account for now? <br></div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- We need a non profit status of this organization so that we donīt have to pay taxes.<br></blockquote></div><div>Agreed. As I wrote: The payout date is important, so we could handle the money later. Or we could use the KDE e.V., if they don't mind? So have a dedicated owncloud flattr account and payout to the KDE e.V. bank account with the tag ownCloud and use it for only this. <br>
</div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- A person to handle the money transfers, book keeping, tax declaration and more.<br></blockquote></div><div>Depends on what we decide to do. We could ask KDE e.V. to handle one transaction every few months, depending on the incoming money, or we could appoint someone, if we have an organization.<br>
(If nooone is found, I would do it. But I think the KDE e.V. solution sound better.) <br></div><div class="im"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
- A several other requirements. </blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Itīs very important to me do this in the right way (TM) because this has a lot of potential to create significant harm inside our community like for example tax implications for individuals, legal implications for some of us, mistrust inside the community about the spending of the money and a lot more<br>
<br>
ownCloud doesnīt have this kind of organization to handle this donations in the right way at the moment. But this is not a problem because we are part of KDE and KDE has the KDE e.V. which is created exactly for that reason.<br>
<br>
So what we should do here is to motivate our users to donate to KDE e.V. (perhaps with a flattr button or something else) and than we can expect from the KDE e.V. to support our developer meetings and other expenses we have.<br>
</blockquote></div><div>I disagree. Why not use a dedicated donation account owned by KDE e.V. for now so switching to a dedicated foundation would be easier.<br>Another method would be letting an individual handle the transactions and donate it with the tag "ownCloud" to kde. (not the best way in my opinion.)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Cheers<br>
Frank<br>
<div><div></div><div><br></div></div></blockquote><div><br>Cheers<br>Michael<br><br>And sorry, don't want to stab you in the back, I just want a reasonable discussion.<br><br> </div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div>
<br>
<br>
On 08.10.2011, at 01:14, Michael Grosser wrote:<br>
<br>
> Hey,<br>
><br>
> I'm Michael Grosser.<br>
> Just to give you a hint who I am:<br>
> I'm the guy providing <a href="http://demo.owncloud.org" target="_blank">http://demo.owncloud.org</a>.<br>
><br>
> For the upcoming release I wanted to suggest to implement <a href="http://flattr.com" target="_blank">flattr.com</a> buttons.<br>
><br>
> If you don't know what flattr is about:<br>
> Flattr is a microdonation system that launched in March 2010 on an invite-only basis[1] and then opened to the public on 12 August of the same year.[2][3]<br>
><br>
> Flattr is a project started by Peter Sunde and Linus Olsson. Users are able to pay a small amount every month (minimum 2 euros) and then click Flattr buttons on sites to share the money they paid among those sites, comparable to an Internet tip jar. (The word "flattr" is used as a verb, to indicate payments through the Flattr system-so when a user clicks a Flattr button and they are logged in to the Flattr site, they are said to be "flattring" the page they are on.) Sunde said, "We want to encourage people to share money as well as content."<br>
> extracted from <a href="http://wikipedia.org" target="_blank">wikipedia.org</a><br>
><br>
> The owncloud account is already set up and the code, is sort of in the start position. It is ready and could be made public in under 5 min.<br>
><br>
> My idea is to have the flattr buttons ready for the release and think about what to do with the money later.<br>
> The money should be held in the flattr account till we know what to do with it. The payout would be the date important for anything legal anyway.<br>
><br>
> My suggestion would be following buttons:<br>
><br>
> one in the <a href="http://demo.owncloud.org" target="_blank">demo.owncloud.org</a> header<br>
> one in the header of <a href="http://owncloud.org" target="_blank">owncloud.org</a><br>
> and one for each specific page<br>
> and later perhaps one in the owncloud installation code (under a contribute tab under settings or so)<br>
><br>
> The reason for so many buttons is in my opinion feedback. Users can appriciate the ownCloud project with the main button in the header, and could appreciate the demo with the button from the demo.<br>
><br>
> As Jacob wrote in irc:<br>
> It's not about having the money from the docs go elsewhere. It is about giving the user the ability to be able to show a "directed" appreciation, e.g. "I really like that you have a demo server. keep it up!" or "That documentation really helped. Thanks!"<br>
> there's one button for the show itself, but another one for each episode to let the user be able to show "yes, _this_ was a great episode, thanks!"<br>
><br>
> What is your opinion?<br>
> No buttons at all? Just one button? Any suggestions?<br>
><br>
> Cheers Michael<br>
><br>
</div></div>> _______________________________________________<br>
> Owncloud mailing list<br>
> <a href="mailto:Owncloud@kde.org" target="_blank">Owncloud@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
<font color="#888888"><br>
Frank Karlitschek<br>
<a href="mailto:karlitschek@kde.org" target="_blank">karlitschek@kde.org</a><br>
<br>
<br>
</font></blockquote></div></div></div><br>
</div><br>