Hi all
According to our project's legal policy document, reverse-engineering
is allowed to study the internals of Windows, but cannot be used as
the basis to write code for particular functions.
What we haven't defined is the process of what happens when someone
suspects that our policy has been violated. I think now is a good time
to do that. I also don't think the offender - even if proven guilty -
should be kicked out of the project (at least not for a 1st time
violation). The code, however, should be removed and rewritten.
If we don't act on this then the problem will only fester and may be
the end of the project one day.
Hartmut: I think you need to come forward with your investigations
results as Steven asked. Whether or not you come back (I hope you do),
we can't ignore this.
Cheers
Jason
On 1/18/06, Steven Edwards <winehacker(a)gmail.com> wrote:
Can you list offending code with a list of svn
commits?
Thanks
--
Steven Edwards - ReactOS and Wine developer
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev