Just a quick report from LinuxWorld London. We've just finished the first day of the exhibition, lots of interest. What surprised me a bit was that the general awareness about the project was somewhat lower than last year in Frankfurt. I guess that 80-90% of the people we spoke last year had already heard about the project, that percentage was a lot lower here (more around 30%).
Another pleasant surprise was the stability of the system. We ran it on an old laptop with a few applications: Quake 1, WinZip, IrfanView, AbiWord. On demand we showed some other apps like regedit, notepad, task manager. The system froze one time when a visitor played around with it, other than that no problems at all. Not a single kernel crash. We had to Tab-K to force a kernel check to show the BSOD to a visitor. I say let's bring out r18189 (I think...) as 0.2.8 (j/k).
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
Ge van Geldorp.
Hi Ge
Thanks for the report! Who else is representing ReactOS besides yourself? In a way, it's a good thing that you're reaching so many people that haven't heard of the project -- this means that the conference will actually pay off in a bigger way.
Also great to hear how stable the system is; a really great testament to our developers!
Cheers Jason
On 10/5/05, Ge van Geldorp gvg@reactos.org wrote:
Just a quick report from LinuxWorld London. We've just finished the first day of the exhibition, lots of interest. What surprised me a bit was that the general awareness about the project was somewhat lower than last year in Frankfurt. I guess that 80-90% of the people we spoke last year had already heard about the project, that percentage was a lot lower here (more around 30%).
Another pleasant surprise was the stability of the system. We ran it on an old laptop with a few applications: Quake 1, WinZip, IrfanView, AbiWord. On demand we showed some other apps like regedit, notepad, task manager. The system froze one time when a visitor played around with it, other than that no problems at all. Not a single kernel crash. We had to Tab-K to force a kernel check to show the BSOD to a visitor. I say let's bring out r18189 (I think...) as 0.2.8 (j/k).
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
Ge van Geldorp. _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Jason Filby wrote:
Hi Ge
Thanks for the report! Who else is representing ReactOS besides yourself? In a way, it's a good thing that you're reaching so many people that haven't heard of the project -- this means that the conference will actually pay off in a bigger way.
Also great to hear how stable the system is; a really great testament to our developers!
Cheers Jason
Hi Jason, It was Ge and myself who were representing the project in London. The second day went just as well as the first, and we now have some _VERY_ exciting news.
However, I'll wait until Ge is back before anything is mentioned on the mail list :)
Regards, Ged.
Not a single kernel crash. We had to Tab-K to force a kernel check to show the BSOD to a visitor. I say let's bring out r18189 (I think...) as 0.2.8 (j/k).
That's wonderful to hear! Well, if we follow the general 3 month per release "rule" we sometimes use, we will be due for a release in another month. I would like to fork this one early if possible. ;0)
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
Awesome!
WD
-- <arty> don't question it ... it's clearly an optimization
New release and me going away for a long voyage.
Thus said. Last month, I had spare internet access, but now I am back in my hometown Munich (SYSTEMS approaching) with plenty of inet again.
However I'm gogin on a big voyage at 11.11.2005 so I *can* make another relase (maybe the mentioned 0.2.8) but after ^ I'm not capable to do any further releases for a unkonwn period. Or, at least I'd experience too big problems. Thus I would like to find a new release manager to replace mine -- at least temproary. ( :-/ ) Maybe this 028-release is a good example to teach one. Anyone interested?
And: I still intend to improve and check-in a script to more-less automate the release process. Mine is currently a dangerous mix of win32-paths and bash scripting. I look forward to rewrite that in a real script language. I for my part like ruby, but you're welcome to convince me to use perl or python or merd or pike or brainfuck or whitespace or...
WaxDragon wrote:
Not a single kernel crash. We had to Tab-K to force a kernel check to show the BSOD to a visitor. I say let's bring out r18189 (I think...) as 0.2.8 (j/k).
That's wonderful to hear! Well, if we follow the general 3 month per release "rule" we sometimes use, we will be due for a release in another month. I would like to fork this one early if possible. ;0)
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
Awesome!
WD
-- <arty> don't question it ... it's clearly an optimization
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
And: I still intend to improve and check-in a script to more-less automate the release process. Mine is currently a dangerous mix of win32-paths and bash scripting. I look forward to rewrite that in a real script language. I for my part like ruby, but you're welcome to convince me to use perl or python or merd or pike or brainfuck or whitespace or...
Or just stick with make/rbuild and implement "make release" ;-) We are going to do a lot more releases in the future so why make it more difficult than that?
Casper
Mostly because I am not that common to ?make. Can I interactively read a value?
Casper Hornstrup wrote:
And: I still intend to improve and check-in a script to more-less automate the release process. Mine is currently a dangerous mix of win32-paths and bash scripting. I look forward to rewrite that in a real script language. I for my part like ruby, but you're welcome to convince me to use perl or python or merd or pike or brainfuck or whitespace or...
Or just stick with make/rbuild and implement "make release" ;-) We are going to do a lot more releases in the future so why make it more difficult than that?
Casper
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Better put the parts that can be put in rbuild in there. This will enable us to easier throw away GNU make one day.
Casper
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Robert Köpferl Sent: 8. oktober 2005 18:15 To: ReactOS Development List Subject: Re: [ros-dev] LinuxWorld report
Mostly because I am not that common to ?make. Can I interactively read a value?
Casper Hornstrup wrote:
And: I still intend to improve and check-in a script to more-less automate the release process. Mine is currently a dangerous mix of win32-paths and bash scripting. I look forward to rewrite that in a real script language. I for my part like ruby, but you're welcome to convince me to use perl or python or merd or pike or brainfuck or whitespace or...
Or just stick with make/rbuild and implement "make release" ;-) We are going to do a lot more releases in the future so why make it more difficult than that?
Casper
Ge van Düsseldorf wrote:
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
That's what you said last time...
-uQ
From: K McI
Ge van Düsseldorf wrote:
People were reacting very nicely. It was nice to see them picking up a flyer rather uninterestedly, start to read, and then suddenly turn back to watch the demo when they realized what the project was all about.
That's what you said last time...
Uhmm, I probably really mean it then :-)