[Owasp-leaders] Fw: Books at lulu

Dave Wichers dave.wichers at owasp.org
Wed Nov 18 23:52:10 EST 2009

Regarding translations of release quality docs, I agree with Mike that they
should be release quality too. I'm not so sure I buy into calling Google
automatic translations release quality.




From: owasp-leaders-bounces at lists.owasp.org
[mailto:owasp-leaders-bounces at lists.owasp.org] On Behalf Of Boberski,
Michael [USA]
Sent: Wednesday, November 18, 2009 8:51 PM
To: owasp-leaders at lists.owasp.org
Subject: Re: [Owasp-leaders] Fw: Books at lulu


My $0.02,


A translation of a release document should be a release. Of a beta a beta.
An alpha an alpha. This kind of thing is an impediment to promoting adoption
to the maximum extent possible. A missed word or phrase in a translation of
a document identified as release can be fixed in a subsequent edition w/o
damaging the OWASP brand or the overall technical content of the document. 


I would go so far as to publish Google/automated translated versions of
documents, anticipating making fixes in subseqent editions. Let's put 12
different versions of all the different docs out there, and let's do it
yesterday. We should be so lucky that people read them carefully enough to
catch corrections in order to make it useful to people in their
organization. The different docs aren't even in the game if someone in a new
setting can't even get a sense of how one of our tools could potentially be
of use.


Related (of equal importance in my mind), tool documentation should
correspond to the release of the tool. A release toolkit should have either
an UNRATED install guide, or one that is release. Tools also need to be
required to produce a minimum of documentation, including install guide,
release notes, admin guide, and a user or programming guide depending on
what the tool is (tool vs. API).




Mike B.



From: owasp-leaders-bounces at lists.owasp.org
[owasp-leaders-bounces at lists.owasp.org] On Behalf Of Juan C Calderon
[johnccr at yahoo.com]
Sent: Wednesday, November 18, 2009 8:29 PM
To: OWASP Leaders
Subject: [Owasp-leaders] Fw: Books at lulu

Hello Leo

yes this is because published translations are considered Beta not release

Leaders/Project Comitee, this is something I forgot to mention at the
summit, Spanish translations are considered Beta regardless is the original
document is release. This because there is not defined a criteria for
translations to be considered release level. 

the questions is if the original document is release would a translation be
release level as well? (personally I don't think so) but if not, then what
would it take to get to that level?

Juan Carlos


----- Forwarded Message ----
From: Leonardo Cavallari Militelli <leonardocavallari at gmail.com>
To: Juan C Calderon <johnccr at yahoo.com>
Sent: Wed, November 18, 2009 11:51:36 AM
Subject: Books at lulu

Hi Juan,
I'm doing a clean up on OWASP books at Lulu and just notice that Testing
Guide 3.0 in Spanish is in beta release.
Can you tell me why that?

As the ENglish version is on Release Quality, it might be a good idea to
check what is missing to produce the equivalent in Spanish. 

Thanks & Best,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-leaders/attachments/20091118/822ea459/attachment.html 

More information about the OWASP-Leaders mailing list