Looking at the ReactOS source

[Gijs Vermeulen]

Hi everyone,

Is it allowed to look at the ReactOS source for function definitions, for
example?
If so, in what ways is it allowed to use/look at the ReactOS source?
I tried to find an answer on the wiki, but didn't find one.

Kind regards,
Gijs

[Jan Havran]

Hi,

I do not see any reason why you could not look at the sources, since most of 
the DLL code in ReactOS is taken from Wine [1] under same licence.

But I am not a Wine dev, so I may be wrong.

[1] 
https://svn.reactos.org/svn/reactos/trunk/reactos/media/doc/README.WINE?view...

On 08. 11. 18 22:41, Gijs Vermeulen wrote:
> Hi everyone,
>
> Is it allowed to look at the ReactOS source for function definitions, for
> example?
> If so, in what ways is it allowed to use/look at the ReactOS source?
> I tried to find an answer on the wiki, but didn't find one.
>
> Kind regards,
> Gijs

[Gabriel Ivăncescu]

On Fri, Nov 9, 2018 at 1:07 PM Jan Havran <havran.jan(a)email.cz> wrote:
> Hi,
>
> I do not see any reason why you could not look at the sources, since most of the DLL code in ReactOS is taken from Wine [1] under same licence.
>
> But I am not a Wine dev, so I may be wrong.
>
> [1] https://svn.reactos.org/svn/reactos/trunk/reactos/media/doc/README.WINE?view...
>
> On 08. 11. 18 22:41, Gijs Vermeulen wrote:
>
> Hi everyone,
>
> Is it allowed to look at the ReactOS source for function definitions, for
> example?
> If so, in what ways is it allowed to use/look at the ReactOS source?
> I tried to find an answer on the wiki, but didn't find one.
>
> Kind regards,
> Gijs

Doesn't ReactOS use the GPL instead of LGPL? That might be
incompatible since it's one-way compatibility (i.e. LGPL->GPL is
allowed but not vice-versa). I don't know with certainty, but you
should definitely ask someone knowledgeable (ReactOS devs?).

Of course this applies if you look at ReactOS code itself not the one
pulled from Wine which should still be under LGPL, but what's the
point of looking at Wine code in ReactOS sources?

[Alexandre Julliard]

Gijs Vermeulen <gijsvrm(a)gmail.com> writes:
> Hi everyone,
>
> Is it allowed to look at the ReactOS source for function definitions, for example?
> If so, in what ways is it allowed to use/look at the ReactOS source?
> I tried to find an answer on the wiki, but didn't find one.

It's better to avoid looking at it. Some of the information was derived
using methods that are not considered safe for Wine.

-- 
Alexandre Julliard
julliard(a)winehq.org

[Austin English]

On Fri, Nov 9, 2018, 06:02 Alexandre Julliard <julliard(a)winehq.org wrote:
> Gijs Vermeulen <gijsvrm(a)gmail.com> writes:
> > Hi everyone,
> >
> > Is it allowed to look at the ReactOS source for function definitions,
> > for example?
> > If so, in what ways is it allowed to use/look at the ReactOS source?
> > I tried to find an answer on the wiki, but didn't find one.
>
> It's better to avoid looking at it. Some of the information was derived
> using methods that are not considered safe for Wine.
>
> --
> Alexandre Julliard
> julliard(a)winehq.org

For the case of function prototypes, would it be acceptable for a second
person to document it, so that the Gijs stays clean? E.g. if bug reporter
copy/pastes the declaration in the bug report without the implementation?

[Alexandre Julliard]

Austin English <austinenglish(a)gmail.com> writes:
> For the case of function prototypes, would it be acceptable for a
> second person to document it, so that the Gijs stays clean? E.g. if
> bug reporter copy/pastes the declaration in the bug report without the
> implementation?

It's better to find other sources of information.

-- 
Alexandre Julliard
julliard(a)winehq.org