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.