Le 2013-11-12 18:24, Robinson Tryon a écrit :
So a little backstory:
When we did the site redesign (for 4.0, IIRC), I procured a number of
source images of all-in-one computers under a permissive license and
wanted to put those in some shared space online (for the
Design/Website teams). When I tried to upload those files to the wiki,
I encountered a couple of different issues including
- The wiki couldn't consistently handle files 5MB+
- Image preview/thumbnails were flakey for larger images
- I had to upload one file at a time
I did a bit of digging for a while and, encouraged by Florian, tested
out a few options and finally decided that ownCloud was a pretty
decent option for storing a bunch of files in a shared space online.
Based on my notes, Florian put ownCloud into service. The application
wasn't perfect, but it had a pretty simple interface and allowed us to
upload even big files (100-200MB was no problem), so it suited our
immediate needs quite well.
We'd done some preliminary testing in the month leading up to the
Milan conference, but hadn't used the system very heavily. By chance,
Charles mentioned that Marketing really, REALLY wanted a simple system
to store files, and we told him that we had just the thing...
This still seems to blur the lines of wiki and OwnCloud use. Are we still
using the wiki for marketing work? I viewed the LibreOffice OwnCloud as a
temporary file storage area where people would upload their work for the
mailing list members to view, BUT, the wiki would remain as our official
file repository tool. Or are we now changing this? If we are, this would
have a large impact on marketing, design and documentation. We store a lot
of docs on our wiki.
Good questions!
I largely see ownCloud as a general-purpose place to store "stuff" for
the project. This includes drafts and papers and images and videos,
big files related to particular bug reports, and basically anything
that we want to share with one another. I generally view the wiki in
the same way.
I know that there are a few things that are a bit more formal on the
wiki, like the Trademark and Branding guidelines:
https://wiki.documentfoundation.org/TDF/Policies/TradeMark_Policy
https://wiki.documentfoundation.org/Marketing/Branding
Those wiki pages are a couple of things that I think might more
appropriate live on a separate website or in a separate namespace to
help demarcate them as being Policy pages, rather than a part of the
anyone-can-edit wiki space.
BUT, the wiki would remain as our official
file repository tool.
So where would you suggest different families of files live?
I think we all see a difference between
computer_image_file_01_of_20.jpg and
finished-draft-of-whitepaper_rtryon.pdf. Thinking off the top of my
head, one option would be to put all of the source files and drafts of
papers/presentations on ownCloud, and then copy just the final
versions of files to....somewhere (I'm reticent to say the wiki).
I believe the way that Documentation handles things is to put all
drafts up into a common folder (ala ownCloud) and then final versions
get published in various places (including on the website and on the
wiki). Would it make sense for Marketing to push final versions of
documents up to
libreoffice.org/marketing/{whitepapers|presentations|(etc..)}/ ? That
could be our way of saying "we consider these documents to be
polished, final versions."
Cheers,
--R
I see more a problem with making workflows different from one section to
another (design, documentation, marketing) which may add confusion for
those of us who help out in more than one area. I see this as just one
more hurdle to getting people to work in a consistent manner.
Perhaps, a better idea would be to get the leads in design,
documentation and marketing to decide on a process and then all follow
the same. This will make it easier for our volunteers to work in more
than one area without having to spend time learning how different one
group works from another.
We are still struggling with trying to engage users to volunteer in the
project, while at the same time, not being clear right from the start as
to how a volunteer is expected to contribute. Adding to the mix, it now
means that a volunteer needs to master the use of OwnCloud and the wiki.
I am not quite clear on the problem of uploading more than one file at a
time, when a search for a wikimedia extensions shows that there is one
available[1] for installation. As for the size of uploaded files, this
is usually set in the configuration file. As for the preview of images,
I am not sure I understand the problem as being flakey.
I agree that uploading a 100-200 megabyte file would be a problem, but,
these types of files would surely fall into a very clear minority of files.
IMO, we need to make the system as easy as possible to attract, engage
and keep our volunteers. Adding to the mix, to me, sounds a little too
frustrating of an event for new volunteers. If we are looking for people
who have a little time to spend helping, well, they may end up spending
all of their time trying to figure out our work habits and not staying.
Cheers,
Marc
[1] http://www.mediawiki.org/wiki/Extension:UploadWizard
--
Marc Paré
Marc@MarcPare.com
http://www.parEntreprise.com
parEntreprise.com Supports OpenDocument Formats (ODF)
parEntreprise.com Supports http://www.LibreOffice.org
--
To unsubscribe e-mail to: marketing+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/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Re: [libreoffice-marketing] Re: LO white paper · dbclinton
[libreoffice-marketing] Re: [libreoffice-documentation] LO white paper · Preston Bernstein
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.