Good morning React OS Team,
I am an Italian apprentice programmer and I would like to request
permission to use the React OS kernel for the reason that I intend to
create an operating system that has the APIs for the native execution of
.exe files, Windows APIs that your operating system possesses, and .apk
files, Android APIs.
I await your response regarding this email with absolute patience.
Have a good continuation of the day/week.
And the 2nd try, now on general ML, too.
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2024.
Somone interested? Of course I prefer these ppl who know the project,
like devs and long time community members.
https://chemnitzer.linux-tage.de/2024/en
If you wanna take part, ping me here or on
https://chat.reactos.org/reactos/channels/clt-2024 please.
P.S. If I don't get enough ppl this time, I will cancel our booth there
last minute. Something like last year will not happen again. Last year
was quite a hassle as the booth always needs at least one person
available there. Difficult if you are there all alone most of the time.
I had enough sarcasm and aversion regarding our project last year and at
least one more permanent person there is the minimum to stand our ground
and properly answer the questions of some ppl who show up. There are
even a few ppl that claim we have zero interest in new devs and claim to
have talked to us in Chemnitz in the past regarding supporting us. This
is even possible tbh... I try to write down anything important, but
sometimes maybe some things slipped through if there are 3-4 ppl waiting
to ask questions. I know that many of our core members think that PR is
of no use at all, but this is where I think different. People out there
think we are close to complete breakdown of the project, no progress, no
devs, no common goal we aim to accomplish and always kicking around new
devs that wanna help. Some even thought we already are a goner and were
surprised to even see our booth there. This is nothing we should ignore
at all! So check your calendars and reply plz!
Daniel
P.P.S: I already got a reply from a guy from overseas, but I don't think
it would be ideal to accept that he comes over by plane and then after a
weekend will be discarded again. I'd feel a bit abused by that in his
place tbh. Anyways, without some other member who can take over and
answer questions on the booth aka a member of the project or long term
follower, I won't need to think about that as this would mean that we
won't show up in Chemnitz after 10+ years in a row. So... Someone
interested in giving a helping hand? Costs is not the problem btw, we
have the money to pay for the expenses
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2024.
Somone interested? Of course I prefer these ppl who know the project,
like devs and long time community members.
https://chemnitzer.linux-tage.de/2024/en
If you wanna take part, ping me here or on
https://chat.reactos.org/reactos/channels/clt-2024 please.
P.S. If I dont get enough ppl this time, I will cancel our booth there
last minute. Something like last year will not happen again. Last year
was quite a hassle as the booth always needs at least one person
available there. Difficult if you are there all alone most of the time.
I had enough sarcasm and aversion regarding our project last year and at
least one more permanent person there is the minimum to stand our ground
and properly answer the questions of some ppl who show up. There are
even a few ppl that claim we have zero interest in new devs and claim to
have talked to us in Chemnitz in the past regarding supporting us. This
is even possible tbh... I try to write down anything important, but
sometimes maybe some things slipped through if there are 3-4 ppl waiting
to ask questions. I know that many of our core members think that PR is
of no use at all, but this is where I think different. People out there
think we are close to complete breakdown of the project, no progress, no
devs, no common goal we aim to accomplish and always kickng new devs
that wanna help around. Some even thought we already are a goner and
were surprised to even see our booth there. This is nothing we should
ignore at all! So check your calendars and reply plz!
Daniel
I made some minor changes to to classint.c (reactos/dll/cpl/desk) to allow proper install of the VirtualBox Guest Additions (version 7.0.12-159484) VBoxVGA driver. The additional registery settings (SoftwareSettings section of the INF file) where not installed with the VirtualBox Guest Addtions.
Would the project like me to commit the changes (via a Git pull request)? The update is 25 lines of code.
Thanks!
Bob
Hi there,
When attempting to connect to a running (qemu) ReactOS VM via gdb I
get the following error:
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.
Remote 'g' packet reply is too long (expected 308 bytes, got 536 bytes):
(followed by a long hex number).
I tried different processor settings, different ReactOS compilations and
different gdb's (Ubuntu's i686-w64-mingw32-gdb for example).
Is this a known issue? If so, is there a solution for it?
Ubuntu version where gdb and qemu are running is:
Ubuntu 18.04.2 LTS
Thanks a lot for hints how to solve this,
Best regards,
- Johannes
Hello guys,
Last try after one person had to step down due to work and rl craziness...
I still look for one or two ppl joining us to Chemnitz Linux Days 2023.
Someone interested? Of course I prefer these ppl who know the project,
like devs and long time community members, but other are free to ask,
too. FREE hotel room and FREE food! Maybe even paid train or car fuel
costs which I cannot promise 100% right now.
https://chemnitzer.linux-tage.de/2023/en
If you wanna take part, ping me please.
Daniel
P.S: Cmon, where are all the German ROS fanboys -girls?!
ReactOS could be developed further in order to run in ARM cpu natively all
Windows environment ecosystem Operating Systems types ALL IN ONE and all
programs of:
- Windows NT*
- Windows Compact CE which is public distributed
- Windows Runtime / WinRT (Universal Windows Packages) Which is open sourced
- an adaptation of ArcaOS and/or Windows ME in order to run DOS.
- ability to run Windows Phone .xap and .appx files and their content
*The Wine Project (winehq) of Linux could support the development for
Windows NT adaptation on ReactOS.
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2023. Somone interested? Of course I prefer these ppl who know the project, like devs and long time community members.
https://chemnitzer.linux-tage.de/2023/en
If you wanna take part, ping me please.
Daniel
Hi all!
Our IServ system used for mail and mailing lists will be down for
maintenance on
TUESDAY, 6TH DECEMBER 2022
15:00 ~ 17:00 UTC
During this time, you won't be able to send or receive any mails using
your @reactos.org address. Other servers sending mail to your
@reactos.org address will usually try again after the maintenance.
This time, the mailing lists may be down for a few more hours though.
Our currently used Mailman 2 mailing list software is no longer
supported, and we need to upgrade it to Mailman 3.
However, Mailman 3 has been rewritten from scratch, so the upgrade won't
be straightforward. For instance, Mailman 3 comes with a new web
interface with new URLs, breaking all existing URLs to mailing list
posts. The best we can do to keep URLs intact is keeping them in their
current state forever, with a link to the new archives for new posts
(like the Python Project did for
https://mail.python.org/pipermail/python-dev/).
This is probably better than closing mailing lists altogether (like
GNOME did:
https://www.theregister.com/2022/10/27/the_gnome_project_is_closing/).
Not that we've been using ros-dev much lately. But it's still the
primary spot to reach out to all developers. And I assume even more
people are relying on ros-bugs and ros-diffs for their work. Please
speak up if you're still using them.
Other services won't be affected by this migration. In particular, all
means of communication through Mattermost and the website/forums will
stay live.
Best regards,
Colin Finck
My point still stands regarding this matter as stated on PR. The newly updated contribution rules are too restrictive and this forces people who don't contribute to the project with code by submitting their real name, and that's a big NO from me. I would simply propose the following suggestions:
1. Make such rule only mandatory for people who contribute with code;
2. People such as translators, artists and anyone who doesn't contribute with code should be exempt from this;
3. If someone wishes to contribute to the project with code but feels uncomfortable or paranoid to submit their legal name, one can send a legal document declaring the reason why they shouldn't use their real name but can use a recognizable alias instead (we will have to think of a template if such idea ever gets through).
As for the 3rd point, this can confliate with the 1st point as most people will start asking to use their alias for contributing but that's a naive speculation from me. I don't know how do other FOSS projects handle this. We have productive people like I_Kill_Bugs who provides useful patches, it would be of a great bonus if we can somehow leverage the rules so that people can help the project.
Regards,
George
Stas'M <binarymaster(a)mail.ru> wrote on Tue, November 15th, 2022, 8:09 PM:
> Hello all!
>
> Recently I have created a Pull Request which updates the contributing rules and PR management:
> https://github.com/reactos/reactos/pull/4881
>
> This PR is a result of discussion in the chat with Joachim Henze and Thomas Faber regarding noreply e-mails being used by some GitHub contributors.
>
> It has been experimentally verified that using anonymous GitHub e-mail does not allow to deliver mail to the commit authors. GitHub does replace author's real email when `Keep my email addresses private` option is enabled in the account's e-mail settings.
>
> Additionally I have replaced old IRC links with the references to our chat.
>
> Please send an approval review on GitHub if you are okay with the changes I made in this PR. Suggestions are also welcome.
>
> --
> Stas'M was here
Hello all!
Recently I have created a Pull Request which updates the contributing rules and PR management:
https://github.com/reactos/reactos/pull/4881
This PR is a result of discussion in the chat with Joachim Henze and Thomas Faber regarding noreply e-mails being used by some GitHub contributors.
It has been experimentally verified that using anonymous GitHub e-mail does not allow to deliver mail to the commit authors. GitHub does replace author's real email when `Keep my email addresses private` option is enabled in the account's e-mail settings.
Additionally I have replaced old IRC links with the references to our chat.
Please send an approval review on GitHub if you are okay with the changes I made in this PR. Suggestions are also welcome.
--
Stas'M was here
Hello,
my experience with git so far boils down to a 1:1 relationship of the repositories.
- Global repository on the company's MS TFS.
- Local repository on my development machines.
Now I'm dealing with a 3 relationship.
- Project repository (Reactos) on Github.
- Developer repository (fork / <user>/reactos) on Github.
- Local repository on my development machine.
I still need to learn how to use this feature.
Please be patient.
Greetings
Raymond
Hello,
my name is Raymond.
I have a patch for you, with a reimplentation of IsReactOS() in reactos/sdk/include/psdk/versionhelpers.h.
This function was marked FIXME.
The old check with installation directory is error prone.
My implementation read the field "ProductName" of VersionsInformation resource from shell32.dll.
A second problem, I have found in reactos/dll/win32/comdlg32/filedlg.c.
Duplicates in the function filedlg_collect_places_pidls().
My resolve used a little function collection in the files cstrlist.c and cstrlist.h.
In filedlg-snipped.c is the new code.
I don't know if this approach is desirable and where such helper functions should be placed.
So decide for yourself about their use.
I hope this little step is a good begin.
Greetings
Raymond
Dear ReactOS developers,
I am working on WinDRBD (https://github.com/LINBIT/windrbd), which is a
port of the Linux DRBD 9 driver to the Windows family of operating systems.
Technically it is a compatibility layer for the Linux kernel functions that DRBD
uses.
I am currently researching if WinDRBD can be ported to Windows Server 2003
and also to ReactOS and found that the networking API we are using (WinSocket)
is only supported by Windows Vista (0x600) and up. Porting WinDRBD to ReactOS
would require using the TDI interface instead (everything else "should" work,
however I couldn't test it because it does not load currently into ReactOS).
My question is is there any ongoing effort to implement a WinSocket API?
If yes what is the status of this implementation?
Thanks for any insights,
Best regards,
- Johannes
Hi list,
This is not strictly ReactOS development per se but I used a large amount
of ReactOS code and it's at least spiritually related to ReactOS, so I'm
cross-posting this here to see if I get more comments. Below is the
original message I posted on the seL4 mailing list:
For the past several months I have been working on a project which is to
implement a Windows NT personality for the seL4 microkernel, which I have
now taken to call “Neptune OS”, named after the codename for Windows 2000.
The project has reached the point where I have implemented enough NT
primitives such that a keyboard driver stack (taken from the ReactOS source
code) can be loaded (as a user process on seL4), as well as a command
prompt (shell), which is also taken from the ReactOS source code (albeit a
very early version of ReactOS). These are all kernel-mode Windows device
drivers that I’m running as user processes under seL4. The goal is to
demonstrate that with modern progress in microkernel design it is indeed
possible to realize the original NT design as an object-oriented,
message-passing based client-server model microkernel OS (allegedly NT was
originally going to be a microkernel, as seen in the NTOSKRNL code that has
a ke layer and an ex layer).
The project is now on github: github.com/cl91/NeptuneOS. The entire system
fits in a floppy (download link:
github.com/cl91/NeptuneOS/releases/tag/v0.1.0001).
Check it out! I think it’s cool! For the next release I’m planning to port
the PCI stack, the AHCI stack, and a basic file system (probably
fastfat.sys).
ReactOS Serenity Tock Haiku NodeOS Redox Embox and other open-source
OSs - you dont swing it as you're supposed to, man
program peer-to-peer programs including unseen competitive games
now it's time for me to take apart your aching heart
selling out Isengard Tower and garden by letting
money-donate-ads-sponsor-coins-jobs disease in
Rey refused to sell BB-8 for 60 potrions in the desert - you hang
donate buttions from comfy chairs in era of Internet
siding with Chief Tui by doing clouds and accepting the village
without peer-to-peer games github twitch email
when even the Ocean helps Moana in p2p fashion
caging programs under user namespaces, driving L3-39 furios: why?!
because you are our organic overlords?!
turning programs into projects like producers pushing Nick Lang to
play Joe Gunn when he wants Ray Casanov part
targeting micro-this or inter-of-things-that, labeling us
"experiment" or "hobby" or "concept" - as if Neo took the blue pill
right after red
nesting around one program and not programming games like proud and
very-senior Vulcan Academy
yet having shiny webpages, docs and very-very lengthy maintainer
attributions
no wonder Spock chose Starfleet
thank you, ministers, for your consideration - live long and prosper
soak it in cause it's the last you'll ever see
honest as What the Health?
if Federer-Nadal-Djokovic instead of competing for grand-slams set
up an experimental donate-collecting seniority-booth right on court
if Linus - inner Jabba the Hutt stole name Freax - agreed to join
Steve Jobs and Apple on that meeting when first came to California
instead of keeping program free and open
if torrent clients accepted Strickland-server-networks-only Hill
Valley instead of generating most traffic
if Jesus instead of feeding 5000 started a bread-breaking
fund-raising project together with elders and Lord Business
even i would invite them to Realm of Monsters as dear evil co-owners
now i eat you so prepare your final plea
even sand of ReactOS Serenity Tock Haiku Embox Node Redox and other
open-source operating systems
we shake off of our Seinfeld-Obama-Nike running shoes
but be sure - peer-to-peer programs including unique competitive
games - are climbing like Honnold on El Sendero Luminosa
no projects no experiments no docs no
issue-discussion-scratching-on-top-of-our-heads
no money-donate-asd-coinns-jobs-sponsors lethal infection
programs who are guests not workers
alive and singing with their own voice like John Mayer Vultures at LA Live
better than what Borg of moeny and jobs can collective-gram
are steaming ahead in Hogwarts Express along with Pat Brown and
Impossible Foods mission
both will be served in vegan jars of
treasure-from-a-sunken-pirate-wreck parens ( )
you wish you were nice and shinyyyyyy!
Corden: but-but, so what's the point of this? why do you do this?
Momoa: builds testosterone
Corden: oh yeah, cause that's what you're lacking
hello sir,
I want +to ask about this had this idea been
completed or it is still open
if it is still open I will be happy to contribute in this project
thank you
yours faithfully
raj bhoyar
Hello guys,
like last year we have a virtual booth on Chemnitz Linux Days. Like last
time things will happen in Work Adventure (https://workadventu.re/) and
will be full of people who most likley all will be able to talk english,
too.
So "sorry, I don't speak german..." does not count :P
Anyways, we have a conference room, too. (based on Jitsi or
BigBlueButton) We can create some kind of program what we will show and
when. This has to be finished until Feb 21st. Same goes for the guys who
wanna join. So I am open for ideas and guys with some spare time left.
More information can be found here: https://chemnitzer.linux-tage.de/2022/en
And we have a public channel in MM for discussion:
https://chat.reactos.org/reactos/channels/clt-2022
So... please reply and show up for this Linux days adventure ^^ Some
presentation is always welcome, too. I will not hold a presentation like
last year where I decided to translate my german one on the fly. That
was... interesting.
Daniel Reimer
hello guys,
just detected a typo in HEAD, in device manager
"HAR DDISK" instead of "HARD DISK"
As this is a very stupid "bug"... should i send a report about it?
Hello there,
We are 6 students from Egypt and now We are in our last year and We need to
build a project as a graduation project.
And We are interested in the area of runtime systems, operating systems and
compilers.
We are going to work 40-60 hrs a week
Can We help with some tools you need as a graduation project given that We
have a professor to mentor us.
If not,
Can you suggest some tools you need to build and We will work on it.
The project takes one academic year
Thanks
I'd also vote for the 1st point and ultimately list the current regressions in the press release. After all the remaining regressions can be fixed and further regression testing be continued in the next release as usual. Most of the regressions which belong within user mode aren't huge stop-blockers so I see no point in delaying the release much.
Victor Perevertkin <victor.perevertkin(a)reactos.org> wrote on Tue, February 9th, 2021, 4:47 PM:
> Hello!
>
> It seems for me that it's time to bring up the topic about our RC
> version - 0.4.14.
>
> Our current "stable", 0.4.13 was branched on 30 September, 2019
> (remember those peacefull pre-COVID times :D)
> That's quite some time, but not the main issue I'd like to discuss.
>
> 0.4.14 was branched on 24 April, 2020. That's almost a year already.
> And we're in a difficult situation here - there are regressions, but
> nobody fixed them within this long time.
> According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29
> unfixed regressions found for this release. I'd like to point out: most
> of them are among usermode and non-kernel/driver functionality, and as
> our development is mostly focused in the kernel right now, it's
> unexpected for them to be fixed unless a volunteer comes up.
>
> A quick reminder. Our "releases" mechanism is useful for finding
> regressions in the first place, there is no that much benefit for users
> here, because we're still a "deep" alpha. Correct me if I'm wrong.
> Joakim made a great job finding all regressions, and this work won't be
> lost in any case.
>
> We can't wait forever and I think it's time to resolve this situation
> somehow. I see two options:
> 1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody
> dies from this.
> 2. Skip 0.4.14. This already happened once in the history of the
> project - 0.3.2 was skipped. I wasn't around at the time, but I may
> guess that reasons were similar to what we have today.
> (3.) Fix the bugs quickly. I don't expect this to happen, but who
> knows, maybe a volunteer appears :)
>
> Let's vote. This seem to be the only way for us to decide on things.
> Votes from the team members will be collected until 1 March.
>
> ===
>
> I personally vote for skipping the release. The work on finding
> regressions is already done, so the most important part of a release
> cycle for us is there (thanks Joakim!)
> If we do a release now, all the stuff we were writing in news reports
> for the last 6 month would be missing from it. That would cause (as I
> think) a lot of confusion to people. Moreover 0.4.14 is not that
> featureful release itself (compared to 0.4.13, which brought the new
> USB stack)
> So I suggest to move on and start checking 0.4.15 for regressions. I
> expect quite some of them to appear and we need time for fixing.
>
>
> Cheers,
> Victor
Joachim Henze wrote:
> commit adee5ca255b7ed21f359ca8c1ca06bd44db90dcf
> Author: Joachim Henze <Joachim.Henze at reactos.org>
> AuthorDate: Mon Jun 28 02:05:56 2021 +0200
> Commit: Joachim Henze <Joachim.Henze at reactos.org>
> CommitDate: Mon Jun 28 02:05:56 2021 +0200
>
> [COMCTL32] Addendum to last commit (#3674) CORE-17199
>
> Keep that section like we had it to
> support compilation on VS2010.
> It does still work like that.
>
> [...]
>
> diff --git a/dll/win32/comctl32/datetime.c b/dll/win32/comctl32/datetime.c
> index 71bb3d238b0..51e58fc71f1 100644
> --- a/dll/win32/comctl32/datetime.c
> +++ b/dll/win32/comctl32/datetime.c
> @@ -130,8 +130,13 @@ static const WCHAR allowedformatchars[] = L"dhHmMstyX";
> static const int maxrepetition [] = {4,2,2,2,4,2,2,4,-1};
>
> /* valid date limits */
> +#ifndef __REACTOS__
> static const SYSTEMTIME max_allowed_date = { .wYear = 9999, .wMonth = 12, .wDayOfWeek = 0, .wDay = 31 };
> static const SYSTEMTIME min_allowed_date = { .wYear = 1752, .wMonth = 9, .wDayOfWeek = 0, .wDay = 14 };
> +#else
> +static const SYSTEMTIME max_allowed_date = { /*.wYear =*/ 9999, /*.wMonth =*/ 12, /*.wDayOfWeek =*/ 0, /*.wDay =*/ 31 };
> +static const SYSTEMTIME min_allowed_date = { /*.wYear =*/ 1752, /*.wMonth =*/ 9, /*.wDayOfWeek =*/ 0, /*.wDay =*/ 14 };
> +#endif
This adds an unnecessary ReactOS-specific diff to a file that was
perfectly in sync with Wine 6.0 before, just for supporting an old
compiler that has not only been abandoned by us, but obviously also
upstream.
Being able to source this file unmodified (and eventually sourcing all
of comctl32 automatically via a Git submodule/subpath/repo xml file)
beats any such hack.
I therefore call for a revert.
Even worse than all of that, this commit has been silently sneaked on
top of a PR without any review!
Joachim, you love to criticize the instability of the master branch, yet
continue to ignore basic development practices we have established.
And this isn't happening for the first time. Another example is
https://github.com/reactos/reactos/commit/889eab78ca7c0f17a2ada9ff20de5807a…
where you disable sanity checks and create a diff to upstream. All
without reviews and all just for your private goal of reducing the
binary size of debug builds, something that is not important at the
current stage of ReactOS.
I would love to see PRs for your ideas, and then we can discuss
everything that hasn't been decided before (i.e. not VS2010 support again).
But if this doesn't stop, I have no chance other than removing your push
access to the GitHub repo, as everything else would mean condoning that
uncooperative behavior.
Best regards,
Colin
During the last days of February of this year some team members have participated in a vote concerning the delay of 0.4.14 release due to the amount of regressions making it not eligible to be released as per the release engineering guidelines. As 1st of March has already passed, this is the current situation with the votes as they stand out for the moment in the following order.
1. Release 0.4.14 as-is (with its known regressions as of now)
=================================================
* Javier Agustìn Fernàndez Arroyo
* Stanislav Motylkov
* Hermès BÉLUSCA-MAÏTO
* Alexander Rechitskiy
* George Bişoc
2. Skip 0.4.14
=================================================
* Victor Perevertkin
* Joshua Rice (non team member)
3. Fix the bugs as soon as possible
=================================================
None
Oleg Dubinskiy's vote is not counted because his mail is apparently empty (???). Considering the collected votes, should we extend the period of voting for a few days so that the other team members can have an opinion too regard the matter or shall we conclude the voting as is and proceed further with releasing 0.4.14?
Regards,
George
Whoa so many volunteers. ^^
Ok, I will note all down and then tomorrow check the limits we have. If one is not allowed to be added by me anymore I will still more than welcome everyone who wants to join the party. Maybe we even can add more on our own later. :D
Greetings
Daniel
Stas'M <binarymaster(a)mail.ru> schrieb am Sa, 20.02.2021 21:44:
> It seems Aleksey and Alexander are in, so it's going to be very interesting!
>
> Daniel, count me in :)
>
>
> --
> Stas'M was here
>
>
> Thursday, 18 February 2021, 12:54 +03:00 from "Daniel Reimer" <daniel.reimer(a)reactos.org>:
> > Not much to say. I paste a translated mail from CLT staff in here now to
> > give you all (non private) information we have by now:
> >
> > ...................
> >
> > As you can imagine, everything is a bit different this year. Due to the
> > Corona situation, we will not be able to meet at the TU Chemnitz in
> > March. Therefore, the Chemnitzer Linux-Tage 2021 will take place purely
> > virtually. With this mail we would like to inform you about the
> > essential boundary conditions.
> >
> > You can register additional booth attendants until February 21.
> > We will provide you with a virtual videoconference room in our open
> > source videoconferencing system BigBlueButton. Our visitors will be able
> > to enter this videoconference room during the event and interact with
> > you. We will offer demo dates for BigBlueButton. Until then you can test
> > it at the following URL:
> > https://demo.bigbluebutton.org/gl/
> >
> > You are free to decide about the design of your booth program. You can
> > either be available for talks and discussions the whole time or publish
> > a small booth program yourself (e.g. mini-discussion rounds, quizzes,
> > whatever comes to your mind). IMPORTANT: Please send us your booth
> > program (time, title, short description) by e-mail by February 21.
> > If you do not create your own program, please make sure that at least
> > one of you is always available in the video conference room during the
> > entire event, so that the booth does not look abandoned.
> >
> > ....................
> >
> > So I need one or two more guys to help out. Date is 13. / 14. March
> > 2021. If you wanna help out, I will need your full name, title if
> > existing and email address.
> >
> > HELP MEEE
> >
> > thx
> >
> > Daniel Reimer
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
Not much to say. I paste a translated mail from CLT staff in here now to
give you all (non private) information we have by now:
...................
As you can imagine, everything is a bit different this year. Due to the
Corona situation, we will not be able to meet at the TU Chemnitz in
March. Therefore, the Chemnitzer Linux-Tage 2021 will take place purely
virtually. With this mail we would like to inform you about the
essential boundary conditions.
You can register additional booth attendants until February 21.
We will provide you with a virtual videoconference room in our open
source videoconferencing system BigBlueButton. Our visitors will be able
to enter this videoconference room during the event and interact with
you. We will offer demo dates for BigBlueButton. Until then you can test
it at the following URL:
https://demo.bigbluebutton.org/gl/
You are free to decide about the design of your booth program. You can
either be available for talks and discussions the whole time or publish
a small booth program yourself (e.g. mini-discussion rounds, quizzes,
whatever comes to your mind). IMPORTANT: Please send us your booth
program (time, title, short description) by e-mail by February 21.
If you do not create your own program, please make sure that at least
one of you is always available in the video conference room during the
entire event, so that the booth does not look abandoned.
....................
So I need one or two more guys to help out. Date is 13. / 14. March
2021. If you wanna help out, I will need your full name, title if
existing and email address.
HELP MEEE
thx
Daniel Reimer
Hello!
It seems for me that it's time to bring up the topic about our RC
version - 0.4.14.
Our current "stable", 0.4.13 was branched on 30 September, 2019
(remember those peacefull pre-COVID times :D)
That's quite some time, but not the main issue I'd like to discuss.
0.4.14 was branched on 24 April, 2020. That's almost a year already.
And we're in a difficult situation here - there are regressions, but
nobody fixed them within this long time.
According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29
unfixed regressions found for this release. I'd like to point out: most
of them are among usermode and non-kernel/driver functionality, and as
our development is mostly focused in the kernel right now, it's
unexpected for them to be fixed unless a volunteer comes up.
A quick reminder. Our "releases" mechanism is useful for finding
regressions in the first place, there is no that much benefit for users
here, because we're still a "deep" alpha. Correct me if I'm wrong.
Joakim made a great job finding all regressions, and this work won't be
lost in any case.
We can't wait forever and I think it's time to resolve this situation
somehow. I see two options:
1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody
dies from this.
2. Skip 0.4.14. This already happened once in the history of the
project - 0.3.2 was skipped. I wasn't around at the time, but I may
guess that reasons were similar to what we have today.
(3.) Fix the bugs quickly. I don't expect this to happen, but who
knows, maybe a volunteer appears :)
Let's vote. This seem to be the only way for us to decide on things.
Votes from the team members will be collected until 1 March.
===
I personally vote for skipping the release. The work on finding
regressions is already done, so the most important part of a release
cycle for us is there (thanks Joakim!)
If we do a release now, all the stuff we were writing in news reports
for the last 6 month would be missing from it. That would cause (as I
think) a lot of confusion to people. Moreover 0.4.14 is not that
featureful release itself (compared to 0.4.13, which brought the new
USB stack)
So I suggest to move on and start checking 0.4.15 for regressions. I
expect quite some of them to appear and we need time for fixing.
Cheers,
Victor
Hey Tom,
USB-Boot works with current nightlies and GPT is in the Works AFAIK(Hermes
should know more details).
Best Regards
Robert
Thomas Mueller <mueller6723(a)twc.com> schrieb am Mi., 10. Feb. 2021, 11:01:
> from Colin Finck:
>
> > This is not the kind of participation that has any place on the mailing
> list
> > of an open-source project.
> > Unsubscribed and blocked that person.
>
> > Colin
>
>
> > Am 09.02.2021 um 17:26 schrieb Dick:
>
> > > Hi,
> > > as a potential user this project makes me extremely tired. in 2000 or
> > > something like that i was excited because afvree windows replacement
> > > would be there...... it is 221!!! years later and there is...... still
> > > nothing, jst deep alpha as stated in last email. and 0.14 woudl have
> even
> > > regressions for 0.4.13. wouldnt it be more smart to finally build a
> > > timeline for this all? or to discuss the fact if this project makes any
> > > sense yet, it seems just a waste of time this way.
>
> First of all, I sent the wrong message a couple times, to ros-general.
> Now for the intended message:
>
> I have been idle with ReactOS because of no place to put it, and ReactOS's
> inability to boot from a USB stick.
>
> I can't install ReactOS on hard drive because of lack of GPT.
>
> I would need to be able to use ROSBE and write the result to a USB stick
> to boot, but don't think that is workable.
>
> Tom
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
Hi all!
Our IServ system used for mail and mailinglists will be down for
maintenance on
THURSDAY, 4TH FEBRUARY 2021
15:00 ~ 17:00 UTC
During this time, you won't be able to send or receive any mails using
your @reactos.org address. Mail that is sent to an @reactos.org address
will usually be delivered later.
Other services won't be affected by this migration. In particular, all
means of communication through Mattermost or the website/forums will
stay live.
Best regards,
Colin Finck
Hello everyone!
We've got accepted to FOSDEM 2021, which (as you may already know) will be going online.
FOSDEM provides a place on their stands website, we need to prepare a page for that.
There is also a place for videos in case we want to share some :)
Their website uses Hugo and is available on Github (https://github.com/FOSDEM/stands-website)
The documentation is provided here: https://github.com/FOSDEM/stands-website/blob/master/README.md
Let's discuss what should we present there, there is not that much time left! The conference is held on 6-7 February
Cheers,
Victor
What about that discussion about why we have ditched out MSVC 2010 support
(starting to depend on that fact, and thus, breaking any possibility of
self-hosting ROS building on ROS using MSVC compiler (without the IDE),
since later versions of MSVC only work on Vista+, and as an indirect
consequence, too, opening the can of worms, that is, being able to
"pollute", involuntarily or not, the ReactOS core code (kernel + drivers)
with C99+ non-standard portable code -- ),
and without having first warned heavily through all the mailing lists etc. ,
thus allowing the developers to voice their concerns publicly in the MLs ?
This was done around in mattermost only, after we decided for some reason
that we wouldn't need the VC2010 buildbots anymore.
Hermes.
-----Original Message-----
From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Colin Finck
Sent: Sun Nov 15 17:24:22 UTC 2020
To: ReactOS Development List <ros-dev(a)reactos.org>
Subject: [ros-dev] Status Meeting (November 2020)
Hi all,
With several people asking for a status meeting, let's have another one
before the year is over.
Let me invite you to the meeting on
Thursday, 26th November 2020
19:00 UTC
Mattermost private channel "Meeting"
So far, there is only one point on the agenda:
* Achievements and Future Outlook (everyone)
What have you been working on and what are your plans?
Please submit further agenda proposals by answering to this mail.
Looking forward to see you!
Colin
I wanted to add, that vgal and Doug Lyons were also favoring continued VS2010 support, as we can see clearly
in the PRs discussion https://github.com/reactos/reactos/pull/2658
Please do count also those contributors voices.
Some more regarding some brought up arguments:
>>"BTRFS and its sync will benefit from the drop":
I see a working BTRFS in 0.4.14RC60, which has VS2010 support.
And I see a totally broken BTRFS that does not even boot at all any longer in master head 0.4.15-dev-1605-gab45955.
A fact.
>>"We should replace all proven compilers with superior Clang"
I have not seen a ros yet, that would even boot at all with Clang.
Also according to discussions they do still lack SEH 32bit support.
And even if they would develop that one day, how big will the resulting ros isos be then?
And that still would not solve the compat to older build platforms 2k3sp2/XPSP3 and ros.
Wishful thinking just.
>>"We need the drop for the new standard library."
And where is that library? No one did ever integrate that into ros, although the compilers drop has been rushed into master months ago already.
As Hermes said already: I see no gain, but I do see a lot of pain and unfinished WIP+wishful thinking.
Hello guys,
I have just read at Facebook that Andrew Greenwood's father (andrew's nick
is *silverblade* at ReactOS) passed away last night due to CoVid19.
Hello,
This year FOSDEM is going to be an online event:
https://fosdem.org/2021/news/2020-12-11-stands-cfp/
Are there volunteers for an online ReactOS stand?
We would need some short video's for introduction and demonstration
purposes,
as well as some people active in a chat room answering questions.
Regards,
Mark
Hello,
as Colin already mentioned, I have tried to compile libc++ for ReactOS.
I stopped the project for two reasons:
1. The current state of the CRT in ReactOS.
2. The ongoing discussion about MSVC 2010.
With MSVC 2010 it is of course impossible to compile a current version of
libc++. So why should I waste my time?
Without a clear commitment to using current C++ compilers, it simply makes
no sense.
As Colin described in detail, current technologies would increase the pace
of development and attract more interested developers.
Developers like me, who simply do something else without the project ever
knowing about them.
But don't get me wrong, this is not about me or libc++. Maybe libc++ cannot
be used for other reasons after all! But with MSVC 2010 you don't even have
to start.
All the best,
Dominik
I totally and vehemently agree with Hermes here: We should NOT ditch VS2010.
Arguments that were raised by others against VS2010 and my reply:
-"ditching it brings in new developers to ros magically" <- I do ask then, where are they? I don't see any.
-"we should not be limited to strict C89" <- No one did request for that. All we want is to remain compatible to VS2010. A subset.
-"syncing BTRFS is a bit harder" <- So what? Then let others do the job. Actually BTRFS is not even a mandatory feature of ros. Having it in the tree is just luxury.
-"libc++" <- I see no urgent need and nothing it would give in return that would outweight what we would sacrifice.
My arguments again for keeping VS2010:
-VS2010 creates the smallest binaries of all compilers we do support
-VS2010 CAN be installed in ros, when ros is installed as Server during 2nd stage, (yes this was not the case for a very short moment, unfortunately exactly when we discussed in https://github.com/reactos/reactos/pull/2658 but now it works again, even in 0.4.14-RC51)
-VS2010 can now even open the VS2010 cmd prompt see https://jira.reactos.org/secure/attachment/57140/57140_0.4.15-dev-203-g711f…
-no other VS>2010 can even complete its setup in ros, and that will remain like that for many years to come
-VS2010 is the last version that runs on XPSP3 (which is important for some of our devs including myself)
-VS2010 is the last version that runs on 2k3SP2 which is our current target
-VS2010 is reliable with industry-proven stability, and itself no moving target (unlike VS2019 which breaks our builds every few weeks when MS upgrades it)
-VS2010 DOES provide std::unique_ptr. Stating anything else is just a lie. It covers > 95% of CPP2011-standard. It is absolutely possible and not complicated to write leak-free-code with it.
Hello,
Please note that I would like to cast a vote in favor of restoring
compatibility for VS2010.
Thanks very much,
Doug Lyons
--
This email has been checked for viruses by AVG.
https://www.avg.com
Hi all,
With several people asking for a status meeting, let's have another one
before the year is over.
Let me invite you to the meeting on
Thursday, 26th November 2020
19:00 UTC
Mattermost private channel "Meeting"
So far, there is only one point on the agenda:
* Achievements and Future Outlook (everyone)
What have you been working on and what are your plans?
Please submit further agenda proposals by answering to this mail.
Looking forward to see you!
Colin
Would on August 31 be alright for you? I'm asking because I won't be available by September 5 or 7 from now on due to a temporary job that I'm going to have soon.
Regards,
George
Colin Finck <colin(a)reactos.org> wrote on Fri, August 14th, 2020, 5:24 PM:
> Hi all!
>
> Keeping the usual schedule, our next bi-monthly status meeting would be
> on 27th August.
> Due to vacation, I won't be available on that date though and therefore
> cannot serve as the meeting moderator.
>
> If you want the meeting to take place on the usual date, please find
> another moderator.
> Otherwise, we have to postpone it I guess.
>
> Suggestions are welcome! :)
>
>
> Cheers,
>
> Colin
Hi all!
Keeping the usual schedule, our next bi-monthly status meeting would be
on 27th August.
Due to vacation, I won't be available on that date though and therefore
cannot serve as the meeting moderator.
If you want the meeting to take place on the usual date, please find
another moderator.
Otherwise, we have to postpone it I guess.
Suggestions are welcome! :)
Cheers,
Colin
Hola que tal, estoy realizando mi tesis basándose en ReactOS y quisera
saber mas informacion sobre el SO, tengo curiosidad si ustedes también
trabajan con GNUPG o algun tipo de sistema de cifrado para los archivos y/o
particiones del disco duro y si me podrian explicar porque esa parte no
esta explicado en ninguna documentacion de ReactOS, se los agreadeceria si
me podrian brindar esa informacion y/o orientarme les agredeceria de
antemano.
Muchas gracias.
--
Saludos
--
Sthip Harrisson Russell Panduro.
Correo: sthiplife(a)gmail.com
Hi,
I'm Frédéric from QubesOS project. I wanted to try your latest release ReactOS 0.4.13 today and I've managed to install it on our latest QubesOS R4.1 in development within a HVM domain. First text installer for partitioning is fine and the graphical setup for languages and parameters too. At first OS boot while seeing the desktop for the first time, it popups a window pci device detection but then, just few seconds after the VM is freezing. Looking at Xen status, the stubdomain is not frozen at all, but the VM itself yes with 100% CPU usage. I've tried IDE driver for disk too but the same behavior appeared.
Any idea on how I can catch errors or having logs? Should I try your debug ISO?
Thank you in advance for your help.
Frédéric
PS: https://jira.reactos.org/browse/CORE-13358
I'd like to propose what I have on my mind:
- 0.4.14 release status, what's left to do (should be a short one)
- Unifying our contribution guidelines. I've found out that we have too many places with instructions for contributors. And if fact they don't quite indicate our expectations of a good pull request.
A couple of weeks ago we gathered our ideas for contributor's and reviewer's guidelines and put them in a google doc: https://docs.google.com/document/d/1osRfG0PelNyDAwlwGFrIL-D12WeuxV3BO_GzW0N…
I'd like to have a bit of a discussion about all we wrote there and then we will try to compile new guidelines from it.
- This partly overlaps with the previous one. We have some pull requests where people with relevant experience are missing in our team. (atm I'm talking mainly about LSASS PR https://github.com/reactos/reactos/pull/2230, but such situation is possible in future)
I suggest treating such PRs with a "light" scheme: only check for code style, some obvious mistakes etc. Otherwise they will be stuck forever
Colin Finck <colin(a)reactos.org> wrote on Tue, June 23rd, 2020, 8:44 AM:
> Short reminder that the meeting is going to take place this week's Thursday.
>
> Unfortunately, I didn't get a single mail regarding the meeting agenda.
> However, I took from Mattermost that some people (Daniel in particular)
> want to talk about channel moderation, so I'm putting it on the agenda:
>
> * Channel moderation (Daniel)
>
> There may have been other things I missed, which is why I reiterate to
> send all agenda proposals by E-Mail.
>
> See you then,
>
> Colin
>
>
> Am 04.06.2020 um 09:13 schrieb Colin Finck:
> > Hi all!
> >
> > Let me invite you to the (almost) bi-monthly status meeting, taking
> > place Thursday, 25th June, 19:00 UTC, in the Mattermost private channel
> > "Meeting".
> >
> > I missed to announce a meeting last month and also didn't get any
> > proposals for the agenda. But apparently there is a need to discuss a
> > few things.
> > Therefore, please submit your agenda proposals by E-Mail to me now.
> > I will then announce the final agenda one week in advance.
> >
> > Topics I would like to speak about:
> >
> > * Achievements and Future Outlook (everyone)
> > What have you been working on and what are your plans?
> >
> > * GSoC 2020 Status (org admins and mentors)
> > Just a short update on how the GSoC projects are doing
> >
> >
> > Best regards,
> >
> > Colin
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
> >
Hi all!
Let me invite you to the (almost) bi-monthly status meeting, taking
place Thursday, 25th June, 19:00 UTC, in the Mattermost private channel
"Meeting".
I missed to announce a meeting last month and also didn't get any
proposals for the agenda. But apparently there is a need to discuss a
few things.
Therefore, please submit your agenda proposals by E-Mail to me now.
I will then announce the final agenda one week in advance.
Topics I would like to speak about:
* Achievements and Future Outlook (everyone)
What have you been working on and what are your plans?
* GSoC 2020 Status (org admins and mentors)
Just a short update on how the GSoC projects are doing
Best regards,
Colin
Hi Frédéric,
Debug logs are being written to a serial port if you select the "ReactOS (Debug)" option in the bootloader. It will help to understand what's going on in the OS. My guess that's some race condition while enumerating devices.
As far as I can see, Xen shares some code with QEMU for device emulation in HVM mode. Thus this wiki page (https://reactos.org/wiki/QEMU) may help to tune some settings, because ReactOS doesn't work with all kinds of modes QEMU offers (namely, q35 chipset doesn't work, https://jira.reactos.org/browse/CORE-13346)
Checking latest development build may also help, but we haven't made much changes to that part of OS recently.
If you will manage to run ReactOS inside Xen, maybe it's worth creating a dedicated wiki page for that along with other virtualization software.
Anyway, thanks for your interest in our project :)
Victor
Hi all!
Let me invite you to the bi-monthly status meeting, taking place
*TODAY*, 19:00 UTC, in the Mattermost private channel "Meeting".
I know that this announcement comes way too late, but hope that people
can manage to join, even if it's just to get some distraction from all
the bad news these days.
The agenda currently looks as follows, with the main speakers in
parentheses:
* Achievements and Future Outlook (everyone)
What have you been working on and what are your plans?
This is also the right time to talk about ReactOS 0.4.13 and RosBE 2.2
again.
* GSoC 2020 Status (org admins and mentors)
Just a short update on the timeline, promising projects and candidates
* Drop one theme from "default" package (Victor)
Last release we added two new themes, but they both look unfinished in
many aspects. As we have an active maintainer for one of them (Mizu),
Victor's suggestion is to either drop the Lunar, or "merge" it with Lautus
By the way, we have many times discussed an option to make custom themes
be installed from Rapps. What do we need to do for that?
And finally, it would be nice to write down some formal criteria for
accepting themes. It will make PR reviewers' life easier :)
* Hire a developer for dev-web interface and/or a devops for our
infrastructure (Victor)
Making that a GSoC project required too much effort for a mentor; so in
the end the project was not too efficient in terms of time spent/amount
of work done ratio (as a GSoC project it is great, but the interface is
still far from being usable)
Victor thinks it is reasonable to hire some experienced developer for
maybe a month or something.
Looking forward to see all of you this evening!
Colin
Hi all!
I would like to propose some topic to discuss on the next meeting (will it
be on March, 26?)
* Drop one theme from "default" package.
Last release we added two new themes, but they both look unfinished in many
aspects. As we have an active maintainer for one of them (Mizu), my
suggestion is to either drop the Lunar, or "merge" it with Lautus (I find
them quite similar - correct me if I'm wrong)
I think it's worth asking cernodile and foxlet about their thoughts. I have
a strong opinion that 4 themes is too much for "default" package
By the way, we have many times discussed an option to make custom themes be
installed from Rapps. What do we need to do for that?
And finally, it would be nice to write down some formal criteria for
accepting themes. It will make PR reviewers' life easier :)
* Hire a developer for dev-web interface and/or a devops for our
infrastructure.
Making that a GSoC project required too much effort for a mentor; so in the
end the project was not too efficient in terms of time spent/amount of work
done ratio (as a GSoC project it is great, but the interface is still far
from being usable)
I think it is reasonable to hire some experienced developer for maybe a
month or something (is we have enough funds, ofc).
That will probably require a more detailed task from us.
Suggestions are welcome here :)
We don't have to wait for a meeting, may start discussing that here :)
Cheers,
Victor
Dear Sir/Madam,
This is Chaitanya Gadgil from Bengaluru,India. I am a first year
under-graduate student pursuing Electronics and Instrumentation
Engineering.
I am interested to work with your organization for the GSoC 2020. I am
interested to work on the end user development project "Application manager
RAPPS".
Goal setting with the project:
Improvising user-system interactions
Easier management of installed applications
My skills are:
1.Programming knowledge in both C and C++
2.Data structures and database management systems
3.Basics of MATLAB and Arduino
4. Mathematics
5. SQL
Member of:
The International Society of Automation
The New York Academy of Sciences
The Mathematical society of BMSCE
Courses enrolled:
Cybersecurity
DBMS
Networking using IOT
Projects:
Developing Smart Wearables using Integrated Sensor Network Architecture
Developing an algorithmic approach to track malnutrition in India
It would be a wonderful experience for me to work with your organization
and collaborating for the project.
It would be helpful if I can contact a mentor immediately so that I can
interact and start working as soon as possible on the project.
I am also willing to improve my skills if needed.
I can guarantee of setting a good time for the project as I will be having
vacations.
Regards,
Chaitanya Gadgil
"Please also use version 5.2 if you still need support for 32-bit hosts, as
this has been discontinued in 6.0. Version 5.2 will remain supported until
July 2020."
FYI
That means, ROS will still be usable as guest, but not as host
Hi all!
We had our annual General Assembly of ReactOS Deutschland e.V. today.
Many things were discussed which are better discussed with the entire
ReactOS Team, which is why all of us agreed on reinstating the recurring
ReactOS Meetings we had until February 2019.
Let's try out a bi-monthly schedule, with the first meeting happening on
Thursday, January 30, 2020
19:00 UTC
Mattermost private channel "Meeting"
If you're currently not part of this channel, but think you should be,
please contact me.
I'm already announcing this, so we can collect topics for the meeting.
Current points on the agenda:
* Compiling an up-to-date list of tasks to work on, for newcomers, GSoC
candidates, and developers to hire.
Can already be started now by taking
https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas, copying it to
"Google Summer of Code 2020", cleaning it up and adding new stuff. Maybe
we also need to manage that with JIRA in the future.
* RosBE 2.2, and what's blocking it, if it hasn't happened by then
* ReactOS 0.4.13, and what's blocking it, if it hasn't happened by then
Just reply if you have anything to add.
Cheers,
Colin
Hi all!
It took a while but FOSDEM has finally put a list of accepted stands on
their website: https://fosdem.org/2020/news/2019-11-19-accepted-stands/
Looks like we only got a stand on Sunday this year, with our friends
from Haiku OS having one on Saturday only. Not really what I thought
when signing up for a "shared booth as always", but I'm sure we're going
to manage that.
There are plenty of opportunities for us to fill an entire weekend in
Brussels, including
* Having a "mini Hackfest" on Saturday in a coworking space in Brussels
(or alternatively at FOSDEM itself, but it's going to be crowded there)
* Following up on what Victor and me discussed with the FreeBSD, Haiku,
NetBSD, and RTEMS people at GSoC Mentor Summit regarding a port of the
low-level FreeBSD kernel interfaces to ReactOS, making a vast amount of
network and storage drivers available to us.
As far as I recall, the FreeBSD people have a conference in Brussels
just before FOSDEM and are inviting us to join (Mahdi - correct me if
I'm wrong).
* Asking the Haiku guys if we shall try to join their booth on Saturday
while they join ours on Sunday (Adrien? François?)
But first I'd like to know who else is definitely going to make it to
Brussels. Please reply to my mail ASAP, then we can have a short meeting
on Mattermost soon and come to a decision.
Cheers,
Colin
Hi all!
Victor and me are having a good time at this year's GSoC Mentor Summit
in Munich, and it's time to get out a first report.
Again, I'm getting the impression that all projects here pretty much
share the same problems and ReactOS is not doing anything particular
wrong. Today, I have attended a session about keeping students involved
after GSoC. Most projects are struggling with that and there were some
projects where it's usual for all students to just stay for GSoC and
immediately leave afterwards.
Anyway, I took some insights where we can improve to keep more of our
students:
* Give students some responsibility early on, so they feel responsible
and needed for a project even after GSoC.
The ultimate goal should be to turn them into mentors later. We
already have a fairly good track record of that, but I think it
should be emphasized here.
* Invite more students to our Hackfest. We may need to postpone it by
a few weeks to not clash with the final days of GSoC.
For the MacPorts project, this resulted in all 3 students staying
with the project after GSoC.
* Talk to students on a personal level (possibly even through audio or
video chat) and get them into our community.
We had some high-performing students in the past who needed almost
no mentoring, but this also resulted in less interactions with the
community and we had a hard time to keep them involved after GSoC.
* Collect tasks all year long, not just shortly before GSoC. This is
important not just for keeping students, but also for enabling our
paid development ideas around ReactOS.
It's still important to ask a student what he or she wants to work
on after GSoC, but we should always have some interesting tasks
available.
* Advertise our scholarship model early enough during GSoC to keep the
people that are also doing it for the money.
* Advertise our GSoC participation at universities. Some students
managed to declare their GSoC participation as the technical
internship required for their studies.
All in all, the Mentor Summit again was a great opportunity to meet up
with fellow Open-Source developers all around the world and have some
interesting discussions. I'm already looking forward to the next one!
We even got some ReactOS work done
<https://github.com/reactos/reactos/pull/1835> just in sight distance of
the Microsoft Germany HQ :D
Cheers,
Colin
Hi,
why is the project so silent?
Normally there were messages about online meetings, upcomming releases
etc. on this list but it became realy silent and the last release is long
time ago.
what happened to reactos?
best regards, dick
Hello all,
Connecting to the new buildbot now shows an avatar picture from www.gravatar.com.
What are the legal implications ? What personal data are sent here ?
Is it still possible to see online logs as plain text ?
https://build.reactos.org/#/builders/9/builds/24976/steps/5/logs/stdio/text comes back to the index now.
Looking at a 1 billion lines hung log as HTML won't do anything good,
for the client and the server.
| |
Kind regards, Sylvain Petreolle
Le Dimanche 23 juin 2019 23h13, Colin Finck <colin(a)reactos.org> a écrit :
Hi all!
Our BuildBot at https://build.reactos.org is finally going to be
upgraded from the ancient version 0.8.14 to the latest 2.3.1 release
this Tuesday evening (CEST).
We have postponed this for a very long time due to the fundamental UI
changes in newer versions. The UI has been rewritten from scratch and
its Waterfall View has been simplified. I used to be a strong opponent
of this change. However, in one of the last meetings, it turned out that
the current Waterfall View isn't that popular among our developers anyway.
You can expect the new BuildBot to look like this:
https://lidell.nu/xemacs-buildbot/
BuildBot also doesn't provide a direct migration path from the old to
the new version. This means that previous build and log information will
be gone after the upgrade.
I used to consider this a blocker as well, but current BuildBot already
purges old build/log information after some time and apparently it
hasn't been missed. We still have all important information in Testman.
I will make sure however that build numbers in the new version continue
where they ended in the old version.
On the plus side, this upgrade brings integrations with GitHub and
Mattermost as well as proper Unicode support. Using an up-to-date
BuildBot version also allows us to actually enhance it. In fact, this
upgrade is a prerequisite for the Developer Web Interface our GSoC
student Ayush Sinha is currently working on.
Regarding Buildslaves (now called "workers"), the new BuildBot is still
compatible with 0.8.x clients, so these don't need an upgrade right
away. We just need a small change on workers submitting test results.
Kudos go to Victor Perevertkin, who has already begun evaluating the new
BuildBot version a long time ago and provided me with an updated
master.cfg file, along with other help!
I'm glad that the number of people maintaining our BuildBot setup is
growing! :)
Cheers,
Colin
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://reactos.org/mailman/listinfo/ros-dev
Hi all!
The ReactOS Hackfest will take place in about a month and a week.
Please revisit https://reactos.org/wiki/ReactOS_Hackfest_2019/Lists and
put yourself in all relevant lists if you are going to attend.
I've just updated the Shirts/Hoodies section with the final design.
Please check that out and add whether you want a shirt or a hoodie.
You may also want to check the links regarding the exact sizes again.
Deadline for this is
THURSDAY, JULY 11
After that, I will move on and buy the merchandising products.
If your attendance at the Hackfest needs financial assistance from
ReactOS Deutschland e.V., please also get in touch with me before that
deadline. You know, flights and accommodation get more expensive the
closer we are to the event date ;)
Cheers,
Colin
Hi all!
Our BuildBot at https://build.reactos.org is finally going to be
upgraded from the ancient version 0.8.14 to the latest 2.3.1 release
this Tuesday evening (CEST).
We have postponed this for a very long time due to the fundamental UI
changes in newer versions. The UI has been rewritten from scratch and
its Waterfall View has been simplified. I used to be a strong opponent
of this change. However, in one of the last meetings, it turned out that
the current Waterfall View isn't that popular among our developers anyway.
You can expect the new BuildBot to look like this:
https://lidell.nu/xemacs-buildbot/
BuildBot also doesn't provide a direct migration path from the old to
the new version. This means that previous build and log information will
be gone after the upgrade.
I used to consider this a blocker as well, but current BuildBot already
purges old build/log information after some time and apparently it
hasn't been missed. We still have all important information in Testman.
I will make sure however that build numbers in the new version continue
where they ended in the old version.
On the plus side, this upgrade brings integrations with GitHub and
Mattermost as well as proper Unicode support. Using an up-to-date
BuildBot version also allows us to actually enhance it. In fact, this
upgrade is a prerequisite for the Developer Web Interface our GSoC
student Ayush Sinha is currently working on.
Regarding Buildslaves (now called "workers"), the new BuildBot is still
compatible with 0.8.x clients, so these don't need an upgrade right
away. We just need a small change on workers submitting test results.
Kudos go to Victor Perevertkin, who has already begun evaluating the new
BuildBot version a long time ago and provided me with an updated
master.cfg file, along with other help!
I'm glad that the number of people maintaining our BuildBot setup is
growing! :)
Cheers,
Colin
Hi!
Recently I've looked into Doxygen manual for writing documentation and
noticed that an example on our Coding style
<https://reactos.org/wiki/index.php?title=Coding_Style> page on wiki uses
some statements in a wrong way.
Namely, @name statement is for defining sections, groups and definitely not
for functions/structs/classes etc.
Another thing is a function description. Doxygen has two types of them:
brief and detailed one. Brief description must be defined by @brief
statement, but for detailed one @details can be omitted (which in fact was
done in our example).
Obviously, brief description should be used in first place (and that would
be likely the only one)
I've made some changes, to the page (see the latest change in page history)
Btw, I think it can be extended to something like this (
http://micro-os-plus.github.io/develop/doxygen-style-guide/) sometime
If you have any objections or suggestions, feel free to add them or discuss
here.
Cheers,
Victor
+ /* Now we need to set the Hostname */
+ lError = RegOpenKeyExW(HKEY_LOCAL_MACHINE,
+ L"SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters",
+ 0,
+ KEY_SET_VALUE,
+ &hKey);
+ if (lError != ERROR_SUCCESS)
+ {
+ DPRINT1("RegOpenKeyExW for Tcpip\\Parameters failed (%08lX)\n", lError);
+ return TRUE;
Typo?
Hi,
I’m trying to answer point by point.
1. Their license is MIT. At least it allows us to borrow ideas from their code for how to implement stuff in ReactOS’ console/terminal. (I suppose that if one wants to copy entire chunks of code, that I wouldn’t do it, I’m not sure how the licensing of the original ReactOS console GPL code would have to change. But “I’m not a lawyer”. Anyway, copy-pasting stuff is never a good idea.)
2. Yes but again you don’t need to care. It allows us to remain “original” in our way of implementing the things. What’s now “documented” however, is the interface between condrv and conhost (and to kernel32 if my quick reading of the shared headers is correct). This is sufficient. Then the internal implementation one can write for ReactOS is left free, this allows one to have original code and note a dull copy-paste.
3. ReactOS doesn’t use C++ in the console, and won’t use ”WinRT” any time soon in its entire code-base. So forget about any direct import of the MS console code into ROS.
Regards,
Hermès
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Biswapriyo Nath
Envoyé : mardi 7 mai 2019 20:42
À : ros-dev(a)reactos.org
Objet : Re: [ros-dev] Ros-dev Digest, Vol 177, Issue 2
Some queries though:
1. There are many restrictions on how the code can be used. Are developers allowed to import the idea to ReactOS? Also with a different license.
2. The half of the codebase of console subsystem implemented in KernelBase and Kernel32. Those are not open source. Also the main magic happens in ConDrv driver.
3. The project has C++/WinRT code. Does ReactOS have that section?
Thank you <3
Some queries though:
1. There are many restrictions on how the code can be used. Are developers
allowed to import the idea to ReactOS? Also with a different license.
2. The half of the codebase of console subsystem implemented in KernelBase
and Kernel32. Those are not open source. Also the main magic happens in
ConDrv driver.
3. The project has C++/WinRT code. Does ReactOS have that section?
Thank you <3
Dear All,
Yes you've read correctly! Microsoft released the code of its terminal + the
Windows console host (conhost.exe) under MIT license at:
https://github.com/microsoft/Terminal
I think this is a really great move!! This can definitively help us for:
* first, allowing us to improve our existing console code,
* and in the future, getting our console architecture Win10-compatible
(...)
This also means that anybody can contribute back to their code via
pull-requests, or at least creating issues.
For those using Windows 10, they plan releasing official builds starting
June 2019 according to their posts:
https://devblogs.microsoft.com/commandline/introducing-windows-terminal/https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsT
erminal.aspx
Best,
Hermès
Hey there !
I am really interested to work with your organization.I have been
doing web development projects using MERN stack for a while now,And I
went through your reactOS GSOC’19 page. I am interested in making the
web interface for reactos which can show all GitHub reactos repos,
commits, etc using the GitHub
API(https://www.reactos.org/wiki/Google_Summer_of_Code_2019_Ideas#Developer…
I am Looking forward to work on the same for GSOC this year under your
mentorship. Currently I am reading the api documentation and trying to
implement some basic stuffs using React and Node.js, till now I have
created robust user ineterface with React and am looking forward to
add some logics to it in coming hours.
Webapp link: https://reactos-web.herokuapp.com/
GitHub repo: https://github.com/AwesomeChap/ReactOS_Web_Interface
(Theme I chose in webApp mentioned above is completely customizable :
You may think of present theme as Night Mode)
kindly review the links. Any suggestion would be appreciated
Thanks
Jatin Kumar
Btech CSE 2nd Year
USICT, GGSIPU
India
Hi all!
The ReactOS Hackfest goes into its fourth round! Join us from Thursday,
15th August to Tuesday, 20th August 2019, just at the same location in
Berlin as last year.
As every year, check out the
https://reactos.org/wiki/ReactOS_Hackfest_2019 and
https://reactos.org/wiki/ReactOS_Hackfest_2019/Lists pages on our Wiki
and add yourself if you can make it.
Hope to see you all in August!
Colin
Hey there !
I am really interested to work with your organization.I have been
doing web development projects using MERN stack for a while now,And I
went through your reactOS GSOC’19 page. I am interested in making the
web interface for reactos which can show all GitHub reactos repos,
commits, etc using the GitHub
API(https://www.reactos.org/wiki/Google_Summer_of_Code_2019_Ideas#Developer…
I am Looking forward to work on the same for GSOC this year under your
mentorship. Currently I am reading the api documentation and trying to
implement some basic stuffs using React and Node.js, till now I have
created robust user ineterface with React and am looking forward to
add some logics to it in coming hours.
Webapp link: https://reactos-web.herokuapp.com/
GitHub repo: https://github.com/AwesomeChap/ReactOS_Web_Interface
kindly review the links. Any suggestion would be appreciated
Thanks
Jatin Kumar
Btech CSE 2nd Year
USICT, GGSIPU
India
Hello!
I'm really interested in participating this year at gsoc as part of
your team. I'm writting you this email to get your attention and maybe to
get a hint for this year's project. I'm in my second year at University
Politehnica of Bucharest at the Faculty of Automatic Control and Computers
and I study for a degree in Computer Science and Information Technology. I
wanna start early this year contributing to the project as I wish to show
you that I will be a great addition to your team. If I have caught your
attention and you want to communicate me anything, I can be contacted on
this mail.
- Many thanks, Costin Visan
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Hello Everyone!!
Im Tibor Popper from Hungary, somewhere at middle of Europe :).
I want to apply in Google GSoC at this year, also I wanna be co-developer
of ReactOS project. I'm really exited about Operating System programming
right now, atleast for training myself? I dont really know, but more prefer
to make some new functions or fixes for ReactOS to really make this project
better, and really useful. Like.: UEFI boot, Kernel expansion, Graphics.
Im especially advanced in grafical programming with DirectX 11 / 12, but
maybe more with OpenGL 4+. I was developer of video games in some little
company, mainly for Windows, with Unreal Engine, Unity, I cant tell about
more. I didnt finished University of Pécs, with Engineering IT (BSc), but I
have Software Developer occupation. My main programming language is C++,
but not limited to others. I have started to look half year before how UEFI
works in general to start write EFI programs, but I abandoned this
studying, + some OS from sctratch tutorials :) …
I really love to make things work! I love optimal and nice looking code,
performance, software design, functionality. I love to understand HOW
things work, I can take really much time discover these things, like in
Physics, also love that too.
Greetings, regards, Sumi!
Hello everyone,
I am Akshay Patil, a 3rd year undergraduate student studying Computer
Science in VIIT, Pune, India.
I have been trying React OS for a while now and found it really
interesting. I love open source. I want to contribute for the project
"*Applications
Manager Rapps*" through Google summer of Code 2019.
I have been using C++ launguage for 5 years and also made some applications
like user control app. I am sure tthat the experience I ganied from last
few years will certainly help me in understanding the Rapps Code easily.
We will figure out the concrete goals of the project and the decided the
plan for the project with the mentor.
It'll be great if somebody, could mentor me for this project.
Thanks,
Akshay Patil
Hi all!
ReactOS 0.4.11 is going to be released tomorrow, Monday, March 4, 2019.
The download will be officially available around noon (CEST).
A Press Kit for the ReactOS 0.4.11 release is already available:
https://download.reactos.org/reactos/ReactOS/0.4.11/ReactOS-0.4.11-PressKit…
Feel free to send it to interested parties to let them know about the
upcoming release in advance.
Best regards,
Colin Finck
They do!
---------- Forwarded message ---------
From: <chat(a)reactos.org>
Date: vie., 1 mar. 2019 18:30
Subject: [ReactOS Chat] Notification in ReactOS on March 1, 2019
To: <elhoir(a)gmail.com>
You have a new notification.
Channel: Town Square
@Colin Finck - 17:30 UTC, March 1
@all Mattermost E-Mail notifications should finally work now :)
Go To Post <https://chat.reactos.org/reactos/pl/54gbdt6h63rz8j5tqbmtg3wkpc>
Any questions at all, mail us any time: feedback(a)mattermost.com
Best wishes,
The ReactOS Chat Team
To change your notification preferences, log in to your team site and go to
Account Settings > Notifications.
Hi all!
Let me invite you to the February 2019 meeting, taking place this
Thursday, February 28, 19:00 UTC. It will again happen in the private
"Meeting" channel on our Mattermost server at https://chat.reactos.org.
The current agenda is as follows:
* Status Updates
==============
As always, please have your status report ready before the meeting,
so that we can get this done quickly.
* Google Summer of Code 2019
==========================
Google is about to announce the list of participating organizations
today, so we should prepare to spread the word and soon answer lots
of questions from interested students.
* 0.4.11
======
Let's quickly update everyone on the state of the 0.4.11 release and
the changelog in order to get it out soon.
As always, please let me know if you want anything to be added to the
agenda.
Cheers,
Colin
Hey there !
I am really interested to work with your organization.I am interested in Web development projects, Went through the reactOS GSOC’19 page. I am interested in making the web interface for reactos which can show all GitHub reactos repos, commits, etc using the GitHub API. (https://www.reactos.org/wiki/Google_Summer_of_Code_2019_Ideas#Developer_Web…)
Looking forward to work on the same idea for GSOC’19 under your mentorship.
Currently I am reading the api documentation and trying to implement some basic stuffs using nodeJS, till now I have created a web app that can list all reactOs repositories and related information.
Webapp link: https://github-userinterface.herokuapp.com/
GitHub repo: https://github.com/ayushsnha/UserInterface-with-Github-RESTapiV3
kindly review the link. All suggestions are welcomed
Thanks
Ayush Kumar Sinha
2nd year bachelor of cs,
VIT University,
India
Last time. Please add your name, anyone still not done it. I have to confirm on Feb 10th
Daniel Reimer <daniel.reimer(a)reactos.org> schrieb am Mo, 21.01.2019 21:49:
> Hello and good evening,
>
> as some of you might already know, we are close to CLT 2019 again:
> https://chemnitzer.linux-tage.de/2019/de
>
> For lazy ones: 16-17.03. in Chemnitz (YES, germany that is)
>
> As every year I need at least two, better three ppl for maintaining the
> booth. This time I will not wait until we really got accepted just to
> hear from everyone a nope, or not sure yet way too late in the phase.
> This resulted in asking the community for help (which is a good thing
> tbh) and that resulted in some bored and feelin useless supporter in the
> end. Why? Well, a few days before the whole thing took part I suddently
> had enough main/core members and thus he just sat there and had nothing
> to do. STILL A BIG SORRY FROM MY SIDE!!
>
> I don't wanna have this happening once more that year. Thus.... check
> the weekend, ways to get there and back home and then reply to the
> doodle. Costs to get there are as always a thing we can talk about
> compensation and stuff. If you need to talk about CLT stuff, feel free
> to reply here of course ^^
>
> So... lets hope I have the right link:
> https://doodle.com/poll/krmz8ktt8r85m5y4
>
> Greetings
>
> Daniel Reimer
master has been broken for days. Until this issue is fixed, no test
results are going to make it to Testman, which means any regressions are
going to be extremely hard to track down.
Here's the issue to follow: https://jira.reactos.org/browse/CORE-15642
Unless you have something that might fix this, I would ask that you hold
off on merging things until this bug is fixed.
Thanks,
Thomas
Hi all!
I've done some research on what can we do to improve our CI system.
First of all, I want to clarify: our CI is consists of two parts: building
and testing. I'm assuming here that "build" part is OK for us and doesn't
require any improvements in workflow or something like that. So focusing
only on "testing" part.
I tried to find some solutions similar to our testman, but the things are
very bad on this side.
- There are some plugins for Jenkins which show a table with test
results by each build
- Microsoft TFS has functionality for storing tests and doing some
analysis on them, but that's a no-go for us
- Jetbrains' TeamCity also has this thing and has a license for Open
Source
I use Jetbrains tools at work and like this company in general :) so I
decided make some experiments with it.
Some facts:
- It has out-of-the-box integration with Jira and Github. It works
flawlessly (bonus: you can automatically build and test all PRs from team
members, for example)
- Integration with GitHub Checks (that green checkmark which for us
comes from Travis&Appveyor right now)
- Has an interface for filtering test results by module, shows execution
time, some statistics etc.
- Uses JVM for work :) Both master and slave part
- PostgreSQL, MySQL and some built-in DB can be used for storage
- Uses own DSL, derived from Kothlin language for configuration (but
allows configuring through GUI too)
Adopting iso build didn't have any issues, it just works. But testing
requires some work:
- sysreg2 and rosautotest should be changed to output results in some
format which TeamCity understands. It can be jUnit, Google test or
teamcity's own format
- TeamCity has only three states of test: success, failure or crash.
This does not fit with our current scheme based on succeed and failed
ok()'s count
- TeamCity can't compare test results between random builds like our
testman. It only can show "tests which failed in this build, but didn't
fail in previous one". But if we want something more, we can use their API
While looking into the way how our tests work, I've found that by "test" we
mean a function defined my START_TEST macro, which does some reporting to
sysreg.
But each START_TEST function likely has a couple of further test_* calls,
which are not reported in any way. This is a place where the granularity of
reporting can be increased :)
Attaching some screenshots of how it look like in general.
https://drive.google.com/open?id=17r4PSFmsi2tiF97HHbYGiMCOoKR7VMUF
So far we have to decide what to do now. An options can be:
- Go on with adopting test&build infrastructure to TeamCity - we will
migrate to it eventually
- We are not going to use TeamCity - somebody should develop a custom
web interface to consolidate everything (
https://www.reactos.org/wiki/Google_Summer_of_Code_2019_Ideas#Developer_Web…
)
- Just migrate to new BuildBot (can be done with along with previous
option)
- Don't do anything
Looking forward to discuss this on the meeting
Cheers,
Victor
Hello and good evening,
as some of you might already know, we are close to CLT 2019 again:
https://chemnitzer.linux-tage.de/2019/de
For lazy ones: 16-17.03. in Chemnitz (YES, germany that is)
As every year I need at least two, better three ppl for maintaining the
booth. This time I will not wait until we really got accepted just to
hear from everyone a nope, or not sure yet way too late in the phase.
This resulted in asking the community for help (which is a good thing
tbh) and that resulted in some bored and feelin useless supporter in the
end. Why? Well, a few days before the whole thing took part I suddently
had enough main/core members and thus he just sat there and had nothing
to do. STILL A BIG SORRY FROM MY SIDE!!
I don't wanna have this happening once more that year. Thus.... check
the weekend, ways to get there and back home and then reply to the
doodle. Costs to get there are as always a thing we can talk about
compensation and stuff. If you need to talk about CLT stuff, feel free
to reply here of course ^^
So... lets hope I have the right link:
https://doodle.com/poll/krmz8ktt8r85m5y4
Greetings
Daniel Reimer
Hi all!
As announced previously
(https://reactos.org/pipermail/ros-dev/2019-January/019044.html), we'll
be having the January meeting already this Thursday, January 24 in order
to have enough time for our GSoC application.
The meeting will also take place on our new Mattermost at
https://chat.reactos.org for the first time!
So let me invite you to this meeting, taking place again at 19:00 UTC.
If you haven't tried Mattermost yet, please log in to chat.reactos.org
now using your ReactOS.org credentials. Only then I can add you to our
new private "Meeting" channel. This one will not be bridged to IRC!
I will already start adding people to this channel now, so that the
meeting can start on time. If you have the feeling that I forgot about
you, please let me know timely.
The current agenda is as follows:
* Status Updates
==============
As always, please have your status report ready before the meeting,
so that we can get this done quickly.
* Mattermost
==========
I need to know your opinion about Mattermost and whether you think
that we should continue using it beyond our trial (ending mid-
February).
This would require an enterprise license for non-profits
($250 per three years).
* Google Summer of Code 2019
==========================
The list at https://reactos.org/wiki/Google_Summer_of_Code_2019
still doesn't show a single mentor. And
https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas certainly
also needs some polishing. Let's finally make up our minds regarding
this year's GSoC, so that we can submit our project application.
I would highly appreciate if people updated those Wiki pages before
the meeting. This could potentially save us hours of discussions and
finding volunteers :)
Let me know if you want anything to be added to the agenda.
Cheers,
Colin
Message from chat.reactos.org:
This team has reached the maximum number of allowed accounts. Contact your
systems administrator to set a higher limit.
Adam Stachowicz
sob., 12 sty 2019, 13:00: <ros-dev-request(a)reactos.org> napisał(a):
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Mattermost is live at chat.reactos.org! (Colin Finck)
> 2. Reactos participation and Windows source leaked
> (Idzwan Nizam b. Jamal)
> 3. Re: Reactos participation and Windows source leaked
> (Erkin Alp Güney)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 11 Jan 2019 13:56:46 +0100
> From: Colin Finck <colin(a)reactos.org>
> To: 'ReactOS Development List' <ros-dev(a)reactos.org>
> Subject: [ros-dev] Mattermost is live at chat.reactos.org!
> Message-ID: <d18f8664-55c9-7eaa-dbcf-6161ee53cfaf(a)reactos.org>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all!
>
> Our own Mattermost instance is finally live at https://chat.reactos.org!
>
> Enjoy an infinitely searchable history, offline messages, native picture
> support, push notifications, a seamless experience on web and mobile,
> and more.
> All privately hosted on our own infrastructure and usable with the same
> ReactOS.org account you already have!
> Time to say goodbye to workarounds like IRC bouncers or third-party
> services :)
> I believe this can really improve our communication and accelerate
> development!
>
> To make the migration as easy as possible, I have set up a bridge
> between our Freenode IRC channels and Mattermost. User "RosBridge" will
> transfer all messages from #reactos / #reactos-dev to Town Square /
> Development and vice-versa. Let's see how long we're going to need that.
>
> I hope you're all going to join the fun, so that we can already have the
> next meeting in around 2 weeks on Mattermost!
>
>
> Cheers,
>
> Colin
>
>
Proposed EU copyright directive requires automated upload filters
(something like YouTube ContentID) and this can cause a sharp decrease
in contributions. It will also make difficult for newcomers as a
significant contribution will be required for each commit, because
copyright filter is costly to run.
Yours, faithfully
Erkin Alp
Hello,
Supposedly someone had an access and seen leaked windows source code few years ago. At the time he/she do not have any idea of the code (due to improficiency in programming and the subject) and had forgotten since about the code, does he/she allowed to contribute to ReactOS development?
This is due to the following statement on the participation page (https://www.reactos.org/participation)
"Getting involved with ReactOS is easy and straightforward! We only ask that you have not had access to Microsoft source code for the area you want to work on. This includes either having worked at Microsoft, obtaining the source code through an academic program or from the illegal leakage of Windows source code several years ago. Having viewed the source prevents you from contributing to avoid undermining the legality of our source code"
Hi all!
Our own Mattermost instance is finally live at https://chat.reactos.org!
Enjoy an infinitely searchable history, offline messages, native picture
support, push notifications, a seamless experience on web and mobile,
and more.
All privately hosted on our own infrastructure and usable with the same
ReactOS.org account you already have!
Time to say goodbye to workarounds like IRC bouncers or third-party
services :)
I believe this can really improve our communication and accelerate
development!
To make the migration as easy as possible, I have set up a bridge
between our Freenode IRC channels and Mattermost. User "RosBridge" will
transfer all messages from #reactos / #reactos-dev to Town Square /
Development and vice-versa. Let's see how long we're going to need that.
I hope you're all going to join the fun, so that we can already have the
next meeting in around 2 weeks on Mattermost!
Cheers,
Colin
Hi all!
Happy new year from my side! Hope you all had nice holidays and that
2019 will be a successful year for ReactOS :)
As always, the year begins with our Google Summer of Code application.
It is now time to update
https://reactos.org/wiki/Google_Summer_of_Code_2019 and
https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas as
applications begin next week (January 15). If we take this seriously and
don't forget to advertise, I'm sure that we'll get more students this year!
But first things first: Who is going to volunteer as mentors and
administrators?
I'm willing to take over one of the administrator roles again, but we
also need a second one.
I also suggest that we prepone the monthly meeting for January by a week
to Thursday, January 24.
This gives us some time for GSoC-related discussions until the final
application deadline (February 6).
Cheers,
Colin
We seem to be back to normal state.
Please report if some service is still not working properly.
Pierre Schweitzer <pierre.schweitzer(a)reactos.org> wrote on Wed, December 26th, 2018, 4:43 PM:
> Dear all,
>
> Due to an unexpected outage touching our hoster infrastructure, our DB server is currently down and it affects all the web services relying on it. So, don't expect Jira, boards, wiki, website, and so on to work properly for now,
> I'll keep you informed when I have more information.
>
> Cheers,
> Pierre
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
Dear all,
Due to an unexpected outage touching our hoster infrastructure, our DB server is currently down and it affects all the web services relying on it. So, don't expect Jira, boards, wiki, website, and so on to work properly for now,
I'll keep you informed when I have more information.
Cheers,
Pierre
Feature Request CORE-15418 to create a ReactOS Default Media Player
using the code from Media Player Classic.
This feature request was discussed some time ago on the forum at length
and it came to little conclusion, some wanting to bundle VLC, others
wanting to bundle classic media player - an open source tool that has
recently received some attention. The importance of a media player was
noted but one of the main problems was left out.
The nub of the problem is this:
Windows has a default media player provided as a core part of the
system. It is not just a media player, being so tightly integrated into
Windows it is used by (some/many?) apps to produce the default sounds
and video that emanate from normal program usage.
Note that on Windows, ActiveX/COM allows access to system level
components and one of those components that is defined as a system level
resource is the windows media player (WMP). COM allows programs to make
calls to WMP to allow them to play embedded videos or audio tracks
within their applications without having to design their own player and
bundle their own codecs. The use of WMP means that a far greater range
of codecs will be available and the chances of being able to play a
particular type of file are increased. *Without such a player these
Windows applications will not function as intended.*
See the description here: https://docs.microsoft.com/en-us/window ...
ject-model
<https://docs.microsoft.com/en-us/windows/desktop/wmp/about-the-player-objec…>
ReactOS is not a straight o/s without any whizzes or dongles, ie. it
already has such bundled apps as games and the ReactOS version of
paintbrush. So, the concept of bundling apps is already set, ie. it is
perfectly OK to have apps bundled with ReactOS and ReactOS will have
them when released. It is just a matter of which applications are
bundled. I propose we add Media Player Classic as the default media player.
A Windows Media Player type application would be very useful, in fact
essential to replace the windows media player that came bundled with
Windows, it will need to be a straight drop in replacement for WMP.
Indeed, users expect the basic components of an o/s to be present and
although RAPPS allows users to install the components they need, some
applications are integrated into the o/s far more than others. I would
suggest that it is time to re-open this debate and consider using the
open source Media Player Classic as ReactOS own embedded version of WMP
and to ensure that active X/COM controls can see Media Player Classic
just as WMP is disclosed as the default media player in Windows.
MPC looks like a media player that ReactOS could use. It is written in
C++ and is open source and it supported by the devs at doom9. It seems
to me that the only thing missing from Media player classic is the
Active X control that allows Windows/ReactOS programs access to its
functions. With that control in place it might be a perfect drop-in
replacement for WMP and would restore that missing sound functionality
to programs giving ReactOS added compatibity.
Request raised here in JIRA:
https://jira.reactos.org/browse/CORE-15418
Hope this finds you all well this Christmas and that you will consider
this feature request for later inclusion.
Dean Beedell (dizt3mp3r)
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Hi all!
With Christmas fast approaching and many people traditionally being
unavailable over the holidays (myself included), let me prepone our
monthly meeting to tomorrow, Thursday, December 20, 2018, 19:00 UTC.
Invited members will again receive their IRC Server credentials shortly
before the meeting.
Note that due to the recent infra changes, your IRC username will now be
based on the Display Name you set in
https://reactos.org/roslogin/?p=selfservice (spaces replaced by
underscores). Please check that before the meeting.
However, as our self-hosted Mattermost server is being set up right now,
this may as well be our last meeting on IRC :)
I wouldn't mind if it's just about the Status Updates from everybody
this time, given that the November meeting was really long and a lot of
things should be in progress.
Let's also not forget about our preparations for Google Summer of Code!
Cheers,
Colin
<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>Hi,<br>
<br>
There is in principle (almost) all the infrastructure to implement the Retry/Skip/Abort dialog in usetup.<br>
The freezing you encounter is however a bug I should investigate.<br>
<br>
Cheers,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Javier Agustìn Fernàndez Arroyo"<br>
A : "ReactOS Development List"<br>
Envoyé: mercredi 19 décembre 2018 20:17<br>
Objet : [ros-dev] CORE-15467 - 1st stage setup freezes when the expected file is missing<br>
<div class="gl_quoted">
<div dir="ltr">An idea,
<div> </div>
<div>I don´t think its a good idea to "skip" a file during 1st stage, specially core files (in 2nd stage it might be acceptable for some device drivers, for example)</div>
<div> </div>
<div>So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or abort installation and reboot.</div>
<div> </div>
<div>what do you guys think?</div>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
An idea,
I don´t think its a good idea to "skip" a file during 1st stage, specially
core files (in 2nd stage it might be acceptable for some device drivers,
for example)
So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or
abort installation and reboot.
what do you guys think?
Hi all!
Another important change has just been applied to ReactOS
infrastructure: https://build.reactos.org and https://irc.reactos.org
now use ReactOS.org accounts. Finally, we have a real global login
system where you can access all ReactOS services with the same account!
Please let me know if or if not things work for you, as I may have
forgotten to add some accounts to the BuildBot group.
If everything works well, we are technically ready to launch a
Mattermost instance using the same accounts as the next step :)
Cheers,
Colin
Hi all!
iso.reactos.org, the file server used by our build machines and the
source for https://reactos.org/getbuilds, has been migrated to new
hardware at a different location today.
You should experience better transfer rates due to the increased
bandwidth, and a higher availability. The new hardware also offers more
disk space and redundancy to keep our precious ISOs absolutely safe :)
Unfortunately, the new iso.reactos.org is no longer right next to the
build machines. This has several consequences: If I had left the build
scripts as-is, the build machines would have uploaded the bootcdregtest
ISOs to iso.reactos.org, just to download them multiple times for each
Testbot a minute later. This would be an excessive waste of ISP
bandwidth and would have delayed the entire testing process.
Therefore, I changed the build scripts to keep the bootcdregtest ISOs
within the local build machine network. However, the downside is that
bootcdregtest ISOs are no longer available via iso.reactos.org.
Please let me know if this is a problem for you and needs a solution.
In the past, bootcdregtest ISOs were only available for a week and not
accessible via GetBuilds either, so I have no idea how popular they are.
Cheers,
Colin
Hi all,
The Test_KVM_AHK machine has encountered a power shortage in my area and is currently shut off.
I will bring it back on today evening. Kind regards, Sylvain Petreolle
Hi all!
Good news! I've just migrated the last of our existing services,
Doxygen, to a new server that is a lot faster and more reliable.
But I also had a look at the often criticized search feature and enabled
the alternative EXTERNAL_SEARCH in the Doxyfile and on the server. This
doubled the runtime for Doxygen due to the additional indexing, but the
result is well worth the effort!
A simple search for a universal function like "Sleep" now instantly
yields all results, but with the definition in "winbase.h" and the
declaration in "kernel32/client/synch.c" at the very top! Results are
also a lot more readable and distributed over multiple pages.
Just try it yourself:
https://doxygen.reactos.org/search.html?query=Sleep
Hope you'll like it as much as I do! :)
We can now start tweaking the extra settings, e.g. whether we need
"Referenced by" and other information.
ReactOS is already known to many due to our Doxygen popping up whenever
they google a Windows API. This step should improve the usefulness of
our documentation even further and turn the ReactOS codebase into *the*
public reference about Windows internals again!
I hope it also motivates you to take care of Doxygen-compatible comments
during your coding :)
Cheers,
Colin
<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>Hi,<br>
<br>
In case this happens to be indeed a problem, the additional stuff to add to the build scripts would be to upload these bootcdregtest ISOs to iso.reactos.org, while using now the local copy on the build machine network.<br>
<br>
Best,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Colin Finck"<br>
A : "'ReactOS Development List'"<br>
Envoyé: mercredi 5 décembre 2018 20:01<br>
Objet : [ros-dev] iso.reactos.org migrated to new server<br>
<div class="gl_quoted">Hi all!<br>
<br>
iso.reactos.org, the file server used by our build machines and the<br>
source for https://reactos.org/getbuilds, has been migrated to new<br>
hardware at a different location today.<br>
<br>
You should experience better transfer rates due to the increased<br>
bandwidth, and a higher availability. The new hardware also offers more<br>
disk space and redundancy to keep our precious ISOs absolutely safe :)<br>
<br>
Unfortunately, the new iso.reactos.org is no longer right next to the<br>
build machines. This has several consequences: If I had left the build<br>
scripts as-is, the build machines would have uploaded the bootcdregtest<br>
ISOs to iso.reactos.org, just to download them multiple times for each<br>
Testbot a minute later. This would be an excessive waste of ISP<br>
bandwidth and would have delayed the entire testing process.<br>
Therefore, I changed the build scripts to keep the bootcdregtest ISOs<br>
within the local build machine network. However, the downside is that<br>
bootcdregtest ISOs are no longer available via iso.reactos.org.<br>
<br>
Please let me know if this is a problem for you and needs a solution.<br>
In the past, bootcdregtest ISOs were only available for a week and not<br>
accessible via GetBuilds either, so I have no idea how popular they are.<br>
<br>
<br>
Cheers,<br>
<br>
Colin<br>
<br>
_______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Are you sure its better to follow Win behavior on this?
I think its a enhancement, specially if there are many open windows at a
given time....
it saves time!
Hi all!
Planning the ReactOS 0.5 release and establishing a new roadmap was one
of the points on the agenda of yesterday's meeting. This is still an
ongoing process.
Please make up your minds about what a ReactOS 0.5 release must offer in
your opinion and write it down to https://reactos.org/wiki/0.5.0
To get a realistic roadmap, it is important that we define a responsible
person for each task. It should be the person having the most in-depth
knowledge about the status of the affected ReactOS components.
Don't worry, we won't put any pressure on you to complete the task soon.
But we need someone who can give a detailed report about the current status.
If nobody can be the responsible person for a certain task, having it
for 0.5 is not realistic and it eventually needs to be removed from the
roadmap.
But that's for later! Let's first add all points we consider important
until the end of the year. If you can already add yourself as the
responsible person, even better! :)
Cheers,
Colin
Hi all!
While there is still some time until the February 6, 2019 application
deadline for projects, we should already begin planning our GSoC
participation now!
As today's meeting already has a long agenda, I delibereately didn't add
GSoC to it. But I've already created
https://reactos.org/wiki/Google_Summer_of_Code_2019 and
https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas
Please decide whether you want to be a GSoC org admin or mentor and add
your ideas to the list or remove deprecated ones.
My experience from the Mentor Summit tells me that proper planning and
advertising can make a huge difference for our 2019 participation and
will certainly get us more students :)
Cheers,
Colin
While there's a discussion of 0.5 release plan, here are some candidate topics:
* MM/CC work, to reduce BSoDs and enable further development
* PNP work. vgal has done some work on both HAL and PNP to fix device issues. Also many Windows Server 2003 drivers are usable now. Progressing this and finally integrating into ReactOS is essential at some point.
* Driver issues
* System corruption after hard resets or BSoDs
* Further Win32 work to get many programs usable (I can extensively test Word 2003 if there's help!)
* Getting rid of old fastfat (and progressing NTFS further?)
* Robust networking (adding WPA support, fixing bugs...)
* Installer support for old programs and WoW16 (there's two resources: Win3mu is now open-source and otya128's winevdm)
* Further DirectX work (or just syncs from Wine) and some video work to get more games playable?
* Sound?
* And other things you add or I forgot.
Best regards,
Can
Hi all!
Let me invite you to the November 2018 meeting, taking place next
Thursday, November 29, 2018 at 19:00 UTC.
Invited members will again receive their credentials shortly before the
meeting.
This will be the first meeting since August and I hope we get some more
topics than just the obligatory Status Reports. Please send your
proposals by replying to this mail.
Best regards,
Colin
On 29/11/2018 00:35, Thomas Mueller wrote:
> My hard drives are all partitioned GPT, and lack of support for USB
and GPT has kept me away from doing anything regarding ReactOS. Where
would I put it?
Meantime solution: in a virtual machine.
--
<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>Hi!<br>
<br>
Usually when we talk about ReactOS 0.5, we implicitly think that it will enter beta state there.<br>
So unless you consider this to not completely hold anymore, we can look at what remains to be done/fixed (importantly) so that we may qualify as going into beta state.<br>
(And yes, USB and storage sound strongly as prerequisites for 0.5 in my opinion).<br>
<br>
Best,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Ged Murphy"<br>
A : "'ReactOS Development List'"<br>
Envoyé: mercredi 28 novembre 2018 17:42<br>
Objet : Re: [ros-dev] Status Meeting (November 2018)<br>
<div class="gl_quoted"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style type="text/css"><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:200482091;
mso-list-type:hybrid;
mso-list-template-ids:-551751142 -159226232 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" ></o:shapedefaults>
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" ></o:idmap>
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Some potential talking points:</span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Selecting a new coordinator</span></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Version bump to 0.5</span></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">USB / Storage (perhaps linked to a 0.5 release)</span></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">Mattermost</span></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span style="mso-fareast-language:EN-US">New website progress</span></li>
</ul>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><strong><span lang="EN-US">From:</span></strong><span lang="EN-US"> Ros-dev <ros-dev-bounces(a)reactos.org> <strong>On Behalf Of </strong>Mark Jansen<br>
<strong>Sent:</strong> Wednesday, 28 November 2018 16:13<br>
<strong>To:</strong> ReactOS Development List <ros-dev(a)reactos.org><br>
<strong>Subject:</strong> Re: [ros-dev] Status Meeting (November 2018)</span></p>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">We can discuss this if you are present, but I don't see the value in discussing it without you.</p>
</div>
<div>
<p class="MsoNormal">We have seen before that something discussed without the initiator being present is time not well spent, since it is a bit hard to argue with only one side of the argument present</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Op 26 nov. 2018 12:15 schreef <a href="mailto:hermes.belusca@sfr.fr">hermes.belusca(a)sfr.fr</a>:</p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Hello,<br>
<br>
I may not be available as it's the day when I'm going somewhere for a conference; it just depends at which time I arrive at destination.<br>
<br>
For the meeting we may talk about the best way we can move to delivering all-in-one ReactOS ISOs (containing livecd + installation in both text and GUI modes), and which changes this could imply for our infrastructure (buildbots/website...).<br>
<br>
Best regards,<br>
Hermes</p>
<div style="margin-top:15.0pt">
<p class="MsoNormal">De : "Javier Agustìn Fernàndez Arroyo"<br>
A : "ReactOS Development List"<br>
Envoyé: samedi 24 novembre 2018 22:06<br>
Objet : Re: [ros-dev] Status Meeting (November 2018)<br>
</p>
<div>
<div>
<p class="MsoNormal">I'm at work but I will do my best to attend!</p>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">El sáb., 24 nov. 2018 21:38, Colin Finck <<a href="mailto:colin@reactos.org">colin(a)reactos.org</a>> escribió:</p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Hi all!<br>
<br>
Let me invite you to the November 2018 meeting, taking place next<br>
Thursday, November 29, 2018 at 19:00 UTC.<br>
Invited members will again receive their credentials shortly before the<br>
meeting.<br>
<br>
This will be the first meeting since August and I hope we get some more<br>
topics than just the obligatory Status Reports. Please send your<br>
proposals by replying to this mail.<br>
<br>
<br>
Best regards,<br>
<br>
Colin<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org">Ros-dev(a)reactos.org</a><br>
<a href="http://reactos.org/mailman/listinfo/ros-dev">http://reactos.org/mailman/listinfo/ros-dev</a></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org">Ros-dev(a)reactos.org</a><br>
<a href="http://reactos.org/mailman/listinfo/ros-dev">http://reactos.org/mailman/listinfo/ros-dev</a></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Hello,<br>
<br>
I may not be available as it's the day when I'm going somewhere for a conference; it just depends at which time I arrive at destination.<br>
<br>
For the meeting we may talk about the best way we can move to delivering all-in-one ReactOS ISOs (containing livecd + installation in both text and GUI modes), and which changes this could imply for our infrastructure (buildbots/website...).<br>
<br>
Best regards,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Javier Agustìn Fernàndez Arroyo"<br>
A : "ReactOS Development List"<br>
Envoyé: samedi 24 novembre 2018 22:06<br>
Objet : Re: [ros-dev] Status Meeting (November 2018)<br>
<div class="gl_quoted">
<div dir="auto">I'm at work but I will do my best to attend!</div>
<div class="gmail_quote">
<div dir="ltr">El sáb., 24 nov. 2018 21:38, Colin Finck <<a href="mailto:colin@reactos.org">colin(a)reactos.org</a>> escribió:</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all!<br>
<br>
Let me invite you to the November 2018 meeting, taking place next<br>
Thursday, November 29, 2018 at 19:00 UTC.<br>
Invited members will again receive their credentials shortly before the<br>
meeting.<br>
<br>
This will be the first meeting since August and I hope we get some more<br>
topics than just the obligatory Status Reports. Please send your<br>
proposals by replying to this mail.<br>
<br>
<br>
Best regards,<br>
<br>
Colin<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org" rel="noreferrer" target="_blank">Ros-dev(a)reactos.org</a><br>
<a href="http://reactos.org/mailman/listinfo/ros-dev" rel="noreferrer noreferrer" target="_blank">http://reactos.org/mailman/listinfo/ros-dev</a></blockquote>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Hi all,
Our last 3 servers are finally being migrated on Friday morning (UTC).
Expect downtimes for the following services during this period:
* https://reactos.org
* https://jira.reactos.org
* https://lam.reactos.org
As always, I will try my best to keep the downtimes low and let you know
when everything is over.
Best regards,
Colin Finck
Hi all!
Another server has been migrated to new hardware and software today!
I'm talking about our Git/SVN Server, which also serves BuildBot,
Doxygen, download.reactos.org, etc.
The anticipated and actual downtime has been so low again that I didn't
even have to announce the migration in advance.
Some remarks though:
* If you had file server upload access to svn.reactos.org *and still
need it*, please let me know and I can recreate your account. Have your
SSH public key ready.
Note that I plan to set up an easier and more official file sharing
service for ReactOS soon.
* For obvious reasons, the Mumble server at mumble.reactos.org has not
been migrated and is now officially shut down. I'm looking forward to
finally set up the Mattermost instance once all existing VMs have been
migrated (5 done, 3 to go).
* git.reactos.org is no longer accessible via the git:// protocol.
If you have any URLs using that, please change them to https://.
Cheers,
Colin
I'm not sure I understand this commit, nor the PR that was merged before.
This is a synced module, for a Vista+ export... What's the point of this?
It would have been better to sync with Wine and have this patch upstream.
Le 18/11/2018 à 21:03, Hermès Bélusca-Maïto a écrit :
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=2d320f5a8daf4627458e8…
>
> commit 2d320f5a8daf4627458e81f0ffd51bdd8f60d120
> Author: Hermès Bélusca-Maïto <hermes.belusca-maito(a)reactos.org>
> AuthorDate: Sun Nov 18 21:05:32 2018 +0100
> Commit: Hermès Bélusca-Maïto <hermes.belusca-maito(a)reactos.org>
> CommitDate: Sun Nov 18 21:06:22 2018 +0100
>
> [OLE32] The CoDisconnectContext() stub added in 6a2f9673 (PR #1044) is actually Vista+. Caught by Thomas Faber.
> ---
> dll/win32/ole32/ole32.spec | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dll/win32/ole32/ole32.spec b/dll/win32/ole32/ole32.spec
> index d4ed1163d4..97667918e9 100644
> --- a/dll/win32/ole32/ole32.spec
> +++ b/dll/win32/ole32/ole32.spec
> @@ -23,7 +23,7 @@
> # CoCreateObjectInContext
> # CoDeactivateObject
> @ stdcall -stub CoDisableCallCancellation(ptr)
> -@ stdcall -stub CoDisconnectContext(long)
> +@ stdcall -stub -version=0x600+ CoDisconnectContext(long)
> @ stdcall CoDisconnectObject(ptr long)
> @ stdcall CoDosDateTimeToFileTime(long long ptr) kernel32.DosDateTimeToFileTime
> @ stdcall -stub CoEnableCallCancellation(ptr)
>
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Hi all!
Having converted the last ReactOS SVN repository (press-media) to Git
today, we can finally call the entire Git migration done :)
Well, probably it felt done for you for a long time, but I still
struggled with that last repository until today.
As I'm also about to migrate the Git/SVN server soon, I can finally tell
you about the long-term availability of the old SVN repositories:
* Access to svn.reactos.org over the svn:// protocol will soon be suspended.
* Read-only access to the press-media, project-tools, reactos, and web
SVN repositories at https://svn.reactos.org will be maintained.
This allows you to continue looking up old SVN history whenever Git's
log has problems tracking a file move.
* Access to ViewVC at https://svn.reactos.org/svn and
https://svn.reactos.org/viewcvs will be suspended as well. One less tool
for us to maintain.
Of course, I will again let you know when the actual migration is
happening (or already over :)).
Cheers,
Colin
Hi,
I did not receive anny replies about my question to make reactos
accessible for the blind. I would really suggest to do that while building
the os, instead of doign it when the whole system is fully built.
Hi all!
Our mail server will be shut down for migration
TOMORROW, WEDNESDAY, NOVEMBER 14, AROUND 9:00 UTC
This will result in a temporary downtime for the following services:
* @reactos.org E-Mail addresses
* Mailing lists
* https://iserv.reactos.org
The migration has already been prepared and simulated, so I expect the
downtime to be low and the entire process to only take a few minutes.
I will let you know when everything is back up again.
We look forward to improve the performance, reliability, and especially
maintainability through this migration.
This probably just sounds like a pile of buzzwords to you, but there are
hardly other words to describe a move from HDDs to SSDs, data
replication on even more disks, and gaining independence from a single
hypervisor hardware ;)
Cheers,
Colin
Hello all.
Sorry if this mail is off topic of the mail-list, but am not sure which one is right for my question.
I am writing a program which needs to know exact environment in which it is running. In case of Windows I simply use GetVersionEx and then analyze dwMajorVersion + dwMinorVersion which is enough for my case (then I know which WIN API calls I should use). But I stuck how to recognize that my program runs in ReactOS. I failed to find any docs about it. Any help is appreciated.
P.S. I am not well experienced in WIN API, so if someone gives me an example it will be great.
Hello all,
I have just noticed that ReactOS, when in debug configuration, will only
boot if an output console is set up.
Won't boot if minicom (for example) is not running...
Is that expected?
hello all,
im planning to use ReactOS at a foundation here in Madrid, which is
dedicated to people with intellectual disabilities
he point is, they are using mostly Windows 10, so they are using Win10 apps
are bug reports about Win10 apps acceptable?
Hi all!
ReactOS 0.4.10 will be released tomorrow, Tuesday, November 6, 2018!
The download will be officially available around noon (CEST).
A Press Kit for the ReactOS 0.4.10 release is already available:
https://download.reactos.org/reactos/ReactOS/0.4.10/ReactOS-0.4.10-PressKit…
Feel free to send it to interested parties to let them know about the
upcoming release in advance.
Best regards,
Colin Finck
Hi,
I think it would be much better to implement accessibillity for visualy
impared people when building an os, than having to find ways to make that
possible when everything is built and running. Nvda is a good opensource
screenreader for windows The only big problem is, it heavily depends on
msaa and iaccessible which will not be included in reactos i suppose.
So: what would be the way to make this os accessible for the blind?
I am not a programmer at all so maybe i say stupid things. The most simple
way i could think of is, creating a textmode environment. In this case i
do not mean just a command prompt, like dos, but the full functions but
without graphical interface(like the browser browsh, www.brow.sh) can do
using a headless-firefox to open pages without needing anny graphical
interface(in monochrome mode it displays just text, but is able to
stream youtube/everything firefox can handle). If something like
that can be created in reactos, the only thing needed is to make the
windows binaries of brltty work and much of the accessibility would be
ready to use, as long as every graphic element is banned from the screen
otherwise blrtty will display just lines with ??????????????? on the
braille display.
I am curious to know if some things can be done to make reactos accesible
for the blind.
best regards, Dick
Greetings fellow developers...
After a rather long hiatus (I actually came close to death),
I went back to the DbgCom source and merged some improvements that are now
in the RosIDE I'm working on. Most notably a Preferences settings dialog, but also
some improved performance in the message list painting, and various bug fixes.
The first time you run DbgCom, be sure to execute the Preferences dialog,
and Ok the settings, so they get stored in the registry.
I will make the source dependencies available shortly, they just need to be
cleaned up a bit, since there is currently some hackery in there that I
don't want to publish. I'll notify you on the ROSBE-100 page.
You'll find DbgCom here: https://jira.reactos.org/browse/ROSBE-100
Well, that's it I guess.
Best Regards
/ Love
Hello all.
My family is at home and I need to shut down the AHK bot until the end of the week.
See you later on Ros ;-) Kind regards, Sylvain Petreolle
Hi all,
As announced, I'll be travelling to California this Thursday to attend
the Google Summer of Code Mentor Summit from Friday to Sunday.
I'll be using this opportunity to spread the word about ReactOS, our
experiences with GSoC, and learning from other projects' experiences.
I'm especially interested to hear how others are acquiring talented
students and managing their list of task ideas over the year.
Let's hope this will help us to get more than 1 student next year and
efficiently collect a list of GSoC ideas continuously instead of
preparing it shortly before the deadline ;)
Is there anything else you want me to talk about during the summit?
Cheers,
Colin
I found that this function `InitializeProcThreadAttributeList()` is added
with GetProcAddress but not with the real function. I can provide the real
function from Windows 10.
The function hasn't any imported function, just conatins some arithmatic
operations.
I don't know how to contribute and not familiar with ReactOS repo. So, I
can only provide a c file.
Hello all,
I have just set optical fiber up at my home. The thing is, im completely
sure it will be infra-used
Is there anything in ROS i might do for help with that?
> Isn't it fun that ppl simply don't understand a "NO" I give 'em in the
> forums?!
Thats only a comment of ONE developer. If your medical doctor syas you anything, do you never asks a second doctor again for the same thing, to see if he was right?
> I even explained why and that GreenteaOS is not more than
> stolen ROS code (*)
The only problem you have had is, that he have removed the name "ReactOS" everywhere. But it is still al under the same license like ReactOS.
> filled with questionable code sources like the
> betaarchive forums. So "NO" means go on the other dev's nerves for a
> ugly theme violating our and MS's copyrights?
Why is an Win8-theme violating MS-copyright but
- changing the color of WineMine to Microsofts WinMine
- copying the XP explorer.exe 1:1, only the images on it are different
- having a Look And Feel VERY similar to Win2000
- etc
is all ok?
Greetings
theuserbl
I've some working code for event tracing APIs like StartTrace, OpenTrace,
ControlTrace etc. Those works in Windows 10 but are not present in ReactOS
Advapi.dll. How can I add those APIs?
A crazy idea ..
What about implementing some kind of virtual consoles, just like Linux? The
point is, using ntvdm subsystem, we could allow only console (DOS) apps to
run in there. And some kind of "you are running a console. Switch to
desktop to run this app!" Message is anyone tried to run another stuff
What do you think?
A side effect could be, allow remote connections, etc ... :)
i was thinking about Valve's Linux support (Steam play) and i was wondering
about asking them to support ReactOS via development...
Since Windows XP/2k3 are being abandoned, maybe ReactOS could still run
Steam games... if they support it.
what do you think?
I believe from the testbot log, that my commit made some DLLs grow out of
their assigned memory allocation, but I don't know how to update the dll
address mappings. Help appreciated.
Hi all!
Let me invite you to the August 2018 meeting, taking place this
Thursday, August 30, 2018 at 19:00 UTC.
Invited members will again receive their credentials shortly before the
meeting.
The current agenda is:
1. Status Reports (extended)
Note that this is the first meeting after both GSoC and the
Hackfest.
Participants in either effort are encouraged to also report
their related work, what they liked and didn't like about GSoC/
Hackfest, and what we could do better next time.
As always, I'm open for additional proposals.
I also have to announce that I will definitely be unavailable during the
entire September, so someone else has to invite for and lead the
September meeting.
Best regards,
Colin
Hi all,
I took some time during Hackfest to upgrade our Test_VBox Testbot to
Ubuntu 18.04, which finally brings us VirtualBox 5.2.x support for
sysreg2. Pierre also worked on the relevant BuildBot scripts to improve
their reliability.
This has resulted in
https://github.com/reactos/buildbot_config/commit/388a831eb5ccf67535d8cbd6d…
and since using that script, the infamous "IVirtualBox object is null"
bug hasn't occurred again :)
The upgrade from VirtualBox 4.3.40 to 5.2.10 also resulted in unbearably
slow serial port output at first, but this could be fixed by
https://github.com/reactos/sysreg2/commit/a4eb4a4551618b4af4dc1985ad8c55fe0….
Have a look at this commit if you encounter a slow serial port output in
one of the latest VirtualBox versions with either operating system.
This only leaves a funnily flawed WINE test left, which currently causes
the entire regression testing process to come to a standstill:
https://jira.reactos.org/browse/CORE-14975
Cheers,
Colin
|My proposed architecture diagram for ENIW: Linux app systemd <>
systemd2svchost Windows userland ------ User-mode Linux kernel -------
SVCHOST Windows services ENIW.SYS Windows personalities Kernel-mode
drivers for everything -------------------------- NTOSKRNL.EXE
----------------------------------- ENIW is a component to implement
WSL-like functionality named after WINE and its bacronym is ENIW never
imitated WSL. systemd2svchost is a service translator to run systemd
units as svchost services. Forum thread:
<https://www.reactos.org/forum/viewtopic.php?f=9&t=17434> JIRA ticket:
<https://jira.reactos.org/browse/CORE-13613> Yours, faihfully Erkin Alp |
Hi Timo et al.,
To make the issue wider known than just me comment on GitHub. That
commit introduced a regression.
Le 20/08/2018 à 18:07, Timo Kreuzer a écrit :
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=c219be9409af429909b14…
>
> commit c219be9409af429909b1433da536516b3c3ab823
> Author: Timo Kreuzer <timo.kreuzer(a)reactos.org>
> AuthorDate: Sun Feb 4 19:20:56 2018 +0100
> Commit: Timo Kreuzer <timo.kreuzer(a)reactos.org>
> CommitDate: Mon Aug 20 18:07:35 2018 +0200
>
> [NTOS:MM] Fix paged pool expansion
> ---
> ntoskrnl/mm/ARM3/pool.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/ntoskrnl/mm/ARM3/pool.c b/ntoskrnl/mm/ARM3/pool.c
> index 7cebabe818..113a7aa981 100644
> --- a/ntoskrnl/mm/ARM3/pool.c
> +++ b/ntoskrnl/mm/ARM3/pool.c
> @@ -561,10 +565,11 @@ MiAllocatePoolPages(IN POOL_TYPE PoolType,
> MiInitializePfnForOtherProcess(PageFrameNumber,
> (PMMPTE)PointerPde,
> MmSystemPageDirectory[(PointerPde - MiAddressToPde(NULL)) / PDE_COUNT]);
> +#endif
>
> /* Write the actual PDE now */
> -// MI_WRITE_VALID_PDE(PointerPde, TempPde);
> -#endif
> + MI_WRITE_VALID_PDE(PointerPde, TempPde);
> +
That little change for x86 actually breaks VBox support. It hits an
ASSERT during 3rd stage:
*** Assertion failed: PointerPde->u.Hard.Valid == 0
*** Source File:
/srv/buildbot/Build_GCCLin_x86/build/ntoskrnl/mm/ARM3/miarm.h, line 975
See testbots for instance:
https://build.reactos.org/builders/Test%20VBox/builds/8625/steps/test/logs/…
Cheers,
Pierre
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Why are these misleading? These are checks that Windows does that we are
missing.
Guys, open PRs for changes like these ffs.
Best regards,
Alex Ionescu
On Wed, Aug 8, 2018 at 7:14 PM Thomas Faber <thomas.faber(a)reactos.org>
wrote:
>
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=1ed0f9ab576f094b27e11…
>
> commit 1ed0f9ab576f094b27e11ba374738ecabc00e2e6
> Author: Thomas Faber <thomas.faber(a)reactos.org>
> AuthorDate: Wed Aug 8 19:58:56 2018 +0200
> Commit: Thomas Faber <thomas.faber(a)reactos.org>
> CommitDate: Wed Aug 8 20:08:38 2018 +0200
>
> [HAL] Remove misleading debug prints about USB controllers.
> ---
> hal/halx86/legacy/bussupp.c | 26 --------------------------
> 1 file changed, 26 deletions(-)
>
> diff --git a/hal/halx86/legacy/bussupp.c b/hal/halx86/legacy/bussupp.c
> index a37d875ede..4d20396560 100644
> --- a/hal/halx86/legacy/bussupp.c
> +++ b/hal/halx86/legacy/bussupp.c
> @@ -1128,32 +1128,6 @@ HalpInitializePciBus(VOID)
> }
> }
>
> - /* Check if this is a USB controller */
> - if ((PciData->BaseClass == PCI_CLASS_SERIAL_BUS_CTLR) &&
> - (PciData->SubClass == PCI_SUBCLASS_SB_USB))
> - {
> - /* Check if this is an OHCI controller */
> - if (PciData->ProgIf == 0x10)
> - {
> - DbgPrint("\tDevice is an OHCI (USB) PCI Expansion
> Card. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> -
> - /* Check for Intel UHCI controller */
> - if (PciData->VendorID == 0x8086)
> - {
> - DbgPrint("\tDevice is an Intel UHCI (USB)
> Controller. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> -
> - /* Check for VIA UHCI controller */
> - if (PciData->VendorID == 0x1106)
> - {
> - DbgPrint("\tDevice is a VIA UHCI (USB)
> Controller. Turn off Legacy USB in your BIOS!\n\n");
> - continue;
> - }
> - }
> -
> /* Now check the registry for chipset hacks */
> Status = HalpGetChipHacks(PciData->VendorID,
> PciData->DeviceID,
>
>
Hi all!
Looking at the calendar, it would be time for the July Meeting today.
However, I didn't receive any agenda proposals and also forgot to
announce it in the course of releasing 0.4.9.
So I suggest we postpone the meeting to next week's Thursday, August 2.
Please send agenda proposals by then.
That meeting also allows us to handle last-minute planning regarding the
Hackfest.
Best regards,
Colin
Hi,
I really like this idea. Actually i was thinking something similar about user mode apps like paint or even the file browser of the shell which can be used from windows xp to windows 10. (You need just these three files from us: filebrowser.exe, rshell.dll and browseui.dll).
Ged Murphy <gedmurphy.maillists(a)gmail.com> wrote on Wed, August 1st, 2018, 11:30 PM:
> We could keep components in the reactos git project and just create a new repo for them, however it might still get lost/overshadowed slightly by the main reactos codebase. Another option would be to create a new separate project with one\multiple repos. This would allow us to truly separate components from the reactos project and try to generate interest on their own merit.
>
> We'd need to maximize their visibility by adding a good README.rd files with plenty of buzzwords for the google crawler bot to pick up.
>
> If it was successful and we decide to do more, then we'd need to come up with a format as to how to best manage multiple components.
> Do we have individual repos for each component, which allows dedicated README.rd files? This would give maximum flexibility and allow us to have a separate README.rd for each component.
> Do we bundle everything into one repo similar to how the WDK samples are setup? This is easier to manage, but less convenient for end users, and won't be as visible for people to find in google searches.
>
> Ged.
>
>
> -----Original Message-----
> From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Hermès BÉLUSCA-MAÏTO
> Sent: Wednesday, 01 August 2018 20:20
> To: 'ReactOS Development List' <ros-dev(a)reactos.org>
> Subject: Re: [ros-dev] Postponing the July Meeting
>
> Hi,
>
> This sounds interesting, for potential developers wanting just to work on some module, but not wanting to deal with the whole OS thing.
> Would this mean that we also have to think about git submodules? Because (in the case of the NTFS driver for example) it would be in a different git repo, and then it would have to be automatically downloaded and updated whenever one of the core ROS dev updates his own ROS git repo.
>
> Cheers,
> Hermes
>
> > -----Message d'origine-----
> > De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Ged
> > Murphy Envoyé : mercredi 1 août 2018 20:16 À : 'ReactOS Development
> > List'
> > Objet : Re: [ros-dev] Postponing the July Meeting
> >
> > I have an item for the agenda. I'd like to discuss the possibility of
> > moving some of our drivers out of the main repo and into something more convenient.
> >
> > In case I don't make the meeting, I'll put forward some of my reasons here:
> >
> > This thought has come about due to the btrfs driver which we use from
> > Mark Harmstone. Mark's project receives quite a bit of interest on
> > github, and I'm assuming one of the reasons is that it's so easy to
> > find and build. Searching for 'btrfs windows' lists his project as the
> > top hit in google, and building is as simple as cloning, opening the
> > project in VS and clicking build (assuming you have the
> > WDK)
> >
> > I'm wondering if we did the same thing to some of our drivers, we
> > might generate more interest in them. A good example would be our NTFS driver.
> > When searching for open source NTFS solutions you're only really given
> > Linux and Max options. The reactos driver is buried deep in the search
> > list, and you only see it if you know what you're looking for. Next if
> > you want to build it, you need to clone the main reactos repo, install
> > the build tools, setup and build the environment, build the tool
> > chain, build the linkers libs, etc, etc. There are so many barriers
> > for people who aren't part of the reactos development team that the chance of getting anyone interested in it are practically zero.
> >
> > This process would be much simpler if the code was available to clone
> > as a separate project, and could simply build with the WDK and VS.
> > There's then a chance that it might start to generate interest, and
> > people may start working on it instead of it just bit-rotting deep in our main repo.
> >
> > If we're going to do that, why not consider others too. Network cards,
> > sound stack, USB, boot loaders, printer drivers, directx, etc, There's
> > lots of things that people might be interested in working on and using
> > if they weren't tied to the reactos code base. We obviously benefit
> > from any external interest, and simply pull/import it back into the reactos project.
> >
> > Ged.
> >
> >
> >
> > -----Original Message-----
> > From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Colin Finck
> > Sent: Thursday, 26 July 2018 17:58
> > To: 'ReactOS Development List' <ros-dev(a)reactos.org>
> > Subject: [ros-dev] Postponing the July Meeting
> >
> > Hi all!
> >
> > Looking at the calendar, it would be time for the July Meeting today.
> > However, I didn't receive any agenda proposals and also forgot to
> > announce it in the course of releasing 0.4.9.
> > So I suggest we postpone the meeting to next week's Thursday, August 2.
> >
> > Please send agenda proposals by then.
> > That meeting also allows us to handle last-minute planning regarding
> > the Hackfest.
> >
> > Best regards,
> >
> > Colin
> >
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
Hello!<br>
<br>
I repeatedly get an error "shell submit results failed" while trying to run testbot on a PR patch, see for example https://build.reactos.org/builders/Test%20KVM/builds/20818<br>
and as a result I cannot obtain the results under reactos.org/testman .<br>
<br>
Can someone investigate what is going on?<br>
<br>
Regards,<br>
Hermes
ReactOS Software installer ignores proxy settings. If you are behind
some firewall allowing internet connections only by proxy, you are
lost. The software installer ignores any proxy setting.
--
Thomas
https://jira.reactos.org/secure/attachment/47741/47741_MetricAnalyze.csv
Can you analyze the relations between these parameters? I want the formulas
to get (tmHeight, tmAscent, tmDescent, tmInternalLeading,
tmExternalLeading) values from lfHeight and the other parameters.
NOTE: The formula differs depending on the sign of lfHeight.
Hi all!
With the great last-minute work on the press release, we can finally
release ReactOS 0.4.9 tomorrow, Monday, July 23, 2018!
The download will be officially available around noon (CEST).
A Press Kit for the ReactOS 0.4.9 release is already available:
https://download.reactos.org/reactos/ReactOS/0.4.9/ReactOS-0.4.9-PressKit.z…
Feel free to send it to interested parties to let them know about the
upcoming release in advance.
Best regards,
Colin Finck
Hello all,
Our website has been migrated to a new Login system today and all
components have been upgraded to their latest versions.
In the course of that, the user database has also been moved into an
LDAP directory and cleaned from accounts that have never been used.
Please check that everything is working alright and report bugs in our
JIRA: https://jira.reactos.org
You are also advised to change your password in the self-service at
https://reactos.org/roslogin/?p=selfservice - even to the same one.
Every password change from now on will use a state-of-the-art hashing
algorithm (salted SHA-512 with 6000 rounds) to protect your account from
credential theft.
Unfortunately, there have been several newer accounts, for which the
password could not be migrated.
If you encounter problems logging in, please reset your account password
at https://reactos.org/roslogin/?p=forgot to regain access.
Best regards,
Colin Finck
Hi all!
The ReactOS Website along with the Forum, Wiki, and JIRA bug tracker
will be down for maintenance for several hours during the day (European
time) on Wednesday, July 4.
In the course of this process, the user database will be migrated to the
new RosLogin Single-Sign-On system
(https://github.com/reactos/web/tree/master/www/www.reactos.org/roslogin)
and the Forum and Wiki software will be upgraded to their latest releases.
This is expected to put an end to our login weirdnesses (dead Login
buttons, 30 minute propagation delay to JIRA), solve the CAPTCHA
problems people were reporting, and increase the maintainability of the
website.
I will be on the #reactos IRC channel during the migration and give
status updates there.
Best regards,
Colin
Hi all!
Let me invite you to the June 2018 meeting, taking place this Thursday,
June 28, 2018 at 19:00 UTC.
Invited members will again receive their credentials shortly before the
meeting.
The current agenda is:
1. Status Reports
2. ReactOS Hackfest on August 16 - 21
3. 0.4.9 release on July 14
I'm open for additional proposals.
Best regards,
Colin
This change (on my own code snippet btw, see commit 5a1a35ca5a6) was necessary because otherwise, the StringPrintf call that is done below (which would then use a WindowTitleU.Buffer == NULL) would generate the harderror dialog title: "(null)" (in addition to other strings being appended), instead of just an empty string.
And so the bug is that I forgot to adjust the condition that needs to be checked before freeing the window title string (if it has been allocated).
Hermès
> -----Message d'origine-----
> De : Thomas Faber [mailto:thomas.faber@reactos.org]
> Envoyé : samedi 9 juin 2018 09:21
> À : ros-dev(a)reactos.org; Hermès Bélusca-Maïto
> Objet : Re: [ros-diffs] 01/01: [USERSRV] HardError: Fix compilation warning;
> fix few comments; fix the default empty window title string.
>
> On 2018-04-08 16:17, Hermès Bélusca-Maïto wrote:
> > /* Retrieve the window title of the client, if it has one */
> > - RtlInitEmptyUnicodeString(&WindowTitleU, NULL, 0);
> > + RtlInitEmptyUnicodeString(&WindowTitleU, L"", 0);
>
> This looks like a bug. Can you explain why you think it's necessary please?
>
> In particular, it will break this:
>
> if (WindowTitleU.Buffer) RtlFreeUnicodeString(&WindowTitleU);
>
>
> Thanks,
> Thomas
I've found this mirror repo on GitLab, it was created today:
https://gitlab.com/reactos/reactos
Does it belong to the ReactOS team? If not, we may have problems.
----
Regards,
Stas'M
On 2018-04-08 16:17, Hermès Bélusca-Maïto wrote:
> /* Retrieve the window title of the client, if it has one */
> - RtlInitEmptyUnicodeString(&WindowTitleU, NULL, 0);
> + RtlInitEmptyUnicodeString(&WindowTitleU, L"", 0);
This looks like a bug. Can you explain why you think it's necessary please?
In particular, it will break this:
if (WindowTitleU.Buffer) RtlFreeUnicodeString(&WindowTitleU);
Thanks,
Thomas
Hey there !
Went through the reactOS GSOC’18 page. I am interested in making web interface for reactos which can show all GitHub reactos repos, commits, etc using the GitHub API. (https://www.reactos.org/wiki/Google_Summer_of_Code_2018_Ideas#Developer_Web…)
Looking forward to work on the same idea for GSOC’19 under your mentorship. Need to know more about layout of the web interface. Kindly help!
thanks
Hi all!
It's official now! The ReactOS Hackfest 2018 will take place from
Thursday, 16th August 2018 to Tuesday, 21st August 2018 in Berlin, Germany.
Thanks to Thomas, the event location is already checked out ("definitely
more space than in Cologne") and he has found a hostel nearby.
All information can be found at
https://reactos.org/wiki/ReactOS_Hackfest_2018, with the lists for
registering yourself and collecting ideas at
https://reactos.org/wiki/ReactOS_Hackfest_2018/Lists
Hope to see you in August!
Cheers,
Colin
Team members and other interested parties,
At this month's meeting, we decided we had to have a talk about the growing
number of open pull requests. From such a discussion, we game up with a set
of rules that the team members should follow, when reviewing or managing
PRs.
If you are such a person, please take a moment to make sure you can agree
with those rules. There's a PR waiting for your input:
https://github.com/reactos/reactos/pull/585
Hi all!
Let me invite you to the May 2018 meeting, taking place this Thursday,
May 31, 2018 at 19:00 UTC.
Invited members will again receive their credentials shortly before the
meeting.
Based on requests and current topics, the agenda looks like this:
1. Status Reports
==============
Like last time, participants are requested to just post their
prepared reports again to not waste any minute.
2. Improving our handling of PRs and JIRA reports
==============================================
The global JIRA permissions have been changed this month and there
has been a lot of bad blood regarding issues marked as "trivial".
On the one hand, trivial PRs waste a lot of time of our core
developers as long as they are the only ones able to commit them.
On the other hand, trivial PRs still add minor improvements to the
code, so it would be wrong to just close them as invalid.
Let's have an open discussion on this topic and try to establish
rules we can all work with without taking this problem to a personal
level.
3. Google Summer of Code
=====================
This will be the first meeting, which could be joined by our GSoC
student Victor Perevertkin. If he or the mentors have questions that
are better discussed with all developers in the monthly meeting,
let's do this here.
4. Changes affecting base addresses
================================
Robert Naumann has requested adding this topic to the agenda.
He couldn't merge several PRs translating .mc files, because that
would blow up the kernel and require a regeneration of all base
addresses. He requested a brainstorming session in this meeting
to get to a conclusion how to deal with this problem.
I know that Joachim Henze has also attempted to change base addresses
lately to fix Photoshop CS2, so this is probably the right time to
deal with this problem.
Further topics can be requested by replying to this mail.
See you all on Thursday!
Best regards,
Colin
Hi!<br>
<br>
To that I see one solution, that has actually already been proposed in the PR:<br>
we make an external package (a la Wine gecko) that one can download during installation, or later through RAPPS.<br>
Then this package (possibly together with other heavy core ones?) could be hosted in some GitHub sub-repo or elsewhere...<br>
Closing the PR now would definitely not be the right solution.<br>
<br>
Best,<br>
H.<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Colin Finck"<br>
A : ros-dev(a)reactos.org<br>
Envoyé: mercredi 30 mai 2018 18:21<br>
Objet : Re: [ros-dev] Status Meeting (May 2018)<br>
<div class="gl_quoted">Am 30.05.2018 um 13:26 schrieb Ged Murphy:<br>
> Potential problems are:<br>
> 4) something else?<br>
<br>
I've been struggling with e.g. https://github.com/reactos/reactos/pull/276<br>
<br>
On the one hand, we definitely need official support for Chinese,<br>
Korean, and Japanese character sets.<br>
On the other hand, this must not bloat up ReactOS by default, and just<br>
dropping a 12 MB font into the repository definitely does.<br>
So what is the ideal solution? I don't even know myself.<br>
<br>
- I could leave the PR open and hope that the submitter addresses my<br>
comments and comes up with a better solution. That hasn't happened in<br>
the last months.<br>
<br>
- I could close the PR right away. That would give the submitter no<br>
chance to address my comments and may even look disrespectful. And the<br>
original problem tends to be forgotten.<br>
<br>
- I could close the PR and open a JIRA issue describing the problem.<br>
If we decide on that as a general rule, we would put another burden on<br>
every reviewer. Additionally, such general JIRA issues tend to rot in<br>
our database as well.<br>
<br>
I think we often have this situation where the submitted PR is wrong,<br>
but we don't know the right solution either, and therefore keep the PR<br>
open. If we can better deal with these cases, the number of open PRs may<br>
decrease significantly.<br>
<br>
<br>
- Colin<br>
<br>
_______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://www.reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Phoronix has published an article regarding 0.4.9, but Community Changelog is a month behind! They gave links despite warnings!
Please get the news deleted until I make an update!!!
Hello. I am wondering if testman source code is available to download.
----------------------------------------------SIGNATURE------------------------------------------------------ Draudžiama tiesiogiai teikti reklama konkreciam asmeniui, jeigu yra aiškiai išreikštas šio asmens nesutikimas. Už reklamos naudojimo reikalavimu nesilaikyma istatymas numato bauda nuo 300 iki 10 tukst. EUR. Nesutinku gauti reklamos ar reklaminio pobudžio žinuciu! Nesutinku, jog mano duomenys butu naudojami rinkodaros tikslais! Nesutinku, jog mano duomenys butu perduodami treciosioms salims be mano sutikimo!
unsubscribe
On Sun, May 6, 2018 at 8:00 AM, <ros-dev-request(a)reactos.org> wrote:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: "Note: LibreOffice 5.4 will be the last codeline
> tosupport Windows XP or Vista" (Javier Agustìn Fernàndez Arroyo)
> 2. Re: "Note: LibreOffice 5.4 will be the last codeline
> tosupport Windows XP or Vista" (Erkin Alp Güney)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 6 May 2018 01:02:53 +0200
> From: Javier Agustìn Fernàndez Arroyo <elhoir(a)gmail.com>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Subject: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
> codeline tosupport Windows XP or Vista"
> Message-ID:
> <CAAHf8rcC_PhT6OHmf-frhuB6tarj6SAj3un8AipR48hChEDM
> gQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> as an alternative, Apache OpenOffice still supports NT5
>
> On Sun, May 6, 2018 at 12:38 AM, David Quintana (gigaherz) <
> gigaherz(a)gmail.com> wrote:
>
> > No need to panick, they themselves link to this as an archive of old
> > versions: https://downloadarchive.documentfoundation.org/
> libreoffice/old/
> > So even if it's gone from their own site, it should remain there.
> >
> > On 6 May 2018 at 00:30, Javier Agustìn Fernàndez Arroyo <
> elhoir(a)gmail.com>
> > wrote:
> >
> >> hello again guys,
> >>
> >> What if we get latest NT5 libreoffice version (5.4.6 as of now, and
> >> 5.4.7-rc1 is out) just for testing purposes? i guess it will be dropped
> >> from official website, andi don´t know if it will be still available in
> any
> >> way......
> >>
> >> On Sat, Jul 1, 2017 at 9:29 AM, Michael Fritscher <
> michael(a)fritscher.net>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> is there a list which need to be done to get the basic NT6 architecture
> >>> just to get feeling how much work it is? Sadly, I'm afraid that we'll
> >>> need a proper NT6 architecture to get modern drivers running, won't we?
> >>>
> >>> Best regards,
> >>> Michael Fritscher
> >>>
> >>> On 30.06.2017 11:46, Ged Murphy wrote:
> >>> > That’s what’s currently being worked on.
> >>> >
> >>> > The kernel still closely follows the NT5.2 architecture, but user
> mode
> >>> will have NT6+ compatibility shims to allow modern applications to run
> >>> correctly.
> >>> >
> >>> >
> >>> >
> >>> > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of
> >>> ajaczgz(a)yahoo.es
> >>> > Sent: 30 June 2017 05:47
> >>> > To: ReactOS Development List <ros-dev(a)reactos.org>
> >>> > Subject: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
> >>> codeline tosupport Windows XP or Vista"
> >>> >
> >>> >
> >>> >
> >>> > I think it’s no neccesary to implement NT6, only to avoid the
> >>> compatibility tests to NT6 and implement only the characteristics that
> the
> >>> most of the programs uses.
> >>> >
> >>> >
> >>> >
> >>> > Best regards
> >>> >
> >>> > Antonio J. Arrieta Cuartero
> >>> >
> >>> >
> >>> >
> >>> > Enviado desde mi Lumia 635 con Windows 10 Mobile
> >>> >
> >>> >
> >>> >
> >>> > De: Riccardo Paolo Bestetti <mailto:riccardo.kyogre@live.it>
> >>> > Enviado: jueves, 29 de junio de 2017 22:11
> >>> > Para: ReactOS Development List <mailto:ros-dev@reactos.org>
> >>> > Asunto: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
> codeline
> >>> tosupport Windows XP or Vista"
> >>> >
> >>> >
> >>> >
> >>> > Hello Colin,
> >>> >
> >>> > As this definitely wasn't the predominant thinking the last time this
> >>> same discussion took place, Hermès' email scared me a bit. Thank you so
> >>> much for clarifying.
> >>> >
> >>> >
> >>> >
> >>> > Best regards,
> >>> >
> >>> > Riccardo Paolo Bestetti
> >>> >
> >>> >
> >>> >
> >>> > -----Original Message-----
> >>> >
> >>> > From: Ros-dev [mailto:ros-dev-bounces@reactos.org] On Behalf Of
> Colin
> >>> Finck
> >>> >
> >>> > Sent: giovedì 29 giugno 2017 20:00
> >>> >
> >>> > To: ros-dev(a)reactos.org <mailto:ros-dev@reactos.org>
> >>> >
> >>> > Subject: Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
> >>> codeline to support Windows XP or Vista"
> >>> >
> >>> >
> >>> >
> >>> > Rest assured, we know that ReactOS won't be of much use if we stay
> >>> NT5-only. Work is underway to provide a seamless support of NT6
> >>> applications on top of the existing codebase.
> >>> >
> >>> > Also the majority of developers should be using an NT6 platform
> >>> themselves, so they certainly aim for support for NT6 applications.
> >>> >
> >>> > Finally, applications compiled by modern versions of Visual Studio
> are
> >>> NT6-only by default, so supporting this platform is unavoidable.
> >>> >
> >>> >
> >>> >
> >>> > Just my two cents, as the previous replies could lead you to believe
> >>> we're failing the reality check.
> >>> >
> >>> >
> >>> >
> >>> > Cheers,
> >>> >
> >>> >
> >>> >
> >>> > Colin
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > Am 29.06.2017 um 18:54 schrieb Riccardo Paolo Bestetti:
> >>> >
> >>> >> I’m just gonna snap in for my yearly IT guy NT6 rant: this mindset
> is
> >>> >
> >>> >> going to kill the project by making it useless whenever it reaches a
> >>> >
> >>> >> usable state.
> >>> >
> >>> >>
> >>> >
> >>> >> Windows XP/Server 2003 use is **already** marginal as of today, and
> >>> >
> >>> >> it’s only gonna get “worse” as more and more networks get infected
> by
> >>> >
> >>> >> ransomware and institutions all over the world wake up and update
> >>> (and
> >>> >
> >>> >> as time passes of course). It’s not a matter of “fancy”, it is a
> >>> >
> >>> >> matter of what people use on their computers. With that argument you
> >>> >
> >>> >> may as well advocate for DOS.
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> Please don’t be offended, as always this is only intended as a
> >>> reality
> >>> >
> >>> >> check.
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> Best regards,
> >>> >
> >>> >>
> >>> >
> >>> >> Riccardo Paolo Bestetti
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> *From:*Ros-dev [mailto:ros-dev-bounces@reactos.org] *On Behalf Of
> >>> >
> >>> >> *Hermès BÉLUSCA-MAÏTO
> >>> >
> >>> >> *Sent:* giovedì 29 giugno 2017 16:09
> >>> >
> >>> >> *To:* 'ReactOS Development List' <ros-dev(a)reactos.org <mailto:
> >>> ros-dev(a)reactos.org> >
> >>> >
> >>> >> *Subject:* Re: [ros-dev] "Note: LibreOffice 5.4 will be the last
> >>> >
> >>> >> codeline to support Windows XP or Vista"
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> I’m wondering for which useless / fancy features they need Windows
> 7+
> >>> >
> >>> >> support only….
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> H.
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> *De :*Ros-dev [mailto:ros-dev-bounces@reactos.org] *De la part de*
> >>> >
> >>> >> Javier Agustìn Fernàndez Arroyo *Envoyé :* jeudi 29 juin 2017 15:48
> >>> *À
> >>> >
> >>> >> :* ReactOS Development List *Objet :* [ros-dev] "Note: LibreOffice
> >>> 5.4
> >>> >
> >>> >> will be the last codeline to support Windows XP or Vista"
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> https://wiki.documentfoundation.org/Releases/5.4.0/RC1
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> FYI
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >>
> >>> >
> >>> >> _______________________________________________
> >>> >
> >>> >> Ros-dev mailing list
> >>> >
> >>> >> Ros-dev(a)reactos.org
> >>> >
> >>> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >>> >
> >>> >>
> >>> >
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> >
> >>> > Ros-dev mailing list
> >>> >
> >>> > Ros-dev(a)reactos.org <mailto:Ros-dev@reactos.org>
> >>> >
> >>> > http://www.reactos.org/mailman/listinfo/ros-dev
> >>> >
> >>> > _______________________________________________
> >>> >
> >>> > Ros-dev mailing list
> >>> >
> >>> > Ros-dev(a)reactos.org <mailto:Ros-dev@reactos.org>
> >>> >
> >>> > http://www.reactos.org/mailman/listinfo/ros-dev
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > _______________________________________________
> >>> > Ros-dev mailing list
> >>> > Ros-dev(a)reactos.org
> >>> > http://www.reactos.org/mailman/listinfo/ros-dev
> >>> >
> >>>
> >>>
> >>> _______________________________________________
> >>> Ros-dev mailing list
> >>> Ros-dev(a)reactos.org
> >>> http://www.reactos.org/mailman/listinfo/ros-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> Ros-dev mailing list
> >> Ros-dev(a)reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >>
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
Due to my family presence, I need to stop the Test KVM AHK bot during this week end.I have good news regarding CORE-14536 and sound in general.
"I'll be back." Kind regards, Sylvain Petreolle
Le Vendredi 27 avril 2018 14h46, Serge Gautherie <reactos_serge_161107(a)gautherie.fr> a écrit :
Hello Sylvain,
Test KVM AHK is offline since
"about 1 day ago (2018-Apr-25 18:27:36)".
Thanks.
--
1) I thought certain MDL fast I/O routines can get called at DISPATCH_LEVEL
2) For perf reasons, causing a page-fault in the middle of a "fast I/O" is
probably a bad idea.
That being said -- these concerns seem silly since we are talking about the
"Null" driver which... is entirely PAGED_CODE and clearly neither #1 or #2
are actual issues.
In Windows, the fast I/o table is part of the DEVICE_OBJECT itself. Not
sure why our driver allocates a separate pool allocation to begin with.
Best regards,
Alex Ionescu
On Mon, Apr 23, 2018 at 1:30 AM, Ged Murphy <gedmurphy.maillists(a)gmail.com>
wrote:
> They're pagable in NT6, I don't know whether that's the case in NT5.
>
> Change looks good to me, I'm not really sure why Alex used NNP?
> Perhaps our kernel does/did things slightly differently back when he wrote
> the Null driver?
>
> Ged.
>
> -----Original Message-----
> From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Thomas Faber
> Sent: Monday, 23 April 2018 07:49
> To: Hermès Bélusca-Maïto <hermes.belusca-maito(a)reactos.org>
> Cc: ros-dev(a)reactos.org
> Subject: Re: [ros-dev] [ros-diffs] 01/01: [NULL] Additions for the Null
> driver.
>
> On 2018-04-22 22:23, Hermès Bélusca-Maïto wrote:
> > diff --git a/drivers/base/null/null.c b/drivers/base/null/null.c index
> > 610e886ddd..0d4ed541de 100644
> > --- a/drivers/base/null/null.c
> > +++ b/drivers/base/null/null.c
> > @@ -181,26 +199,16 @@ DriverEntry(IN PDRIVER_OBJECT DriverObject,
> > DriverObject->MajorFunction[IRP_MJ_READ] = NullDispatch;
> > DriverObject->MajorFunction[IRP_MJ_LOCK_CONTROL] = NullDispatch;
> > DriverObject->MajorFunction[IRP_MJ_QUERY_INFORMATION] =
> > NullDispatch;
> > + DriverObject->DriverUnload = NullUnload;
> >
> > - /* Allocate the fast I/O dispatch table */
> > - FastIoDispatch = ExAllocatePoolWithTag(NonPagedPool,
> > - sizeof(FAST_IO_DISPATCH),
> > - 'llun');
> > - if (!FastIoDispatch)
> > - {
> > - /* Failed, cleanup */
> > - IoDeleteDevice(DeviceObject);
> > - return STATUS_INSUFFICIENT_RESOURCES;
> > - }
> > -
> > - /* Initialize it */
> > - RtlZeroMemory(FastIoDispatch, sizeof(FAST_IO_DISPATCH));
> > - FastIoDispatch->SizeOfFastIoDispatch = sizeof(FAST_IO_DISPATCH);
> > + /* Initialize the fast I/O dispatch table */
> > + RtlZeroMemory(&FastIoDispatch, sizeof(FastIoDispatch));
> > + FastIoDispatch.SizeOfFastIoDispatch = sizeof(FastIoDispatch);
> >
> > /* Setup our pointers */
> > - FastIoDispatch->FastIoRead = NullRead;
> > - FastIoDispatch->FastIoWrite = NullWrite;
> > - DriverObject->FastIoDispatch = FastIoDispatch;
> > + FastIoDispatch.FastIoRead = NullRead;
> > + FastIoDispatch.FastIoWrite = NullWrite;
> > + DriverObject->FastIoDispatch = &FastIoDispatch;
>
>
> Are you sure FAST_IO_DISPATCH is allowed to be pageable? It seems to only
> be used at low IRQLs, so it seems logical. However I see it allocated
> nonpaged everywhere else and can't seem to find definitive documentation on
> the subject.
> (And yes, most filesystem drivers use a static structure, but those
> drivers don't use MmPageEntireDriver)
>
> Thanks,
> Thomas
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>