Thread: [beepcore-ruby-discuss] Re: BEEPcore-ruby

At 10:29 AM 5/14/2003 -0700, Nathan Droft wrote:

>Hi Dan,

Hi Nathan,

>It has been a while since I signed up for the beepcore-ruby
>project. I still want to contribute. Is anything happening?
>
>Let me know where things are.

Well, more or less were they were when I last tried to jump start this. 
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.

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.

And bring your friends!

Thanks for your support.


-- 
Dan Moniz <dn...@po...> [http://www.pobox.com/~dnm/]

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
--

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 05:38 AM 5/27/2003 +0200, Nathan Droft wrote:

>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 :-)

Thanks for adding your code in Nathan.

If you could, try to see if you can rearrange the layout. I notice that 
currently, the code is checked in under the following CVS tree:

beepcore-ruby/beepcore-ruby/src/prototype/curne/src

I'd like if we kept to:

beepcore-ruby/prototype/curne/src

Or something similar and less confusing.

Thanks for your support.


- -- 
Dan Moniz <dn...@po...> [http://www.pobox.com/~dnm/]

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0
Comment: Please see <http://www.pobox.com/~dnm/keys.html>

iQA/AwUBPyeS7lmE1hyKYjtREQK+AACgnS6TJUcOW33ld4JeyCNHQMXH1rYAoIH/
7b28JTOTFD+5cXRbJmFAcl1I
=4h7o
-----END PGP SIGNATURE-----

Hi Dan

Dan Moniz wrote:

> Thanks for adding your code in Nathan.
>
>If you could, try to see if you can rearrange the layout. I notice that 
>currently, the code is checked in under the following CVS tree:
>
>beepcore-ruby/beepcore-ruby/src/prototype/curne/src
>
>I'd like if we kept to:
>
>beepcore-ruby/prototype/curne/src
>
>Or something similar and less confusing.
>
>Thanks for your support.
>
I think if you check that you will the source layout is as you expect. 
The beepcore-ruby/beepcore-ruby is a cosmetic detail of the CVSview 
page. If you do a  cvs co beepcore-ruby  the source comes out with the 
following structure:
beepcore-ruby
beepcore-ruby/src
beepcore-ruby/src/prototype
beepcore-ruby/src/prototype/curne
beepcore-ruby/src/prototype/curne/src
--
/BEEP - Adding another layer to the OSI model/
http://sourceforge.net/projects/beepcore-ruby/