[ros-dev] Re: Mail server maintenance on Tuesday, 6th December

[Colin Finck]

Hi all!

It took a while, but the mail server and mailing list migration is 
finally done!


Say hello to https://lists.reactos.org -- which provides a much better 
web interface to browse, search, and manage our mailing lists.
I've migrated ros-announce, ros-dev, ros-diffs, ros-general, and 
ros-priv. I saw no need for migrating any other lists, though this could 
be done any time (with full archives) if the need arises.
If you're subscribed to any of these lists, nothing changes for you. You 
will continue to receive your mails as usual.
If you want to change your settings, you will need to create an account 
at https://lists.reactos.org. You can connect that account to one or 
more E-Mail addresses and configure your subscription settings for all 
ReactOS mailing lists. The previous autogenerated per-subscription 
passwords no longer apply.


We're still providing the old archives at e.g. 
https://reactos.org/pipermail/ros-dev to keep existing URLs intact. 
However, they are no longer updated (and point to the URL of the new 
archives).


Let me know if anything broke or if you find any broken URLs to the old 
mailing lists. Or better fix them right away :)


Kudos go again to Martin von Wittich from IServ GmbH, who provided 
valuable assistance during the migration!


Best regards,

Colin


Am 30.11.2022 um 18:10 schrieb Colin Finck:

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

___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev


OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list -- ros-dev@reactos.org
To unsubscribe send an email to ros-dev-le...@reactos.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

[ros-dev] Mail server maintenance on Tuesday, 6th December

[Colin Finck]

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


OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [reactos] 01/01: [COMCTL32] Addendum to last commit (#3674) CORE-17199

[Colin Finck]

Joachim Henze wrote:

commit adee5ca255b7ed21f359ca8c1ca06bd44db90dcf
Author: Joachim Henze 
AuthorDate: Mon Jun 28 02:05:56 2021 +0200
Commit: Joachim Henze 
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 = , .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 =*/ , /*.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/889eab78ca7c0f17a2ada9ff20de5807a293cdfe 
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



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] The situation with version 0.4.14

[Colin Finck]

Hey Victor,

Thanks for bringing up that topic again. Indeed, it's really time for 
0.4.14..


I want to get forward with the release, hence I tend to vote for 1.
However, it's also wrong to just ignore Joachim's tremendous work in 
compiling the list of regressions, and his valid concerns.


Which is why I suggest a compromise: Let's come together next weekend 
(20/21 February) and try to kill as many regressions as possible: 
https://reactos.org/wiki/Tests_for_0.4.14#known_unfixed_regressions_in_descending_order_of_introduction


It may or may not work, but then we have at least tried everything we 
can as a volunteer-driven open-source project.


Who else is going to join?

Cheers,

Colin


Am 09.02.2021 um 16:47 schrieb Victor Perevertkin:

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


___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev





OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] The situation with version 0.4.14

[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.
when things go on this slow when will reactos 1.0 finally be there? in 
2050? who cna tell if we even run software on a laptop or pc than, if 
there is even a device available on which this will runn at all or if 
there would be one singel user wanting to use something not totlaly 
ai-driven?
reactos was ment as a user-project, like ubuntu for many users as their 
desktop os. now it is just some fun for a few devs resulting in nothing 
usable after 20 years. what is the idea behind this? if i was the 
maintainer of this project i would state this:

we can do 2 things: 1. work hard and build version 1.0 in 5 years from now
or 2. stoop this waste of time of running behind the facts and having to 
rebuild it everytime agian because the project goes to slow for hardware 
it is written for to end up in a museum before somethign happens.

as an end-user i am highly disappointed in this project.


___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev




OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Mail server maintenance on Thursday, 4th February

[Colin Finck]

The maintenance went well and all services should be back up.
Please let me know if you encounter any problems using the mail system 
or mailinglists.


Colin


Am 24.01.2021 um 21:53 schrieb Colin Finck:

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


___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev





OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Mail server maintenance on Thursday, 4th February

[Colin Finck]

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



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2020)

[Colin Finck]

Hello everybody and a happy new year!

Am 26.11.2020 um 09:27 schrieb Colin Finck:
So let's have an open discussion and voting process right here on the 
mailing list for everyone to see, to decide this once and for all!
Just reply to this mail, tell about your reasons - and more importantly 
tell whether you support or reject dropping MSVC 2010 support.


Votes by CORE REACTOS MEMBERS are then counted on 1ST JANUARY 2021.


1st January has passed and it's time to count the votes cast on the 
mailing list.
First of all, a big thank you to the people who have submitted their 
opinions! Your votes matter to get the best possible overview on this topic.


It's a pity that many developers have not replied, when I'm sure that 
they have an opinion here.
On the other hand, it's quite understandable considering that this is 
already the 3rd (and definitely last!) time we are debating this matter.


So without further ado, here are the votes everyone can gather from the 
replies on ros-dev:



Dropping MSVC 2010 support for building ReactOS
===
* Colin Finck
* Dominik Hornung
* Ged Murphy
* Mark Jansen
* Stanislav Motylkov
* Victor Perevertkin

Keeping MSVC 2010 support for building ReactOS
==
* Doug Lyons
* Hermès Bélusca-Maïto
* Joachim Henze
* Oleg Dubinskij


Third discussion, third time it's the same result.
Thanks for providing a clear answer on that!

Note that I haven't applied the "CORE REACTOS MEMBERS" filter here, but 
that would lead to roughly the same number of votes getting subtracted 
on both sides.
I also leave it up to you to merge this result with the votes cast in 
https://github.com/reactos/reactos/pull/2658. However, there is just no 
calculation where the "Keeping" fraction has a majority.



I'm glad to say that this result allows us to continue improving 
ReactOS. By not sticking with abandoned compilers like MSVC 2010 
indefinitely, we can leverage the powers of C99 and C++11 and all 
third-party projects that have been developed after 2010.


Victor's recent integration of WDF/KMDF has already paved the way for a 
new storage stack that many of you could already test.
And an import of libc++ would finally fix the mess that our current C++ 
STL support is.



Cheers,

Colin



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2020)

[Colin Finck]

1. Visual Studio 2010 is the last version that works (or almost works) 
on ReactOS [...]

2. Dropping useful features is not really a good idea at all.


Oleg, nobody wants to take away any features here. VS2010 will continue 
to run on ReactOS now and in the future. This discussion is merely about 
*compiling ReactOS* with VS2010.


Everyone, please put personal preferences aside and think about the big 
picture:

We don't have the workforce Microsoft had when creating Windows XP.
The only way we can ever create a compatible OS is by leveraging modern 
technologies not yet available back then and building on the open-source 
work third parties have already done for us.
If we however decide to limit us to 10-year-old technologies now, we can 
do neither. Don't expect us to ever get this project into a usable state 
in a lifetime then.

The future of the project is at stake here!

I don't want to repeat myself, so let me just link to the reasoning I 
already gave:

* https://reactos.org/archives/public/ros-dev/2020-December/019158.html
* https://github.com/reactos/reactos/pull/2658#issuecomment-619540076
* https://github.com/reactos/reactos/pull/2658#issuecomment-629498043
* https://github.com/reactos/reactos/pull/2658#discussion_r427615924
* https://github.com/reactos/reactos/pull/2658#issuecomment-631113317


Best regards,

Colin Finck



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2020)

[Colin Finck]

Joachim, I know about your obsession with Windows XP, which makes it 
hard to introduce any tool that was created in the last 5 years to 
improve ReactOS development.
In fact, I've already spent multiple days on porting current CMake and 
Ninja back to Windows XP just to not lock you out [1] [2] [3].


A few of your statements can't be left unchallenged though.



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?


Hah, nice try! People aren't accepting a 2-year-old decision on dropping 
VS2010 support yet, even hijack unrelated PRs to mix requested style 
changes with a call for restoring VS2010 support [4] - and you're 
already asking for the new developers coming from that "welcoming" 
attitude towards modern technologies..
Let me be straight: This ain't gonna happen until we import a C++ 
standard library that actually supports modern C++!


Anyway, it's not like my claims are unfounded. Quoting Dominik2 from 
Mattermost, one of the potential new developers:


   "if 2020 is the year were ReactOS is ready to leave the 80ths of
   programming (win32 and C), let me know."

He already put his money where his mouth is and started importing 
Clang's up-to-date and maintained libc++ into ReactOS. Unfortunately, 
the efforts got halted for now by the equally sorry state of our CRT.




-"we should not be limited to strict C89" <- No one did request for that. All 
we want is to remain compatible to VS2010.


Requesting compatibility with VS2010 is exactly the same as requesting 
us to stay with C89.

Visual Studio has no C99 support until version 2013 [5] [6].



-"syncing BTRFS is a bit harder" <- So what? Then let others do the job.
-"libc++" <- I see no urgent need and nothing it would give in return that 
would outweight what we would sacrifice.


I get the feeling that you still believe we can code an entire operating 
system on our own and don't need any third-party components..
We already need VS2010-specific hacks for almost every library we 
import. As someone who has done that kind of work in the past, let me 
tell you that it adds at least a day of work for each sync. Work that is 
unthankful and could otherwise be spent on actual ReactOS development.
Multiply that by the number of external dependencies and you get an idea 
of the wasted time.


Besides, you don't seem to be aware of the sad state of C++ runtime 
support in ReactOS: We're currently trying to get away with the 
unmaintained C++98 STLport on MSVC builds and the *ROSBE-PROVIDED* GNU 
libstdc++ on GCC builds.
Each RosBE release requires a new hack in our tree to somehow glue RosBE 
libstdc++ (compiled against RosBE CRT) and target code (compiled against 
ReactOS CRT) together [7]. The result is still undebuggable, as it has 
symbol addresses belonging to the unique libstdc++ build of that RosBE 
installation.


Calling that situation "no[t] urgent" is grossly negligent.



My arguments again for keeping VS2010:
-VS2010 creates the smallest binaries of all compilers we do support


This is not a metric that is in any way relevant for an alpha-stage 
operating system that only exists as Debug builds..
Get someone to spend a day or two on optimizing our Release builds and 
figuring out what blows up the binaries on other compilers, and this 
argument will no longer hold.




-VS2010 CAN be installed in ros, when ros is installed as Server during 2nd 
stage
-VS2010 can now even open the VS2010 cmd prompt


Yes, that's a really nice achievement, and exactly why nobody here wants 
to remove support for *running* VS2010 *under* ReactOS :)


This entire discussion is only about *compiling ReactOS* with VS2010. 
Which, if made a strict requirement for the upcoming years, jeopardizes 
the future of the project, as I illustrated above.




-no other VS>2010 can even complete its setup in ros, and that will remain like 
that for many years to come


Again, you're not looking into the future here and totally neglect the 
application support for NT6+ that is being worked on.




-VS2010 [...] covers > 95% of CPP2011-standard.


Not even close: [8]


Best regards,

Colin Finck


[1] https://github.com/libuv/libuv/pull/2800
[2] https://github.com/reactos/CMake/commits/cmake-3.17.2-reactos
[3] 
https://github.com/ninja-build/ninja/pull/1674#pullrequestreview-425803525

[4] https://github.com/reactos/reactos/pull/3094#pullrequestreview-541258099
[5] https://stackoverflow.com/q/6688895
[6] 
https://devblogs.microsoft.com/cppblog/c99-library-support-in-visual-studio-2013/
[7] 
https://github.com/reactos/reactos/commit/fdd1d7d60c33b08f4181df8e81c739694762898b

[8] https://msdn.microsoft.com/en-gb/library/hh567368.aspx



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2020)

[Colin Finck]

Am 25.11.2020 um 22:26 schrieb Hermès BÉLUSCA-MAÏTO:

What about that discussion about why we have ditched out MSVC 2010 support


You mean reintroducing an ancient compiler that forces us to hack around 
its incapacity to deal with anything more modern than C89? One that 
already makes it harder to import third-party components and attract new 
developers?


Let's face it, we already make our incredible job of writing a 
Windows-compatible operating system even harder than Microsoft's - by 
supporting both GCC and MSVC. We spend enormous amounts of time to just 
get the basics right for both toolchains, and still fail at things like 
the C++ standard library. Ditching MSVC 2010 finally paves the way for 
importing a modern and trusted third-party C++ library like Clang's 
libc++ to replace our hacked and unmaintained stlport. Going even 
further, we could finally draw from the huge pool of talented C++ 
developers, who leverage the benefits of C++11 and beyond. Think about 
that next time you debug a memory leak or a deadlock that would have 
been impossible through std::unique_ptr or std::mutex.


This project won't ever become usable in a lifetime if we don't go with 
the time but stick to old habits forever. There is no inherent value in 
supporting old compilers, just wasted developer time.
And don't tell me about self-hosting: It's not like anybody productively 
uses ReactOS for building ReactOS right now. If you just want to 
demonstrate that, use the RosBE GCC-based toolchain. I already spent 
hours on backporting that back to ReactOS/Windows XP...



Now I usually would have put that on the agenda for the meeting and 
asked for a vote.
But as this year's ditching of MSVC 2010 is just the implementation of a 
meeting decision from 2 years ago 
(https://reactos.org/project-news/december-2018-meeting-minutes/), 
meeting votes are apparently not considered binding here. Neither is 
apparently the discussion we had in the related PR 
https://github.com/reactos/reactos/pull/2658.



So let's have an open discussion and voting process right here on the 
mailing list for everyone to see, to decide this once and for all!
Just reply to this mail, tell about your reasons - and more importantly 
tell whether you support or reject dropping MSVC 2010 support.


Votes by CORE REACTOS MEMBERS are then counted on 1ST JANUARY 2021.


At this point, it should be obvious that I myself SUPPORT the decision 
to ditch building ReactOS with MSVC 2010.



Cheers,

Colin



OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (November 2020)

[Colin Finck]

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


OpenPGP_0x1BA74E70456BA1A9.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Not available for Status Meeting (August 2020)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (June 2020)

[Colin Finck]

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@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (June 2020)

[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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (March 2020)

[Colin Finck]

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

___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Reinstating the ReactOS Meetings

[Colin Finck]

This is a reminder about the upcoming meeting taking place this Thursday.

The updated agenda:
* Our GSoC 2020 Application (deadline is 5th February)
* RosBE 2.2 and what's blocking it
* ReactOS 0.4.13 and what's blocking it
* For the FOSDEM attendees: Planning for the upcoming weekend in Brussels

Colin


Am 12.12.2019 um 22:30 schrieb Colin Finck:
> 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
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Reinstating the ReactOS Meetings

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] FOSDEM 2020

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Report from the GSoC Mentor Summit 2019

[Colin Finck]

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
 just in sight distance of
the Microsoft Germany HQ :D

Cheers,

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Hackfest 2019 - Deadline for Merchandising and Financial Assistance

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] BuildBot Upgrade on Tuesday

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] MS Console/Terminal stuff (was: "RE: Ros-dev Digest, Vol 177, Issue 2")

[Colin Finck]

> 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.

We've been over-cautious with legal matters long enough, so let's get
this one straight: MIT is fully compatible with any version of GPL.
This is confirmed by GNU:
https://www.gnu.org/licenses/license-list.en.html#X11License

You can take as much code as you want from the Terminal repo and
integrate it into our GPL code, as long as you add the copyright and
permission notice from
https://github.com/microsoft/Terminal/blob/master/LICENSE to the file
header. Our work will stay GPL while those imported portions may also be
used under the terms of the MIT license.


> 3.   ReactOS doesn’t use C++ in the console

We've also been over-cautious with C++ in the past. But as we're moving
to GCC 8+ and MSVC 2015+, it's also time to reconsider our usage of C++.

Honestly, our project goal is hard enough as is! Let's not make it
harder by clinging to C and expecting everyone to happily spend time on
buffer sizes and pointer arithmetics when an STL container would do the
same job.
Since C++11, you finally have guarantees about STL buffers being
contiguous, so std::string and std::vector have become universal
alternatives to char[] and C arrays.
On that note, has anyone tried replacing our STLport with a newer STL
(such as LLVM's libc++) that is maintained and supports newer C++ features?


Cheers,

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS Hackfest 2019 will take place from 15th to 20th August in Berlin

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS 0.4.11 to be released tomorrow, March 4, 2019 - Press Kit is online!

[Colin Finck]

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.zip
Feel free to send it to interested parties to let them know about the
upcoming release in advance.


Best regards,

Colin Finck



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (February 2019)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (January 2019) - Now on Mattermost!

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Ros-dev Digest, Vol 173, Issue 5

[Colin Finck]

Am 13.01.2019 um 09:59 schrieb Adam Stachowicz:
> Message from chat.reactos.org :
> 
> This team has reached the maximum number of allowed accounts. Contact
> your systems administrator to set a higher limit.

Should be fixed now. Thanks for reporting!

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Mattermost is live at chat.reactos.org!

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Google Summer of Code 2019 Application

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (December 2018)

[Colin Finck]

Mails have been sent to the addresses set in your reactos.org website
accounts. Please check your inboxes!

Cheers,

Colin


Am 19.12.2018 um 09:40 schrieb Colin Finck:
> 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
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (December 2018)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] BuildBot and irc.reactos.org now using ReactOS.org accounts

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Doxygen migrated - now with a reasonable search feature!

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] iso.reactos.org migrated to new server

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS 0.5 Planning

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Colin Finck]

Mails have been sent and IRC server started.
Please check your inboxes and join!

See you at 19:00 UTC

Colin


Am 24.11.2018 um 21:37 schrieb Colin Finck:
> 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
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Colin Finck]

Am 29.11.2018 um 11:05 schrieb Javier Agustìn Fernàndez Arroyo:
> let me add a last topic: website translations
> 
> Old website could be translated, current one can not. And i think its
> good for the final user to see the webpage in his/her own language...

I agree and this is one of the reasons why we chose Hugo for the new
website.

While there is no reason to translate technical developer content on the
Wiki, the website is geared towards the end-user and should be available
in multiple languages to account for our international community.

I don't think we need to put this on the agenda of today's meeting, but
I can reaffirm this during my report about the new website.


- Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Google Summer of Code 2019

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Colin Finck]

Am 29.11.2018 um 10:28 schrieb Colin Finck:
> 2. Web and Infrastructure Projects (Victor P. and Colin)
>=

Addendum to these:

  - Community.ReactOS.org (Colin)
  - Doxygen (Colin)



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2018)

[Colin Finck]

Am 24.11.2018 um 21:37 schrieb Colin Finck:
> 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.

The current agenda is as follows:

1. Status Reports since August (everyone)
   ==
   Please prepare your Status Reports now, so we get this done quickly.

2. Web and Infrastructure Projects (Victor P. and Colin)
   =
   In particular:
 - Updated developer web interface (Victor P.)
 - AppDB similar to Wine's (Victor P. and Colin)
 - BuildBot (Victor P. and Colin)
 - New website (Colin)
 - Mattermost (Colin)
 - Nextcloud (Colin)

3. Jira tickets workflow (Victor P.)
   =

4. ReactOS 0.5 Planning (everyone)
   ===
 - From a user perspective (i.e. what shall work?)
 - From a technical perspective (i.e. who needs to implement what
   components?)

   I don't think anybody has already prepared a detailed plan, so we
   should collect our ideas and expectations for a 0.5 release and
   write them down at https://reactos.org/wiki/0.5_Planning
   Let's also try to define responsible persons and timeframes for each
   task, otherwise a plan is useless.

5. ReactOS Deutschland e.V. Update and ReactOS Hackfest(s) 2019 (Colin)
   
   Will just give a quick update on the German foundation as we will
   have a General Assembly in 2 weeks and reelect all Board members.
   Also a quick survey if it makes sense to have 2 Hackfests each year
   and your preferred dates for that.

6. All-in-one ISOs combining Live-CD and GUI Installer (Hermes)
   
   Will only be discussed if Hermes is present.

7. Miscellaneous (everyone)
   
   If you disagree with me excluding a topic from the agenda, we can
   discuss it here.


In my opinion, "Selecting a new coordinator" makes no sense as long as
nobody announces to spend significantly more time on ReactOS and comes
up with a clear vision for the project, just like an election program.
Otherwise, a new coordinator cannot really make a difference and we can
just leave the situation as is.
"USB / Storage" was merged with 0.5 Planning.
"Wine Syncs" will or will not be a topic depending on the presence of
Amine Khaldi. We can probably discuss it shortly as part of his Status
Report.

This may look like a tough schedule, however as many points depend on
me, I'll do my best to prepare my statements and get this done quickly.
All of you, please do the same. This should hopefully give us enough
time for 0.5 Planning.


See you this evening!

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (November 2018)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Website and JIRA Migration on Friday

[Colin Finck]

The migration is over and everything should be back to normal.
Jira has also been upgraded to the latest version in the process.

Please let me know if anything stopped working for you.

Colin


Am 21.11.2018 um 20:43 schrieb Colin Finck:
> 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
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Website and JIRA Migration on Friday

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Git/SVN Server migrated

[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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

[ros-dev] Last SVN repo finally converted to Git

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Mail server downtime tomorrow

[Colin Finck]

Everything went well and all mail services are back up again!
The entire downtime has been around 10 minutes.

Colin


Am 13.11.2018 um 10:51 schrieb Colin Finck:
> 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
> 
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Mail server downtime tomorrow

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS 0.4.10 to be released tomorrow, November 6, 2018 - Press Kit is online!

[Colin Finck]

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.zip
Feel free to send it to interested parties to let them know about the
upcoming release in advance.


Best regards,

Colin Finck



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Upcoming Google Summer of Code Mentor Summit

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Win8 theme for ReactOS?

[Colin Finck]

While Hermès' answer is totally correct, let me outline our reasons for
that.

First of all, you are right that ReactOS needs to work on its outer
appearance. Many ReactOS developers agree with that and this is also
what the press criticizes first on each ReactOS release.

However, that problem isn't solved by simply ripping off the Windows 8
look & feel and violating Microsoft's copyrights in the process.
ReactOS needs a distinct theme to be memorized as a unique operating
system and not just a poor copy of Windows.

Besides, GreenteaOS has imported their theme without any information
about sources and copyrights
(https://github.com/GreenteaOS/Deprecated/commit/1a75a25554427dc79a87a718ac674090bb605523)
and apparently wants no association with ReactOS
(https://github.com/GreenteaOS/Deprecated/commit/74db330786c0ee27bd76cf34a3156cb6b972311e).
Therefore, the only safe thing for us is staying away from any
GreenteaOS files as well.

Cheers,

Colin


Am 08.09.2018 um 23:58 schrieb Hermès BÉLUSCA-MAÏTO:
> Please don't include any "GreenteaOS" stuff in ReactOS!!
> 
> Hermès.
> 
>> -Message d'origine-
>> De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de theUser BL
>> Envoyé : samedi 8 septembre 2018 16:54
>> À : ros-dev@reactos.org
>> Objet : [ros-dev] Win8 theme for ReactOS?
>>
>> A while ago I have asked in the forum, if the modified Lautus-theme of
>> GreenteaOS could beintegrated in ReactOS
>> https://www.reactos.org/forum/viewtopic.php?f=2=16788
>> Sadly the theme is called in GreenteaOS Lautus, too. Here the source of it
>> https://github.com/GreenteaOS/Deprecated/tree/master/third-
>> party/reactos/media/themes/lautus.msstyles
>> But it looks like Windows 8.
>>
>> Here a screenshot of the Greentea Windows 8 like theme on ReactOS. Choose
>> one link. I have uploaded it multiple times on multiple places, because some
>> picture-uploading-sides delete its files from time to time
>>
>> https://image.ibb.co/gTsPkU/Virtual_Box_React_OS_0_4_9_08_09_2018_16_2
>> 2_18.png
>> http://img4host.net/upload/081642005b93dfb8c233a.png
>> https://img3.picload.org/image/dlpgdlow/virtualbox_reactos0.4.9_08_09_.png
>> https://cdn3.imggmi.com/uploads/2018/9/8/e016c5a6842640ac5f7436ee2e9b
>> 04e7-full.png
>> https://i.imgur.com/mCUvsLy.png
>>
>> EmuandCo is against the integration of the Win8-theme in ReactOS. But he is
>> the only ReactOS-developer in the ReactOS-forum. So I now also ask here, what
>> the other developers thinking about it.
>>
>> Greetings
>> theuserbl
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (August 2018)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Test_VBox finally fixed - but a flawed test remains

[Colin Finck]

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/388a831eb5ccf67535d8cbd6df2cc927fb9af5a9
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/a4eb4a4551618b4af4dc1985ad8c55fe0b3a57b2.
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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Postponing the July Meeting

[Colin Finck]

Am 01.08.2018 um 20:16 schrieb Ged Murphy:
> 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.
> [...]
> If we're going to do that, why not consider others too. Network cards, sound 
> stack, USB, boot loaders, printer drivers, directx, etc

Using Git submodules to make ReactOS more manageable and increase its
exposure was also my ultimate vision prior to the Git move.
However, after a vivid discussion back then, we had damn good reasons
for sticking with a Monorepo.

First, take into account that Git submodules come with their own drawbacks:

  1) If you branch from "master" in our "reactos" repository, its
submodules will stay on "master". In a branch workflow, you basically
have to create a branch for each submodule you want to touch and then
update submodule links.

  2) Git always checks out submodules at their root paths. There is no
way to include just a subdirectory of a submodule. This can be
problematic if you want a submodule to make sense on its own and as part
of the big "reactos" repository at the same time.

  3) You need more commits to achieve the same, because you first commit
into the submodule and then commit to "reactos" to update the submodule
link. This can be annoying when there are lots of submodules.

There are alternatives like "subtrees" and Google's "repo" tool, but
they come with their own drawbacks, most notably worse support from our
toolchain.
People involved back then may check out the "Reactos Git migration plan"
and "Git Migration Decisions" Google Docs files from that time, as well
as the mailing list discussions. There are also numerous blog posts
about failed migrations to Git submodules.
Let me quote from our decisions back then:

  * "There are no modules yet that can be built on their own or which
are big enough to justify a split from the main repository at this point."

  * "components should only be split into separate repo if the component
factored out is useful on its own [and] if the component is HUGE and
optional"


So if people still want to split off components into separate
repositories, we first have to do our homework. In my opinion, this
includes:

  * Providing a minimal CMake-based ReactOS SDK that can compile both a
single component like Paint and the entire OS.

  * Deciding on a generic structure for each submodule to come:
README.md, directories, where bugs are filed, Continuous Integration

For the bugs part, we could actually create a JIRA project for each
submodule and move existing bugs there.
Regarding Continuous Integration, our BuildBot should be made more
flexible to accept in-tree configuration files (like Travis-CI). It
would then be able to serve standalone projects as well. BuildBot 0.9.x
supports "BuildBot Travis" for that.
Of course, we could also go fully Travis-CI/AppVeyor, but then we're in
serious trouble if they ever cease service. Additionally, jobs may be
queued for a long time if their servers are overloaded.

Finally, always consider whether a module serves a real purpose on its
own. For instance, BTRFS is something Windows doesn't offer, so it has a
huge exposure on GitHub. On the contrary, NTFS is something Windows can
usually do better, so our own NTFS driver may hardly be popular as a
separate project. However, I would love to be proven wrong on this!


Best regards,

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Postponing the July Meeting

[Colin Finck]

Invitations have been sent, please check your inboxes!

Colin


Am 26.07.2018 um 18:57 schrieb Colin Finck:
> 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@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Repetitive "shell submit results failed" errors when running testbot manually

[Colin Finck]

I have checked the web server and the new "performance" configuration
made it consume more RAM than available. This caused some website
unavailabilities lately (500/502 error codes), which were also the cause
for the failing submissions.

I have now reduced the maximum number of simultaneous requests served
and restarted the affected components. Everything should be back to
normal and hopefully work more reliable in the future.

Cheers,

Colin


Am 01.08.2018 um 18:28 schrieb Hermès BÉLUSCA - MAÏTO:
> Hello!
> 
> 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
> and as a result I cannot obtain the results under reactos.org/testman .
> 
> Can someone investigate what is going on?
> 
> Regards,
> Hermes
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Postponing the July Meeting

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS 0.4.9 to be released tomorrow, July 23, 2018 - Press Kit is online!

[Colin Finck]

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.zip
Feel free to send it to interested parties to let them know about the
upcoming release in advance.


Best regards,

Colin Finck



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Website migrated to a new Login system

[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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Website Maintenance on Wednesday, July 4

[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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (June 2018)

[Colin Finck]

Credentials have been sent, please check your inboxes!

Colin


Am 24.06.2018 um 10:59 schrieb Colin Finck:
> 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
> 
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (June 2018)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Announcing the ReactOS Hackfest 2018 in Berlin

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (May 2018)

[Colin Finck]

Am 30.05.2018 um 13:26 schrieb Ged Murphy:
> Potential problems are:
> 4) something else?

I've been struggling with e.g. https://github.com/reactos/reactos/pull/276

On the one hand, we definitely need official support for Chinese,
Korean, and Japanese character sets.
On the other hand, this must not bloat up ReactOS by default, and just
dropping a 12 MB font into the repository definitely does.
So what is the ideal solution? I don't even know myself.

- I could leave the PR open and hope that the submitter addresses my
comments and comes up with a better solution. That hasn't happened in
the last months.

- I could close the PR right away. That would give the submitter no
chance to address my comments and may even look disrespectful. And the
original problem tends to be forgotten.

- I could close the PR and open a JIRA issue describing the problem.
If we decide on that as a general rule, we would put another burden on
every reviewer. Additionally, such general JIRA issues tend to rot in
our database as well.

I think we often have this situation where the submitted PR is wrong,
but we don't know the right solution either, and therefore keep the PR
open. If we can better deal with these cases, the number of open PRs may
decrease significantly.


- Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (May 2018) - topic "get the demo laptop running completly and enable automated tests"

[Colin Finck]

Am 30.05.2018 um 09:39 schrieb mich...@fritscher.net:
>   * (unformated) printing (already working)

Unfortunately, my demonstration back in 2015 was merely a
proof-of-concept using low-level printer APIs.
They work indeed, however almost every Win32 printing application uses
the high-level GDI APIs or a datatype conversion through a printer
driver. Both parts are still unimplemented.

Nevertheless, carrying a printer is hardly an option for most
exhibitions, so I don't consider this too important when we only talk
about demonstration purposes.


> I think the main stumbling is the lack of automated tests on the laptop.
> So I would suggest to enable one of the laptops to do automated testing.
> At one point, ros could even be booted via PXE, so it should be fairly
> easy.
> 
> Either we could put it into the data center rack, or I'm willing to
> build and host such a setup at home.
> Either way, I'm willing to donate a IP KVM switch and a network power
> switch to make such setup possible.

Everyone, please remember that a similar setup is already in place at my
home and completely unused: The Kaasimir GPU Testing Machine.

I have built a 4-port network power switch for it (supporting either
simple circuit switching, power/reset button switching or Wake-on-LAN)
and Kaasimir comes with two Raritan eRIC KVM-over-IP cards.

I've basically been waiting for interested developers since my
presentation in August to hand them an account and let them improve
ReactOS GPU support.
But maybe the machine is even more interesting when we connect one of
its KVM-over-IP cards to a Dell Latitude D531 ReactOS testing laptop.
Would require working ReactOS PXE support, how far has that progressed?
And who would actually benefit from such a setup? I don't want to put
time into this if nobody wants to work with that setup anyway..


- Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (May 2018)

[Colin Finck]

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



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (April 2018)

[Colin Finck]

Credentials have been sent, please check your inboxes!


Am 24.04.2018 um 13:59 schrieb Colin Finck:
> Hi all!
> 
> Let me invite you to the April 2018 meeting, taking place this Thursday,
> April 26, 2018 at 19:00 UTC.
> 
> There have been no requests for additional agenda points yet and I'm not
> aware of any developments of the outstanding points of last meeting, so
> right now the agenda only includes the Status Updates.
> If there is something you want discussed this month, please reply to
> this mail.
> 
> As waiting for every developer's Status Report still wastes too much
> time each month, I'm asking everyone to prepare a short text in advance.
> Unlike previous meetings, let's all try to post our status updates
> simultaneously this time and let the IRC server handle the congestion.
> This may make some reports harder to read, but we should be able to move
> on much quicker.
> 
> 
> Best regards,
> 
> Colin
> 
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (April 2018)

[Colin Finck]

Hi all!

Let me invite you to the April 2018 meeting, taking place this Thursday,
April 26, 2018 at 19:00 UTC.

There have been no requests for additional agenda points yet and I'm not
aware of any developments of the outstanding points of last meeting, so
right now the agenda only includes the Status Updates.
If there is something you want discussed this month, please reply to
this mail.

As waiting for every developer's Status Report still wastes too much
time each month, I'm asking everyone to prepare a short text in advance.
Unlike previous meetings, let's all try to post our status updates
simultaneously this time and let the IRC server handle the congestion.
This may make some reports harder to read, but we should be able to move
on much quicker.


Best regards,

Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (March 2018)

[Colin Finck]

The credentials have been sent. Please check your inboxes and join the
IRC server!


Am 22.03.2018 um 11:03 schrieb Colin Finck:
> Hi all!
> 
> With GSoC and 0.4.8 approaching, and many interesting things going on,
> it's finally time for a monthly meeting again. Let me invite you to the
> March 2018 meeting, taking place next Thursday, March 29, 2018.
> Time will be 19:00 UTC as always.
> 
> The agenda so far includes:
> - Status Updates
>==> Please prepare a short text what you did since January,
>so we can finish this quickly!
> - GSoC
> - 0.4.8 Status und Release Planning
> - Hackfest 2018?
> 
> Please let me know if you want anything else to be added to the agenda.
> 
> Just as the last few times, the meeting will take place on a custom IRC
> server. The required credentials will be sent shortly before the meeting
> to a group of ReactOS members. If you think you belong to this group,
> but didn't get a mail last time, please also let me know in advance.
> 
> 
> See you on Thursday!
> 
> Colin
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (March 2018)

[Colin Finck]

Hi all!

With GSoC and 0.4.8 approaching, and many interesting things going on,
it's finally time for a monthly meeting again. Let me invite you to the
March 2018 meeting, taking place next Thursday, March 29, 2018.
Time will be 19:00 UTC as always.

The agenda so far includes:
- Status Updates
   ==> Please prepare a short text what you did since January,
   so we can finish this quickly!
- GSoC
- 0.4.8 Status und Release Planning
- Hackfest 2018?

Please let me know if you want anything else to be added to the agenda.

Just as the last few times, the meeting will take place on a custom IRC
server. The required credentials will be sent shortly before the meeting
to a group of ReactOS members. If you think you belong to this group,
but didn't get a mail last time, please also let me know in advance.


See you on Thursday!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] GSoc Proposal (WebSite)

[Colin Finck]

Hey Volodymyr,

Thanks for your application!
Help on the website is really appreciated as we currently lack web
developers.

It would be great if you could join #reactos and #reactos-dev on
Freenode IRC, so we could talk some more and introduce you into the
current state of our website.
Also don't forget to submit your application to the Google Summer of
Code page as well. I cannot check right now if you already did ;)

Cheers,

Colin


Am 19.03.2018 um 23:07 schrieb Вова Титаренко:
> *
> 
> GSoc Proposal
> 
> Project: Developer Web Interface
> 
> Author: Volodymyr Tytarenko
> 
> bovati...@gmail.com 
> 
> 
> General info:
> Full name: Volodymyr Tytarenko
> 
> Languages:
> 
>  1.
> 
> Russian (Fluently)
> 
>  2.
> 
> Ukrainian (Fluently)
> 
>  3.
> 
> Polish (Fluently)
> 
>  4.
> 
> English (Intermediate)
> 
> Timezone: (GMT+1) Warsaw
> ReactOS account: titar
> 
> IRC Nickname: titar
> 
> 
> About me:
> 
> I am second year student in Poland. I study informatics at University of
> Silesia in the specialty of developing web application. Programming is
> my passion. I started programming from the age of 15 and now i have 4
> games for android, several programs on java for my needs and a lot of
> projects for freelance
> 
> 
> Time Commitment:
> 
> The main important thing, what can obligations my time in summer it’s a
> my University exams in June, but its only around 10 days, and i believe
> i will have a few exemption from the exam, because last time i had only
> 1 exam out of 6. Second thing it’s a 1 week holiday in end of July or
> start August, but it’s not 100%. I can spend 5-6 hours per day on this
> project including holidays.
> 
> 
> Technical skills:
> 
> FrontEnd: HTML5, CSS, JavaScript and MithrillJS (arround 20)
> BackEnd: PHP
> DataBase: MySQL
> 
> UX, UI, WebDesign, Git
> Work with different public API: GitHub, Telegram, Instagram, Facebook,
> VK, different weather api and other.
> 
> I have experience Designing api for my own projects.
> 
> My test design for a similar task (Custom ERP and CRM):
> 
> 
> 
> 
> Proposed Project:
> 
> Develop a web system of managing and showing commits, builds, PRs and
> other informations for developers of ReactOS.
> 
> I really want to work on a Website for ReactOS. I believe that I have
> enough knowledge to contribute to the operating system ReactOs in this way.
> 
> 
> Milestones:
> 
>  1.
> 
> Design basic interface and basic functionality.
> 
>  2.
> 
> Develop basic website with Integration githubAPI.
> 
>  3.
> 
> Gradual increase of site functionality from the list of ideas
> reactos.org 
> 
> Developing a website with the provision that at every moment we need to
> have a fully working website, gradually adding new features
> 
> 
> I hereby swear that I have not used nor seen the source code to any
> version of the Windows operating system nor any Microsoft product that
> may be related to the proposed project that is under a license
> incompatible with contribution to ReactOS, including but not limited to
> the leaked Windows 2000 source code and the Windows Research Kernel.
> 
> *
> 
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] GSoC 2018

[Colin Finck]

Am 18.03.2018 um 10:30 schrieb Huw Campbell:
> As I suggested last year as well, I would strongly suggest trying to use
> this opportunity to attack
> one of the core issues for reactos, such as stabilising the memory
> manager; bringing up
> SMP support; or boldly porting to x64.

From the experiences of the last years, our students hardly begin as NT
experts who could attack the most complex problems right away.
Even less, we could make up a roadmap for these problems and find
adequate mentors.

Therefore, we explicitly focus on smaller tasks this year. There are
enough important ones and students are more likely to succeed *and* stay
with the project.


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] 01/01: [WTSAPI32] Sync with Wine 3.0. CORE-14225

[Colin Finck]

Am 22.01.2018 um 14:25 schrieb Ged Murphy:
> Is this really a sync up?
> It takes implemented functions are returns them to stubs

I had asked the same question the other day: Given that many
Wine-Staging patches never made it into upstream, could we actually lose
features with the sync to WINE 3.0?
And the answer was "definitely"...

I think now it's time to establish a new strategy of dealing with WINE
DLLs. When ReactOS and WINE were still heavily implementing the
fundamentals, blindly syncing up DLLs to their WINE counterparts may
have been a solution. But nowadays, WINE development has considerably
slowed down. This led to the creation of Wine-Staging after all.
On the other hand, ReactOS has also evolved and needs to maintain
application compatibility over releases. We can hardly guarantee that
when blindly dumping foreign code into our repository.

So what could be a solution?
Even if Wine-Staging has not yet released a 3.x version, they publish a
nice set of patches:
https://github.com/wine-compholio/wine-staging/tree/master/patches
Applying them to our DLLs wherever possible should bring back the
missing features we just lost.

In the long term, we could leverage the power of Git and fork the WINE
repository on GitHub. We could then apply Wine-Staging patches and our
own changes to that repository. Syncing with upstream would now be
possible by merging commits instead of overwriting files. In the end,
DLLs from that repository could be blindly imported into the ReactOS
repo again. No more maintaining of "wininet_ros.diff" and the like :)

I hope we can have a solution before branching for 0.4.8. Otherwise,
I suspect that we will lose many features of 0.4.7 and the recent
history. For instance, DXTn support just got enabled in ReactOS, but it
has always been based on Wine-Staging code.


As James used to say: WINE Is Not Enough!

- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Making bluescreens more useful

[Colin Finck]

I'm supporting Thomas idea and Pierre's additional suggestions.
Let's show the world that BSODs can be useful!

- Colin


Am 11.01.2018 um 07:36 schrieb Pierre Schweitzer:
> Good idea!
> I would just have a few suggestions to make it even more useful:
> - "Consider filing a ticket at https://jira.reactos.org/ if it wasn't
> already reported there. To do so, provide information on what..."
> 
> - "Ideally, try to reproduce the problem while capturing a debug log
> that you should translate afterwards.
> See https://;
> 
> Cheers,
> Pierre
> 
> Le 11/01/2018 à 00:48, Thomas Faber a écrit :
>> We often get bug reports with just a screenshot of a bluescreen; we then
>> go ahead and tell people that bluescreens are basically useless, they
>> should get a debug log and a backtrace, and also remember to tell us
>> what version they're using.
>>
>> Since there's actually no reason why bluescreens need to be useless, I
>> thought I'd try to change that.
>> I've attached an example. The source for this quick PoC can be found at
>> https://github.com/ThFabba/reactos/commit/6a9f172b76bd11f763598c16e5d47299eec1971c
>>
>> Thoughts?
>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
> 
> 
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] First NT6+ application support in ReactOS

[Colin Finck]

Hi all!

Starting with build 0.4.8-dev-655-g63a3a2c, ReactOS has first support
for NT6+ applications (aka programs written for Windows Vista, Windows
7, etc.). Please retest such applications under ReactOS!

As newer Windows APIs are still missing in ReactOS, I would be surprised
if a high number of NT6+ applications suddenly works.
However, many applications may just be compiled by a new Visual Studio
without using any modern APIs. They could work now.

My "Hello World" compiled by VS 2017 v141 toolchain printed many
messages about missing apiset DLLs in the debug log, but otherwise works
well. So the next step should obviously be finishing and integrating
Mark's work on the apiset DLLs in
https://github.com/learn-more/reactos/commits/apisets
But interestingly, the build produced by the v141_xp toolchain also
looks for these apiset DLLs. Therefore, it would be possible that an
application expects a full NT6 system when finding them. Consequently,
application compatibility could be compromised if we just dump all
apiset DLLs into ReactOS, applications now expect NT6, but the OS
continues to behave like NT5 by default.

This is why I suggest detecting an NT6+ application in ntdll to have it
auto-apply a shim that lets ReactOS behave like an NT6 OS. The apiset
DLLs should only be available in this mode, but not for the NT5
personality of ReactOS. Let's not import the apisets before the ntdll
shim work is done in order to preserve our existing application
compatibility.


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] RAPPS Database now maintained in https://github.com/reactos/rapps-db

[Colin Finck]

Hi all!

We all wanted the RAPPS Database to leave the main source tree for a
long time. When Alexander Shaposhnikov asked me today if it was possible
to regenerate the rappmgr.cab on every commit, I took the opportunity
and split off the /media/rapps folder (including all history) into its
own repository: https://github.com/reactos/rapps-db

As a bonus, the public database at
https://svn.reactos.org/packages/rappmgr.cab is now automatically
updated with every commit to that repository.

I hope you'll like that change :)


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Project-tools repository converted to Git - Welcome our 18 new repos!

[Colin Finck]

Write access to the "project-tools" SVN repository has now been
disabled, the new Git repos have been mirrored to
https://git.reactos.org, and the development team got write access to them.

Now only "press-media" and "web" remain to be converted until the entire
migration can be considered done :)

Enjoy!

Colin


Am 31.12.2017 um 18:11 schrieb Colin Finck:
> Hi all,
> 
> I just finished converting our "project-tools" SVN repo to Git and
> splitting it up into individual repositories in the process.
> These repos have already been uploaded to GitHub
> (https://github.com/reactos), so you can have a look and comment easily.
> Welcome these 18 new repositories:
> 
> * ahk_tests
> * buildbot_config
> * git-tools
> * irc
> * Message_Translator
> * monitoring
> * packmgr (Archived)
> * project-tools-archive (Archived)
> * Qemu_GUI
> * reactosdbg
> * Release_Engineering
> * RosBE
> * rosev_ircsystem
> * rosev_jameicaplugin
> * RosTE
> * sysreg2
> * sysreg3 (Archived)
> * vmwaregateway
> 
> I haven't given anyone write access yet. I think this is acceptable for
> the moment while we check if there are any outstanding issues with the
> conversion.
> Please let me know until January 7. If everything is okay by then, I
> will add write access again and officially move development away from
> the project-tools SVN repo.
> 
> 
> Have a good start into 2018!
> 
> Colin
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Postponing December Status Meeting

[Colin Finck]

Credentials have been sent, please check your inboxes.

Cheers,

Colin


Am 28.12.2017 um 17:22 schrieb Colin Finck:
> Hi all!
> 
> If we follow our usual schedule, the December Status Meeting would be
> today. With such a late announcement and many people still on holidays,
> I suggest postponing it to next Thursday, January 4, 2018. Time will be
> 19:00 UTC as always.
> I already asked on #reactos-dev and got some approvals, so consider this
> the official meeting invitation :)
> 
> This also gives you one week from now for agenda proposals.
> Additionally, we have got some new contributors in the recent months.
> If you think you should join the meeting or know somebody who should
> join, please let me know in advance.
> 
> See you all next year!
> 
> Colin
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Project-tools repository converted to Git - Welcome our 18 new repos!

[Colin Finck]

Hi all,

I just finished converting our "project-tools" SVN repo to Git and
splitting it up into individual repositories in the process.
These repos have already been uploaded to GitHub
(https://github.com/reactos), so you can have a look and comment easily.
Welcome these 18 new repositories:

* ahk_tests
* buildbot_config
* git-tools
* irc
* Message_Translator
* monitoring
* packmgr (Archived)
* project-tools-archive (Archived)
* Qemu_GUI
* reactosdbg
* Release_Engineering
* RosBE
* rosev_ircsystem
* rosev_jameicaplugin
* RosTE
* sysreg2
* sysreg3 (Archived)
* vmwaregateway

I haven't given anyone write access yet. I think this is acceptable for
the moment while we check if there are any outstanding issues with the
conversion.
Please let me know until January 7. If everything is okay by then, I
will add write access again and officially move development away from
the project-tools SVN repo.


Have a good start into 2018!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Postponing December Status Meeting

[Colin Finck]

Hi all!

If we follow our usual schedule, the December Status Meeting would be
today. With such a late announcement and many people still on holidays,
I suggest postponing it to next Thursday, January 4, 2018. Time will be
19:00 UTC as always.
I already asked on #reactos-dev and got some approvals, so consider this
the official meeting invitation :)

This also gives you one week from now for agenda proposals.
Additionally, we have got some new contributors in the recent months.
If you think you should join the meeting or know somebody who should
join, please let me know in advance.

See you all next year!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Small suggestion for the abandoned SVN mirror on GitHub

[Colin Finck]

Am 17.12.2017 um 10:08 schrieb Alexander Shaposhnikov:
> Hold on, there was some vgal work being reviewed! I don't know if he had
> already transfered it to the new repo.

Last change on that Pull Request 24 days ago.
Ok, I've unarchived reactos-deprecated-gitsvn-dont-use for the moment
until this Pull Request is closed.


- Colin



signature.asc
Description: OpenPGP digital signature
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] ReactOS 0.4.7 to be released tomorrow, 6th December 2017 - Press Kit is online!

[Colin Finck]

Am 17.12.2017 um 04:13 schrieb encoded:
> Please mark release in jira please. Thanks!

Done. Thanks for reporting!

Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Small suggestion for the abandoned SVN mirror on GitHub

[Colin Finck]

Hi Dmitry,

Thanks for the suggestions! I just did that :)

Cheers,

Colin


Am 17.12.2017 um 05:14 schrieb Dmitry D. Chernov:
> Good day everyone.
> 
> I'm talking about this repo:
> https://github.com/reactos/reactos-deprecated-gitsvn-dont-use
> 
> To prevent pull-requesting to it I suggest to use new GitHub feature "archive 
> this repository".
> To enable it, just open the "Settings" page and go to the bottom.
> "Archived" repos are marked as read-only and could not be pull-requested.
> 
> It's also would be nice to disable unused "Projects" tab in this repo for the 
> great justice of perfectionism.
> 
> ___
> 
> Dmitry D. Chernov
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] PineappleFund

[Colin Finck]

Am 14.12.2017 um 17:45 schrieb Colin Finck:> Nope. But let's draft an
application!

We applied :)


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] PineappleFund

[Colin Finck]

Am 14.12.2017 um 17:38 schrieb Alexander Shaposhnikov:
> Has anyone actually applied?

Nope. But let's draft an application! I guess that's just a reply to
that Reddit post?

We have ReactOS Deutschland e.V. as a legally established non-profit
organization in Germany, so we are technically as charitable as the
OpenBSD Foundation.
And we have a Bitcoin account belonging to the project. Details are at
https://reactos.org/donating


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Colin Finck]

Thanks for the numerous replies! Let's stop at this point and not talk
this topic to death ;)
Even if we don't know yet how many HALs are to be kept, we agree on
reducing the number of HALs from the current 6. There is also no point
in a final decision on this until we have code to back it.

I have begun by deduplicating some code:
https://github.com/reactos/reactos/pull/193
It has also turned out that HalpCalibrateStallExecution was not broken
in the APIC HAL, but relied on the I/O APIC. Unlike the Local APIC, this
one is disabled by default in VirtualBox. When enabling it, the APIC HAL
fails at a later stage.
However, we may still merge both implementations of
HalpCalibrateStallExecution into a generic one at some point.


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Colin Finck]

Am 11.12.2017 um 01:18 schrieb Hermès BÉLUSCA-MAÏTO:> If you basically
put all the HALs into one, then you obtain bloated stuff (which remains
in memory for the whole life of the OS). Example: standard HAL is 1MB
vs. ACPI HAL which is few kBHave you actually checked what makes up this
difference?
Hint: hal/halx86/legacy/bus/pci_vendors.ids


> Note that if Windows nowadays has only one hal, it's because they now support 
> basically only one "architecture"/platform, namely, ACPI multiprocessor (to 
> put it simple). It has its pros, but also a lot of cons.

That doesn't mean we need to do the same. We can have one HAL for all
(Pentium and newer) x86 platforms. The overhead of additional checks at
boot-up is negligible. That should be a solution for 99% of the people
out there. The rest may still go and trim down our HAL to their needs.

But let's not pretend we can maintain multiple x86 HALs for all x86
computers out there. Do you really want to test X HALs with Y different
systems? Ensure that a legacy HAL runs on a modern ACPI system? What
would be the point?


> Besides this, I've a question about your observation that in the APIC hal 
> (not ACPI) there's different implementation of HalpCalibrateStallExecution 
> and HalpInitializePICs / HalpInitializeLegacyPIC . Isn't it precisely because 
> these stuff are completely different from the standard PICs used in platforms 
> for which the standard HAL (and possibly the ACPI HAL) are used?

Absolutely not! You need to reprogram the standard PICs also on an APIC
system, and this is precisely what both functions do. Put them into a
diff tool to see for yourself.

The same goes for timers. Even with the introduction of ACPI Timers,
Local APIC Timers, and Time-Stamp Counters, you still need a traditional
one (like RTC or PIT) for calibration at system startup. Simply because
the newer ones don't run at a known fixed frequency.
The Legacy HAL successfully employs an algorithm based on the RTC while
the APIC HAL unsuccessfully tries to use the PIT.


> Actually we should, because the detection might not work (of course in our 
> simple case "ACPI UP/MP" vs. "Standard", it's simple, but think about other 
> platforms where there can be subtle differences)

Tell me about a single one we cannot detect and which is worth to
support. I don't recall that we ever recommended our testers to choose a
different HAL at setup.


> And normally it's not the setup that decides about the HAL, but the 
> bootloader.

That defies your previous point about the setup initializing the
registry depending on the HAL.
If we can let the user select a Legacy HAL in the boot loader after
installing with an ACPI HAL, it is also technically possible to have one
HAL that encompasses both.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Merging our x86 HALs

[Colin Finck]

Am 10.12.2017 um 19:38 schrieb David Quintana (gigaherz):
> Colin: Are we talking merge and decide which method to use at runtime

Exactly! We don't even need boot flags: Just like the setup currently
detects an ACPI-compliant computer, the HAL could do this at boot-up.
It's also not too hard to detect the presence of an APIC.

I think a universal HAL for every x86 machine wouldn't be noticeably
larger than an ACPI+SMP HAL.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Merging our x86 HALs

[Colin Finck]

Hi all,

I have been looking into our HALs recently on the promise that it is a
huge mess that needs fixing. Well, as a start I could imagine merging
our 6 possible x86 HALs (Legacy, ACPI, APIC, ACPI+APIC, SMP, SMP+ACPI)
into a single one, even if Windows ships individual ones. I see many
advantages of that:

* Less duplications and reduced mess: Right now, the APIC HAL hangs at
HalpCalibrateStallExecution during boot, a function that has been fixed
and universally implemented in all non-APIC HALs. The APIC HAL also
duplicates HalpInitializePICs as HalpInitializeLegacyPIC.
If you look at the SMP code, it didn't even receive the last build
system changes and has conflicting implementations for APIC functions.
A single x86 HAL would ensure that all possible configurations are
maintained.

* Future-proof: How is one going to implement newer features like x2APIC
with a structure like that? Would it get another HAL, be integrated into
the APIC HAL, or what?
We wouldn't have such problems with a single x86 HAL.

* Less setup work and testing: Currently, 1st stage setup detects the
computer type and installs the appropriate HAL. As such, every
additional HAL needs to be added to 1st stage setup code.
The user is also able to select a custom HAL during setup, even if it
wouldn't work on the machine. We should give neither the user nor the
setup the ability to decide. The HAL itself knows best at boot-up what
features to enable and what not.

* Convenience: The same ReactOS installation could be used on several
different x86 computers.


So is this the way to go or do I miss something important?


Best regards,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] ReactOS 0.4.7 to be released tomorrow, 6th December 2017 - Press Kit is online!

[Colin Finck]

Hi all!

With all release preparations done, we can finally give a release date
for ReactOS 0.4.7: Tomorrow, Wednesday, 6th December 2017. During that
day (European time), the release will be published.

A Press Kit for ReactOS 0.4.7 is already available:
https://sourceforge.net/projects/reactos/files/ReactOS/0.4.7/ReactOS-0.4.7-PressKit.zip
Feel free to send it to interested parties to let them know about the
upcoming release in advance.


Best regards,

Colin Finck

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (November 2017)

[Colin Finck]

Am 29.11.2017 um 22:07 schrieb Colin Finck:> As always, you will get
credentials for our private IRC server shortly
> before the meeting.

Mails have been sent, please check your inboxes.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Status Meeting (November 2017)

[Colin Finck]

Hi all!

Let me invite you to the monthly status meeting taking place tomorrow,
November 29, 19:00 UTC.
As always, you will get credentials for our private IRC server shortly
before the meeting.

No agenda proposals have been submitted to me so far. If that doesn't
change, we may have a short meeting just for status reports. Please have
them ready, so we get it done quickly!
FYI, I expect the 0.4.7 Press Release to be ready tomorrow, so we can
soon send out the Press Kit and make the downloads available.

See you tomorrow!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] RosTests/RosApps in GitHub CI

[Colin Finck]

Am 03.11.2017 um 14:20 schrieb Thomas Faber:
> If this is nontrivial I may have a look at it myself but someone would
> need to point me to the right configuration/scripts please.

The Travis configuration is in
https://github.com/reactos/reactos/blob/master/.travis.yml

Code that already filters by path (/rostests/) is in
https://svn.reactos.org/svn/project-tools/trunk/git-tools/buildbot_sendchange.py?revision=2360=markup

Hope that helps!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Question about commits with no commit log, or commits with no files but just the log, on Git.

[Colin Finck]

Am 16.10.2017 um 12:22 schrieb Hermès BÉLUSCA - MAÏTO:> After having noticed
> https://github.com/reactos/reactos/commit/50ae5e7c5268222718174221366169e2b115b06a
> I am wondering whether it is possible to add mechanisms (like git
> pre-commit hooks) that check for, and
> prevent potential problematic commits like, commits without commit log,
> or commits with no files (but with a log).

Not using GitHub.
But you are all more than welcome to request that feature independent of
each other and maybe they consider it for the future :)

It may be possible though that we ship a number of client-side Git hooks
and settings with RosBE. Setting "pull.rebase=1" by default may be
another candidate.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] JIRA up again - Do we still need FishEye?

[Colin Finck]

Hi all!

Our two Atlassian tools JIRA and FishEye have been unavailable for some
hours again. I have brought JIRA back up, but FishEye has been eating
RAM and CPU like crazy again. In my opinion, this is unacceptable for a
tool that is just a simple commit browser to us. Also I don't have any
time to constantly monitor it this weekend, so I'm leaving it shut down
for now.

With us having https://github.com/reactos/reactos/commits/master and
https://git.reactos.org/?p=reactos.git;a=summary now, do we still need
FishEye at all?
If so, please tell me what features of it you would miss if it stays
down. Maybe there are other alternatives.

My last FishEye "performance" bug report took 3 months to resolve, and
I'm reluctant to go the same route again for another such bug..


Cheers,

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Testing Pull Requests

[Colin Finck]

Am 14. Oktober 2017 01:26:09 MESZ schrieb James Tabor 
:
>Can we still use the ID for patches from Jara?

Sure! They are processed using "git apply" now.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[ros-dev] Testing Pull Requests

[Colin Finck]

Hi all!

Apart from basic build testing through AppVeyor and Travis-CI, you can
now also run all regression tests for the code belonging to a Pull Request.

Just log in to our BuildBot at https://build.reactos.org with your
development account credentials (formerly "SVN credentials"), select a
builder in the waterfall view and fill the field "Branch" in the "Force
a Build" section. You have two options here:

* "refs/pull//head"
  Builds your branch, unmodified.
  That means, if you haven't kept your branch up to date with the main
  ReactOS repo, latest changes won't be included.

* "refs/pull//merge"
  Builds the changes of your branch merged to the main ReactOS repo.
  That means, latest changes in the main ReactOS repo will be included.

Replace  by the number of your Pull Request.

As the resulting hash may be hard to predict, the "prepare source" step
will now give detailed information about the latest commit included in
your build:
https://build.reactos.org/builders/Build%20GCCLin_x86/builds/19201/steps/preparing%20source/logs/stdio


Have fun!

Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] [ros-diffs] [reactos] 01/01: Fix remaining text file line endings in the tree. (#18)

[Colin Finck]

Sorry for the huge diff E-Mail to ros-diffs!

I have just configured git_multimail.py to a maximum of 5000 lines to
not let that happen again. We can again reduce the limit later on if it
turns out to be still too much.


Best regards,

Colin Finck

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] Status Meeting (September 2017)

[Colin Finck]

Credentials have been sent, please check your inboxes!

Still nothing more than status reports on the agenda, so I'm looking
forward to a short and effective meeting :)

Cheers,

Colin


Am 28.09.2017 um 15:43 schrieb Colin Finck:
> Hi all!
> 
> Let me invite you to the monthly status meeting taking place today,
> September 28, 19:00 UTC.
> As always, you will get credentials for our private IRC server shortly
> before the meeting.
> 
> No agenda proposals have been submitted to me so far. If that doesn't
> change, we will have a meeting just for the status reports. Please have
> them ready, so we get it done quickly!
> 
> A lot of tasks from our long last meeting are also still in progress
> (not just the Git migration), so I wouldn't mind having a short meeting
> this time.
> 
> See you in a few hours!
> 
> Colin
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] once agaon about ReactOS trademark infringement by Facebook

[Colin Finck]

We already discussed this privately back in February 2015, so let's get
some facts straight:

* We own a ReactOS trademark in Russia, registered in 2008.
I don't find any trademark related to ReactJS.

* If you search just for "React", you find a lot of trademarks by
various unknown companies coexisting next to each other.

* I am not interested in sueing other parties on questionable grounds,
and I guess this applies to the other developers too. Especially not if
they are into Open Source as well.
This is also a question of attitude!

* The least we can do is keeping up our Russian trademark and register
it in other countries too, using the priority of the Russian one.
This gives us power to defend against any claims from third parties.

If we develop a good relationship with the ReactJS guys, we could
mutually put disambiguation links on both websites and solve any
problems that way.

Best regards,

Colin Finck



Am 27.09.2017 um 11:34 schrieb Alexander Rechitskiy:
> Hi!
>  
>  
> Please, read this!
>  
> https://www.reactos.org/forum/viewtopic.php?f=2=16671
>  
> -- 
> Best regards, Alexander Rechitskiy
>  
> 
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev