Proposed EU copyright directive requires automated upload filters
(something like YouTube ContentID) and this can cause a sharp decrease
in contributions. It will also make difficult for newcomers as a
significant contribution will be required for each commit, because
copyright filter is costly to run.
Yours, faithfully
Erkin Alp
Hello,
Supposedly someone had an access and seen leaked windows source code few years ago. At the time he/she do not have any idea of the code (due to improficiency in programming and the subject) and had forgotten since about the code, does he/she allowed to contribute to ReactOS development?
This is due to the following statement on the participation page (https://www.reactos.org/participation)
"Getting involved with ReactOS is easy and straightforward! We only ask that you have not had access to Microsoft source code for the area you want to work on. This includes either having worked at Microsoft, obtaining the source code through an academic program or from the illegal leakage of Windows source code several years ago. Having viewed the source prevents you from contributing to avoid undermining the legality of our source code"
Hi all!
Our own Mattermost instance is finally live at https://chat.reactos.org!
Enjoy an infinitely searchable history, offline messages, native picture
support, push notifications, a seamless experience on web and mobile,
and more.
All privately hosted on our own infrastructure and usable with the same
ReactOS.org account you already have!
Time to say goodbye to workarounds like IRC bouncers or third-party
services :)
I believe this can really improve our communication and accelerate
development!
To make the migration as easy as possible, I have set up a bridge
between our Freenode IRC channels and Mattermost. User "RosBridge" will
transfer all messages from #reactos / #reactos-dev to Town Square /
Development and vice-versa. Let's see how long we're going to need that.
I hope you're all going to join the fun, so that we can already have the
next meeting in around 2 weeks on Mattermost!
Cheers,
Colin
Hi all!
Happy new year from my side! Hope you all had nice holidays and that
2019 will be a successful year for ReactOS :)
As always, the year begins with our Google Summer of Code application.
It is now time to update
https://reactos.org/wiki/Google_Summer_of_Code_2019 and
https://reactos.org/wiki/Google_Summer_of_Code_2019_Ideas as
applications begin next week (January 15). If we take this seriously and
don't forget to advertise, I'm sure that we'll get more students this year!
But first things first: Who is going to volunteer as mentors and
administrators?
I'm willing to take over one of the administrator roles again, but we
also need a second one.
I also suggest that we prepone the monthly meeting for January by a week
to Thursday, January 24.
This gives us some time for GSoC-related discussions until the final
application deadline (February 6).
Cheers,
Colin
We seem to be back to normal state.
Please report if some service is still not working properly.
Pierre Schweitzer <pierre.schweitzer(a)reactos.org> wrote on Wed, December 26th, 2018, 4:43 PM:
> Dear all,
>
> Due to an unexpected outage touching our hoster infrastructure, our DB server is currently down and it affects all the web services relying on it. So, don't expect Jira, boards, wiki, website, and so on to work properly for now,
> I'll keep you informed when I have more information.
>
> Cheers,
> Pierre
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
Dear all,
Due to an unexpected outage touching our hoster infrastructure, our DB server is currently down and it affects all the web services relying on it. So, don't expect Jira, boards, wiki, website, and so on to work properly for now,
I'll keep you informed when I have more information.
Cheers,
Pierre
Feature Request CORE-15418 to create a ReactOS Default Media Player
using the code from Media Player Classic.
This feature request was discussed some time ago on the forum at length
and it came to little conclusion, some wanting to bundle VLC, others
wanting to bundle classic media player - an open source tool that has
recently received some attention. The importance of a media player was
noted but one of the main problems was left out.
The nub of the problem is this:
Windows has a default media player provided as a core part of the
system. It is not just a media player, being so tightly integrated into
Windows it is used by (some/many?) apps to produce the default sounds
and video that emanate from normal program usage.
Note that on Windows, ActiveX/COM allows access to system level
components and one of those components that is defined as a system level
resource is the windows media player (WMP). COM allows programs to make
calls to WMP to allow them to play embedded videos or audio tracks
within their applications without having to design their own player and
bundle their own codecs. The use of WMP means that a far greater range
of codecs will be available and the chances of being able to play a
particular type of file are increased. *Without such a player these
Windows applications will not function as intended.*
See the description here: https://docs.microsoft.com/en-us/window ...
ject-model
<https://docs.microsoft.com/en-us/windows/desktop/wmp/about-the-player-objec…>
ReactOS is not a straight o/s without any whizzes or dongles, ie. it
already has such bundled apps as games and the ReactOS version of
paintbrush. So, the concept of bundling apps is already set, ie. it is
perfectly OK to have apps bundled with ReactOS and ReactOS will have
them when released. It is just a matter of which applications are
bundled. I propose we add Media Player Classic as the default media player.
A Windows Media Player type application would be very useful, in fact
essential to replace the windows media player that came bundled with
Windows, it will need to be a straight drop in replacement for WMP.
Indeed, users expect the basic components of an o/s to be present and
although RAPPS allows users to install the components they need, some
applications are integrated into the o/s far more than others. I would
suggest that it is time to re-open this debate and consider using the
open source Media Player Classic as ReactOS own embedded version of WMP
and to ensure that active X/COM controls can see Media Player Classic
just as WMP is disclosed as the default media player in Windows.
MPC looks like a media player that ReactOS could use. It is written in
C++ and is open source and it supported by the devs at doom9. It seems
to me that the only thing missing from Media player classic is the
Active X control that allows Windows/ReactOS programs access to its
functions. With that control in place it might be a perfect drop-in
replacement for WMP and would restore that missing sound functionality
to programs giving ReactOS added compatibity.
Request raised here in JIRA:
https://jira.reactos.org/browse/CORE-15418
Hope this finds you all well this Christmas and that you will consider
this feature request for later inclusion.
Dean Beedell (dizt3mp3r)
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Hi all!
With Christmas fast approaching and many people traditionally being
unavailable over the holidays (myself included), let me prepone our
monthly meeting to tomorrow, Thursday, December 20, 2018, 19:00 UTC.
Invited members will again receive their IRC Server credentials shortly
before the meeting.
Note that due to the recent infra changes, your IRC username will now be
based on the Display Name you set in
https://reactos.org/roslogin/?p=selfservice (spaces replaced by
underscores). Please check that before the meeting.
However, as our self-hosted Mattermost server is being set up right now,
this may as well be our last meeting on IRC :)
I wouldn't mind if it's just about the Status Updates from everybody
this time, given that the November meeting was really long and a lot of
things should be in progress.
Let's also not forget about our preparations for Google Summer of Code!
Cheers,
Colin
<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>Hi,<br>
<br>
There is in principle (almost) all the infrastructure to implement the Retry/Skip/Abort dialog in usetup.<br>
The freezing you encounter is however a bug I should investigate.<br>
<br>
Cheers,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Javier Agustìn Fernàndez Arroyo"<br>
A : "ReactOS Development List"<br>
Envoyé: mercredi 19 décembre 2018 20:17<br>
Objet : [ros-dev] CORE-15467 - 1st stage setup freezes when the expected file is missing<br>
<div class="gl_quoted">
<div dir="ltr">An idea,
<div> </div>
<div>I don´t think its a good idea to "skip" a file during 1st stage, specially core files (in 2nd stage it might be acceptable for some device drivers, for example)</div>
<div> </div>
<div>So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or abort installation and reboot.</div>
<div> </div>
<div>what do you guys think?</div>
</div>
<!-- PART SEPARATOR --><br>
<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
Ros-dev(a)reactos.org<br>
http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
An idea,
I don´t think its a good idea to "skip" a file during 1st stage, specially
core files (in 2nd stage it might be acceptable for some device drivers,
for example)
So, if "cloning" the Win2k3 behavior, i would set only 2 options: retry or
abort installation and reboot.
what do you guys think?
Hi all!
Another important change has just been applied to ReactOS
infrastructure: https://build.reactos.org and https://irc.reactos.org
now use ReactOS.org accounts. Finally, we have a real global login
system where you can access all ReactOS services with the same account!
Please let me know if or if not things work for you, as I may have
forgotten to add some accounts to the BuildBot group.
If everything works well, we are technically ready to launch a
Mattermost instance using the same accounts as the next step :)
Cheers,
Colin
Hi all!
iso.reactos.org, the file server used by our build machines and the
source for https://reactos.org/getbuilds, has been migrated to new
hardware at a different location today.
You should experience better transfer rates due to the increased
bandwidth, and a higher availability. The new hardware also offers more
disk space and redundancy to keep our precious ISOs absolutely safe :)
Unfortunately, the new iso.reactos.org is no longer right next to the
build machines. This has several consequences: If I had left the build
scripts as-is, the build machines would have uploaded the bootcdregtest
ISOs to iso.reactos.org, just to download them multiple times for each
Testbot a minute later. This would be an excessive waste of ISP
bandwidth and would have delayed the entire testing process.
Therefore, I changed the build scripts to keep the bootcdregtest ISOs
within the local build machine network. However, the downside is that
bootcdregtest ISOs are no longer available via iso.reactos.org.
Please let me know if this is a problem for you and needs a solution.
In the past, bootcdregtest ISOs were only available for a week and not
accessible via GetBuilds either, so I have no idea how popular they are.
Cheers,
Colin
Hi all,
The Test_KVM_AHK machine has encountered a power shortage in my area and is currently shut off.
I will bring it back on today evening. Kind regards, Sylvain Petreolle
Hi all!
Good news! I've just migrated the last of our existing services,
Doxygen, to a new server that is a lot faster and more reliable.
But I also had a look at the often criticized search feature and enabled
the alternative EXTERNAL_SEARCH in the Doxyfile and on the server. This
doubled the runtime for Doxygen due to the additional indexing, but the
result is well worth the effort!
A simple search for a universal function like "Sleep" now instantly
yields all results, but with the definition in "winbase.h" and the
declaration in "kernel32/client/synch.c" at the very top! Results are
also a lot more readable and distributed over multiple pages.
Just try it yourself:
https://doxygen.reactos.org/search.html?query=Sleep
Hope you'll like it as much as I do! :)
We can now start tweaking the extra settings, e.g. whether we need
"Referenced by" and other information.
ReactOS is already known to many due to our Doxygen popping up whenever
they google a Windows API. This step should improve the usefulness of
our documentation even further and turn the ReactOS codebase into *the*
public reference about Windows internals again!
I hope it also motivates you to take care of Doxygen-compatible comments
during your coding :)
Cheers,
Colin
<span style="font-family:arial,helvetica,sans-serif; font-size:12px"></span>Hi,<br>
<br>
In case this happens to be indeed a problem, the additional stuff to add to the build scripts would be to upload these bootcdregtest ISOs to iso.reactos.org, while using now the local copy on the build machine network.<br>
<br>
Best,<br>
Hermes
<div class="gl_quote" style="margin-top: 20px; padding-top: 5px;">De : "Colin Finck"<br>
A : "'ReactOS Development List'"<br>
Envoyé: mercredi 5 décembre 2018 20:01<br>
Objet : [ros-dev] iso.reactos.org migrated to new server<br>
<div class="gl_quoted">Hi all!<br>
<br>
iso.reactos.org, the file server used by our build machines and the<br>
source for https://reactos.org/getbuilds, has been migrated to new<br>
hardware at a different location today.<br>
<br>
You should experience better transfer rates due to the increased<br>
bandwidth, and a higher availability. The new hardware also offers more<br>
disk space and redundancy to keep our precious ISOs absolutely safe :)<br>
<br>
Unfortunately, the new iso.reactos.org is no longer right next to the<br>
build machines. This has several consequences: If I had left the build<br>
scripts as-is, the build machines would have uploaded the bootcdregtest<br>
ISOs to iso.reactos.org, just to download them multiple times for each<br>
Testbot a minute later. This would be an excessive waste of ISP<br>
bandwidth and would have delayed the entire testing process.<br>
Therefore, I changed the build scripts to keep the bootcdregtest ISOs<br>
within the local build machine network. However, the downside is that<br>
bootcdregtest ISOs are no longer available via iso.reactos.org.<br>
<br>
Please let me know if this is a problem for you and needs a solution.<br>
In the past, bootcdregtest ISOs were only available for a week and not<br>
accessible via GetBuilds either, so I have no idea how popular they are.<br>
<br>
<br>
Cheers,<br>
<br>
Colin<br>
<br>
_______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://reactos.org/mailman/listinfo/ros-dev</div>
<div class="gl_quoted"> </div>
</div>
Are you sure its better to follow Win behavior on this?
I think its a enhancement, specially if there are many open windows at a
given time....
it saves time!
Hi all!
Planning the ReactOS 0.5 release and establishing a new roadmap was one
of the points on the agenda of yesterday's meeting. This is still an
ongoing process.
Please make up your minds about what a ReactOS 0.5 release must offer in
your opinion and write it down to https://reactos.org/wiki/0.5.0
To get a realistic roadmap, it is important that we define a responsible
person for each task. It should be the person having the most in-depth
knowledge about the status of the affected ReactOS components.
Don't worry, we won't put any pressure on you to complete the task soon.
But we need someone who can give a detailed report about the current status.
If nobody can be the responsible person for a certain task, having it
for 0.5 is not realistic and it eventually needs to be removed from the
roadmap.
But that's for later! Let's first add all points we consider important
until the end of the year. If you can already add yourself as the
responsible person, even better! :)
Cheers,
Colin