Re: Russian translations

On Mon, Aug 15, 2016 at 1:40 PM, Ivan E. Panchenko <
i(dot)panchenko(at)postgrespro(dot)ru> wrote:

> Dear colleagues,
>
> 15.08.2016 12:59, Magnus Hagander пишет:
>
>
>
> On Mon, Aug 15, 2016 at 11:06 AM, Oleg Bartunov <obartunov(at)gmail(dot)com>
> wrote:
>
>> On Mon, Aug 15, 2016 at 11:55 AM, Magnus Hagander <magnus(at)hagander(dot)net>
>> wrote:
>> >
>> >
>> > On Mon, Aug 15, 2016 at 10:48 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> >>
>> >> On Wed, Aug 10, 2016 at 8:59 PM, Stefan Kaltenbrunner
>> >> <stefan(at)kaltenbrunner(dot)cc> <stefan(at)kaltenbrunner(dot)cc> wrote:
>> >> > On 08/07/2016 12:27 PM, Pavel Luzanov wrote:
>> >> >> Please, consider this path to include reference to Russian
>> translation
>> >> >> in the docs page: https://www.postgresql.org/docs
>> >> >>
>> >> >> Now it really patch for git://git.postgresql.org/git/pgweb.git
>> >> >> repository.
>> >> >
>> >> > commited - should show up on the website soon.
>> >>
>> >> You realise this sets a new precedent in that we're linking to a
>> >> commercial website for a translation of our docs? All the existing
>> >> ones are non-commercial community sites.
>> >>
>> >> I'm not saying I object to that (I don't, as long as the translation
>> >> is good, and similar expectations are held of the site as are held to
>> >> those offering packages), but others may feel differently and not
>> >> realise what just happened.
>> >
>> >
>> >
>> > I also notice that the first link on the page goes to the postgres pro
>> > distribution rather than the community one. And the text on the linked
>> page
>> > pitches a sales contact for postgres pro.
>> >
>> > I see no major problem having it linked on the postgres pro site
>> (though I
>> > would prefer it to be a non-profit site, but it's not that important),
>> but I
>> > would ask for a landing-page that we link to that only has the community
>> > docs in it directly, and that does not have a sales pitch on it.
>> >
>> > Also, if google translate is correct, it specifically says you can't
>> use it
>> > for commercial use. Would it be possible to add a clarification of what
>> that
>> > means? All our other documentation is freely available for use. Again,
>> there
>> > is no problem with it not being that -- but defining what it refers to
>> is
>> > probably a good idea (e.g. is it OK to use it by somebody who provides
>> > PostgreSQL training in Russian, and just not OK if they want to re-sell
>> it,
>> > print it, or something like that, or is that kind of use also covered)?
>> > (This might be covered in the Russian text and missed in the
>> translation so
>> > if so, just clarify the translation for the list, please).
>>
>> We all are open to suggestion, let's discuss the requirements to
>> translation.
>>
>> 1. The link should goes to the page with translated community versions
>>
> Something like this: https://postgrespro.ru/docs/postgresql
>
> 2. That page should be commerce-free and contains links to the
>> original documentation
>>
> Commerce-free... How free ? We would like to keep some main navigation
> menu (may be, in a reduced form) with its links about products and services
> etc.
>

I see no problem keeping the navigation menu. If we keep the commercial
information off the page itself, having itin the menus is fine (compare to
for example the EDB download pages)

> 3. All documentation should be provided without any restrictions and
>> for free. That should be directly stated.
>>
> Presently, we want to restrict the commercial use of the Russian
> translation. It means that the text is not BSD-licensed, and cannot be
> freely included in any commercial products. Magnus, do you consider this
> acceptable in the sense of your comments?
>
>
I don't have a problem with such restrictions, but I think it would be good
to clarify what it exactly means.

For example, can a russian speaker use the documentation if he's giving
postgresql training? Does it make a difference if he prints the
documentation and uses it vs uses it online?

//Magnus