Aagghhhhh!!! Why is everything always done over IRC????

 

The neglection of the reactos mailing lists is one of this _big_ things this project does wrong.

 

-          It forces the community into a sort of hidden niche group and alienates people who don’t use IRC

-          It gives the impression that reactos activity is low. There are thousands of people who follow this project aren’t on IRC and have no idea of what is going on.

-          It arguably deters new people from joining because they can’t really get to grips with the project without becoming a slave to IRC

-          It means important discussions are missed, even by the core team, if they aren’t watching the IRC chat 24/7 or miss a PM

 

I could go on and on with reasons of why you neglect the mailing lists is so harmful, but I fear no one will listen to my cries.

Maybe I should vent my frustration in IRC for the niche community, and we can all have an internal discussion about it???

 

Ged.

 

 

 

 

From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Aleksey Bragin
Sent: 27 October 2010 13:54
To: ReactOS Development List
Subject: Re: [ros-dev] Networking

 

Yes, please feel free to join our channel when you have any questions. I will create a branch for your coming work, if you like.

 

Thanks!

 

 

WBR,

Aleksey.

 

On Oct 27, 2010, at 2:47 PM, Olaf Siejka wrote:



Hiya

 

Discussing issues on ros-dev maillist is fine. I asked Aleksiej to pass you the irc channel discussion mostly for helping you out with basic ROS stuff like compilation, VM setup and testing issues.

 

Regards

 

2010/10/27 Oleg Baikalow <obaikalow@gmail.com>

Hi,

I see you're busy discussing other stuff and my message went unnoticed :) I made a look to existing network branches, found many of them. LWIP is interesting. Alexey said the best way is to join your irc channel. I will try to occasionally join, but in your project, mailing list must be a primary point of discussion not irc channel.

 

I think I start from making a simple, but robust tcpip driver (with help of numerously available source code of tcp/ip protocol implementations). Hopefully you could give me branch access, it's gonna be hard to develop it with patches.

 

// Oleg Baikalow.

 

P.S. I really like your "kernel coding style", quite rare to see that in opensource projects. Most of foss projects utilize linux-alike stlye, whic is harder to read and not that clean.