Lesson plan
Michael Meeks (software developer)
Michael Meeks is a British software developer. He is primarily known for his work on GNOME, OpenOffice.org and now LibreOffice . He has been a contributor to the GNOME project for a long time working on its infrastructure and associated applications, particularly CORBA, Bonobo, Nautilus and GNOME accessibility. He has worked at Novell, SuSE and then Collabora. Meeks is a free software hacker who has contributed a lot of time to decreasing program load time. He created the direct binding, hashvals, and dynsort implementations for GNU Binutils and glibc. Most of this work was focused at making OpenOffice.org and now its fork LibreOffice start faster, and was later subsumed into the "-hash-style=gnu" linking optimization. He supports LibreOffice and Evolution as the free software solutions for document editing and groupware. Meeks is a Christian, which he says made him think about the moral aspects of his own illegal use of non-free software and converted him finally to free software.
Article summary
Michael Meeks is a British software developer. He is primarily known for his work on GNOME, OpenOffice.org and now LibreOffice . He has been a contributor to the GNOME project for a long time working on its infrastructure and associated applications, particularly CORBA, Bonobo, Nautilus and GNOME accessibility. He has worked at Novell, SuSE and then Collabora. Meeks is a free software hacker who has contributed a lot of time to decreasing program load time. He created the direct binding, hashvals, and dynsort implementations for GNU Binutils and glibc. Most of this work was focused at making OpenOffice.org and now its fork LibreOffice start faster, and was later subsumed into the "-hash-style=gnu" linking optimization. He supports LibreOffice and Evolution as the free software solutions for document editing and groupware. Meeks is a Christian, which he says made him think about the moral aspects of his own illegal use of non-free software and converted him finally to free software.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.