Hello,
I want to share that I just had a pleasure to meet Jan "JaixBly" two
days ago in Sweden once again. We discussed many ReactOS-related topics,
and had fun with a newly delivered Raspberry Pi.
We've covered future plans for ReactOS development, testing
infrastructure, Samba integration, ARM processors support and many other
things.
A photo when we took a break from trying to get WiFi working in
Raspberry Pi and went outside: http://savepic.org/2407687.jpg
Best regards,
Aleksey Bragin.
Hi all,
My name is Simon and I am blind.
I saw in the archives that there was a short subject about
accessibility in ReactOS in 2010.
The NVDA screenreader was tested there and wasn't working.
Can someone tell me the current status of this?
Maybe there could be a collaboration between ReactOS devs and NVDA
devs to get accessibility in ReactOS?
NVDA can be found on www.nvda-project.org.
Daily snapshots can be found on
http://nvda.sf.net/snapshots/.index.html
Just some thoughts.
Greetings from Austria,
Simon
Fantastic!
Smss2 will be happy :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of ion(a)svn.reactos.org
Sent: 16 July 2012 00:42
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ion] 56906: [NTOSKRNL]: Implement support for session pool (not yet enabled) and session space (implemented and enabled, but nobody is calling the APIs yet). [NTOSKRNL]: Implement MmMapViewOInSess...
Author: ion
Date: Sun Jul 15 23:42:27 2012
New Revision: 56906
URL: http://svn.reactos.org/svn/reactos?rev=56906&view=rev
Log:
[NTOSKRNL]: Implement support for session pool (not yet enabled) and session space (implemented and enabled, but nobody is calling the APIs yet).
[NTOSKRNL]: Implement MmMapViewOInSessionSpace, MmUnmapViewInSessionSpace. Win32k needs to use these to we can test them.
Modified:
trunk/reactos/ntoskrnl/mm/ARM3/i386/init.c
trunk/reactos/ntoskrnl/mm/ARM3/miarm.h
trunk/reactos/ntoskrnl/mm/ARM3/pfnlist.c
trunk/reactos/ntoskrnl/mm/ARM3/pool.c
trunk/reactos/ntoskrnl/mm/ARM3/procsup.c
trunk/reactos/ntoskrnl/mm/ARM3/section.c
Hi,
I've noticed that the ROS-Diffs list (or rather the hook sending to it)
consistently fails on revisions that have special chars in their commit
message.
E.g. there is no message for r56846, r56844, r56763, r56754 etc.
(sorry Hermès :p)
This goes back as far as r23711 (August 2006), for which the archive
shows no message [1].
It apparently did work at some point because r20354 (December 2005) and
earlier seem to have ROS-Diffs messages [2] (although possibly because
special chars didn't make it into the mails' subjects).
Is there a chance this could be fixed?
And in the meantime, could I ask the devs to refrain from using special
chars? (don't know about you, but the missing messages are quite an
annoyance to me, as this is the most convenient platform for code
review)
Thanks!
-Thomas
[1] http://www.reactos.org/pipermail/ros-diffs/2006-August/thread.html
[2] http://www.reactos.org/pipermail/ros-diffs/2005-December/010731.html
July 2012 Meeting A Minutes
2012-07-05
19:00 UTC
dev.reactos.org, #meeting
Proceedings
===========
* Meeting started at 19:16 UTC by Aleksey Bragin.
* Point 0: CD/Product Store
* Point 1: Update/Team Plan
* Point 2: Website Update
* Point 3: Internet Declaration
Due to scheduling constraints by some participants, the question of a
team store and sale of ReactOS CDs was moved to be the first topic.
* Point 0
Ziliang Guo presented the question of CD sales and merchendise sales
in general. Amine Khaldi updated the team on the work he and others
have done to get storefronts up and going. The primary concern was a
lack of decent designs for the stores. Ziliang was tasked with
contacting graphic artists he knows in the community to see if this
can be remedied. The decision of what to do with the promo CDs was
left to Ziliang as well.
* Point 1
Aleksey Bragin stated that he intended to help with Jira integration
with the new site, which is necessary as a replacement for bugzilla.
He also hopes to help with making the build environment more user
friendly.
Olaf Siejka reported on a variety of regressions in freeldr and the
win32 subsystem that he wants fixed as they are blocking further
development and testing. Other developers asked for specific reports
to be assigned to them and reviewed whether they thought they knew the
cause of regressions.
Collaboration with the UniATA developer was also discussed, with
reports that upstream patches have been accepted and suggestions on
further work that can be done.
* Point 2
Danny Gotte was not present so this point was skipped.
* Point 3
Pierre Schweitzer presented the Internet Declaration
(http://www.internetdeclaration.org/freedom), a statement of beliefs
drafted by various groups that wish the internet to remain free of
censorship and ensure user privacy. Many other organizations have
signed onto it and Pierre asked whether the ReactOS Foundation should
also do so. This was put to a vote and passed with overwhelming
support.
* Other Decisions
Ziliang requested that all developers be added onto the public
relations mailing list. This was approved.
Meeting was closed at 20:38 by Aleksey Bragin
Minutes were prepared by Ziliang Guo
Hello!
I was away this week, so the meeting at the usual time got canceled.
I propose to conduct meeting next thursday, 5th of July. If someone
would not be able to make it - please email me.
Regards,
Aleksey Bragin.
Hello everyone!
I just got freeldr working properly (sort of) on the iPhone 4!
Currently, I use Apple's iBSS
(first stage DFU bootloader), with the go command patched to always branch to
0x41000000. 0x41000000 contains the actual LLB, which is relocated to
0x42000000.
The LLB will initialize the ReactOS loader console and ARM loader
block, which is sent
to FreeLoader, just like on Omap3/Zoom2MDK and Versatile/PB.
Time to get ramdisks working. :)
http://goput.it/uc5.jpg <- There's your picture.
-- winocm
Barring any last minute hiccups, we expect to have a meeting this
Thursday. I am sending out this email because we have a PR topic we need
to discuss and I would like as many devs present as possible, and
considering Aleksey is likely asleep by now, I felt we needed this out
before "tomorrow" to give people enough heads up. Aleksey can make a more
formal announcement with other agenda points if he has them.
Z