Hi,
bjoern wrote on 2013-12-03 14:57:
That is ouf course intended in the end. But up until then the Wiki is still a
better choice than ownCloud as most people already have accounts there.
yes, _UNTIL THEN_, the wiki is better, as I don't have to manually
approve accounts there. Emphasizing the "until then" part so heavily, so
it's clear to everyone. ;-)
And no matter to which value we will raise the limit in the new Bugzilla, there
always will be freaky corner cases that might need more space. As essentially
everything in bugzilla is there for eternity, we shouldnt raise the limit too
high. So in the end, we need some form of storage anyway.
Exactly that is the reason why the wiki is not the best solution in the
long run either. Anything there is also for eternity, the database
grows, we need larger backup storages - it is kind of a domino effect,
unneeded for simply file storage. We share the same pain here. ;-)
As the wiki has a rather high limit (25MB) and it should be possible to delete
stuff again from there (right?), it doesnt look too bad a fallback to me for
No, not totally, "some" database entries are always there in the end, so
"deleting" is not the right word. :)
So _if_ we are using a solution that kinda sucks, we should use _one_ (wiki) and
not two (wiki and ownCloud).
Yes, I agree, as long as it is temporarily.
Yes, account creation makes all these a stillborn. For it is easier to tell the
reporter to upload to his dropbox/UbuntuOne/Whatever and us to pick it up from
there.
I am of course happy with that as well, just as I am with other
proposals. My only requirement is that uploading (not downloading) must
be authenticated to avoid abuse, and that this authentication must be
encrypted, which effectively rules out FTP. Towards anything else, I am
open, of course.
IMHO no. The wiki was used before for this, so lets not throw in another tool
into the mix -- so lets roll back on ownCloud usage for this, and _stay_ with
the wiki. Not because its the right solution, but because we introduced that
already and we dont have anything better right now. Aka: lets not stack one
temporary bandaid storage on top of another temporary bandaid storage. Lets
stick with the first temporary bandaid (wiki).
I agree.
IMHO, the best solution we could hope for is something helping us like this
- to let the enduser upload the file in question to the Dropbox-equivalent of
his choice
I agree so far.
- then have a TDF service where our QA guys can throw an URL at (via email,
webinterface, ssh login)
- this service then downloads the file and saves it for us on our mirror
Is that really required? It requires some development time (and
everybody knows I lack those skills :-) - if it's temporarily anyways,
why not just grabbing the file from Dropbox & co.?
Oh, and welcome to the world of http://www.xkcd.com/1172/ ;)
:D
Florian (confused that reply-to-all on this lists does not include the
original sender... so if you reply, Cc me manually)
_______________________________________________
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
