25:
FOLDOC under GNU FDL? Your question has thrown me into a quandary. I had not seen
Knowledge (XXG) before. It is so close in spirit and function to the new FOLDOC software I am working on that I am wondering whether I should continue with FOLDOC at all or whether I shouldn't just redirect all effort
16:
Received: from diver.doc.ic.ac.uk by mail.metrostate.edu; Fri, 24 Aug 2001 17:41:40 -0500 Received: from seagull.doc.ic.ac.uk ( ident=root) by diver.doc.ic.ac.uk with esmtp (Exim 3.16 #7) id 15aPe2-0003NC-00 for Axel.Boldt at obscured1.metrostate.edu; Fri, 24 Aug 2001 23:41:42 +0100 Received:
26:
to
Knowledge (XXG). Can you think of any reason to keep it seperate? In the short term, I am more than happy for you to add FOLDOC's content to Knowledge (XXG) and hereby release it under GNU FDL. -- Denis Howe <dbh at obscured5.doc.ic.ac.uk: -->
17:(from dbh at localhost) by seagull.doc.ic.ac.uk (8.9.3/8.8.8) id XAA18948; Fri, 24 Aug 2001 23:41:39 +0100 Date: Fri, 24 Aug 2001 23:41:39 +0100 Message-Id: <200108242241.XAA18948 at seagull.doc.ic.ac.uk: -->
21:(message from Axel Boldt on Tue, 21 Aug 2001 19:51:21 +0100) Subject: Re: Incorporate Foldoc content into Knowledge (XXG)? References: <200108211851.TAA27377 at seagull.doc.ic.ac.uk: -->
33:
18:
X-Authentication-Warning: seagull.doc.ic.ac.uk: dbh set sender to dbh at obscured2.doc.ic.ac.uk using -f From: Denis Howe <dbh at obscured3.doc.ic.ac.uk: -->
47:
41:
24:
entry would cause trouble. Would it be possible to get a version of : -->
23:
your requirement of presenting your copyright notice with every : -->
20:
In-reply-to: <200108211851.TAA27377 at seagull.doc.ic.ac.uk: -->
19:
To: Axel Boldt <Axel.Boldt at obscured4.metrostate.edu: -->
27:
Free On-Line
Dictionary of Computing http://www.foldoc.org/
34:
8:
7:
14:
1:
64:
48:Knowledge (XXG) copyright
55:
63:
62:
58:
57:
56:
54:
53:
52:
38:
37:
28:
12:
11:
5:
61:
59:
51:
50:
40:
39:
15:
13:
10:
9:
6:
4:
3:
2:
60:
49:
46:
45:
43:
36:
35:
32:
30:
29:
31:See also:
42:Category
22:: -->
44::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.