[Savannah-register-public] [task #3659] Submission of The FreeType Project

[Sylvain Beucler]

This is an automated notification sent by Savannah.
It relates to:
                task #3659, project Savannah Administration

==============================================================================
 LATEST MODIFICATIONS of task #3659:
==============================================================================

               Posted by: Sylvain Beucler <Beuc>
               Posted on: 2005-01-20 17:59 (Europe/Paris)
    _______________________________________________________

Follow-up Comment:
Hi,



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



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.



Additional instructions are available from
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, go
to

http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude



Since you are dual-licensing, here is the recommanded notice:



     Copyright (C) year1, year2  CopyrightHolder1

     Copyright (C) year3, year4  CopyrightHolder2

     ...



     You may copy, modify, and redistribute this file under the terms

     of the GNU General Public License version 2 (or, at your option,

     any later version), and/or the FreeType License.



     [standard GPL notice]



     [standard FreeType notice]





You may need to update the notice to refer to the approriate file names that
contain the licenses (I see you added them in docs/).



You can take this opportunity to add some missing notices (for example, in
src/otlayout) :)





Also, some of the documentation files are big and non-trivialm, and should
carry copyright and license notices as well. We recomment the GDFL for
these.





If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project.  Upon review, we will
reconsider your project for inclusion in Savannah.



Regards.



==============================================================================
 OVERVIEW of task #3659:
==============================================================================

URL:
  <http://savannah.gnu.org/task/?func=detailitem&item_id=3659>

                 Summary: Submission of The FreeType Project
                 Project: Savannah Administration
            Submitted by: wl
            Submitted on: mar 18.01.2005 à 23:45
         Should Start On: jeu 20.01.2005 à 00:00
   Should be Finished on: jeu 20.01.2005 à 00:00
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: Beuc
             Open/Closed: Open
                  Effort: 0.00

    _______________________________________________________



Site Admin. Approval/Edition URL:
 <https://savannah.gnu.org/admin/groupedit.php?group_id=7246>


###### ORIGINAL SUBMISSION DETAILS ######

System Group Name:
-----------------
  freetype


Full Name:
----------
  The FreeType Project
  

Type:
-----
  non-GNU


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


Other License: 
--------------
  FreeType is dual-licensed with another free license

specific to FreeType (which has an advertising clause

and is thus incompatible to the GPL).


Description:
------------
  FreeType 2 is a software font engine that is designed to be small,

efficient, highly customizable and portable while capable of

producing high-quality output (glyph images). It can be used in

graphics libraries, display servers, font conversion tools, text

image generation tools, and many other products as well.



Note that FreeType 2 is a font service and doesn't provide APIs to

perform higher-level features, like text layout or graphics processing

(e.g. colored text rendering, "hollowing", etc.). However, it greatly

simplifies these tasks by providing a simple, easy to use and uniform

interface to access the content of font files.



FreeType 2 is released under two open-source licenses: our own

BSD-like FreeType License and the GPL.



By default, FreeType 2 supports the following font formats:



    * TrueType fonts (and collections)

    * Type 1 fonts

    * CID-keyed Type 1 fonts

    * CFF fonts

    * OpenType fonts (both TrueType and CFF variants)

    * SFNT-based bitmap fonts

    * X11 PCF fonts

    * Windows FNT fonts

    * BDF fonts (including anti-aliased ones)

    * PFR fonts

    * Type42 fonts (limited support)




Other Software Required:
------------------------
  


Other Comments:
---------------
  

#########################################


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: jeu 20.01.2005 à 17:59        By: Sylvain Beucler <Beuc>
Hi,



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



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.



Additional instructions are available from
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, go
to

http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude



Since you are dual-licensing, here is the recommanded notice:



     Copyright (C) year1, year2  CopyrightHolder1

     Copyright (C) year3, year4  CopyrightHolder2

     ...



     You may copy, modify, and redistribute this file under the terms

     of the GNU General Public License version 2 (or, at your option,

     any later version), and/or the FreeType License.



     [standard GPL notice]



     [standard FreeType notice]





You may need to update the notice to refer to the approriate file names that
contain the licenses (I see you added them in docs/).



You can take this opportunity to add some missing notices (for example, in
src/otlayout) :)





Also, some of the documentation files are big and non-trivialm, and should
carry copyright and license notices as well. We recomment the GDFL for
these.





If you are willing to make the changes mentioned above, please provide us
with an URL to an updated tarball of your project.  Upon review, we will
reconsider your project for inclusion in Savannah.



Regards.










==============================================================================

This item URL is:
  <http://savannah.gnu.org/task/?func=detailitem&item_id=3659>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/