Re: [Openclips-development] Re: OpenCLIPS

[Glen M. <mc...@ne...>]

Hey Folks,

I downloaded the openclips source and had a look at the TODO file.=20
Looks great. Let's get cracking.

I'll get started on some of the more administrative stuff:
1) Identify the files with project name and license (well . . . I'll=20
sort out the license first)
2) Change all the documentation to refer to us
3) Create a basic webpage for http://openclips.sourceforge.net
4) Snag the urls "openclips.org" and "www.openclips.org" and point them=20=

to the sf site
5) Start reverse engineering the source

Thomas, will you look into the warnings and the headers? (The first two=20=

items on your TODO list). If anyone else on the list has time for an=20
action item please speak up.

Then we should be ready for a release!

I'm very much in favor of keeping the core engine in ANSI C so that it=20=

will be as portable as possible.

Let me know what you think.

Best Regards,
~Glen


On 21-Sep-04, at 9:25 AM, <ths...@po...> wrote:

> On Tue, 21 Sep 2004 07:27:05 -0700 Tim Cook wrote:
>  > The OpenCLIPS project has been approved on SourceForge.=A0 The=20
> relevant
>  > links are below.
>  About time :-) I've been getting sick of seeing "Invalid Project".
>
> > Thomas Sutton will be uploading the base source code that we will be
>  > starting from.=A0
> Done. It is in the openclips module under the projects cvsroot.
>
> The CLIPS source (version 6.22) is up with the test cases distributed=20=

> on
>  the ghg.net site (though they don't have a "real" testing framework
>  written yet). There are also some examples, also from somewhere on
> ghg.net. The test cases and examples I have included presuming that=20
> they
>  are provided under the same conditions as CLIPS itself but I haven't=20=

> checked.
>
> > Once the package has been verified that it installs and runs, I=20
> propose
>  > that the first order of business is to properly identify all files=20=

> with
>  > the project name and distribution license and immediately create a
>  > release of OpenCLIPS.
>
>  > Thoughts?
>  At the moment, the LICENCE document in CVS is a BSD-like licence (the
>  FreeBSD copyright notice s/FreeBSD/OpenCLIPS/) so I changed the=20
> projects
>  licence in the sf.net catagorisation, we can change it back later if
>  needed, but I'd prefer to keep OpenCLIPS as free as possible, in line
>  with the original CLIPS release into the public domain.
>
> There is also a brief TODO in CVS with a number of administrivia and=20=

> some
> preliminary cleanup work that we'll need to do. It should really be
>  expanded into a roadmap of some description. I think it would be wise=20=

> to
>  have a rough sketch of the future directions and a first release out
>  before announcing the project widely (e.g. on the CLIPS mailing=20
> lists).
>
> > Project Page:
>  > https://sourceforge.net/projects/openclips/
> > Mailing list:
>  > http://lists.sourceforge.net/lists/listinfo/openclips-development
>
> > Cheers,
>  > Tim
>
> Cheers,
>  Thomas Sutton
>
>
>
>
>
> -------------------------------------------------------
>  This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
>  Project Admins to receive an Apple iPod Mini FREE for your judgement=20=

> on
>  who ports your project to Linux PPC the best. Sponsored by IBM.
>  Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Openclips-development mailing list
>  Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openclips-development
>
> --
>  Incoming mail is certified Virus Free.
>  Checked by AVG Anti-Virus (http://www.grisoft.com).
>  Version: 7.0.271 / Virus Database: 264.9.4 - Release Date: 9/21/2004
> =A0