Naming the beast

Started by Blacklord, June 26, 2006, 05:39 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Blacklord

xlar54 has come up with the following suggestions for a name :

Red Dragon BBS (mythical)
Omega BBS (the last BBS)
Citadel BBS (mythical)
128NET BBS (8 bit net)
InterCom BBS (obvious)
CBBS

Anyone have others to toss into the ring ? make your suggestions & once we have a development team built, I'll throw 'em up for the vote.

Lance

Guest

How about OpenBBS128 which reflects it's foundations in Free Open Source Software and that it runs on the Commodore 128.  Any name that specifies that it will be a "final" bbs, or anything else like that is not realistic, and I don't think a name using mythical or historical references are appropriate.

christianlott1

I'm intersted in your interface but I'm more interested in your code to make the I/O work.

A unifying project name would be appropriate but for my side, I'd like mine to run on both 64 and 128.

Will the feature set include IRC?

The 'open' name has been used in EVERYTHING, so I'm thinking that's kind of lame. Also, directly naming the BBS is lame too. The syops should be able to customize this system to the point of naming their BBS themselves.

Sooo - when I asked about feature set - what exactly is a standard bbs? Are their features which should NOT be implemented on a bbs, like standard email checking via yahoo, etc?

Sooo - if this is a hybrid bbs, maybe that's what we should name it - hybrid bbs or Unstandard BBS, etc...

Maybe we should come up with a different acronym than BBS but just reserve the BBS as a module within a larger system.

Blacklord

Quote from: christianlott1I'd like mine to run on both 64 and 128.
I think a C64 implementation is out of scope in that the project would need to be severely downsized to cope with the limitations of the C64 compared with the 128 (ie, lesser memory, slower speed, lack of 80 colum mode). However, nothing stopping someone from forking it later on if they want to, but not as part of the original design.

Lance

xlar54

It will certainly be configurable so that the Sysop can name their system - what he's refering to is the "brand" name.  (like Centipede, Omni, CNet 128, etc).

We wont need to agree on a name right away.  But keep the ideas coming in on this thread.  Giving what Payton was saying, Ill toss out there "OpenNET 128".  OpenXXX may have been overused, but I do agree, it conveys pretty quickly that this is an open source system.

David Nelson

Quote from: admin
Quote from: christianlott1I'd like mine to run on both 64 and 128.
I think a C64 implementation is out of scope in that the project would need to be severely downsized to cope with the limitations of the C64 compared with the 128 (ie, lesser memory, slower speed, lack of 80 colum mode). However, nothing stopping someone from forking it later on if they want to, but not as part of the original design.
I was just about to say something similar. Once the 128 version is up and running, if some people are interested in trying to downsize it and see what will fit on a 64, that'd be great. The differences are likely to be large enough that trying to support both right now would be like trying to write the BBS twice. Get one done and then port to the other. :)

-David

bill.mann

I'm not sure that OpenNET conveys a BBS though. Sounds more like a networking protocol. Just a thought!