taskSavannah Administration - Tasks: task #4949, Submission of Pelican

 
 

task #4949: Submission of Pelican

Submitter:  -Deleted Account- <sebn>
Submitted:  Sat 19 Nov 2005 03:43:05 PM UTC
   
 
Should Start On:  Fri 18 Nov 2005 11:00:00 PM UTC Should be Finished on:  Sun 01 Jan 2006 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 19 Jun 2006 05:07:04 PM UTC, comment #6: 

Hello.

I had a short look at your source code and didn't find any problems for us... so we won't review your project again..

Have fun on Savannah.

Sebastian Wieseler <kickino>
Sun 20 Nov 2005 12:44:51 PM UTC, comment #5: 

Hi,

I have approved your project for inclusion in Savannah.

We will be reviewing the cvs code in a month (or better at your request) to check if the source files contain appropriate copyright notice and permission-to-copy statements at the beginning of every file of source code.
Our review would help catch potential legal issues early.

You should get an automated email with more information shortly.

Regards,

Sebastian Wieseler <kickino>
Sun 20 Nov 2005 12:39:11 PM UTC, comment #4: 

This is ok for me :)

-Deleted Account- <sebn>
Sun 20 Nov 2005 12:17:18 PM UTC, comment #3: 

Hi,

Your projects meets the Savannah requirements, except that we cannot review your source code yet.

We can approve it, and review the code in the near future (or better, at your request).
We will among other check if the source files contain appropriate copyright notice and permission-to-copy statements
at the beginning of every file of source code. Our review would help catch potential legal issues early.

If then the source code does not meet our requirements (for example, non-free dependencies),
we will then discuss the issue and possibly remove the project from Savannah.

Is this ok for you?

Sebastian Wieseler <kickino>
Sun 20 Nov 2005 02:31:46 AM UTC, comment #2: 

As said in the description, the project will use C++ and x86 assembly languages, and will be built using scons (which is written in Python).
So, needed tools are : cpp/g++, nasm (LGPL), and python 2.x (GPL compatible).

The project is a learning purpose kernel project, and will not rely on any external library to run (means no legal issues).
At the beginning, it should be tested using Bochs (LGPL) and GDB.

There is no code available for the moment.
Everything will be released under GPL/FDL.

Of course, no large files will be stored in the CVS repository. Needed files (harddisk binary images, for example) will be generated by build script (using bximage/fdisk/mkfs/grub).

The whole documentation will be written using DocBook/XML, translation files will be generated using xml2po, translators will use any PO compatible tool (gtranslator, kbabel, vim), output will be build using po2xml (Gnome), xsltproc (Gnome), and maybe tidy (W3C license).

I would like to have some online project presentation, and documentation available on website, and share source code (at least one other developer should join the project soon, if not rejected).

-Deleted Account- <sebn>
Sat 19 Nov 2005 07:29:38 PM UTC, comment #1: 

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


At first, we need a detailed technical description that specifies such requirements as programming languages and external libraries.


At second, please include a (perhaps 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.



At third, in order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the beginning of every file of source code.

In addition, if you haven't already, please include a copy of the plain text version of the GPL,
available from http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.
To learn why a copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.




At fourth, in order to release your project^Wdocumentation properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING' (http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.




And at last but not least, please notice that as mentioned in the registration pages, we do not host complete distros,
distros isos, packages repositories, etc, for space and bandwidth reasons.
We may just offer support for organisational purpose and in-house developed software (such as iso creation scripts).

How do you plan to use the Savannah services?

Regards,

Sebastian Wieseler <kickino>
Sat 19 Nov 2005 03:43:05 PM UTC, original submission:  

A new project has been registered at Savannah
The project account will remain inactive until a site admin approve or discard the registration.


######### REGISTRATION ADMINISTRATION #########

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific "Group Administration" page, accessible only to site administrators, effectively logged as site administrators (superuser):

  <https://savannah.nongnu.org/admin/groupedit.php?group_id=8136>


######### REGISTRATION DETAILS #########

Full Name:
----------
  Pelican

System Group Name:
-----------------
  pelican

Type:
-----
  non-GNU software &amp; documentation

License:
--------
  GNU General Public License V2 or later

Description:
------------
  The Pelican project will be an effort make OS development learning easier, by writing a simple, easy to understand kernel, and document it.

- The initial target plateform is x86 (used by a lot of people).
- The kernel will be written in C++ (object oriented) and asm.
- The project will try to provide various implementations for the kernel architecture and functionalities, in order to ease the experimentation process.
- The kernel API will be documented with some automated documentation tool.
- A lot of documentation (installation manual, contributors manuals , technical articles) will be written (DocBook/XML), translated (using xml2po, po2xml, and gtranslator) in as many languages as possible (starting with english and french), and generated in various output formats (XHTML/PS/PDF) using XSLT.
- The project will use the SCons build tool.
- Source code will be released under the GPL licence. Documentation will use the FDL.
- The project will need a website.


Other Software Required:
------------------------
  To build the project, people must have :
- A Gnu build environment (gcc, binutils, gdb).
- The Grub, with its multiboot check tool.
- The Bochs emulator.
- The SCons build tool (and a typical python environment).
- A DocBook environment (DTDs, stylesheets, xsltproc, xml2po, po2xml).
- The (unknown) automated source code documentor.


-Deleted Account- <sebn>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 8 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-06-19 kickino CategoryApproved Projects to be Reviewed Project Approval
    StatusNone Done
    Open/ClosedOpen Closed
2005-11-20 kickino Should be Finished on2005-11-28 2006-01-01
2005-11-20 kickino CategoryProject Approval Approved Projects to be Reviewed
    StatusNeed Info None
2005-11-19 kickino StatusNone Need Info
    Assigned toNone kickino

Back to the top

Powered by Savane 3.13-02a9.
Corresponding source code