And the 2nd try, now on general ML, too.
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2024.
Somone interested? Of course I prefer these ppl who know the project,
like devs and long time community members.
https://chemnitzer.linux-tage.de/2024/en
If you wanna take part, ping me here or on
https://chat.reactos.org/reactos/channels/clt-2024 please.
P.S. If I don't get enough ppl this time, I will cancel our booth there
last minute. Something like last year will not happen again. Last year
was quite a hassle as the booth always needs at least one person
available there. Difficult if you are there all alone most of the time.
I had enough sarcasm and aversion regarding our project last year and at
least one more permanent person there is the minimum to stand our ground
and properly answer the questions of some ppl who show up. There are
even a few ppl that claim we have zero interest in new devs and claim to
have talked to us in Chemnitz in the past regarding supporting us. This
is even possible tbh... I try to write down anything important, but
sometimes maybe some things slipped through if there are 3-4 ppl waiting
to ask questions. I know that many of our core members think that PR is
of no use at all, but this is where I think different. People out there
think we are close to complete breakdown of the project, no progress, no
devs, no common goal we aim to accomplish and always kicking around new
devs that wanna help. Some even thought we already are a goner and were
surprised to even see our booth there. This is nothing we should ignore
at all! So check your calendars and reply plz!
Daniel
P.P.S: I already got a reply from a guy from overseas, but I don't think
it would be ideal to accept that he comes over by plane and then after a
weekend will be discarded again. I'd feel a bit abused by that in his
place tbh. Anyways, without some other member who can take over and
answer questions on the booth aka a member of the project or long term
follower, I won't need to think about that as this would mean that we
won't show up in Chemnitz after 10+ years in a row. So... Someone
interested in giving a helping hand? Costs is not the problem btw, we
have the money to pay for the expenses
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2024.
Somone interested? Of course I prefer these ppl who know the project,
like devs and long time community members.
https://chemnitzer.linux-tage.de/2024/en
If you wanna take part, ping me here or on
https://chat.reactos.org/reactos/channels/clt-2024 please.
P.S. If I dont get enough ppl this time, I will cancel our booth there
last minute. Something like last year will not happen again. Last year
was quite a hassle as the booth always needs at least one person
available there. Difficult if you are there all alone most of the time.
I had enough sarcasm and aversion regarding our project last year and at
least one more permanent person there is the minimum to stand our ground
and properly answer the questions of some ppl who show up. There are
even a few ppl that claim we have zero interest in new devs and claim to
have talked to us in Chemnitz in the past regarding supporting us. This
is even possible tbh... I try to write down anything important, but
sometimes maybe some things slipped through if there are 3-4 ppl waiting
to ask questions. I know that many of our core members think that PR is
of no use at all, but this is where I think different. People out there
think we are close to complete breakdown of the project, no progress, no
devs, no common goal we aim to accomplish and always kickng new devs
that wanna help around. Some even thought we already are a goner and
were surprised to even see our booth there. This is nothing we should
ignore at all! So check your calendars and reply plz!
Daniel
I made some minor changes to to classint.c (reactos/dll/cpl/desk) to allow proper install of the VirtualBox Guest Additions (version 7.0.12-159484) VBoxVGA driver. The additional registery settings (SoftwareSettings section of the INF file) where not installed with the VirtualBox Guest Addtions.
Would the project like me to commit the changes (via a Git pull request)? The update is 25 lines of code.
Thanks!
Bob
Hi there,
When attempting to connect to a running (qemu) ReactOS VM via gdb I
get the following error:
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
warning: No executable has been specified and target does not support
determining executable automatically. Try using the "file" command.
Remote 'g' packet reply is too long (expected 308 bytes, got 536 bytes):
(followed by a long hex number).
I tried different processor settings, different ReactOS compilations and
different gdb's (Ubuntu's i686-w64-mingw32-gdb for example).
Is this a known issue? If so, is there a solution for it?
Ubuntu version where gdb and qemu are running is:
Ubuntu 18.04.2 LTS
Thanks a lot for hints how to solve this,
Best regards,
- Johannes
Hello guys,
Last try after one person had to step down due to work and rl craziness...
I still look for one or two ppl joining us to Chemnitz Linux Days 2023.
Someone interested? Of course I prefer these ppl who know the project,
like devs and long time community members, but other are free to ask,
too. FREE hotel room and FREE food! Maybe even paid train or car fuel
costs which I cannot promise 100% right now.
https://chemnitzer.linux-tage.de/2023/en
If you wanna take part, ping me please.
Daniel
P.S: Cmon, where are all the German ROS fanboys -girls?!
ReactOS could be developed further in order to run in ARM cpu natively all
Windows environment ecosystem Operating Systems types ALL IN ONE and all
programs of:
- Windows NT*
- Windows Compact CE which is public distributed
- Windows Runtime / WinRT (Universal Windows Packages) Which is open sourced
- an adaptation of ArcaOS and/or Windows ME in order to run DOS.
- ability to run Windows Phone .xap and .appx files and their content
*The Wine Project (winehq) of Linux could support the development for
Windows NT adaptation on ReactOS.
Hello guys,
I still look for one or two ppl joining us to Chemnitz Linux Days 2023. Somone interested? Of course I prefer these ppl who know the project, like devs and long time community members.
https://chemnitzer.linux-tage.de/2023/en
If you wanna take part, ping me please.
Daniel
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
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
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
