Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Re: [tdf-discuss] Donations system: pay for a feature


Hello Carlo,

Le jeudi 16 mai 2013 à 09:09 +0200, Carlo Strata a écrit :
Hi Everyone,

in any case (!) none has answered to my initial question and moreover 
has to be avoided changing the thread object and throw away one person's 
suggest or a simply discuss. So that now I have to renew my question 
with another all new post!!! Thank you!

[OT] I have donate to LibreOffice some money and sure many of my time 
since 28.09.2010 to spread his use, to make it in mind to many people in 
Italy and in my local engineer professional association.


Thank you a lot BTW!

In any case I think that resources like University Students, Google SoC, 
... are and remain useful to both sides ;-) (TDF/Community/Users and 
Students themselfes).

I also want to find an approved new feature list in TDF or LibreOffice 
site...

I think we do have what you are looking for:
https://www.libreoffice.org/features/ (and linked pages from there)
https://www.libreoffice.org/index.php/download/4-0-new-features-and-fixes/

and of course, the wiki pages:
https://wiki.documentfoundation.org/ReleaseNotes/4.0

Hope this helps,

Charles.



Have all a sunny day,

Carlo

ing. Carlo Strata
-
via Botticelli 1/4
30031 Dolo - VE
Italia - Italy
-
tel./fax +39.041.822.0665
cell. +39.347.85.69.824
Skype carlo.strata
Google carlo.strata.69
-
carlo.strata@tiscali.it
PEC: carlo.strata@ingpec.eu

Il 16/05/2013 01.58, Steve Edmonds ha scritto:

On 2013-05-16 07:45, Joel Madero wrote:

Any payments and/or donations must be accounted for and if the person
paying has any intent it to go to xyz, then by regulations we may 
need to
account for that payment/donation and where it went to.

That is the real problem with targeted donations and payments.  
There will
be a mess in paperwork to deal with it.  Opt in, opt out, What it 
was used
for.  Keeping track of all of who pays what, for what, can cost more 
than
thepayment in paperwork and legal fees.

This has been discussed quite a bit on user list and brought up 
during ESC
at some point and I thought the consensus was "we'll just let them do 
what
they want" and not endorse, support, etc... any of that. I thought that
kept us out of legal muddy waters. It'd be similar to me just going to a
friend who is a programmer and saying "dude, can I pay you $100 to 
fix this
issue" - a contract completely out of TDF's hands.


Best,
Joel
Would this paid for feature not then create a fork in the code, then 
are you committing to maintaining that branch until some time (may be 
never) that the branch feature is voted into the main code base. It 
seems a bit impractical when you have a continually evolving product 
to pay to add a feature unless you are assured it will be included in 
the main code base and maintained.
Steve





-- 
Charles-H. Schulz
Co-Founder & Director, The Document Foundation,
Zimmerstr. 69, 10117 Berlin, Germany
Rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint




-- 
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.