Groklaw

Groklaw was an online legal-news publication and research community focused on issues affecting free and open-source software. Pamela Jones, a paralegal who initially wrote under the name “PJ,” began the project as a law blog on May 16, 2003. Its name came from “grok,” a term associated with deep or intuitive understanding, reflecting the site's aim of helping lawyers and technically minded readers understand one another's fields. The site's earliest articles addressed disputes involving file sharing, copyright, and software litigation. Its second post examined the SCO Group's lawsuit against IBM, a case that became the central subject of Groklaw's work. SCO, formerly Caldera Systems, claimed that IBM had misappropriated Unix-related intellectual property in Linux and sought to impose legal and commercial pressure on Linux users and distributors. Groklaw followed the case closely, explaining pleadings, hearings, discovery disputes, ownership questions, and technical evidence for a broad readership. It also examined related litigation involving Novell, DaimlerChrysler, AutoZone, and Red Hat. Groklaw's distinctive model combined legal commentary with volunteer technical research. Jones translated legal developments into accessible language, while programmers, historians, lawyers, and other readers supplied information about Unix history, operating-system development, source-code practices, standards, and intellectual-property law. This collaborative approach helped the publication investigate claims that were difficult to evaluate from legal documents alone. The site's articles and comments were generally sympathetic to Linux and free software and skeptical of what its community described as fear, uncertainty, and doubt, or FUD, directed at open-source projects. The project expanded beyond daily reporting. Grokline assembled a historical timeline concerning Unix ownership and intellectual property, while Grokdoc sought to produce accessible Linux documentation for new users. Groklaw also covered software patents, the Digital Millennium Copyright Act, digital rights management, open standards, the drafting of version 3 of the GNU General Public License, Microsoft's efforts to standardize Office Open XML, and Oracle's claims concerning Google's use of Java-related technology in Android. The site became influential among journalists, lawyers, developers, and open-source advocates. It received recognition from organizations and publications including the Electronic Frontier Foundation, the Free Software Foundation, Google and O'Reilly's open-source awards, the American Bar Association Journal, and the Library of Congress web-archiving program. Its reporting was also cited in legal scholarship and used as a reference point in coverage of the SCO litigation. Groklaw entered a consolidation phase in 2009, concentrating on preserving and organizing its accumulated legal history. Jones announced in April 2011 that new publication would end on the site's eighth anniversary because the original mission concerning the SCO lawsuits had largely been fulfilled. Mark Webbink became editor, and Jones later resumed an editorial role after new patent and copyright disputes involving Android revived the need for coverage. The final major article appeared on August 20, 2013. Jones said that pervasive government surveillance had undermined the privacy required for the site's collaborative work and that she could no longer continue under those conditions. The domain and portions of the archive remained intermittently accessible for years. The site was reported as unavailable or unstable at various times, and later domain-status changes made access and continuity uncertain. Groklaw is therefore best understood as a defunct or dormant web publication whose historical archive and collaborative research remain significant to the history of open-source legal advocacy and technology journalism.

Groklaw began on May 16, 2003, when Pamela Jones created a law blog intended to make technology-related legal developments understandable to people in the software community. Jones had legal training as a paralegal but was not a programmer, while many of the site's readers had extensive technical knowledge. The publication's central method emerged from this difference: Jones interpreted legal documents and proceedings, and readers contributed technical explanations, historical evidence, and source-code analysis. The first article discussed the Grokster file-sharing litigation and contrasted it with the earlier Napster case. The second article, published the next day, addressed the SCO Group's lawsuit against IBM. That dispute quickly became the site's defining subject. SCO argued that IBM had improperly contributed Unix-related material to Linux and pursued claims involving copyrights, contracts, and trade secrets. Groklaw tracked the case document by document and explained its implications for Linux developers, distributors, businesses, and users. As readership expanded, the project moved beyond its original blogging platform. On November 22, 2003, an independent Groklaw website went online, hosted by ibiblio and built with Geeklog. The site developed into a substantial community publication, with volunteer participants attending hearings, locating historical documents, interviewing figures in the software and legal industries, and discussing technical questions relevant to court proceedings. Its work covered Linux development practices, C programming, operating-system history, standards organizations, intellectual-property law, and the provenance of Unix code. Groklaw's coverage broadened as the SCO controversy developed. It discussed SCO's cases involving IBM, Novell, DaimlerChrysler, and AutoZone, as well as Red Hat's litigation and the broader commercial effects of threats against Linux users. It also examined Microsoft's intellectual-property assertions concerning Linux, software patents, the DMCA, digital-rights management, open standards, and the development of GPLv3. The site reported on Microsoft's campaign to secure international standardization for Office Open XML and later covered Oracle's litigation against Google concerning Java technology used in Android. The project spawned related initiatives. Grokline researched and presented a timeline of Unix ownership and intellectual-property history. One important result was the publication of a previously sealed 1994 settlement from USL v. BSDi, obtained through a California public-records process involving the University of California. Grokdoc, launched in 2004, pursued a separate goal of creating clear documentation for people new to Linux. Groklaw also published historical material about Unix, GNU, and Linux and provided a venue for detailed discussion of free-software legal policy. Its editorial position was openly favorable to free and open-source software and opposed to what its contributors characterized as FUD. This orientation made Groklaw a valuable resource for readers seeking an alternative to corporate statements and conventional technology reporting, but it also made the site a target for criticism. In 2005, a Linux publication ran a controversial attempt to identify Jones, accompanied by alleged personal information. The publisher later issued an apology after complaints and advertiser pressure. SCO executives also suggested that Jones worked for IBM and questioned the site's legitimacy; Jones and IBM denied the allegation. These disputes became part of the wider media and legal controversy surrounding the SCO cases. Groklaw gained recognition for making complicated cases accessible and for the depth of its collaborative research. It received awards and honors from the Electronic Frontier Foundation, the Free Software Foundation, open-source award programs, technology publications, and the American Bar Association Journal. The Library of Congress selected it in 2010 for a web-archiving project focused on legal blogs. In January 2009, Groklaw entered a second phase centered on cleaning up and preserving its legal history. In April 2011, Jones announced that new articles would end on May 16, the site's eighth anniversary, because the publication had fulfilled its original objective of documenting the SCO lawsuits. Mark Webbink was named editor, but Jones later returned to editorial work after new patent and copyright disputes involving Android. On August 20, 2013, the site published its final article. Jones explained that mass online surveillance made the confidential collaboration required by Groklaw impossible. The archive's later availability was inconsistent. Parts of the website remained accessible at some points, while the domain was reported as intermittently unavailable and later redirected or displayed unrelated content. Regardless of its later technical condition, Groklaw remains historically important as an early example of collaborative online legal journalism, a major source of public research on the SCO-Linux disputes, and a meeting point between lawyers, programmers, historians, and open-source advocates.

• 2013

  Publication ends

  [1]Groklawen.wikipedia.org

  Groklaw's final major article cites online surveillance and the loss of privacy needed for collaborative work.

• 2011

  Editorial transition announced

  [1]Groklawen.wikipedia.org

  Jones announces an end to daily publication and identifies Mark Webbink as the new editor.

• 2010

  Selected for Library of Congress web archiving

  [1]Groklawen.wikipedia.org

  The site is selected in the Library of Congress web-archiving program's legal-blog category.

• 2009

  Second phase focuses on preservation

  [1]Groklawen.wikipedia.org

  Groklaw shifts toward consolidating and cleaning up its accumulated legal-history archive.

• 2004

  Grokline and Grokdoc projects begin

  [1]Groklawen.wikipedia.org

  Related projects address Unix ownership history and accessible Linux documentation.

• 2003

  Groklaw is founded

  [1]Groklawen.wikipedia.org

  Pamela Jones launches Groklaw as a law blog covering legal issues relevant to technology and free software.

• 2003

  Standalone site goes online

  [1]Groklawen.wikipedia.org

  The growing publication moves from Radio UserLand to a standalone ibiblio-hosted website using Geeklog.

A community-supported, pro-free-and-open-source legal-information publication that translated complex technology disputes into accessible explanations and combined legal analysis with technical investigation.

• Online legal journalism · 2003

  Groklaw legal-news articles

  The site's principal offering was a continuing body of articles explaining lawsuits, intellectual-property disputes, standards controversies, and policy questions affecting Linux and other free and open-source software. Articles combined plain-language legal interpretation with technical context and links to primary documents.

• Legal and technical research project · 2004

  Grokline

  Grokline was a research initiative that organized the history of Unix ownership and related intellectual-property claims. Its work helped document the chain of ownership and transactions relevant to disputes surrounding Unix and Linux.

• Linux documentation · 2004

  Grokdoc

  Grokdoc was intended to produce practical, clear documentation for new Linux users. It extended Groklaw's educational mission from legal explanation into user-oriented open-source documentation.

• 2005

  Attempted identification and exposure of Pamela Jones

  A Linux publication attempted to identify the previously anonymous Groklaw editor and published alleged personal information, including purported contact details and an image said to show her home. The publisher later apologized after complaints and advertiser pressure. The episode became a prominent controversy surrounding Groklaw's privacy and editorial independence.

  Source

• 2005

  Dispute over alleged IBM affiliation

  SCO representatives publicly suggested that Jones or Groklaw worked for IBM. Jones denied the allegation, and IBM also denied it in a court filing. The claims were part of a broader campaign of criticism directed at the site's coverage of SCO's litigation.

  Source

Read more

• 2004Grokline Unix ownership research

  International online audience

  Grokline assembled historical evidence concerning Unix ownership and intellectual-property transfers, including a previously sealed USL v. BSDi settlement.

  Outcome. The published material clarified parts of the historical record used in debates over Unix and Linux rights.

  Source
• 2003SCO-Linux litigation coverage

  International online audience

  Groklaw built its reputation through sustained reporting and collaborative analysis of SCO's litigation against IBM and related claims involving Linux, Unix copyrights, contracts, and alleged code misappropriation.

  Outcome. The coverage became the site's defining body of work and contributed to public understanding of the technical and legal issues in the cases.

  Source

• 2013

  Publication discontinued because of surveillance concernsStrategy

  Background

  Jones said that pervasive monitoring had undermined the privacy necessary for readers to collaborate on sensitive legal and technical subjects.

  Action taken

  Groklaw stopped publishing major new material after its August 20, 2013 article.

  Aftermath

  The publication became an archive rather than an active news community, with later access to the domain and content becoming inconsistent.

  Source

• 2011

  End of daily publication announcedStrategy

  Background

  Jones concluded that Groklaw had largely fulfilled its original mission of documenting the SCO lawsuits.

  Action taken

  She announced that new articles would stop on the site's eighth anniversary and transferred editorial responsibility to Mark Webbink.

  Aftermath

  Jones later resumed editorial involvement when new patent and copyright disputes involving Android created fresh concerns for the open-source community.

  Source

• 2009

  Shift toward archival consolidationStrategy

  Background

  After years of reporting on the SCO litigation and related disputes, Groklaw sought to preserve and organize its accumulated legal research.

  Action taken

  The site entered a second phase focused on cleanup, consolidation, and historical documentation rather than only current reporting.

  Aftermath

  The change reinforced Groklaw's role as a reference archive for open-source legal history.

  Source

1. 1Groklawen.wikipedia.org