[Savannah-hackers] Re: submission of CRiX Operating System - savannah.nongnu.org

[Mathieu Roy]

Hi,

I'm evaluating the project you submitted for approval in Savannah.



address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Shawn Debnath <address@hidden> described the package as follows:
> License: mbsd
> Other License: Copyright (c) 2002, Shawn Debnath.
> 
> All rights reserved.
> 
> Redistribution and use in source and binary forms, with or without
> 
> modification, are permitted provided that the following conditions
> 
> are met:
> 
> 1. Redistributions of source code must retain the above copyright
> 
>    notice, this list of conditions, and the following disclaimer.
> 
> 2. Redistributions in binary form must reproduce the above copyright
> 
>    notice, this list of conditions, and the following disclaimer in the
> 
>    documentation and/or other materials provided with the distribution.
> 
> 3. The name of the author may not be used to endorse or promote products
> 
>    derived from this software without specific prior written permission.
> 
> THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
> 
> IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
> 
> OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
> 
> IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
> 
> INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
> 
> NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> 
> DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> 
> THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> 
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
> 
> THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> 
> Package: CRiX Operating System
> System name: crix
> Type: non-GNU
> 
> Description:
> CRiX  Operating System
> 
> Part of my undergraduate research at Purdue University. I am developing an 
> operating system that will provide real time support for multimedia 
> applications. I have already started on this project, and have written 
> significant code for it. You can take a look at it @ 
> http://p4.crix.org/cgi-bin/index.cgi 
> 
> The first release of CRiX has been set after the following  features have 
> been implemented:
> 
> * Boot - DONE
> 
> * Setup pre-kernel environment - DONE
> 
> * Load and execute kernel code - DONE
> 
> * Initialize virtual memory management - DONE
> 
> * Initialize interrupt handling and timer services - DONE
> 
> * Make basic kernel thread scheduling available. - IN WORKS
> 
> Although at its infancy, CRiX has a Solaris like virtual memory
> management system. The scheduler, which is currently being written,
> will provide simple round robin scheduling, but as the research
> progresses, it will be modified to improve efficiency, and
> reliability. Some features like execution profiling is planned for
> the first release of CRiX.


We do not host complete operating system. You may host here part of
the system (kernel, for instance) but not the whole thing in one
project.

Apart from that, you should, in your registration, include an (temporary) URL
pointing to the source code.  The description you gave when
registering will not be read by the general public. If you are still
concerned with privacy, however, you can forward the code to me by
email.

We wish to review your source code, even if it is not functional, to
catch potential legal issues early.  

For example, to release your program properly under the GPL you must
include a copyright notice and permission-to-copy statements at the 
beginning of every file of source code.  This is explained in
http://www.gnu.org/licenses/gpl-howto.html.  Our review would help
catch potential omissions such as these.


Please register your project once more with the changes
mentioned above.  

We cannot track projects that have been answered but not approved, so
we must ask you to register the project whenever you change the
registration. Make sure to apply all changes so you need to reregister
only once.

The re-registration URL found in our acknowledgement of your earlier
registration will direct you to the proper location.

Regards,



-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english