LPGL functions in Reactos that are stub in Wine

hippy hip exspasticcomics at yahoo.com
Mon Sep 4 15:14:48 CDT 2006


> I'm afraid it's the other way around at this
> point - the burden of proof is on ReactOS to show
> that their code is clean :-(

A)-no offense, but this sounds like something SCO
would say. if you got something (from reactOS current
that is already audited..) that you can prove is
dirty- please due so. people need facts. 


> Until ReactOS has been given a clean bill of
> health by an outside auditor, ReactOS developers
> are fairly restricted in how they can help Wine;
> posting bug reports against Wine may be about the
> best they can do.
> - Dan

B) i agree with the outside auditor thing. at least
before final version comes out. what they're doing is
'fringe' enough that they need to be able to back up
the 'cleanness' of their code in a major way. though i
do for one believe their internal audit is real- but i
agree an outside audit at some time would be much
better.

C) if wine's offical policy on reactos is to not
except contributions from them until a complete audit
is done on them by an outside source- that's fine.
pretty hardline- but absolutely fine. though- there is
a difference between making accusations & having a
policy. the first ends up dragging reactos' name
through the mud, & -in turn, if they get a clean bill
of health will end up dragging wine's name though the
mud & will not do anyone any good in the end. the
second protects everyone and leaves room for a future.

both wine & reactos are great projects & if done
correctly will have a huge impact on things in the
future. but the direction these conversation seem to
be taking doesn't help anyone.

i think you just need a policy.

(cheerleading all the way... lol)  



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 



More information about the wine-devel mailing list