Re: [ros-dev] Development request

Hi! Thank you for an interest in our project. Am I right, you are interested in a project which involves development tools like dynamic code analysis, verification, debugging, etc.? Victor Perevertkin On Sun, 2021-09-26 at 18:26 +0200, Mohamed Atef wrote: > Hello there, > We are 6 st

[ros-dev] The situation with version 0.4.14

Hello! It seems for me that it's time to bring up the topic about our RC version - 0.4.14. Our current "stable", 0.4.13 was branched on 30 September, 2019 (remember those peacefull pre-COVID times :D) That's quite some time, but not the main issue I'd like to discuss. 0.4.14 was branched on 24

[ros-dev] FOSDEM 2021 preparation

Hello everyone! We've got accepted to FOSDEM 2021, which (as you may already know) will be going online. FOSDEM provides a place on their stands website, we need to prepare a page for that. There is also a place for videos in case we want to share some :) Their website uses Hugo and is

Re: [ros-dev] Status Meeting (November 2020)

As I said, "It doesn't work without the standard library support". You will need to use a different standard library for old compilers Victor On Mon, 2020-12-21 at 18:47 +0100, Hermès BÉLUSCA-MAÏTO wrote: > But there is one thing here, it doesn't work without the standard > library > > support.

Re: [ros-dev] Status Meeting (November 2020)

Many words were said already about dropping the support for old compilers. I agree with all of them and want to put one more argument on top of it from myself. There are a lot of innovations happen in compilers and tooling. Big companies put thousands of man-hours to improve compiler toolchains

Re: [ros-dev] Status Meeting (November 2020)

Hey, > How much work needs to be done to get newer versions of MSVC > running This needs our compatibility layer to be finished (it's progressing, but slowly) > How big is the danger to lose the capability to exchange ReactOS > and Win 2k3 system files? As far as I know, we don't have issues

Re: [ros-dev] Status Meeting (June 2020)

I'd like to propose what I have on my mind: - 0.4.14 release status, what's left to do (should be a short one) - Unifying our contribution guidelines. I've found out that we have too many places with instructions for contributors. And if fact they don't quite indicate our expectations of a

Re: [ros-dev] [QubesOS] Debug first boot

Hi Frédéric, Debug logs are being written to a serial port if you select the "ReactOS (Debug)" option in the bootloader. It will help to understand what's going on in the OS. My guess that's some race condition while enumerating devices. As far as I can see, Xen shares some code with QEMU for

[ros-dev] Topics for next Meeting

Hi all! I would like to propose some topic to discuss on the next meeting (will it be on March, 26?) * Drop one theme from "default" package. Last release we added two new themes, but they both look unfinished in many aspects. As we have an active maintainer for one of them (Mizu), my suggestion

Re: [ros-dev] wined3d, Mesa for Windows

If somebody will do it, these projects can be used :) But AFAIK nobody is going to work on graphics anytime soon On Sat, Jan 11, 2020 at 10:52 AM Javier Agustìn Fernàndez Arroyo < elh...@gmail.com> wrote: > Hello guys, > > Please have a look at this website! >

[ros-dev] Coding style fixes/improvements

Hi! Recently I've looked into Doxygen manual for writing documentation and noticed that an example on our Coding style page on wiki uses some statements in a wrong way. Namely, @name statement is for defining sections, groups and definitely

[ros-dev] New CI investigation

Hi all! I've done some research on what can we do to improve our CI system. First of all, I want to clarify: our CI is consists of two parts: building and testing. I'm assuming here that "build" part is OK for us and doesn't require any improvements in workflow or something like that. So

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

Hi all! May I suggest one point to discuss? :) The number of NT6+ issues and PRs is growing and looks like some statement about it should be published, so we can just put a link and don't explain our position to everybody. The contents of such statement is a point for discussion. I'm not

Re: [ros-dev] GSOC 2019 - Costin Visan

org/issues/?jql=labels%3Dstarter-project%20and%20resolution%20%3D%20Unresolved%20> label for that, but feel free to take any. What's your area of interest? Kernel mode stuff, user space, web development? Cheers, Victor Perevertkin On Tue, Dec 18, 2018 at 6:19 PM costin visan wrote: > Hello!

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

> >I don't think anybody has already prepared a detailed plan, so we >should collect our ideas and expectations for a 0.5 release and >write them down at https://reactos.org/wiki/0.5_Planning There is already page for 0.5 - https://reactos.org/wiki/0.5.0 On Thu, Nov 29, 2018 at

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

by someone from Devs. But nobody does it for a while and there is no easy way to distinguish "accepted" tickets from others. I think we should return back to following this scheme or create a new one if this is not convenient. Cheers, Victor Perevertkin сб, 24 нояб. 2018 г., 23:38 Coli

Re: [ros-dev] New member

Hi, Nikita! Answered you directly in Russian Cheers, Victor On Wed, Oct 10, 2018 at 10:46 PM Никита wrote: > Hello, guys! > > I'm freelanсe fullstack web-developer (also i am C++ and C developer to, > but my skill not so high in those subj). By the way i have my own team of > designers. > So,

[ros-dev] Yet another GSoC proposal

internals. Thanks! Victor Perevertkin ___ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev