Summary

  • Bunyip Information Systems marketed Archie as a commercial product from October 1992, charged Archie sites licence and support fees, and was named registered owner of the ARCHIE trademark in Canada on 2 December 1994.
  • Nothing in the six inspected documents shows McGill University transferring the service, the software rights or the name, and Alan Emtage's own January 1994 announcement said individual volunteer sites owned and operated their Archie servers.

The status report that dates the sale

The cleanest date in the file comes from a document with no commercial interest in the answer. RFC 1689, a status report on networked information retrieval published in August 1994, states that "the archie system became a commercial product in October, 1992, marketed by Bunyip Information Systems Inc." (printed p. 20; RFC 1689). The same report, a few pages earlier, lists software licensing and sponsored development contracts among Archie's funding sources (printed p. 17), which is a plain admission that the money came from customers, not from a research grant. Later in the document Bunyip appears as the supplier of Archie server software, with its commercial implementation described as replacing the McGill project version (printed pp. 20–21).

A 1993 Internet Business Journal account supplies the corporate chronology that RFC 1689 leaves out. It dates the formation of Bunyip by Peter Deutsch and Alan Emtage to January 1992 and the availability of the commercially supported rewrite to October 1992, then says it without decoration: "Currently, all of the Internet's archie sites pay the license and support fees." (Internet Business Journal, 1993). Note what that sentence is and is not. It is business reporting, not a licence instrument, and it supplies no formation day, no transfer date and no name-assignment clause. The operator paid. The searches stayed free to the person typing the query. That distinction is the whole commercial model in one line, and it is the model the earlier BTW reporting on Archie described from the user side rather than the contract side.

Who actually owned a server

The most useful sentence in the whole record comes from the founder himself, in a public announcement of 19 January 1994 preserved in the W3C archives. Emtage identifies McGill as the origin of the Archie server software and Bunyip as the organization then providing continued support — and then writes that "each archie server is owned and operated by individual volunteer sites around the Internet" (announcement, 19 January 1994).

That single line dismantles the tidier story in which a company simply took the machine over. Bunyip supplied software and support; the servers belonged to the sites running them. The same message promises a free Gopher-index upgrade to existing servers and supplies no general redistribution licence for the software, which is consistent with a support-and-licence business rather than a giveaway.

A 2005 National Academies chapter puts it more loosely, calling Bunyip "the company that took over operation of the Archie service" (printed p. 296, section 6.2.1; Signposts in Cyberspace). It is a retrospective description, and it reproduces no contractual instrument, no takeover date and no licence condition. It also dates Archie's first release to 1989, while the Savetz account dates the initial listing scripts to June 1990. Both datings stand in the record as given. Neither establishes when custody changed, because neither is about custody.

The contemporary technical literature agrees with the support framing rather than the ownership one. RFC 1580, published in March 1994, credits Alan Emtage, Peter Deutsch and Bill Heelan at McGill with developing Archie and states that "now archie is supported by Bunyip Information System Inc., Canada" (printed pp. 37–38; RFC 1580). Supported. Not assigned.

The name on the registry

If the software's title was murky, the name was not. The Canadian Intellectual Property Office record names Bunyip Information Systems Inc. as registered owner of the ARCHIE trademark for computer programs, filed 23 September 1993 and registered 2 December 1994 (CIPO record 0737622). The displayed record does not identify an assignment from McGill; registration is a fact about the register, not about the transaction that preceded it.

The same page carries two details worth reading slowly. A security-agreement entry dated 19 January 1999 names the Royal Bank of Canada, which tells you the mark was collateral for a lender without telling you anything about software licence terms. And the action history records expungement for failure to renew on 15 July 2010 — the name outlived the company's diligence by a decade and a half, then lapsed for want of a filing fee.

One anomaly belongs in the text rather than in a footnote. The Claims field states Canadian use of the mark as early as 1980, which predates every development chronology in this file. It is reported here as the field displays it, and it is not used to date anything.

What the record does not contain

Six documents, and not one of them is an assignment, a purchase agreement or a written licence instrument for the Archie server software or the name. That absence is a fact about the inspected record, not a finding that no agreement existed; a transaction of this kind would plausibly have lived in a university contracts office or a lawyer's file rather than on the open web.

The licence question stays open for a second reason. Two documents that could have carried copyright or distribution language could not be read: an Archie source-code file timed out when opened, and an archived TeX documentation file returned an unsupported media type. So the honest statement of the gap is narrow and specific: no general written redistribution grant for the commercial Archie server appears in the six sources read here, and the freeware and public-domain language quoted at RFC 1689 page 21 attaches to client programs rather than to the commercial server.

That is what a twenty-year custody trail looks like when nobody writes the memorandum. A commercialization date with a month but no day. A formation month with no day. A filing date, a registration date, an expungement date. And between McGill's project and Bunyip's price list, a hinge nobody documented in public — which is precisely the part a reader would want to hold someone to.