freeride-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[FR-devel] Re: Redistribution question


From: Richard Kilmer
Subject: [FR-devel] Re: Redistribution question
Date: Mon, 10 Mar 2003 22:23:56 -0500

Thanks why...I was trying to figure out how to take the next step in asking if we could use it to run our syndicate ;-)

Anyway, I am just cc'ing this to the FreeRIDE list to let others know that project "Who's your daddy" is a go...ah...I mean, we can add yaml.rb to FreeBASE with your permission.

-rich

On Sunday, March 9, 2003, at 01:52  AM, why the lucky stiff wrote:

Hey Rich.

Please do whatever you like with the YAML.rb library.  Honestly, if you
want to change the name, reattribute it to yourself and start the
largest syndicate of corruption this world has seen, you have my
permission.  I don't want licensing or the structure of my distribution
to limit your project's path.

Future incarnations of YAML.rb will be included with Ruby. I don't plan
on doing anymore development on the module outside of the Ruby
distribution.  (Except to say that I will have a package available for
integration with pre-1.8 Ruby.)

I am also passing this message on to the YAML-Core list, as I'm sure
many will enjoy reading about your evangelism.

Wonderful news about OSCON.  Gluck,

_why

Richard Kilmer (address@hidden) wrote:
Why,

We are, as you know, totally sold on YAML for FreeRIDE plugin
configuration data.  The core of FreeRIDE is the FreeBASE plugin
manager.  That is really where YAML is used, and that directory
contains only eight files.  We are working to make FreeBASE a released
library in its own right (mainly for 'marketing' reasons ;-)  It will
be useful for anyone who wants a plugin-based application.  It will
also allow us to grow expertise in the Ruby community in writing
FreeBASE plugins (which in turn will work seamlessly under FreeRIDE).

The question is, the only third-party library we depend on right now is
yaml.rb.  Do you mind if we drop that file into our 'freebase'
directory and make it part of it?  In our code, that file will be
accessed through:

require 'freebase/yaml'

All appropriate copyrights, yada yada yada will be maintained, of
course with attribution to the yaml4r library and your expert
authorship.

Is this cool with you?

Thanks,

Rich

BTW:  I got a presentation accepted at O'Reilly's Open Source
Convention speaking on Ruby and FreeRIDE (and...of course...YAML)...so
that should be fun!

Also, I did training for a system I developed on a DARPA research
project that uses FreeBASE as the plugin framework, so I got to teach
folks how to edit YAML files...they all thought it was pretty cool.








reply via email to

[Prev in Thread] Current Thread [Next in Thread]