Hi Jim, glad to hear from you about this :-)
> But mostly it's because I hadn't *removed* lesser-used communication > channels from the website. So we have all these places linked from > the "Forums" page, but some places are not very populated. People already *on* the lesser-used channels are unlikely to notice the new channels: See for example me who just notices the extreme silence on the freedos-kernel mailing list or you yourself who assumed the SF kernel sources are current, while the github fork of Jeremy could be pushed via regular reminders on SF and freedos-kernel, maybe even with little blog style "cool things which happened in the github kernel" quarterly news? ;-) Or the example of my noticing a problem with directories-as- disks in dosemu2: It turned out that 1. you now have to load guest drivers for write access to work correctly and 2. The dosemu2 people have given up on running classic FreeDOS and only use their own heavily updated kernel and shell variants and only test for bugs in those. Nice, automated tests :-) > But the freedos-kernel list is not used very much. Looking at the > archive, this hasn't seen more than a few emails per *year* in the > last several years. What if we retired the freedos-kernel list and > encouraged any kernel development discussion to happen on > freedos-devel? Sounds like a good idea, if Jeremy and any other kernel experts have the time for such discussion? I think it would really help to have more communication about what is going on, both because it inspires devel and because it inspires and empowers users. > https://www.facebook.com/groups/freedos/ > This is seeing a lot of discussion. No idea, social media do not exist in my anti-social life ;-) No instagram either. Luckily most youtube videos are accessible without logging in to tell google who watched what when why. > I'd generally describe it as a place where people talk about > how they are using FreeDOS. So basically it is a freedos-user to be used by those who like websites which cannot be visited with DOS based browsers ;-) > https://twitter.com/freedos_project> > I use this pretty frequently, but usually to "broadcast" stuff That makes sense, Twitter is for broadcasting small news bites. I hope you also post the more interesting ones in some sort of news section of the website as before? > * I also will tweet small news items from the FreeDOS Twitter account > that I wouldn't usually post on the website. Generally, when someone > announces a new project for FreeDOS (usually a game) I'll tweet about I MYSELF would be happy to read about all of those on freedos-user, but I do not know whether others would feel flooded? I sometimes forward announces discussed on BTTR to freedos-user myself, but I skip the more exotic ones. > https://www.youtube.com/freedosproject Given the category description, it sounds like a nice channel for more entertaining DOS lifestyle items. > https://freedos-project.blogspot.com/ > I had been doing a lot of writing here... What makes that better than a blog on freedos.org? > DOS Ain't Dead > <http://www.bttr-software.de/forum/index.php> > This isn't a "FreeDOS" forum, but I follow it and re-post any > interesting announcements on the FreeDOS Twitter, or the website See above ;-) > And some lesser used communication channels: > > Slack Did not even know we had any...? > IRC I only remember the I7C one, but cannot even reach Tassilo now! I would need to reach him to fix something, though... Having 42 IRCers on your new DOS IRC sounds like not so few? > USENET Did not know that newsgroups have specific FreeDOS traffic, assumed this to be a left-over from classic MS DOS times. > And we also have the Wiki for documentation and other information, and > the bug tracker on SourceForge to track bugs and feature requests. In theory yes, but there seem to be zero reactions to reports :-( At least that is what made dosemu2 abandon attempts to contact the maintainers of classic FreeDOS components and just go fork. Regards, Eric PS: How about the two FreeCOM branches? And binaries, changelogs and lists of known issues for Blair-LFN and classic separately? _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
