On Sun, May 17, 2009 at 6:20 AM, Daniel Reimer daniel.reimer@stud-mail.uni-wuerzburg.de wrote:
Xiaoming Gao wrote:
2009/5/17 magnus johnsson <magnusjjj@gmail.com mailto:magnusjjj@gmail.com>
... 2009/5/17 James Tabor <jimtabor.rosdev@gmail.com <mailto:jimtabor.rosdev@gmail.com>>: > Well, first off, you should stay away from the leaked source..... Just > keep up to date with the SDK and WDK. But, you can be a good wine > developer and work with them since you know linux. wine developers use > leaked source daily and rewrite it to look like linux source, so > you'll fit in nicely there. Excuse me? Don't go there. You should know better than to say things like that, even if it was a joke.
Joke, yes, a little one, maybe.....
Question should be, Where is the full discloser of the wine audit? Status on every file in the source with author information. When the wine audit started, there was a major wine rewrite going on with files moving about in the wine tree,,, very fishy stuff too.... Where is the accountability? Just Alexandre Julliard or Jeremy White?
So, in stating what I had posted, is it a joke, we really don't know. Until real data is posted by the SFLC we will not know. I guess we will see a patent treaty with wine and Microshaft before then.
See, they kept the focus on us the whole time, and since most of you have short memories, that is the one thing they count on.
But i'm just only interested in ReactOS,so i'll keep on caring it,and i think i can give some suggests although i can't develop it..
You can, but I only if you tell us what code parts of the leaked code you did look at. You will be excluded from this prts in ROS. The rest is open to be coded on by you.
No, it is a no starter, right out of the gate. He can not be part of this group.