Ros-dev November 2022

ros-dev@reactos.org

3 participants
3 discussions

Mail server maintenance on Tuesday, 6th December
by Colin Finck 13 Dec '22

13 Dec '22

Hi all! Our IServ system used for mail and mailing lists will be down for maintenance on TUESDAY, 6TH DECEMBER 2022 15:00 ~ 17:00 UTC During this time, you won't be able to send or receive any mails using your @reactos.org address. Other servers sending mail to your @reactos.org address will usually try again after the maintenance. This time, the mailing lists may be down for a few more hours though. Our currently used Mailman 2 mailing list software is no longer supported, and we need to upgrade it to Mailman 3. However, Mailman 3 has been rewritten from scratch, so the upgrade won't be straightforward. For instance, Mailman 3 comes with a new web interface with new URLs, breaking all existing URLs to mailing list posts. The best we can do to keep URLs intact is keeping them in their current state forever, with a link to the new archives for new posts (like the Python Project did for https://mail.python.org/pipermail/python-dev/). This is probably better than closing mailing lists altogether (like GNOME did: https://www.theregister.com/2022/10/27/the_gnome_project_is_closing/). Not that we've been using ros-dev much lately. But it's still the primary spot to reach out to all developers. And I assume even more people are relying on ros-bugs and ros-diffs for their work. Please speak up if you're still using them. Other services won't be affected by this migration. In particular, all means of communication through Mattermost and the website/forums will stay live. Best regards, Colin Finck

1 1

Re: [ros-dev] Update contributing rules and PR management
by George Bişoc 16 Nov '22

16 Nov '22

My point still stands regarding this matter as stated on PR. The newly updated contribution rules are too restrictive and this forces people who don't contribute to the project with code by submitting their real name, and that's a big NO from me. I would simply propose the following suggestions: 1. Make such rule only mandatory for people who contribute with code; 2. People such as translators, artists and anyone who doesn't contribute with code should be exempt from this; 3. If someone wishes to contribute to the project with code but feels uncomfortable or paranoid to submit their legal name, one can send a legal document declaring the reason why they shouldn't use their real name but can use a recognizable alias instead (we will have to think of a template if such idea ever gets through). As for the 3rd point, this can confliate with the 1st point as most people will start asking to use their alias for contributing but that's a naive speculation from me. I don't know how do other FOSS projects handle this. We have productive people like I_Kill_Bugs who provides useful patches, it would be of a great bonus if we can somehow leverage the rules so that people can help the project. Regards, George Stas'M <binarymaster(a)mail.ru> wrote on Tue, November 15th, 2022, 8:09 PM: > Hello all! > > Recently I have created a Pull Request which updates the contributing rules and PR management: > https://github.com/reactos/reactos/pull/4881 > > This PR is a result of discussion in the chat with Joachim Henze and Thomas Faber regarding noreply e-mails being used by some GitHub contributors. > > It has been experimentally verified that using anonymous GitHub e-mail does not allow to deliver mail to the commit authors. GitHub does replace author's real email when `Keep my email addresses private` option is enabled in the account's e-mail settings. > > Additionally I have replaced old IRC links with the references to our chat. > > Please send an approval review on GitHub if you are okay with the changes I made in this PR. Suggestions are also welcome. > > -- > Stas'M was here

1 0

Update contributing rules and PR management
by Stas'M 15 Nov '22

15 Nov '22

Hello all! Recently I have created a Pull Request which updates the contributing rules and PR management: https://github.com/reactos/reactos/pull/4881 This PR is a result of discussion in the chat with Joachim Henze and Thomas Faber regarding noreply e-mails being used by some GitHub contributors. It has been experimentally verified that using anonymous GitHub e-mail does not allow to deliver mail to the commit authors. GitHub does replace author's real email when `Keep my email addresses private` option is enabled in the account's e-mail settings. Additionally I have replaced old IRC links with the references to our chat. Please send an approval review on GitHub if you are okay with the changes I made in this PR. Suggestions are also welcome. -- Stas'M was here

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev November 2022