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