Ros-dev

ros-dev@reactos.org

5788 discussions

FOSDEM 2020

by Colin Finck

Hi all! It took a while but FOSDEM has finally put a list of accepted stands on their website: https://fosdem.org/2020/news/2019-11-19-accepted-stands/ Looks like we only got a stand on Sunday this year, with our friends from Haiku OS having one on Saturday only. Not really what I thought when signing up for a "shared booth as always", but I'm sure we're going to manage that. There are plenty of opportunities for us to fill an entire weekend in Brussels, including * Having a "mini Hackfest" on Saturday in a coworking space in Brussels (or alternatively at FOSDEM itself, but it's going to be crowded there) * Following up on what Victor and me discussed with the FreeBSD, Haiku, NetBSD, and RTEMS people at GSoC Mentor Summit regarding a port of the low-level FreeBSD kernel interfaces to ReactOS, making a vast amount of network and storage drivers available to us. As far as I recall, the FreeBSD people have a conference in Brussels just before FOSDEM and are inviting us to join (Mahdi - correct me if I'm wrong). * Asking the Haiku guys if we shall try to join their booth on Saturday while they join ours on Sunday (Adrien? François?) But first I'd like to know who else is definitely going to make it to Brussels. Please reply to my mail ASAP, then we can have a short meeting on Mattermost soon and come to a decision. Cheers, Colin

4 years, 9 months

Report from the GSoC Mentor Summit 2019

by Colin Finck

Hi all! Victor and me are having a good time at this year's GSoC Mentor Summit in Munich, and it's time to get out a first report. Again, I'm getting the impression that all projects here pretty much share the same problems and ReactOS is not doing anything particular wrong. Today, I have attended a session about keeping students involved after GSoC. Most projects are struggling with that and there were some projects where it's usual for all students to just stay for GSoC and immediately leave afterwards. Anyway, I took some insights where we can improve to keep more of our students: * Give students some responsibility early on, so they feel responsible and needed for a project even after GSoC. The ultimate goal should be to turn them into mentors later. We already have a fairly good track record of that, but I think it should be emphasized here. * Invite more students to our Hackfest. We may need to postpone it by a few weeks to not clash with the final days of GSoC. For the MacPorts project, this resulted in all 3 students staying with the project after GSoC. * Talk to students on a personal level (possibly even through audio or video chat) and get them into our community. We had some high-performing students in the past who needed almost no mentoring, but this also resulted in less interactions with the community and we had a hard time to keep them involved after GSoC. * Collect tasks all year long, not just shortly before GSoC. This is important not just for keeping students, but also for enabling our paid development ideas around ReactOS. It's still important to ask a student what he or she wants to work on after GSoC, but we should always have some interesting tasks available. * Advertise our scholarship model early enough during GSoC to keep the people that are also doing it for the money. * Advertise our GSoC participation at universities. Some students managed to declare their GSoC participation as the technical internship required for their studies. All in all, the Mentor Summit again was a great opportunity to meet up with fellow Open-Source developers all around the world and have some interesting discussions. I'm already looking forward to the next one! We even got some ReactOS work done <https://github.com/reactos/reactos/pull/1835> just in sight distance of the Microsoft Germany HQ :D Cheers, Colin

4 years, 11 months

INVALID OPCODE

by katahiromz .

An error occurred in FreeLoader v3.0. 0x06: Exception 06: INVALID OPCODE

4 years, 12 months

why is the project so silent?

by Dick

Hi, why is the project so silent? Normally there were messages about online meetings, upcomming releases etc. on this list but it became realy silent and the last release is long time ago. what happened to reactos? best regards, dick

5 years

Re: [ros-dev] [ros-diffs] [reactos] 01/01: [NETAPI32] Add the NetpAllocStrFromWStr helper function

by Thomas Faber

Hey Eric, On 2019-08-24 14:01, Eric Kohl wrote: > +PSTR > +WINAPI > +NetpAllocStrFromWStr( > + _In_ PWSTR InString) > +{ > + UNICODE_STRING UnicodeString; > + OEM_STRING OemString; > + ULONG Size; > + NET_API_STATUS NetStatus; > + NTSTATUS Status; > + > + RtlInitUnicodeString(&UnicodeString, InString); > + > + Size = RtlUnicodeStringToOemSize(&UnicodeString); > + NetStatus = NetApiBufferAllocate(Size, > + (PVOID*)&OemString.Buffer); > + if (NetStatus != NERR_Success) > + return NULL; > + It seems like OemString.MaximumLength should be initialized before calling RtlUnicodeStringToOemString? > + Status = RtlUnicodeStringToOemString(&OemString, > + &UnicodeString, > + FALSE); > + if (!NT_SUCCESS(Status)) > + { > + NetApiBufferFree(OemString.Buffer); > + return NULL; > + } > + > + return OemString.Buffer; > +} Best, Thomas

5 years

Re: [ros-dev] [ros-diffs] [reactos] 01/01: [NETAPI32] Implement DsDeregisterDnsHostRecordsA

by Thomas Faber

Hey Eric, On 2019-08-24 22:58, Eric Kohl wrote: > diff --git a/dll/win32/netapi32/netlogon.c b/dll/win32/netapi32/netlogon.c > index 2c068dc176b..73a0324f0fa 100644 > --- a/dll/win32/netapi32/netlogon.c > +++ b/dll/win32/netapi32/netlogon.c > @@ -313,10 +313,58 @@ DsDeregisterDnsHostRecordsA( > _In_opt_ GUID *DsaGuid, > _In_ LPSTR DnsHostName) > { [...] > + > + if (DnsDomainName != NULL) > + { > + pDnsDomainNameW = NetpAllocWStrFromAnsiStr((PSTR)DnsDomainName); > + if (pDnsDomainNameW == NULL) > + { > + status = ERROR_NOT_ENOUGH_MEMORY; > + goto done; > + } > + } > + > + pDnsHostNameW = NetpAllocWStrFromAnsiStr((PSTR)DnsDomainName); UserNT points out that you probably meant DnsHostName here rather than DnsDomainName. > + if (pDnsHostNameW == NULL) > + { > + status = ERROR_NOT_ENOUGH_MEMORY; > + goto done; > + } > + Best, Thomas

5 years

Re: [ros-dev] BuildBot Upgrade on Tuesday

by Sylvain Petreolle

Hello all, Connecting to the new buildbot now shows an avatar picture from www.gravatar.com. What are the legal implications ? What personal data are sent here ? Is it still possible to see online logs as plain text ? https://build.reactos.org/#/builders/9/builds/24976/steps/5/logs/stdio/text comes back to the index now. Looking at a 1 billion lines hung log as HTML won't do anything good, for the client and the server. | | Kind regards, Sylvain Petreolle Le Dimanche 23 juin 2019 23h13, Colin Finck <colin(a)reactos.org> a écrit : Hi all! Our BuildBot at https://build.reactos.org is finally going to be upgraded from the ancient version 0.8.14 to the latest 2.3.1 release this Tuesday evening (CEST). We have postponed this for a very long time due to the fundamental UI changes in newer versions. The UI has been rewritten from scratch and its Waterfall View has been simplified. I used to be a strong opponent of this change. However, in one of the last meetings, it turned out that the current Waterfall View isn't that popular among our developers anyway. You can expect the new BuildBot to look like this: https://lidell.nu/xemacs-buildbot/ BuildBot also doesn't provide a direct migration path from the old to the new version. This means that previous build and log information will be gone after the upgrade. I used to consider this a blocker as well, but current BuildBot already purges old build/log information after some time and apparently it hasn't been missed. We still have all important information in Testman. I will make sure however that build numbers in the new version continue where they ended in the old version. On the plus side, this upgrade brings integrations with GitHub and Mattermost as well as proper Unicode support. Using an up-to-date BuildBot version also allows us to actually enhance it. In fact, this upgrade is a prerequisite for the Developer Web Interface our GSoC student Ayush Sinha is currently working on. Regarding Buildslaves (now called "workers"), the new BuildBot is still compatible with 0.8.x clients, so these don't need an upgrade right away. We just need a small change on workers submitting test results. Kudos go to Victor Perevertkin, who has already begun evaluating the new BuildBot version a long time ago and provided me with an updated master.cfg file, along with other help! I'm glad that the number of people maintaining our BuildBot setup is growing! :) Cheers, Colin _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.org http://reactos.org/mailman/listinfo/ros-dev

5 years, 2 months

Hackfest 2019 - Deadline for Merchandising and Financial Assistance

by Colin Finck

Hi all! The ReactOS Hackfest will take place in about a month and a week. Please revisit https://reactos.org/wiki/ReactOS_Hackfest_2019/Lists and put yourself in all relevant lists if you are going to attend. I've just updated the Shirts/Hoodies section with the final design. Please check that out and add whether you want a shirt or a hoodie. You may also want to check the links regarding the exact sizes again. Deadline for this is THURSDAY, JULY 11 After that, I will move on and buy the merchandising products. If your attendance at the Hackfest needs financial assistance from ReactOS Deutschland e.V., please also get in touch with me before that deadline. You know, flights and accommodation get more expensive the closer we are to the event date ;) Cheers, Colin

5 years, 2 months

BuildBot Upgrade on Tuesday

by Colin Finck

Hi all! Our BuildBot at https://build.reactos.org is finally going to be upgraded from the ancient version 0.8.14 to the latest 2.3.1 release this Tuesday evening (CEST). We have postponed this for a very long time due to the fundamental UI changes in newer versions. The UI has been rewritten from scratch and its Waterfall View has been simplified. I used to be a strong opponent of this change. However, in one of the last meetings, it turned out that the current Waterfall View isn't that popular among our developers anyway. You can expect the new BuildBot to look like this: https://lidell.nu/xemacs-buildbot/ BuildBot also doesn't provide a direct migration path from the old to the new version. This means that previous build and log information will be gone after the upgrade. I used to consider this a blocker as well, but current BuildBot already purges old build/log information after some time and apparently it hasn't been missed. We still have all important information in Testman. I will make sure however that build numbers in the new version continue where they ended in the old version. On the plus side, this upgrade brings integrations with GitHub and Mattermost as well as proper Unicode support. Using an up-to-date BuildBot version also allows us to actually enhance it. In fact, this upgrade is a prerequisite for the Developer Web Interface our GSoC student Ayush Sinha is currently working on. Regarding Buildslaves (now called "workers"), the new BuildBot is still compatible with 0.8.x clients, so these don't need an upgrade right away. We just need a small change on workers submitting test results. Kudos go to Victor Perevertkin, who has already begun evaluating the new BuildBot version a long time ago and provided me with an updated master.cfg file, along with other help! I'm glad that the number of people maintaining our BuildBot setup is growing! :) Cheers, Colin

5 years, 2 months

Coding style fixes/improvements

by Victor Perevertkin

Hi! Recently I've looked into Doxygen manual for writing documentation and noticed that an example on our Coding style <https://reactos.org/wiki/index.php?title=Coding_Style> page on wiki uses some statements in a wrong way. Namely, @name statement is for defining sections, groups and definitely not for functions/structs/classes etc. Another thing is a function description. Doxygen has two types of them: brief and detailed one. Brief description must be defined by @brief statement, but for detailed one @details can be omitted (which in fact was done in our example). Obviously, brief description should be used in first place (and that would be likely the only one) I've made some changes, to the page (see the latest change in page history) Btw, I think it can be extended to something like this ( http://micro-os-plus.github.io/develop/doxygen-style-guide/) sometime If you have any objections or suggestions, feel free to add them or discuss here. Cheers, Victor

5 years, 3 months

← Newer
1
...
4
5
6
7
8
9
10
...
579
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev