taskSavannah Administration - Tasks: task #3659, Submission of The FreeType Project

 
 

task #3659: Submission of The FreeType Project

Submitted by:  Werner LEMBERG <wl>
Submitted on:  Tue 18 Jan 2005 11:45:30 PM UTC  
 
Should Start On: Thu 20 Jan 2005 12:00:00 AM UTCShould be Finished on: Thu 20 Jan 2005 12:00:00 AM UTC
Category: Approved Projects to be ReviewedPriority: 5 - Normal
Status: Wait replyPrivacy: Public
Percent Complete: 0%Assigned to: Alex Fernandez <alexfernandez>
Open/Closed: OpenEffort: 0.00

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Thu 30 Jun 2011 11:14:17 PM UTC, comment #6:

Hi,

There are some issues pending from the project registration
process. Is the project in Savannah ready for review?

Thanks!

Alex Fernandez <alexfernandez>
Site AdministratorIn charge of this item.
Sun 21 Nov 2010 10:30:04 PM UTC, comment #5:

Hi,

There are some issues pending from the project registration
process. Is the project in Savannah ready for review?

Thanks!

Alex Fernandez <alexfernandez>
Site AdministratorIn charge of this item.
Sun 05 Jun 2005 03:26:26 PM UTC, comment #4:

[Please use the tracker to reply]

> We are still waiting for an answer from the FSF lawyers regarding
> compatibility of the FreeType license with the GPL :-(


Ok, we'll look at the code later then.

> > You should also add notices to the documentation. We recommend the
> > GFDL for this kind of work.
>
> For simplicity and easier updating I'll refer to the same
> dual-licensing stuff currently. This will change as soon as we
> receive a definite answer from the lawyers.


Ok.

> BTW, are the Debian people already accepting GFDL?


Sebastian tells me he didn't hear of any progress.
Why they activate the non-free repository by default yet do not accept the GFDL is beyond me :/

> Hehe, many national patent agencies have approved software patents
> inspite of not being allowed to do that. Additionally it is next to
> useless to develop software which can't be used in the USA legally...


RMS recently told me "It is silly to give more power to patents by cowering in fear of them even when they are not being enforced.". I think it is good to make clear those patents are not enforceable at the moment in Europe. As for me I only discovered recently that I could legally create GIFs, because somebody pointed me France doesn't accept software patents. I don't think I would help fighting legalization of software patents if I believed they were already in place :)

Sylvain Beucler <Beuc>
Sat 04 Jun 2005 09:22:49 AM UTC, comment #3:

As promised I'm reviewing at the source code now - abeilt 3 months 1/2 later than expected :)

What did you decide wrt dual licensing eventually? Your notices point to a "LICENSE.TXT" file. I found a "license.txt" which mention dual-licensing.

Several files lack copyright and license notices. Please update this files.

You should also add notices to the documentation. We recommend the GFDL for this kind of work.
Here are the standard instructions:
In order to release your project properly and unambiguously under the GFDL, 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.

Last, you might want to rephrase a part of PATENTS.
"BE IT IN COMMERCIAL OR OPEN SOURCE PRODUCTS."
to
"BE IT IN PROPRIETARY OR FREE SOFTWARE PRODUCTS."
I suppose you know the following texts:
http://www.gnu.org/philosophy/words-to-avoid.html#Commercial
http://www.gnu.org/philosophy/free-software-for-freedom.html

Incidentally why does those patents make legal issues in France at the moment? Were software patents already legal here in 1999?

Please contact us with this tracker asap, when you have an updated CVS repository ready.

Regards.

Sylvain Beucler <Beuc>
Thu 20 Jan 2005 10:21:40 PM UTC, comment #2:

Ok, I approve the project using the "no source code" procedure; that means we provide you an account and will check if everything is ok within one month.

You will receive a mail notification shortly.

-------

> 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.


We will do that, of course. Currently, we don't have CVS access
(since the machine is broken), so it would be optimal for us if you
can install the CVS tarballs as-is on savannah without public access,
and that only David and I can modify files in the CVS until the
project is in good shape.

Is this possible?

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


Actually, the otlayout directory is dead code and will be removed
soon...

Sylvain Beucler <Beuc>
Thu 20 Jan 2005 05:59:24 PM UTC, comment #1:

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.

Sylvain Beucler <Beuc>
Tue 18 Jan 2005 11:45:30 PM UTC, original submission:

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:
---------------

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

Werner LEMBERG <wl>

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by alexfernandez (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 11 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 02 Dec 2010 10:52:28 PM UTCalexfernandezStatusIn Progress=>Wait reply
    Sun 21 Nov 2010 10:30:04 PM UTCalexfernandezStatusNone=>In Progress
      Assigned toBeuc=>alexfernandez
    Sun 05 Jun 2005 03:26:26 PM UTCBeucCategoryProject Approval=>Approved Projects to be Reviewed
      StatusWait reply=>None
    Sat 04 Jun 2005 09:22:49 AM UTCBeucCategoryApproved Projects to be Reviewed=>Project Approval
      StatusNone=>Wait reply
    Thu 20 Jan 2005 10:21:40 PM UTCBeucCategoryProject Approval=>Approved Projects to be Reviewed
    Thu 20 Jan 2005 07:38:04 AM UTCBeucShould Start On-=>Thu 20 Jan 2005 12:00:00 AM UTC
      Should be Finished on-=>Thu 20 Jan 2005 12:00:00 AM UTC
      Assigned toNone=>Beuc

    Back to the top


    Powered by Savane 3.1-cleanup