Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZKFJx-0005C0-MJ for pgsql-docs@arkaria.postgresql.org; Wed, 29 Jul 2015 00:34:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZKFJw-0001Sf-4d for pgsql-docs@arkaria.postgresql.org; Wed, 29 Jul 2015 00:34:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZKFJv-0001SY-MV for pgsql-docs@postgresql.org; Wed, 29 Jul 2015 00:34:07 +0000 Received: from mail-lb0-f181.google.com ([209.85.217.181]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZKFJe-0000XV-JG for pgsql-docs@postgresql.org; Wed, 29 Jul 2015 00:34:06 +0000 Received: by lbbyj8 with SMTP id yj8so85473887lbb.0 for ; Tue, 28 Jul 2015 17:33:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6Ha8LgVQNBgH/1BSpOzgatiJNWyHiIod3RBe2YPHiK8=; b=IZ877Vm6uGBsYw/0Y25Z4AcwyhtrSL8xXkrLbZhBmFQzqysGcVfotEYw/wAtZ9oDGz 58T1o9g+fjL1n40ntKErZNrcK08Eeafe7yYx5FSG8TiSoE5UGk/ITALz1VwqslGYcnDh GEfN9EuGabXex8lgfwKU73sozKwAr8A/HIhTb7xmHL3ocQgFxvjNnPqUwbB3kZLA//cN y6DsHP+1WrR9xySHlAGhOP1+fXKdaehyL9riuQJ1xPIiYKeeh7CTcN3G11ChpFG2EiEF r1b6MDxJSIqZgplkpsoXrUM4PabyyNxTQ4cBbo3fh1JqKmQTCSzI21fo/qZSRpRfaIuq lhZA== X-Gm-Message-State: ALoCoQl61BRDOM4OrN16OVgP31XQ9r//MhpgqOKyfNXsb1QQz1qybgLLxkyAJOLSuqY2cU3qZ5vq MIME-Version: 1.0 X-Received: by 10.152.87.72 with SMTP id v8mr1246608laz.124.1438130028677; Tue, 28 Jul 2015 17:33:48 -0700 (PDT) Received: by 10.112.92.103 with HTTP; Tue, 28 Jul 2015 17:33:48 -0700 (PDT) In-Reply-To: <55B686EA.9030003@agliodbs.com> References: <55B686EA.9030003@agliodbs.com> Date: Wed, 29 Jul 2015 09:33:48 +0900 Message-ID: Subject: Re: Fwd: Publishing PG docs From: Kisung Kim To: Josh Berkus Cc: pgsql-docs@postgresql.org, rnd , =?UTF-8?B?6rCV7LKg7Iic?= Content-Type: multipart/alternative; boundary=001a11c364108025fd051bf8bd50 X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --001a11c364108025fd051bf8bd50 Content-Type: text/plain; charset=UTF-8 Dear Josh Berkus Thank you for your reply. We are translating the PostgreSQL documentation into Korean now and willing to contribute the results to the community. And it will be also a big pleasure if we can translate the error messages and contribute to the community. Can you give some advises about how we can start it? Finally, our company has many developers who are analyzing the PostgreSQL source code and we hope to contribute to the community by developing or patching the engine in near future as well as the translation work. We hope to keep the contact with the core team and to contribute the community in many ways. Thank you. (C)Bitnine, Kisung Kim, Ph.D https://sites.google.com/site/kisungresearch/ E-mail : kskim@bitnine.co.kr Office phone : 070-4800-3321 Mobile phone : 010-7136-0834 Fax : 02-568-1332 2015-07-28 4:30 GMT+09:00 Josh Berkus : > Mr. Kim, > > > We are a postgreSQL company in South Korea. > > As a one of our efforts to spread postgreSQL in our country, > > we plan to publish the Korean version of the postgreSQL documentation as > > a printed book > > via Acorn publisher(which is one of the biggest IT publisher in Korea). > > > > But we think that we should check and solve some licensing issues > > with regards to the copyrights of the PG docs. > > > > We will translate the PG docs to the Korean language, and publish the > > translated book. > > And Acorn publisher will sell the books commercially, > > which means that they will seek to make a commercial incomes by selling > > the books. > > > > Is there any issues with selling the translated book commercially? > > We know that the English version was sold by Furtus.com (Is it alive?). > > Any body who is concerned to this issue, please, let us know and give > > some helps. > > The documentation is licensed as open source, under the PostgreSQL > license. As long as you include a copy of the license in the book, > printing it and selling it is perfectly legal. > > There's also the issue of using the PostgreSQL trademark. While this > use of the trademark (on a copy of the documentation) is explicitly > allowed within the Trademark Policy > (https://wiki.postgresql.org/wiki/Trademark_Policy) you can get a > specific authorization by emailing the PostgreSQL Core Team > (pgsql-core@postgresql.org). > > Finally, if you're doing this: how about some help translating the > PostgreSQL documentation and error messages into Korean? We could > really use it. > > -- > Josh Berkus > PostgreSQL Experts Inc. > http://pgexperts.com > --001a11c364108025fd051bf8bd50 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear Josh Berkus

Thank you for your rep= ly.

We are translating the PostgreSQL documentatio= n into Korean now=C2=A0

and willing to contribute = the results to the community.

And it will be also = a big pleasure if we can translate the error messages and contribute to the= community.

Can you give some advises about how we= can start it?

Finally, our company has many devel= opers who are analyzing the PostgreSQL source code

and we hope to contribute to the community by developing or patching the e= ngine in near future

as well as the translation wo= rk.

We hope to keep the contact with the core team= and to contribute the community in many ways.

Tha= nk you.




=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0


(C)Bitnine, Kisung Kim, Ph.D
https://sites.google.= com/site/kisungresearch/
E-mail :=C2=A0kskim@bitnine.c= o.kr
Office phone=C2=A0: 070-4800-3321
Mobile phone :=C2=A0010-71= 36-0834
Fax : 02-568-1332


2015-07-28 4:30 GMT+09:00 Josh Berkus <josh= @agliodbs.com>:
Mr. Kim,
> We are a postgreSQL company in South Korea.
> As a one of our efforts to spread postgreSQL in our country,
> we plan to publish the Korean version of the postgreSQL documentation = as
> a printed book
> via Acorn publisher(which is one of the biggest IT publisher in Korea)= .
>
> But we think that we should check and solve some licensing issues
> with regards to the copyrights of the PG docs.
>
> We will translate the PG docs to the Korean language, and publish the<= br> > translated book.
> And Acorn publisher will sell the books commercially,
> which means that they will seek to make a commercial incomes by sellin= g
> the books.
>
> Is there any issues with selling the translated book commercially?
> We know that the English version was sold by Furtus.com (Is it alive?)= .
> Any body who is concerned to this issue, please, let us know and give<= br> > some helps.

The documentation is licensed as open source, under the PostgreSQL license.=C2=A0 As long as you include a copy of the license in the book, printing it and selling it is perfectly legal.

There's also the issue of using the PostgreSQL trademark.=C2=A0 While t= his
use of the trademark (on a copy of the documentation) is explicitly
allowed within the Trademark Policy
(https://wiki.postgresql.org/wiki/Trademark_Policy<= /a>) you can get a
specific authorization by emailing the PostgreSQL Core Team
(pgsql-core@postgresql.org= ).

Finally, if you're doing this: how about some help translating the
PostgreSQL documentation and error messages into Korean?=C2=A0 We could
really use it.

--
Josh Berkus
PostgreSQL Experts Inc.
http:= //pgexperts.com

--001a11c364108025fd051bf8bd50--