Opensource World Conference (Malaga, 2010), is accepting papers for the meeting that is going to take place on 27/28 October.
"The Open Source World Conference (OSWC) is probably the most important European event related to open source technologies.
Following six editions of this conference organized by the regional governments of Andalusia and Extremadura in collaboration with the most important companies in the sector, this conference has become a unique event open to everyone interested in the field of software innovation, from users, social agents and developers, through to business leaders, investors and members of public administrations."
Andalusia and Extremadura governments are pushing quite hard toward the Opensource administration.They are working together to use just Opensource apps and OSes in their Universities and Administrations. Actually they have created some Opensource OSes as Guadalinex(a Linux distro) and some opensource organizations to push and support opensource ideas. In this conference companies and investors will meet, so maybe we can find some kind of Companies or Government support.
Projects, this year, will be elected by votes. Other projects are pushing quite hard.
So as this is not another OpenSource meeting but THE OpenSource meeting, I want you to push and vote. We made in Sourceforge Awards and we can do it again.
Creating an user takes less than 1 minute: http://www.opensourceworldconference.com/malaga10/?q=en/user/register
Vote "5-star" in this page(after Login): http://www.opensourceworldconference.com/malaga10/?q=node/953
I promise to make my best PR to find in this meeting any ReactOS opportunity.
If there is any, I will find it. :)
_________________________________________________________________
Accede a tu Hotmail en un solo clic ¡Descárgate Internet Explorer 8 y empieza a disfrutar de todas las ventajas!
http://www.ayudartepodria.com/
Hello,
A recent CMAKE commit has made me notice that a NOSWPAT option determines if FreeType hinting should be used or not. Please note that the Apple patent on the technology recently expired, and this option is not needed anymore, as hinting should always be enabled.
-r
Hi,
I'd like to announce that as of r48278, you can build a full x64 bootcd
(including rostests, not rosapps) from trunk.
That means from now on, I can quickly see when someone breaks 64 bit
compatibility: http://reactos.ath.cx:8081/waterfall
So please don't cast PVOID to ULONG ;-)
Regards,
Timo
PS: no, it doesn't boot to desktop
Hi
I'd like to propose a small change: converting freeldr into a PE file.
The current freeldr / setupldr are raw binaries, which makes them easy
to handle for the bootsector but it disqualifies them from proper
debugging with gdb. A solution is to convert them into PE format. As
there is no space to implement a real PE loader in the bootsector, the
image must not use a .bss section, this can easily be done with a linker
script.
I have this working in my WC.
With the result we can use gdb for debugging freeldr including symbols.
The only thing still to solve is how to remove rsym data from the files,
without stripping all symbols. Rsym data makes the file twice as big,
too big to be loaded in to real mode memory.
Any objections / suggestions?
Regards,
Timo
Hi all,
im visiting the compatibility database page frequently, and im still seeing
people testing applications against 0.3.1 ....
0.3.11 is too old currently, there have been tons of bugfixes, new features,
and overall changes that affect many applications since 0.3.11 release. Lots
of them have changed their behavior into ReactOS since those changes.
What i want to say is, compatibility with 0.3.11 is quite meaningful right
now, due to massive changes in ReactOS lately. Lets use HEAD revisions to
test new apps, and report bugs against it :)
cheers!
Jérôme,
Need to go through your commit list and check and see which ones need
to be pushed to the trunk. So far as I see (read), the changes look
good.
Thanks,
James
After Olaf's mentioning of increased buildtimes I'd like to throw 2
different, independent and major changes to our build process into
discussion. One is about rbuild and one is about the file layout. I'd
like to start with the rbuild related topic.
What I suggest only for consideration, is a move away from rbuild and
instead using CMake.
CMake is available for Windows and *nix, for Windows both as commandline
ans as a lightweight gui tool.
It is capable of translating a portable buildfile format into different
makefile formats, including nmake and project files for VS and
CodeBlocks. It seems incredibly fast compared to rbuild and probably
provides every feature we ever need. Although the syntax is a tiny bit
more complex than rbuild files, it's much better than writing makefiles.
Adding support for building with MSVC should be relatively easy. It's
not really a suggestion, as I'm not sure about all the details, but I
think it's worth reviewing and taking into consideration.
The second thing is about the file layout. I will post a seperate mail soon.
Regards,
Timo