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

Le 2011-06-28 04:31, David Nelson a écrit :

On Tue, Jun 28, 2011 at 9:20 AM, Christoph Noack<>  wrote:
So, to me, the aim of consistent screenshots make totally sense - even or especially from a 
community POV.
Well, in any case, as someone who is a constant presence in the LibO
docs team, I'll certainly cooperate in promoting/coordinating uptake
of the initiative if it takes off.

But, like I already said, I'm wary of complexifying the process of
getting involved in docs contribution, and I don't feel like seeing
things get over-regulated in the docs team. A) Don't we get enough of
that in daily life already? Contributing to an OS project is supposed
to be fun, not an over-regulated part-time job with as many rules as
your day job.

On the contrary, this effort is to give clarity to taking screenshots. It is not fun, when you find that there are no people joining in, for example, taking screenshots, because there is no protocol. When the directions are clear and organised, then people join. With lack of clarity, people may show their hands up for a project and then loose faith where there is no help or direction. After all, this is what our LibreOffice is based on, a clear set of directions on how to build great documents. The documentation team uses established "styles" for their documentation. Imagine, if there were no styles, where would the documentation effort be then?

B) It is so easy to scare new contributors off. For some
time now, practically every newcomer has faded after just a short time
of getting involved. If there's too much outside interference from
people who don't actually regularly take part in the English docs
team's life, it might not actually help us build a stable docs team,

I think that by now everyone can see the pattern, it is the same as with the OOo. There have already been comments on the lists that the same pattern has re-established itself with a core group doing most of the documentation, just as with the OOo. If this is the case (and it is), then our methods need to change. By establishing clear protocols on taking screenshots should enable more people to jump in and help out, and, will also help veteran members speak with one voice with respect to screenshot quality for our great documentation.

I am not sure what you call outside interference. In any part of LibreOffice, there are many ways to contribute. Also, sometimes, a new fresh pair of eyes may help out. If you find that you are lacking in contributors and you are doing the same as before (OOo), then maybe, having a change in some aspects of the protocols (in this case, screenshots) may help.

C) Personally, I just don't see any need for standardization and

Bernhard has summed up all of the reasons that were proposed on uniformization on this discussion thread in a recent post. Just in case you missed it, you may find it here: I think he has put it all very eloquently and as plain as possible. I think the reasons for writing up protocols are overwhelming.

However, if this thing gets off the ground and has broad support, I'll
certainly cooperate as a good team player. I'll be monitoring the

BTW, all this is just my 2 cents. Please don't shoot me down for
voicing it. TIA.

Hey, no problem, we are all contributing on the conversation and eventually, something will come of it. Now is the time to offer opinions and contributions to the discussion. I have already put up my hand to help out with screenshots and I am sure we will be able to steer newcomers to the documentation team to the "screenshots protocols" page as a place where they can get their feet wet, while they ramp up to more contributions on the team.



Marc Paré

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.