Topics (messages 2846 through 2859):
[tdf-discuss] Updates overwriting User settings
2846 - Robert Derman <robert.derman@pressenter.com>
[tdf-discuss] Re: Updates overwriting User settings
2847 - Larry Gusaas <larry.gusaas@gmail.com>
[tdf-discuss] Re: Updates overwriting User settings
2848 - Robert Boehm <boehm.robert1@gmail.com>
[tdf-discuss] FreeDesktop Bugzilla
2849 - Michael Meeks <michael.meeks@novell.com>
[tdf-discuss] FreeDesktop Bugzilla
2850 - BRM <bm_witness@yahoo.com>
OOoCon 2010 Talk (was: Re: [tdf-discuss] FreeDesktop Bugzilla)
2851 - Christoph Noack <christoph.noack@documentfoundation.org>
[tdf-discuss] FreeDesktop Bugzilla
2852 - Michel Gagnon <michel@mgagnon.net>
OOoCon 2010 Talk (was: Re: [tdf-discuss] FreeDesktop Bugzilla)
2853 - Christian Lohmaier <lohmaier+ooofuture@googlemail.com>
[tdf-discuss] FreeDesktop Bugzilla
2854 - Duane <genomega@earthlink.net>
[tdf-discuss] FreeDesktop Bugzilla
2855 - Johannes Bausch <johannes.bausch@gmail.com>
[tdf-discuss] FreeDesktop Bugzilla
2856 - Rainer Bielefeld <RainerBielefeld_OOo_QA@bielefeldundbuss.de>
[tdf-discuss] FreeDesktop Bugzilla
2857 - jonathon <toki.kantoor@gmail.com>
[tdf-discuss] How To Contribute
2858 - animesh meher <animeshmeher@hotmail.com>
[tdf-discuss] How To Contribute
2859 - David Nelson <commerce@traduction.biz>
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
OOo has never overwrittin the user settings on my Mac in the three and a half years I've been
using a Mac.
--
_____________________________________________________________________________
Larry I. Gusaas
*Moose Jaw, Saskatchewan Canada
Website: http://larry-gusaas.com
"An artist is never ahead of his time but most people are far behind theirs." - Edgard Varese *
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
--
As the trials of life continue to take their toll, remember that there
is always a future in Computer Maintenance.
-- National Lampoon, "Deteriorata"
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
On Fri, 2010-11-12 at 15:36 +0100, Friedrich Strohmaier wrote:
LibreOffice already has the selectable help/about version text so it
can be cut/pasted.
Yeeey!!
:-)
"Version key (paste from help->about):"
That's what I allways dreamed from in OOo!!
Nice - so - I guess we can do still better. It would be -really- nice
if we could cut/paste a block of text (perhaps a non-human-readable
chunk) that we could parse in javascript to auto-fill-out many of the
fields accurately:
platform / exact version / enabled extensions /
java version / etc. etc.
I'll add this as an easy hack.
As/when we have a defined URL, we could add a 'file a bug' link that
could even auto-populate that. Lots of fun is possible. First we need
some draft of the form / flow / wizard[in a single page] to fill in to
file the bug I think.
Good news. LibO will make the race!! :o))
If we can get people excited and contributing, make QA a fun job
instead of a duplicate triaging nightmare etc. we'll do well :-) thanks
for your support.
ATB,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
From: Michael Meeks <michael.meeks@novell.com>
On Fri, 2010-11-12 at 15:36 +0100, Friedrich Strohmaier wrote:
LibreOffice already has the selectable help/about version text so it
can be cut/pasted.
Yeeey!!
:-)
Hardly. Now you've got two things that can go wrong for a bug report.
Sure it's less the user has to remember, but now you're relying the user
being able to reliably copy/paste for the bug report too - information that
may not be easily accessible - e.g. if they can't run the software due to it
crashing, perhaps without generating the crash report manager.
"Version key (paste from help->about):"
That's what I allways dreamed from in OOo!!
Nice - so - I guess we can do still better. It would be -really- nice
if we could cut/paste a block of text (perhaps a non-human-readable
chunk) that we could parse in javascript to auto-fill-out many of the
fields accurately:
platform / exact version / enabled extensions /
java version / etc. etc.
I'll add this as an easy hack.
As/when we have a defined URL, we could add a 'file a bug' link that
could even auto-populate that. Lots of fun is possible. First we need
some draft of the form / flow / wizard[in a single page] to fill in to
file the bug I think.
Why bother? If you can do that, then you can just as easily have it load the web
page
in a browser for the user to simply review and sign off on, or even just have
another
dialog come up that directly submits the information to the system without
having to
go through a web browser - which would be even better to do so as to cover users
that don't necessarily have Internet access since you could then create a zip
file and
give them instructions on what to do when they _do_ have Internet access (or
provide
a means to send it at a later time).
Seriously, Thunderbird has a means to capture a crash report and save it for
later
submittal. They recognize that not all users are able to access the Internet or
their
mail system at all times. LibO needs to account for that too.
And no, copy/paste is not a step in the right direction here.
Ben
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
Am Freitag, den 12.11.2010, 07:43 -0500 schrieb Charles Marcus:
On 2010-11-12 6:01 AM, Michael Meeks wrote:
Perhaps we want a simple hash in addition to that - that combines
vendor, version, platform, and so on - and that we demand - so we
can
detect wrong values that people enter for version / etc. - thus not
tempting them to file an old bug vs. a newer version just to get
attention ;-) would be easy to do.
"Version key (paste from help->about):"
I don't understand why this should have to be manually entered by the
user.
Good question, short answer: There is no reason. At least no real
technical reason ...
At the OOoCon 2010 (and before), we already talked how to improve the
issue gathering and tracking from the user's and the supporter's
point-of-view. The current idea is a small first step to some agreement
between the different contributors ... because - from what I understand
- it is more the differences how the projects handle these issues, than
a technical problem.
The discussion at the OOoCon 2010 made clear to me, that - if people go
for such a (let's call it) automated issue gathering system, to say
"yes, software does contain bugs". And it requires some agreement across
different projects / Linux distributions how to harmonize such a system,
so that every contributor can have some benefit.
And here, the experience of the projects and the current workflows seem
to differ to such an extend, that the "given" manual system provides
reasonable flexibility. Another experience people talked about was, that
fixing the known bugs is already a lot of effort. But, I still consider
this "costly" for the users and the people doing the support on the
mailing lists.
However, we collected some ideas within the presentation / workshop ...
so if you like dynamic camera movements and emotional debates, then
please have a look at the conference video [1].
As strange as it sounds, I'm happy for each of the tiny improvements ...
and after a long time, we start to address these improvements. Okay, the
remaining comments might better be located on another mailing list :-)
Cheers,
Christoph
[1] Video (approx. 700 MB!)
http://users2.ooodev.org/~ooocon2010/01_september/FT_409/18.15_charles_schulz_mechtilde_stehmann.flv
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
I don't know about others, but I, for one, NEVER send those automated
crash reports. It feels a bit like big brother watching over my shoulder.
--
Michel Gagnon
Montréal (Québec, Canada) -- http://mgagnon.net
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
On Fri, Nov 12, 2010 at 11:50 PM, Christoph Noack
<christoph.noack@documentfoundation.org> wrote:
[1] Video (approx. 700 MB!)
http://users2.ooodev.org/~ooocon2010/01_september/FT_409/18.15_charles_schulz_mechtilde_stehmann.flv
120MB
http://users2.ooodev.org/~cloph/videos/10-09-01_FT_409_18.15_charles_schulz_mechtilde_stehmann.mkv
ciao
Christian
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
How do you expect problems to be resolved if they are not reported?
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
better:
* ask the user once at the beginning if he wants to report crashes and
list the information THERE
* NEVER include things like the current program's memory page dump or
something alike
* then DO NOT ask again but just send it
alternative:
* pop-up which sais that a crash report can be sent if the user wishes, but:
* it only has a input field where the user can say for himself what
happened and when
* checkbox saying something like: "include relevant data", where
"data" really leads to ALL the data being sent
The current problem is that hardly anyone trusts these crash reports -
that's what I experience when talking to friends about that issue. So
we first have to make the user think that something is being done.
I've repeatedly used the "Firefox made me sad"-thing but I've never
used the crash report before.
Joey.
I don't know about others, but I, for one, NEVER send those automated
crash reports. It feels a bit like big brother watching over my shoulder.
You are kidding right?
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
May be we open some Task-Issues at FreeDesktop Bugzilla
Started here:
<https://bugs.freedesktop.org/show_bug.cgi?id=31592>
Rainer
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
On 11/12/2010 01:12 PM, Charles Marcus wrote:
Bug#'s? Thunderbird has never had a problem 'retrieving' our mail in our office, and we've been
using it (40-60 users over the years) since about
version 0.8, so whatever your problem is/was, obviously it is/was
something fairly obscure.
The issue quite literally is: "Too many email accounts with too much
mail to be retrieved".
jonathon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJM3s0OAAoJEOpnmQXT8Ln/Mi4IAMBVm+STQDAdLI/d1pb6YYfv
C1Y+68kSQADfxxcYjVWOq116CWfSzBYuyi1gM4Vbk82XXmw6epxea09DxqzxCKYR
dUW+Ss8QEC4yymkq3fJebs0Xye+Gxhkph35RadxNfOc/hq5nJHJPIbKCQEBBlMWb
8kHStmujSeuXxRY2tUyaSqsc0VQxZnOyLT0MZXyJb8f6Ivo3a2W9NJwBJyQt7TA4
KrWSrq2SMuV5nH+ekkP/LQwEiT0mTcYTWoiwwikeiftUf3oKJJO62Cy2OR/V1Q6n
AuhyVsgkCSMbIniMxJLPDZXWc94sko8GA4+dBT3YtTnYrJRJHbxblRt+9GqBwEw=
=yd3i
-----END PGP SIGNATURE-----
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
Hi! Friends=2C
New Comers like me would like to contribute to Libre Office .
I have some experience in c++ and could contribute if guided properly.
If someone can send me a guide.=20
Ill also contact different blogs like omgubuntu.co.uk=2C muktware.com=2C ww=
w.webupd8.org.=20
Thanks and Cheers=2C
Animesh
=
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
I'm not sure there is a "guide" as such, but you could go chat to the
devs on IRC, or write to the devs' mailing list. You can also browse
the "how to contribute" section of the main site, and have a look at
the wiki... I've pasted lots of useful links below [1] (including
links to the various resources I mentioned).
HTH. Welcome to the community. :-)
David Nelson
[1] Useful links
============
LibreOffice marketing mailing list: marketing+subscribe@libreoffice.org
The Document Foundation general discussions mailing list:
discuss+subscribe@documentfoundation.org
LibreOffice developers mailing list:
http://lists.freedesktop.org/mailman/listinfo/libreoffice
LibreOffice user support mailing list: users+subscribe@libreoffice.org
Our Nabble gateway for easy mailing list browsing:
http://www.documentfoundation.org/nabble/
The Document Foundation contacts page:
http://www.documentfoundation.org/contact/
LibreOffice dedicated IRC channel: #libreoffice at irc.freenode.net
TDF dedicated IRC channel: #documentfoundation at irc.freenode.net
Follow TDF via @docufoundation on Twitter: http://twitter.com/docufoundation
Follow TDF via @docufoundation on identi.ca: http://identi.ca/docufoundation
Visit the TDF website: http://www.documentfoundation.org
Visit the TDF/LibO wiki: http://wiki.documentfoundation.org
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***