|
Grex > Oldcoop > #364: Agenda for BOD meeting, Tuesday, 9/26/06, 8PM | |
|
| Author |
Message |
| 17 new of 66 responses total. |
aruba
|
|
response 50 of 66:
| 
Sep 28 04:46 UTC 2006 |
I agree with the principles Nate cites.
|
remmers
|
|
response 51 of 66:
|
Sep 28 16:49 UTC 2006 |
Re #46: Right, there are plenty of talented people who log in to Grex.
As you say, "We have PhDs, professional system administrators,
programmers...the list goes on."
As a practical matter, I wonder how much of those talents would actually
be available to us, given people's busy lives and time constraints. For
example, my impression is that you have some technical skills that would
be of value to Grex. Can you estimate how many hours per week you would
have available to devote those skills to Grex? How big a personal
commitment could you afford?
|
cross
|
|
response 52 of 66:
|
Sep 28 19:51 UTC 2006 |
Doing what, though? I'd volunteer to work on grexsoft again, but when I *was*
working on it, no one else was at all interested and after a while it just
became a pleasant but ultimately useless time sink for me. Then again, it
never made it through the last OpenBSD upgrade. Hmm. Maybe I should
volunteer for staff to reinstall it. I wonder how receptive staff and the
board would be to such a thing? (That's a real question.)
grexdoc could also use some reoganization.
|
tod
|
|
response 53 of 66:
|
Sep 28 20:00 UTC 2006 |
We should build an opensource replica of the grex system.
|
cross
|
|
response 54 of 66:
|
Sep 28 20:02 UTC 2006 |
It's most of the way there, except for a picospan replacement.
|
tod
|
|
response 55 of 66:
|
Sep 28 20:13 UTC 2006 |
Maybe you should think about transcoding Eagle's Nest BBS or something
Take your pick of BBS...
ftp://sunsite.unc.edu/pub/linux/system/bbs
|
cross
|
|
response 56 of 66:
|
Sep 28 22:28 UTC 2006 |
I've looked at a lot of those; they're basically all pretty poorly
implemented. I think that one of the things that made Picospan and YAPP
reasonably successful is that, imperfect though they are, they integrate
reasonably well into the Unix paradigm. Most of the menu-based BBS systems
don't really do that.
I think the best thing to do would be define a protocol for how a
client/server BBS system would look like; what kind of RPC's (or functional
equivalent) would one want? PostItem, PostResponse, etc, and then build a
system on top of that. This is essentially what Jan did with
backtalk/fronttalk, but he chose to use HTTP as the basic protocol, which
eliminates a lot of the state-full-ness of the whole thing and makes some
things difficult; hence not all of PicoSpan is in fronttalk (and of course
it still has that damn bug where a C-style NUL character ' \ 0 ' terminates
an input buffer because it's not properly quoted...).
|
tod
|
|
response 57 of 66:
|
Sep 28 22:54 UTC 2006 |
I'm satisfied using YABB. Its flat file and neat.
|
cross
|
|
response 58 of 66:
|
Sep 28 23:02 UTC 2006 |
Does it have a command line interface?
|
tod
|
|
response 59 of 66:
|
Sep 28 23:49 UTC 2006 |
Currently developing a lynx friendly front end for it.
|
cross
|
|
response 60 of 66:
|
Sep 28 23:54 UTC 2006 |
Hmm. That's not quite the same thing.... (But still a good idea....)
|
tod
|
|
response 61 of 66:
|
Sep 29 00:39 UTC 2006 |
re #60
Thank of the mobile phone possibilities
|
slynne
|
|
response 62 of 66:
|
Sep 29 00:51 UTC 2006 |
resp:52 I would be happy to see you on staff
|
cross
|
|
response 63 of 66:
|
Sep 29 01:04 UTC 2006 |
Regarding #61; Good point.
Regarding #62; Thanks!
|
naftee
|
|
response 64 of 66:
|
Sep 29 03:50 UTC 2006 |
yeah; you were doing good work on GreXsoft, cross.
|
spooked
|
|
response 65 of 66:
|
Oct 12 09:48 UTC 2006 |
I would support a new system
|
mary
|
|
response 66 of 66:
|
Oct 12 10:32 UTC 2006 |
Me too.
|