<br><br>
<div><span class="gmail_quote">On 1/19/06, <b class="gmail_sendername">Steven Edwards</b> <<a href="mailto:winehacker@gmail.com">winehacker@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>On 1/19/06, Alex Ionescu <<a href="mailto:ionucu@videotron.ca">ionucu@videotron.ca</a>> wrote:
<br>> 1) Those magic sizes were calculated in my head and I didn't have time<br>> 2) This is not a matter of driver compatibility. The fast system call<br><br>In regards to points 1 and 2 your explanation can be left up to the
<br>other developers to decide. When Hartmut, Filip, Art, and every other<br>developer on irc/email says there is a problem I tend to believe them.<br>I think the kernel developers should decide if there are violations<br>
and remove any cod that is found to be offending. I think that if it<br>was all implemented in the methods you described then no, its not as<br>bad a violation as its made out to be. However its still a issue.<br><br>> 3) I find the idea of removing code that "Violates policy" ludicrous. No
<br>> one has the right to dermine if some piece of code violates policy or<br>> not, especially if the author writing it denies it. Only a judge or<br>> lawyer should be able to make that decision. Additionally, in this
<br><br>I guess we never should have reverted Jon Wilsons patches that were<br>copy/pasted from MSDN because they were just function prototypes and<br>not real code. No the same rules apply. What point is there in having<br>
rules if we don't hold to them?<br><br>> specific case, what could be done? The code is in SVN and even if<br>> rewritten it will 1) look the same, excpt "edx" would become "esi" and<br>> vice-versa 2) a judge would still argue that "hey, you had the previous
<br>> code in SVN for over a year, you've all been tainted and could've just<br>> as easily looked at it". Furthermore, such attitude might start<br>> devolving into a dangerous witchhunt. Don't like someone's code? Report
<br>> them and have it removed! This communist-era and fascist-era behaviour<br>> deeply scares me and reminds me of a country and regime which I fled. I<br>> do not want to see it happen, because it would slowly kill and rip apart
<br>> this project.<br><br>At the risk of pissing off another developer, I have to say it. Your<br>development methods and attitude have been doing that. Hartmut is<br>leaving because of code he feels is tainted by the methods you use.
<br>Ge' spends less and less time working on ReactOS because he can't deal<br>with your methods or behavior. Blight would not have been so pissed<br>off about you breaking KDB if you had not fucked up the formatting at<br>
the same time you "fixed" it so he could have at least followed the<br>code and tried to fix it or added a hack. He might not have even been<br>so pissed off had you given a damn and helped him fix it.<br><br>> These monthly Alex-bashings are starting to tire me very much and maybe
<br>> it's time I took an offensive position instead of a defensive one. I do<br>> not want to start naming names, but many of our developers have already<br>> violated our policy in different ways. If you actively start enforcing
<br>> it, then it will be my duty as an active developer to enforce it as<br>> well, meaning that hiding any information I have concerning other<br>> developers' violations would be considered as complicity, so I would be
<br>> legally bound to report them. In other words, this would mean that the<br>> project would lose half of its developers.<br><br>Now lets get down to it. Lets say even if you have not violated the<br>rules we agreed up and all of the developers are wrong about needing
<br>to revert some of your patches. I do not take well to threats. I do<br>not appreciate it, nor does anyone else. I do not want to work with<br>you any longer on this project. If you want to make threats, I suggest<br>you take your ball and go play somewhere else.
<br><br>> I am sick of being treated as the black sheep and the "example". This<br>> stops here. I have always been put in the spotlight for almost any<br>> action I took, and I've always taken steps to repair it. But these
<br>> public trials of guilt have passed a limit. Either start questionning<br>> everyone and treating every developer the same, or stop using me as a tool.<br><br>Stop doing things that drive developers away from this project. If you
<br>want to try and destroy this project out of some childish revenge then<br>come out, make your accusations and be done with it, otherwise play by<br>the rules.<br><br>I propose a vote on Hartmuts proposal depending on if he will stay
<br>with the project<br><br>Audit and rewrite code that is found to violate the IP Policy Doc<br>[X] Yes<br>[] No<br><br>--<br>Steven Edwards - ReactOS and Wine developer<br><br>"There is one thing stronger than all the armies in the world, and
<br>that is an idea whose time has come." - Victor Hugo<br><br>_______________________________________________<br>Ros-dev mailing list<br><a href="mailto:Ros-dev@reactos.org">Ros-dev@reactos.org</a><br><a href="http://www.reactos.org/mailman/listinfo/ros-dev">
http://www.reactos.org/mailman/listinfo/ros-dev</a><br></blockquote></div>
<div><br>Audit and rewrite!</div>
<div> </div>
<div>I founded San Diego ROS Users Group. We are Alpha testing on Real hardware.</div>
<div>If ROS becomes extinct we will become SD SkyOS UG.<br clear="all"><br>-- <br>David Johnson<br>Voice Talent<br><a href="http://www.davefilms.us">http://www.davefilms.us</a><br>DaveFilms Digital Media - Audio [TM]<br>
Producer , Writer,<br>Production Director/ Designer </div>