Point 1: Status Reports

Amine Khaldi is doing the usual, Wine syncs and anything he can help with.

Colin Finck finished his university studies after almost 7 years! On the ReactOS side of things he converted the "web" repo to Git. The only SVN repo left is "press-media", but it's too fat for a simple conversion, so a conversion ruleset with commit filters will have to be written first.
Colin also worked on his RosLogin Single-Sign-On system along with a MediaWiki upgrade and modules for our Drupal and Wiki. Still left is a phpBB upgrade and module as well as the importer script before this can be deployed. When this is live, Colin expects less login weirdness on the web services, such as no more 30 minute delay of account changes propagating to JIRA. After that, Drupal could finally start to be dropped for the Git-managed Jekyll static page CMS.

David Quintana has been working on a little project called TransDiffer, to help fix errors in translation files, such as missing strings in some language files. He also made a PR for others to review fixes to the language files.

Mark Jansen did some work on FLS callbacks and added basic verifier hooks in LDR. He also started writing a driver for the E1000 line of network cards (Intel 82545EM to be precise, which is the default VMWare network adapter).

Pierre Schweitzer worked on fixing CC and FS to make it possible to build ReactOS on ReactOS. He also fixed fsck running on our FAT partitions.

Stanislav Motylkov has fixed multiple bugs in the Paint applications, including some crashes when zooming out.

Point 2: Improving our handling of PRs and JIRA reports

The number of open PRs on GitHub has steadily risen, and if nothing is done, they will just continue to increase. Some are waiting for requested changes, some are just sitting there, and for some, it's hard to make a decision on what to do with them. Other problems also exist in the handling of the PRs.

Colin used PR #276 as an example of a PR without a solution, and started the discussion from there. After a long discussion of a set of rules, the rules were narrowed down to the following:

If a PR has at least one approval, it can be merged after 1 week of waiting for additional comments. If you consider the change trivial enough or it has at least 3 approvals, it may also be merged right away.

If a PR stays in "changes requested" for 2 weeks, and that change has not been done in the meantime, it shall be closed.

If you require a review from a particular person, assign the PR to that person. Don't just rely on the "review requested" feature of GitHub.

Don't feel obliged to comment everything you see, just for the sake of commenting. Be it on JIRA, GitHub, or even on IRC.

Refrain from

Asking the contributor to do unrelated work

Editing the code without asking first

Closing without providing a reason

Merging with the intention to rewrite that code soon after

David Quintana volunteered to make a PR for the new rules, to allow other developers not present during the meeting, to comment and suggest changes. The PR was later opened as PR #585.

Point 3: Google Summer of Code

Victor Perevertkin is our only GSoC student this year, and he was welcomed to the monthly meetings. He didn't have anything in particular to discuss during the meeting, but mentioned he was setting up a debug environment for developing bootloader code at the moment.

Be sure to check out Victor's blog for more information on his progress.

The mentors to Victors (Hermès Bélusca-Maïto, Oleksandr Shaposhnikov, Pierre Schweitzer and Thomas Faber) were asked to assign a primary mentor on the next GSoC meeting.

On the topic of GSoC, some concerns were expressed about the "Make a small contribution" rule for ideas that do not touch core ReactOS code. The rule will be considered to be dropped for such ideas next year.

Point 4: Changes affecting base addresses

Robert Naumann requested a brainstorming session for the meeting to get a conclusion on how to deal with changes that affect base addresses. He couldn't merge several PRs translating .mc files, because that would blow up the kernel and require a regeneration of all base addresses.

Mark Jansen wrote a script a while ago to regenerate base addresses. Changing the base addresses could trigger regressions, so Mark advised against doing it automatically, but will commit his python script, so Robert (and others) can use it manually.

Point 5: Miscellaneous

The last agenda point covers USB status in general and getting the demo laptop running completely and adding it into our testbot.

As for the USB status, this is unchanged since the last meeting, and can be read in the previous Meeting Minutes.

When it comes to the demo laptop, Colin said that if anyone would benefit from a remote Dell D531, they should reply to his mail. Kaasimir, a remote computer used mainly for GPU debugging and testing which Colin set up previously, has been unused so far, so Colin will only spend time on the above if it really benefits someone in particular.