Initial Announcement of The GNOME Project 1997

Bismillahirrahmanirrahim.

https://mail.gnome.org/archives/gtk-list/1997-August/msg00123.html

I copied here some first lines from that page:

  • From: Miguel de Icaza <miguel nuclecu unam mx>
  • To: gtk-list redhat com, kde fiwi02 wiwi uni-tuebingen de, guile cygnus com
  • Subject: The GNOME Desktop project.
  • Date: Fri, 15 Aug 1997 22:19:34 -0500

  		       The GNOME Desktop project
   	        (GNU Network Object Model Environment)
		http://bananoid.nuclecu.unam.mx/gnome

 

End of copying.

Windows 10 License Restrictions On The Users

Bismillahirrahmanirrahim.

Ade Malsasa Akbar <teknoloid@gmail.com>

I am not a lawyer, and here I act only as a regular computer user that just mentioning texts from Microsoft Windows 10 license. This article lists the restrictions on the users from Windows 10 license (retail or oem). In other words, this article collects what you are forbidden to do towards Windows according to Windows 10 license. I try to show the restrictions as many as possible here but not complete of course, because I avoid the things I don’t know here. I accept comments here but please stand for the users freedom, not merely absolute monopoly for the sake of the vendor. Continue reading

Is Free Software Secure?

Bismillahirrahmanirrahim.

Ade Malsasa Akbar <teknoloid@gmail.com>

I am not a security expert, I am just a regular user of GNU/Linux operating systems. I want to revive this blog again with much more intense free software awareness materials than before. And in this article I want to explain in a very simple way why free software is secure to non-technical users of GNU/Linux and free software.

I want to emphasize generally two questions here, “is free software secure?” and “is nonfree software secure?” to give any newcomer in GNU/Linux community understand why they need to reject nonfree software because of its insecurity nature. Continue reading

Support Open Document Format

Bismillahirrahmanirrahim.

Let us promote Open Document Format (ODF). The only reason I write this article is because the confusions of Microsoft Document Format (OOXML) brought by Microsoft Office against Open Document Format (ODF) brought by LibreOffice (and companions). The another reasonable reason for me is no exact match in search engine I found for “support open document format” keywords even until today. So I need to explain shortly why it is important to support ODF (and another open formats) followed by mentioning many important link resources for that. So please use ODF, use LibreOffice (or its companions), use them as far as we can. Then promote them. Propagate them so another one will use them either. I hope this article will be widely useful.

Summary

This article is a short collection of the reasons why ODF is important and why we need to avoid OOXML usages. Why we need to use LibreOffice (or its companions) and why we need to avoid Microsoft Office usage. I’m talking in Free Software (and Open Source) scope. So keep inside this scope if you want to comment please.

1. What is Open Document Format?

Open Document Format (ODF, OpenDocument) is an open format for digital documents. It consists of ODT for word processor, ODS for spreadsheet, ODP for presentation, and some more. It is popular to be LibreOffice’s default document format. It is open format comparable to Microsoft Document OOXML (DOCX/XLSX/PPTX). This is non-technical description.

Open Document Format for Office Applications (ODF) is an OASIS Consortium‘s standard format based on XML for word processor, spreadsheet, and presentation applications which has been accepted as ISO standard ISO/IEC 26300. ODF is based on Sun Microsystem’s document format for OpenOffice.org. Technical documentation of Open Document Format is can be downloaded below. Technical specification of ODF can be downloaded below. This is technical description.

For more detailed explanation about ODF, refer here:

2. Why Open Document Format is Important?

Because ODF is the most vendor-neutral open format for digital documents[TDF, OOXML]. It means no one patented the format specification, it is royalty-free format, no single vendor can lock the format of the document files, it means anyone permitted to create any software without patent risk forever, and it means it is readable/writable in any application worldwide.

  • For governments: it is important to use ODF[Swapnil, OOXML][Wikibooks, Benefit][OpenDocument Fellowship, Government] because if the governments use patent-encumbered format (and as the consequence is also using proprietary software) to manipulate state document, there is no guarantee for the state confidential documents not to be leaked to the vendor. There is no guarantee if format/software vendor can not read or can not lock the software applications and furthermore lock the document files. There is no guarantee that vendor can not modify remotely any confidential document created using those document formats and proprietary software. Also, it is very important for governments to ensure no state resident can be discriminated[OASIS, Benefit] in data access because of a document format or forced to buy certain product from certain vendor[OpenForumEurope, Government].
  • For end users: it is important to use ODF (and one of the consequence is using Free Software/Open Source) because its compatibility towards other software. ODF is not patented, furthermore i.e. LibreOffice is Free Software so no algorithm to read/write ODF is patented. By using ODF, somebody helps FOSS community and also helps ODF to be recognized widely.

3. What Applications To Support Open Document Format?

LibreOffice and its companions. They are Free Software, such as:

  1. Apache OpenOffice (formerly OpenOffice.org): free office suite from Sun Microsystem which LibreOffice created from. Now Apache Foundation handles its development. Licensed in Apache License 2.0.
  2. Calligra Office: free office suite from KDE. Licensed in GNU GPL and LGPL.
  3. NeoOffice: free office suite from Planamesa Software for Apple Mac OS X. Licensed in GNU GPL.
  4. Abiword: free word processor from Abisource. Licensed in GNU GPL v2.
  5. Gnumeric: free spreadsheet from GNOME Project. Licensed in GNU GPL.
  6. WebODF: free web based office suite. Licensed in GNU AGPL.

They are safe to use. And their native document formats are safe also.

4. What is OOXML?

Office Open XML (OOXML) is digital document format from Microsoft for word processors, spreadsheets, and presentations. It consists of mainly three formats: DOCX, XLSX, and PPTX. They are popular for being default document format in Microsoft Office 2007 and later. This is non-technical description.

Office Open XML (OOXML) is a XML-based document file format from Microsoft for mainly word processors, spreadsheets, and presentations applications. This format standardized by ECMA (ECMA-376) then by ISO & IEC (ISO/IEC 29500). Technical specification of Office Open XML can be downloaded in http://www.ecma-international.org/publications/standards/Ecma-376.htm. This is technical description.

For more detailed explanation, see below or see section 1 above.

5. Why Microsoft OOXML Format is Need To Be Avoided?

  • OOXML is not widely compatible with another software applications, it is best to read/modify perfectly only in Microsoft products (i.e. Microsoft Office). Even different version of Microsoft Office can not or difficult to read same OOXML format from earlier version[Wikipedia, OOXML][Swardley, OOXML][OIDBD, OOXML][ICTS, OOXML][Robweir, OOXML][Office, OOXML].
  • OOXML is encumbered in software patents[NOOOXML, Ambush]. That is dangerous for Free Software and Open Source community. Why is patent dangerous? Read below.
  • OOXML is covered by not-forever-covering[Arstechnica, Patent] Microsoft Promises[Wikipedia, Promise]. Microsoft promised “not to sue” only for “current” format of OOXML, so there is no guarantee Microsoft will keep their promises for newer version of patent-encumbered OOXML format.
  • OOXML consists of 6000 pages long[ECMA, 376] document (to compare it, POSIX/SUSv3[Wikipedia, SUS] is only 3700 pages) so it is really difficult for any Free Software developer to create perfect filter to read/write into OOXML.
  • http://www.fsf.org/campaigns/opendocument/reject: this page explains why it is even better to deny Microsoft Office.
  • OOXML is second standard approved by ISO after ODF. We need only one standard.
  • Read this Linux Foundation Wiki article https://wiki.linuxfoundation.org/en/Architects_on_OOXML mentioning many GNU/Linux software arcitect expert statements about OOXML. Those (Free Software users) who are looking for experts’ statements should read this.

6. Why Software Patent is Dangerous?

Please read more appropriate links stated below explaining how dangerous patent is. I suggest you to read sequentially number by number below.

  1. https://www.debian.org/reports/patent-faq.en.html: good start to know software patent problems and its impact to any Free Software/Open Source community.
  2. http://www.gnu.org/philosophy/software-patents.en.html: describing detailed software patent problems, which is bigger than proprietary software problems.
  3. http://www.getgnulinux.org/en/linux/misunderstanding_free_software (section 4): the best summary of two mentioned articles above, suitable for newbie.
  4. http://noooxml.wikidot.com/patents: (NO)OOXML is dedicated wiki explaining OOXML format in case of so users can avoid it. Those (Free Software users) who need complete OOXML references should refer to this.

7. Am I Alone With This Patent Problem?

No. Every big community and company in GNU/Linux scope aware about this problem. Please read their defense policies against software patents.

Outside them, there are also organizations to dealing with patent problems against Free Software/Open Source. These are not all, but just what I can collect for now.

8. Am I Alone to Promote ODF?

No. There are many special organizations formed to face these problems. Whether they are developing software to support ODF, or they do fundamental things about ODF, or they do educational purposes to promote ODF. They are:

  1. http://www.opendocumentformat.org: official site of Open Document Format.
  2. http://www.fsf.org/campaigns/opendocument: Free Software Foundation’s official statement in supporting ODF.
  3. http://www.documentliberation.org: one of the most important software project which has developed free libraries for ODF, SVG, and another document formats available in the world.
  4. http://documentfoundation.org: The Document Foundation, organization which forked OpenOffice.org and created LibreOffice. One of the biggest supporter for ODF.
  5. https://www.oasis-open.org/standards: OASIS Consortium, the creator of ODF.
  6. http://libreoffice.org: LibreOffice official site.
  7. http://en.swpat.org: End Software Patents project’s wiki.
  8. http://noooxml.wikidot.com: (NO)OOXML, dedicated wiki explaining OOXML for Free Software users.
  9. http://ooxmlisdefectivebydesign.blogspot.com: personal blog explaining many aspects of OOXML including detailed benchmarks from Free Software users’ prespective.
  10. http://standards.iso.org/ittf/PubliclyAvailableStandards: Open Document Format in ISO official list of standards. See section ISO/IEC 26300:2006.
  11. http://opendocumentfellowship.com: a volunteer organization with members around the world to promote ODF.
  12. http://opendocument.xml.org: official community gathering for Open Document Format in XML.org.
  13. http://www.webodf.org: free web based ODF editor.
  14. https://wiki.linuxfoundation.org/en/Architects_on_OOXML: already explained.

9. So Practically What Can I Do?

End Users:

  • Use LibreOffice in every operating system (including Windows, Mac OS X, BSD, or any further operating system). Or, use any other of its companions mentioned earlier.
  • Save as in ODF formats (.odt, .ods, .odp).
  • Send email attachments as ODF format. Not in Microsoft OOXML format. Microsoft Office 2010 and later can save and edit ODF.
  • Deny politely any .docx (OOXML) email attachment sent by another.
  • Encourage people to install LibreOffice in every operating system possible. Or, install any other of its companions.
  • Encourage people to use ODF too.
  • Educate people like (or more than) this article tells you about importance of the ODF.

Companies:

  • If you are big company, you can consider to support ODF by officially using ODF as your company document format or donate to LibreOffice development project. Of course you can donate to another of its companions too.
  • If you provide software service, you can consider to support ODF as your service document format. For example, if you have web based (server based) service, please add read/modify ODF document support.

Writer

  • Translate this article into your language and spread it.
  • Create better article than this and spread it.
  • Put ODF banners (or edit it first) created by me in your blogs.
  • Create better banners than mine.

Important Links

References

  1. [TDF, OOXML] https://wiki.documentfoundation.org/LibreOffice_OOXML
  2. [Swapnil, OOXML] http://www.linuxveda.com/2014/11/29/never-use-microsofts-ooxml-pseudo-standard-format
  3. [Wikibooks, Benefit] https://en.wikibooks.org/wiki/FOSS_Open_Standards/Importance_and_Benefits_of_Open_Standards#Benefits_of_Using_Open_Standards
  4. [OpenDocument Fellowship, Government] http://www.opendocumentfellowship.com/government
  5. [OASIS, Benefit] https://www.oasis-open.org/committees/download.php/21450/oasis_odf_advantages_10dec2006.pdf
  6. [OpenForumEurope, Government] http://openforumeurope.org/wp-content/uploads/2015/06/OFE-COIS-DFD-ODF-Open-Document-Principles-for-Government-Technology-March-2015.pdf
  7. [Wikipedia, OOXML] https://en.wikipedia.org/wiki/Microsoft_Office_XML_formats#Limitations_and_differences_with_Office_Open_XML
  8. [Swardley, OOXML] http://blog.gardeviance.org/2013/12/once-more-unto-breach-dear-friends-once.html
  9. [OIDBD, OOXML] http://ooxmlisdefectivebydesign.blogspot.co.id/2008/03/backwards-compatible-one-more-lie-by.html
  10. [ICTS, OOXML] http://www.icts.uct.ac.za/modules.php?name=News&file=article&sid=7076
  11. [Robweir, OOXML] http://www.robweir.com/blog/2006/09/ooxml-compatibility-pack.html
  12. [Office, OOXML] https://support.office.com/en-ca/article/Open-a-Word-2016-or-2013-document-in-an-earlier-version-of-Word-45C4DD2F-BF7B-4A0D-9FF2-7B2FF6B733F0
  13. [NOOOXML, Ambush] http://noooxml.wikidot.com/patents
  14. [Arstechnica, Patent] http://arstechnica.com/information-technology/2008/03/sflc-ooxml-could-poses-patent-threat-to-gpl-licensed-software
  15. [Wikipedia, Promise] https://en.wikipedia.org/wiki/Microsoft_Open_Specification_Promise
  16. [ECMA, 376] http://www.ecma-international.org/publications/standards/Ecma-376.htm
  17. [Wikipedia, SUS] https://en.wikipedia.org/wiki/Single_UNIX_Specification

Bleeding Edge Style Posting

Bismillahirrahmanirrahim.

I maintain about a dozen of blogs, both in Indonesian and English, and all of them talk about GNU/Linux. As a real newbie, I have written probably more than 500 articles (including ebooks) about GNU/Linux within them and outside of them. Recently I found many of my GNU/Linux friends in Indonesia excited about using Archlinux. They love Archlinux bleeding edge style of distributing software packages, they said it is rolling release. Apparently I was excited too in the way of AUR, where my friends can get newest version of same program I use directly. Archlinux gave them more advantages than Ubuntu (official or PPA) in this case. Archlinux’s bleeding edge style, I describe it personally as forever LTS, not waiting (not freezing) for stable package to release a new package. I take that concept into my new writing style. I call it bleeding edge posting. This article is also a bleeding edge post.

Advantages

After seeing bleeding edge way of Archlinux, recently I thought I must take that way to write. So I fire up my old blog (restava) to bear my new style of writing. I call this style bleeding edge posting. I don’t wait my writing for long-time editing. I post my posts directly. A bleeding edge post of me is an article which is containing at least a title and a sentence. But every post contains exactly one single idea, any new idea I find, so I don’t need to be frustrated when I find an idea and I must post it quickly. A bleeding edge post is usually finished in one time sitting duration. The main advantage of bleeding edge posting is I don’t need to wait to post any new idea where waiting is a very frustrating thing for a writer like me. It is a big win, where I can provide myself ideas collection in one place so I can make more long-editing posts in another blogs based on bleeding edge posts in bleeding edge blog. It is just similar thing between Fedora (bleeding edge*) and Red Hat Enterprise Linux (conservative edge**). My restava blog is “Fedora”, and my another blogs are “Red Hat Enterprise Linux”. Another advantage is I will never forget any of new ideas anymore. Another advantage of doing bleeding edge posting is I can fill my blog with more posts every month. If you are a writer, especially in GNU/Linux scope, bleeding edge posting saves your time so much.

Examples

  • If I find something important about apt, I can write it directly. I don’t need to compose a complete writing draft, do a little research first, experience errors, fixing errors, making conclusion, etc. I write what I find, although it is just a title. Example.
  • If I find something important about Scribus and Inkscape, I can write it directly. Example and example.
  • If I find something important about Slackware and Archlinux, I do it. Example.
  • Every time I try a new GNU/Linux distribution in a live session, I always take many screenshots of it. If I have many screenshots of gNewSense, Trisquel, openSUSE, new version of Ubuntu, I can be frustrated if I don’t post them. So bleeding edge posting saves my frustration. Examples.
  • Then outside of this scope, I can write more polished post based on bleeding edge blog on another blogs. I can spend time writing long posts there, after I collect enough bleeding edge posts here. For example, after posting a post about screenshots collection of recent Ubuntu, I can write a proper Ubuntu review based on screenshots collected. Example.

It Spreads

Well, I coined my own style bleeding edge posting about one year ago. It starts with my restava. I proofed I like this style so much. It gives me more convenient way of writing. I felt comfortable so much with this style. So, I began to spread this style into my another blog. Not just restava. I did it on desaininkscape, I did it here and inside this article too.

How About Tutorial Articles?

Yes, I admit that tutorial needs more times to write. So basically I can’t write tutorial in bleeding edge style. I must write tutorials in a very careful way, very comprehensive way. Every tutorial should be correct, should be free from errors. Yes, I place my tutorials in my conservative edge blogs especially my main blog. My main blog is just one. But because I have already accustomed with bleeding edge style, I can write long articles as technical GNU/Linux tutorials. Actually they are intended to be personal notes only but anyone can consider them as tutorials. I have few examples here and here. Yes, bleeding edge style can be used as a way to write comprehensive tutorials. Surprise.

I Know It’s Funny

If you are a distribution developer, you probably will laugh at me. I know it’s funny, though. But truly Archlinux bleeding edge style is the source of this style. Probably you have more proper terms than bleeding edge posting and have using it before me. Please, you can let me know.

_______

*) I describe Fedora as bleeding edge to compare quickly, to make sense quicker. I know Fedora prefer to be credited as leading edge. To sum it up, bleeding edge = risky while leading edge = not risky. Thanks for alunux @ #ubuntu-indonesia to point me.

**) I describe Red Hat Enterprise Linux as conservative edge just because I don’t know the antonym of bleeding edge. I don’t find it anywhere. If you know, please let me know.