Results of the second hackathon on ReactOS: we are switching to GitHub
Hi, Habr! Now we will tell something interesting.
From 14 to 18 August 2017 in Cologne (Germany) the second in the history Hackfest on ReactOS was held. We want in this post to share a brief digest of the results of this event and lift the veil of secrecy over the events taking place there.
This time, at Hakfest, the number of people participating was 2 people less than last time, which of course is a little sad. But this was more than compensated by the fact that developers such as Vadim Galyant, Hermès Bélusca-Maïto, David Quintana took an active part in the correspondence format, and all active users of the ReactOS VK group participated in testing the developments. ')
Monday live stream
The first experiments. Microsoft Windows Recovery Console recognizes ReactOS.
On Thursday, Colin Fink gave a master class on proper licensing code.
Before and after the hackathon, Colin was engaged in bringing information about licenses for various components of ReactOS to a single species. The project uses components under various compatible free licenses, now all this information is correctly reflected in accordance with the standard.
Right on the hackathon, we tested the improvements of the USB stack, which Vadim achieved.
As a result, thanks to the event, 18 bugs were closed and 103 commits (from 75636 to 75533 revisions) were committed to the main project development tree. Of course modestly, but dry figures do not reflect the whole point. One of the participants of Hackfest, Mark Jensen, at the hackathon completed the main stage of development and activated support for compatibility with programs for older versions of Windows. Now this function is in ReactOS. And Alexander Shaposhnikov at Hakfest completed the upgrade of the RAPPS application manager . All developments Hakfest get into the upcoming version of ReactOS 0.4.7!
But the most important thing that the developers devoted the first two days of the event was a discussion of the detailed plan for moving the project to GitHub . And so that you understand the effectiveness of this discussion - the move happened and is happening right now, on October 3.
For a long time, the project has been constantly bombarded with questions about the need to switch from SVN to Git and GitHub, although the project already had ReadOnly mirrors long ago. But activists argued that this was unfavorable and constantly promised to overwhelm us with patches and pull requests. Of course, the prospect was seductive, although we understood that promises were likely to remain promises, and the existing workflow with SVN remained a completely reliable way of development. Therefore, we have several times tried to find some kind of compromise solution that would allow us not to change anything globally. Unfortunately, they did not lead to the desired result. Therefore, we had to resort to the development of a strategic migration plan , the results of which you will see today!
Follow the news!
PS During the migration process, some services of the official site may be temporarily unavailable.