Dan Moniz wrote:
> What really needs to be done is to release some code, so people can
> start seeing some progress. This is my fault. I tried to drum up some
> discussion on the project lists I created through SourceForge back in
> September, but that hasn't happened yet. I know Michael is waiting for
> code and may be progressing along with his own BEEP implementation in
> Ruby for his MUD project. I would very much like to merge those
> efforts, which he and I have talked about a lot before, but I stall
> out and lose touch with him.
I am in a similar situation where I would like to have a BEEP lib for my
own projects. I started some code also, though its just a skeleton of an
implementation. I think maybe a good first step would be to get all the
code that different people have made out there.
I have put my own code scribbles in CVS under
beepcore-ruby/src/prototype/curne/src. I suggest that others that have
code put their's in beepcore-ruby/src/prototype/<username>/src so we can
compare notes. My own code is not worth much, its mostly a gesture :-)
> If you're still interested, I can still use the help, mostly to keep
> myself motivated. Subscribe to the lists and pepper me with questions.
> I'll re-re-re-re-dust off the draft functional spec doc and update it
> to actually say something worthwhile and would love to send that
> around to the lists for comments.
I hope I speak for all of us, certainly for myself, when I say that we
signed up for this project because it is worthwhile doing. Personally I
have great interest in seeing a functional BEEP implementation for Ruby.
> And bring your friends!
:-)
> Thanks for your support.
Not to mention it. Ruby BEEP Core is a collective effort right?
Curne
--
|
