savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of The OpenCookBook - savannah.gnu.org


From: David Grant
Subject: Re: [Savannah-hackers] submission of The OpenCookBook - savannah.gnu.org
Date: Sat, 11 Sep 2004 21:21:06 -0700
User-agent: Mozilla Thunderbird 0.7.3 (X11/20040812)

Elfyn McBratney wrote:

Hi,

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

On Sat, Sep 11, 2004 at 05:21:03AM -0400, address@hidden wrote:
A package was submitted to savannah.gnu.org
This mail was sent to address@hidden, address@hidden


David Grant <address@hidden> described the package as follows:
License: fdl
Other License: Package: The OpenCookBook
System name: opencookbook

Savannah's mission is to host free software projects, and we want the public
to think of them as free software projects.  A project name that says "open"
will tend to lead people to think of the project as "open source" instead of
"free software".

We would be glad if you accept to use "free" instead of "open" in your
project name.
Sorry. Ok, let's call it "The FreeCookBook", and the system name will be "freecookbook".

Type: GNU

Your project is not part of the GNU project, so we cannot accept its current
type.  We want to maintain the distinction between 'GNU' and 'non-GNU'
projects. If your project is approved for inclusion into Savannah, we will
set its type to 'non-GNU'.

If your project is accepted into the GNU project you may change its type.
You can do this by asking us.
Sorry about that. I must not have been thinking when I answered the type question.

Description:
I am not sure if you guys support this kind of project, but I think it is
an interesting and very useful one.  There are some free recipe websites
out there but often I find there are just TOO many recipes.  Other
websites like allrecipes.com make people pay to see certain recipes.

The goal is to create a free open-source cookbook (of food recipes) using
an amazing (but simple) latex class called 'cooking' by Axel Reichert.
This class has a great way of structuring the recipe layout which you can
see in the source code I provided.

Note that Savannah supports projects of the Free Software movement, not
projects of the Open Source movement.

We are careful about ethical issues and insist on producing software that is
not dependent on proprietary software.

While Open Source as defined by its founders means something pretty close to
Free Software, it's frequently misunderstood.  For more information, see
http://www.gnu.org/philosophy/free-software-for-freedom.html.

Understood. I'm moderately aware of the OSS and Free Software movement and their philosophies.

The cookbook would contain many recipes.  Initially, the cookbook would
contain almost any recipe.  Recipes would be decided upon by the developers
whether or not to include them.  Identical recipes would be merged so as to
find the ultimate recipe.  For example, unless two recipes for spaghetti
sauce differ significantly, the two recipes will be combined, taking the
best of each to make the best recipe.  This cookbook will start off as
being the best of the best, only the best recipes out there.  Eventually
as the project expands I would like to have several cookbooks branch off
into a desert-only cookbook, a vegetarian-only cookbook, a main course-only
cookbook, and so on.  This is easily achieved by using \inlude statements,
to include recipes of certain types.  Using latex as the processing system
gives us a lot of flexibility, especially with regards to changing the
output format of the recipes later.

The source code of my cookbook is here.
http://www.davidgrant.ca:81/myCookbook.tar.gz   I have many more that I

In order to release your project properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the
title page of each work.
Yes, I was planning to add this so that it comes up on the 2nd page of each document when compiled to dvi, ps, or pdf. Additionally I was going to place a GPL header on each .tex source file (unless this is not strictly necessary, but I'm pretty sure it is as many other free projects do this).

In addition, if you haven't already, please copy a copy of the plain text
version of the FDL, available from http://www.gnu.org/licenses/fdl.txt, into
a file named "COPYING".
Right, I'll do that.

Additional instructions are available from
http://www.gnu.org/licenses/fdl.html.

want to add but I need a place on the web to store them, and which allows
others to share and add easily through CVS, which usually works pretty
good for Latex, but will work better for recipes, where less information
is stored per line, than with usual Latex documents.

I have one person on the internet who also uses the latex cooking class and
is willing to help contribute some recipes to get us started.

Other Software Required:
latex (tetex for linux or miktex for windows, for example)
cooking package for latex

"Linux" is just a kernel of a more complex system that we like to refer to as
GNU/Linux, to emphasize the ideals of the Free Software movement.

For more information, see http://www.gnu.org/gnu/linux-and-gnu.html.
Sorry, I should have said GNU/Linux, my bad. I will have to get into the habit of doing that now.

Other Comments:
If you reject, can you please communicate to me if there is any way I can
change it in order to make it acceptable or explain your reasons.

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.

I will provide you with an updated tarball URL once I have read the documentation on how to comply with the license fully and have made ALL the changes.

Thanks,

David

Regards,



--
David J. Grant
http://www.davidgrant.ca:81

Attachment: david.grant.vcf
Description: Vcard


reply via email to

[Prev in Thread] Current Thread [Next in Thread]