[openbeos] Re: Charter

["Ithamar R. Adema" <ithamar@xxxxxxxxx>]

Sounds great! Let's in principle call this Draft #1 ;-)

Only thing I see is that by stating you want to create an OpenSource BeOS 
clone, you remove the chance of saying that you only intended to
improve the existing BeOS if legal issues came up ;-)

Regards,

Ithamar.


At 16:52 18-8-2001 -0500, you wrote:

>Ok, so far no one seems real concerned about trademark issues. But keep
>this in mind -- legal departments for corporations don't give a poop
>about the little guys, they serve their master and do so very
>efficiently and aggressively if need be. This may never become a big
>issue, but... you've been warned!
>
>
>Here's another something to chew on:
>
>How about declaring some kind of Charter or Mission Statement? (I admit
>that I hate the sound of 'Mission Statement' because so many corps have
>them and they are always total bullshit)
>
>Basically, this is a declaration of what the project is about, it's
>goals, requirements, etc. Sure would be nice for everyone to be on the
>same wave length, ya know?
>
>Here's my sketch of a possible Charter (assuming the 'openBeOS' name
>doesn't get us sued):
>
>
>OpenBeOS Charter
>------------------------------
>
>Description:
>OpenBeOS is an open source implementation of the BeOS operating system.
>
>Mandate:
>To provide complete source and binary compatibility for all
>applications written for BeOS R5. This means that:
>a) any application that runs on BeOS R5 can be run unaltered on
>OpenBeOS
>b) any source code that compiles and runs on BeOS R5 can be compiled
>and run unaltered on OpenBeOS
>
>Architectures:
>The first goal is to achieve the Charter Mandate on intel x86
>platforms. This may be followed by other machine architectures in the
>future.
>
>Design:
>OpenBeOS will implement the entire BeOS R5 API. This API can be
>extended over time, but will alway retain
>backwards compatibility. The BeBook and other documentation from Be
>Inc. will serve as the official guideline for the OpenBeOS API. As
>extensions are made, the documentation will be updated to reflect this.
>
>Source Code:
>The OS kernel is written in C. All remaining source code is written in
>C++ and complies with the OpenTracker guidelines.
>
>
>
>
>
>Obviously this isn't very complete, but it's a start. I mean, you've
>got to get people to agree on what they're trying to do if there's
>going to be any progress. Thoughts?

Ithamar R. Adema
Information Engineering Associates Ltd
http://www.ieadev.com

• References:
  • [openbeos] Charter
    • From: Daniel Reinhold

Other related posts:

[openbeos] Charter

[openbeos] Re: Charter