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


Hello Florian,

Le Tue, 26 Nov 2013 11:24:50 +0100,
Florian Effenberger <floeff@documentfoundation.org> a écrit :

Hello,

Charles-H. Schulz wrote on 2013-11-26 10:53:

Certainly, I'm not criticizing infra. But when in Milano we -the
people participating in the marketing workshop - requested a simple
ftp server, the answer was that OwnCloud was the appropriate tool.

back in the early days, many people complained to me that setting up
a simple FTP server does not work for them, because

1. they don't know how this tool works
2. they are behind a router configuration not allowing FTP

And let's not forget that _ALL_ access credentials for FTP are 
transferred _UNENCRYPTED_ over the wire, providing an anonymous
upload facitiliy for all kind of stuff for everyone.

You see, any tool has its drawbacks. :/ I am not saying ownCloud is 
perfect, but you need to start somewhere. Otherwise we would need 12 
months of deep evaluation before anything can be set up, to consider 
each and any use case...

I think what is required is some short information on how ownCloud
works with regards to file sharing. So, here's the story:

Per se, files in ownCloud are private and only belong to you.

You can share any file or folder in ownCloud by the "share" icon next
to it. This sharing could either be done on a user basis, so you
share it directly with an ownCloud user, who optionally can edit it,
or "via link" to the general public.

Those links usually look quite odd, e.g. 
https://owncloud.documentfoundation.org/public.php?service=files&t=3b219f29a1b7057eeca23ecc6d3d4d84&path=//Design

What Robinson has done is to create a folder called "common" with his 
account. He shared it with the public for reading. At the same time,
to selected users, he shares it writable. This means that e.g. you
and me see this folder in their ownCloud accounts and can directly
open it and push files to it.

The link usually to use for that folder is 
https://owncloud.documentfoundation.org/public.php?service=files&t=3b219f29a1b7057eeca23ecc6d3d4d84&path=

Agreeably, this link looks ugly, so Robinson thankfully sent me a 
RewriteRule to make it look like this

https://owncloud.documentfoundation.org/common/

All subfolders can be addressed for public reading in the same way.
As an example

https://owncloud.documentfoundation.org/public.php?service=files&t=3b219f29a1b7057eeca23ecc6d3d4d84&path=//Documentation

is now

https://owncloud.documentfoundation.org/common/Documentation

Does this shed some light?
Please, I'm honest with that question, I'd like that issue sorted out
- if there are still open questions, let me know.


Speaking only for myself here: yes. I'm not sure it's something that
other contributors can work with and I'd hate to have a tool like this
just to myself :-)

Best,
-- 
Charles-H. Schulz 
Co-founder, The Document Foundation,
Kurfürstendamm 188, 10707 Berlin
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint
Mobile Number: +33 (0)6 98 65 54 24.


-- 
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.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.libreoffice.org/global/website/
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.