Re: Fwd: Publishing PG docs

Поиск
Список
Период
Сортировка
От Tair Sabirgaliev
Тема Re: Fwd: Publishing PG docs
Дата
Msg-id etPan.55acdab9.7d9fe558.fd6@MacBook-Pro.local
обсуждение исходный текст
Ответ на Fwd: Publishing PG docs  (Kisung Kim <kskim@bitnine.co.kr>)
Список pgsql-docs
Hi,

The documentation has Copyright notice here: http://www.postgresql.org/docs/9.4/static/LEGALNOTICE.html
I’m not a lawyer, but basically it lists 3 paragraphs to be included in all copies, modified versions or other uses.
Though not sure how this applies to to ‘translations’..

-- 
Tair Sabirgaliev
Bee Software, LLP

On July 20, 2015 at 11:22:49, Kisung Kim (kskim@bitnine.co.kr) wrote:

Dear,

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.

Thank you, everybody.

Kisung Kim.

  

                                                                                                                                                       


(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


В списке pgsql-docs по дате отправления:

Предыдущее
От: Kisung Kim
Дата:
Сообщение: Fwd: Publishing PG docs
Следующее
От: Vignesh Raghunathan
Дата:
Сообщение: Possible mistake in Section 63.6 - 9.6devel Documentation