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

2018-05-30 Thread Robert Naumann
rg > Envoyé: mercredi 30 mai 2018 18:21 > Objet : Re: [ros-dev] Status Meeting (May 2018) > > 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/

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

2018-05-30 Thread hermes . belusca
sub-repo or elsewhere... Closing the PR now would definitely not be the right solution. Best, H.‌ De : "Colin Finck" A : ros-dev@reactos.org Envoyé: mercredi 30 mai 2018 18:21 Objet : Re: [ros-dev] Status Meeting (May 2018) Am 30.05.2018 um 13:26 schrieb Ged Murphy: Potential proble

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

2018-05-30 Thread Oleksandr Shaposhnikov
P.S. I don't see Giannis email in the list :/30 трав. 2018 р. 19:51 Oleksandr Shaposhnikov пише:I think we should BOTH automatically merge when 2+ review approvals are given, automatically close PR's stalled in "changes requested" state for some time AND don't hesitate to merge PR's via a button

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

2018-05-30 Thread Oleksandr Shaposhnikov
I think we should BOTH automatically merge when 2+ review approvals are given, automatically close PR's stalled in "changes requested" state for some time AND don't hesitate to merge PR's via a button on the website.I had an idea in my head for quite some time to make a not that can automate

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

2018-05-30 Thread 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

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

2018-05-30 Thread 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

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

2018-05-30 Thread Daniel Reimer
If this does not count, then I vote for this topic, too. Fun fact here, I am listed as core developer :P Greetings Daniel Am 30.05.2018 um 09:39 schrieb mich...@fritscher.net: Good day, just as a suggestion for this or a following meeting (I'm no "core developer", so I can not attend to

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

2018-05-30 Thread Ged Murphy
From: Ros-dev On Behalf Of Colin Finck Sent: Monday, 28 May 2018 08:16 To: 'ReactOS Development List' Subject: [ros-dev] Status Meeting (May 2018) 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 rec

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

2018-05-30 Thread michael
Good day, just as a suggestion for this or a following meeting (I'm no "core developer", so I can not attend to it): Additional topic: "Get the demo laptop running completely and add it into our testbot" As the main lesson learnt from the CLT18, we have almost no visible advantages

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

2018-05-29 Thread Alexander Rechitskiy
Agenda proposal:USB status in general and how to build ReactOS in ReactOS with USB-parts enabled. 28.05.2018, 10:17, "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

[ros-dev] Status Meeting (May 2018)

2018-05-28 Thread 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 ==