FEED Validator

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 2, column 0: Use of unknown namespace: http://planet.intertwingly.net/ [help]

  <feed xmlns="http://www.w3.org/2005/Atom" xmlns:planet="http://planet.intert ...
  

• line 11, column 97: Self reference doesn't match document location [help]

  ... rel="self" type="application/atom+xml"/>
                                               ^

• line 804, column 33: Two entries with the same value for atom:updated: 2017-05-06T04:06:33Z [help]

      <updated>2017-05-06T04:06:33Z</updated>
                                   ^

• line 1776, column 15: p contains bad characters (2 occurrences) [help]

      (人人生æ?¥æ˜¯ä¸ºäº†æŽ¨åŠ¨æ–‡æ˜Žä¸?断进步的)
                 ^

• line 2064, column 109: li contains bad characters [help]

  ... 14/5786620192096256">seaside part 1</a>  and <a href="http://www.google ...
                                               ^

• line 2190, column 39: Identifier "https://www.foresightlinux.se" is not in canonical form (the canonical form would be "https://www.foresightlinux.se/") (22 occurrences) [help]

        <id>https://www.foresightlinux.se</id>
                                         ^

Source: http://feeds.feedburner.com/foresightplanet?format=xml

1. <?xml version="1.0"?>
2. <feed xmlns="http://www.w3.org/2005/Atom" xmlns:planet="http://planet.intertwingly.net/" xmlns:indexing="urn:atom-extension:indexing" indexing:index="no"><access:restriction xmlns:access="http://www.bloglines.com/about/specs/fac-1.0" relationship="deny"/>
3.  <title>Foresight Linux Planet</title>
4.  <updated>2017-08-04T15:41:02Z</updated>
5.  <generator uri="http://intertwingly.net/code/venus/">Venus</generator>
6.  <author>
7.    <name>Foresight Linux Project</name>
8.    <email>infra@foresightlinux.org</email>
9.  </author>
10.  <id>http://planet.foresightlinux.org/atom.xml</id>
11.  <link href="http://planet.foresightlinux.org/atom.xml" rel="self" type="application/atom+xml"/>
12.  <link href="http://planet.foresightlinux.org" rel="alternate"/>
13.  
14.  <entry>
15.    <id>tag:omaciel.github.io,2017-07-03:just-what-is-a-quality-engineer-part-2.html</id>
16.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/aBh-qIIoCD8/just-what-is-a-quality-engineer-part-2.html" rel="alternate" type="text/html"/>
17.    <title>Just What Is A Quality Engineer? Part 2</title>
18.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><img alt="Picture of `Batman`_" class="align-left" src="http://feeds.feedburner.com/images/batman-is-qe.jpeg" style="width: 25pc; height: 25pc;"/>
19. <p>The <a class="reference external" href="https://omaciel.github.io/just-what-is-a-quality-engineer-part-1.html">last time</a> I wrote about <strong>Quality Engineering</strong>, I mentioned that some of the reasons why people are not familiar with this term are, in no particular order:</p>
20. <ul class="simple">
21. <li>'Quality' is usually something that is added as an after thought and doesn't really come into the picture, if ever, until the very end of the release process</li>
22. <li>Nobody outside of a QA team really knows what they do. It has something to do with testing...</li>
23. <li>Engineering is usually identified with skills related to writing code and designing algorithms, usually by a developer and not by QA</li>
24. </ul>
25. <p>A quick search on Google shows the following results:</p>
26. <ul class="simple">
27. <li>104,000,000 hits for "Software Engineer"</li>
28. <li>86,900,000 hits for “Quality Control”</li>
29. <li>83,100,000 hits for “Quality Assurance”</li>
30. <li>5,390,000 hits for “Quality Engineer”</li>
31. </ul>
32. <p>As you can see, it is no wonder that whenever I say 'quality engineer' people always think that what I really meant to say was 'quality assurance' or 'quality control'. The term is just not that well-known! So in order to clarify what the difference is between these professions, today I'd like to talk a little bit about <strong>quality assurance</strong> and what I usually think whenever someone tells me that they either work in QA or have a 'QA team'.</p>
33. <p>Wikipedia tells us that the terms 'quality assurance' (QA) and 'quality control' (QC) are often used interchangeably to refer to ways of ensuring the quality of a service or product.</p>
34. <p>Furthermore,</p>
35. <blockquote>
36. "Quality assurance comprises administrative and procedural activities implemented in a quality system so that <strong>requirements</strong> and goals for a product, service or activity will be <strong>fulfilled</strong>. It is the systematic <strong>measurement</strong>, <strong>comparison</strong> with a standard, <strong>monitoring</strong> of processes and an associated <strong>feedback loop</strong> that confers <strong>error prevention</strong>."
37. -- <a class="reference external" href="https://en.wikipedia.org/wiki/Quality_assurance">Wikipedia</a></blockquote>
38. <p>That is quite a mouth full (the emphasized words are mine), but I feel that it does a good job at stating the following ideas:</p>
39. <ul class="simple">
40. <li>Quality Assurance and/or Quality Control is used to assure the quality of a product, but there is no clear distinction as to when in the release process it should be used. In my experience, it usually happens when the product is close to being shipped!</li>
41. <li>Used to make sure that <strong>requirements</strong> (the what) are <strong>fulfilled</strong> (the how)</li>
42. <li>Used to measure, monitor and compare results against a standard</li>
43. <li>Used for error preventions (which to me denotes a reactive mode compared to a proactive mode)</li>
44. </ul>
45. <p>In other words, those who do quality assurance for a living are involved in verifying that the final version of the product being tested delivers exactly what was designed with the expected behavior and outcome. It requires that the QA person fully understand what is being added to or changed in the product and, most importantly, what the end result should be. Testing is definitely a big part of the 'day to day' activities for someone in QA, which does provide useful information to create a positive feedback loop and hopefully increase error prevention.</p>
46. <p>Here's what I don't like about this whole business though:</p>
47. <p>Quality is something that must be part of all phases of a product and <strong>not</strong> at the very end of the process. A good QA person is usually so familiar with the product being tested that one could say that QA <strong>is</strong> the first customer a company has! If you have someone in your team who can fully understand how your product works, where the pain points are, knows at a glance if a new feature or a fix does not follow the existing standards, and has the ability to tell you if something doesn't feel right, would you want to hear this type of feedback at the very end? By then, can you really afford to put things on hold and re-design your product??? In my experience, the answer to this question has 99.99% of the time been 'No'.</p>
48. <p>Quality is the responsibility of everyone involved with a product and not only of those in QA! Everyone, document writers, translators, user experience (UX) experts, product managers, you name it, everyone should be in the business of delivering and assuring the quality of the product! If you bought something, would you be OK with accepting mediocre user experience, documentation, features and translations? I doubt it.</p>
49. <p>Monitoring and measuring how a product compares against some set of standardized benchmarks is definitely important but as customers request more and more new features and the product's complexity increases, are your benchmarks also keeping up with all these changes? More importantly, since <strong>you</strong> are the one using the product day and night, do you have any input into updating the benchmarks? I certainly hope so.</p>
50. <p>Lastly, if your job is to make sure that no product 'goes out the door' without a thorough validation, that it works as expected and that all known issues have been fixed, aren't you forgetting something? What about the issues that are not known yet? You may be thinking that I'm joking, but seriously. If all you do is prevent errors from being shipped to your customers, how about detecting them as early as possible to give all major stake-holders enough time to make a decision as to what should be done with them? Again, if you're catching them at the end of the release cycle, it could be too late.</p>
51. <p>If your company has a QA team, then you're already ahead of the game, since it is only when customer dissatisfaction is very high and the final numbers for the quarter start to look gloomy that people start paying attention to delivering quality. But it is not enough if you're only kicking the can down the road only to find yourself facing the same scenario later on! Quality, good quality, is what everyone in your team should be striving for... not some times, but all the time!</p>
52. <p>If you are in a QA team, do you ever feel like you're ahead of the game or feel like you're constantly playing catch up? Do you wish you could have a chance to catch issues as early as possible? Wouldn't you want to stop racing against the clock to get issues verified and have a shot at doing more exploratory testing and identify problems early on? Would you say 'no' to an opportunity to provide some insight into how the product could be improved and perhaps how some work-flows could be simplified to increase the usability?</p>
53. <p>It should be clear by now that quality is something that should be something systemic for any project or company who takes their customer satisfaction as their top priority! Sure you can test the product as much as you (or your QA team) can handle, but you'd be only treating the symptoms. Maintaining a 'quality first' mentality and improving existing processes to make sure that quality is an integral part of everyone's day to day activities is primordial if you really want to make a bigger impact!</p>
54. <p>This is when a Quality Engineer comes in! A Quality Engineer is someone who can actively and continuously keep driving improvements to the release cycle process and are in the unique position to help the entire team adopt these improvements so that everyone is using the same methodologies.</p>
55. <p>Next time I will then talk about <strong>quality engineering</strong> (QE), what it is, what it isn't, and how you should be either hiring more QE or, if you're in QA, how you should be working to become a QE!</p>
56. <p>As always, please let me know what your thoughts are on this topic as I'd live to get some constructive feedback!</p>
57. <blockquote>
58. Disclaimer: The opinions contained within this article are mine alone and do not necessarily represent the opinions of any entity whatsoever with which I have been, am now or will be affiliated.</blockquote>
59. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/aBh-qIIoCD8" width="1"/></div>
60.    </content>
61.    <updated>2017-07-03T04:00:00Z</updated>
62.    <published>2017-07-03T04:00:00Z</published>
63.    <category term="qa"/>
64.    <category term="qe"/>
65.    <category term="quality engineering"/>
66.    <category term="work"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/just-what-is-a-quality-engineer-part-2.html</feedburner:origLink>
67.    <author>
68.      <name>Og Maciel</name>
69.    </author>
70.    <source>
71.      <id>https://omaciel.github.io/</id>
72.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
73.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
74.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
75.      <title>Journal of an Open Sourcee</title>
76.      <updated>2017-07-03T04:00:00Z</updated>
77.    </source>
78.  </entry>
79.  
80.  <entry>
81.    <id>tag:omaciel.github.io,2017-06-30:just-what-is-a-quality-engineer-part-1.html</id>
82.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/4me100a0yhA/just-what-is-a-quality-engineer-part-1.html" rel="alternate" type="text/html"/>
83.    <title>Just What Is A Quality Engineer? Part 1</title>
84.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><img alt="Picture of `Batman`_" class="align-left" src="http://feeds.feedburner.com/images/batman-is-qe.jpeg" style="width: 25pc; height: 25pc;"/>
85. <p>Whenever I meet someone for the first time, after we get past the initial niceties typically involved when you meet someone for the first time, eventually the conversation shifts to work and what one does for a living. Inevitably I'm faced with what, at a first glance, may sound like a simple question and the conversation goes like this:</p>
86. <ul class="simple">
87. <li>New acquaintance: "What do you do at Red Hat?"</li>
88. <li>Me: "I manage a team of quality engineers for a couple of different products."</li>
89. <li>New acquaintance: "Oh, you mean quality assurance, right? QA?"</li>
90. <li>Me: "No, quality <strong>engineers</strong>. QE."</li>
91. </ul>
92. <p>What usually followed then was a lengthy monologue whereby I spent usually around ten to fifteen minutes explaining what the difference between QA and QE is and what, in my opinion, sets these two professions apart. Now, before I get too deep into this topic, I have to add a disclaimer here so not to give folks the impression that what I'm talking about is backed by any official definition or some type of professional trade organization! The following are my own definitions and conclusions, none of which were pulled out of thin air, but backed by (so far) 10 years of experience working on the field of delivering quality products. If there are formal definitions out there, and they match with my own, it is by pure coincidence.</p>
93. <p>Why the term 'Quality Engineer' is not well known I'm not sure, but I have a hunch that it may be related to something I noticed throughout the 10 years that I have spent on this field. In my personal experience, 'quality' is something that is not always considered as part of the creation of a new company, product or project. Furthermore, the term 'quality' is also not well defined or understood by those involved in actually attempting to 'get more' of it.</p>
94. <p>In my experience, folks usually forget about the word 'quality', whatever that may be, happily start planning and developing their new ideas/products and eventually ship it to their customers. If the customer complains that something is not working or performing as advertised or it doesn't meet their expectations, no problem. Someone will convey the feedback back to the developers, a fix will eventually be provided and off it goes to the customer. Have you ever seen this before? I have!</p>
95. <p>Eventually, assuming that the business is doing well and is attracting more paying customers, it is highly likely that support requests or requests for new features will increase. After all, who wants to pay for something that doesn't work as expected? Also, who doesn't want a new feature of their own either? Depending on the size of the company and the number of new requests going into their backlog, I'd expect that either one of the following events would then take place:</p>
96. <ul class="simple">
97. <li>More tasks from the backlog would be added to individual's 'plates', or</li>
98. <li>New associates would be hired to handle the volume of tasks</li>
99. </ul>
100. <p>I guess one could also stop accepting new requests for support or new features, but that would not make your customers happy, would it?</p>
101. <p>Regardless of the outcome, the influx of new tasks is dealt with and if things get out of control again, one could always try to get an intern or distribute tasks more evenly. Now, notice how the word 'quality' has not been mentioned yet? It is no accident that to solve an increase of more work, most often than not the number one solution used is to throw more resources at it. There's even a name for this type of 'solution': <a class="reference external" href="https://en.wikipedia.org/wiki/The_Mythical_Man-Month">The Mythical Man-Month</a>.</p>
102. <p>You see, sadly, 'quality' is something that usually only becomes important as an afterthought. It is the last piece added to the puzzle that comprises the machinery of delivering something to an end user. It is only when enough angry and unsatisfied paying customers make enough noise about the unreliability or usability of the product that folks start asking: "Was this even tested before being put on the market?"</p>
103. <p>If the pain being inflicted by customer feedback is sharp enough, a <strong>Quality Assurance</strong> (QA) team is hastily put together. Most of the time in my experience, this is a Team of One usually made up of one of the developers who after being dragged kicking and screaming from his cubicle, eventually is beat into accepting his new role as a button pusher, text field filler, testing guy. Issues are then assigned to him and a general sense of relief is experienced by all. Have you also seen this before? I have! I'm 2 for 2 so far!</p>
104. <p>The idea is that by creating a team of one to sit in the receiving end of the product release cycle, nothing would get shipped until some level of 'quality' is achieved. The fallacy with this statement, however, is that no matter how agile your team may be, the assurance of the quality for a product somehow is still part of a <a class="reference external" href="https://en.wikipedia.org/wiki/Waterfall_model">waterfall model</a>. Wouldn't it be better if problems were caught as early as possible in the process instead of waiting until the very end? To me that is a no brainer but somehow the process of testing a product is still relegated to the very end, usually when the date for the release is just around the corner.</p>
105. <p>Why is the term <strong>Quality Engineer</strong> not well known then? I feel that the answer is comprised of several parts:</p>
106. <ul class="simple">
107. <li>'Quality' doesn't come into the picture, if ever, until the very end of the game;</li>
108. <li>If there is a QA team, nobody outside of that team really knows what they do. It has something to do with testing...</li>
109. <li>Engineering is usually identified with skills related to writing code and designing algorithms, usually by a developer and not by QA;</li>
110. </ul>
111. <p>No surprise that quality engineering is something foreign to most!</p>
112. <p>OK, so what <strong>is</strong> a <strong>Quality Engineer</strong> then? Glad you asked! The answer to that I shall provide in a subsequent post, as I still need to cover some more ground and talk about what 'quality' is, what someone in QA does and finally what is a QE!</p>
113. <p>My next article will continue this journey through the land of Quality and Engineering, and in the meantime, please let me know what you think about this subject.</p>
114. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/4me100a0yhA" width="1"/></div>
115.    </content>
116.    <updated>2017-06-30T04:00:00Z</updated>
117.    <published>2017-06-30T04:00:00Z</published>
118.    <category term="qa"/>
119.    <category term="qe"/>
120.    <category term="quality engineering"/>
121.    <category term="work"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/just-what-is-a-quality-engineer-part-1.html</feedburner:origLink>
122.    <author>
123.      <name>Og Maciel</name>
124.    </author>
125.    <source>
126.      <id>https://omaciel.github.io/</id>
127.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
128.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
129.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
130.      <title>Journal of an Open Sourcee</title>
131.      <updated>2017-07-03T04:00:00Z</updated>
132.    </source>
133.  </entry>
134.  
135.  <entry>
136.    <id>tag:omaciel.github.io,2017-06-27:on-reading-and-writing.html</id>
137.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/NWP8BppWK3Q/on-reading-and-writing.html" rel="alternate" type="text/html"/>
138.    <title>On Reading and writing</title>
139.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left">
140. <img alt="Picture of 'On Writing'" src="http://feeds.feedburner.com/images/stephen-king-on-writing.jpg"/>
141. </div>
142. <p>This week I started reading <a class="reference external" href="https://www.goodreads.com/book/show/7143113-on-writing">On Writing</a>: A Memoir of the Craft by <a class="reference external" href="https://www.goodreads.com/author/show/3389.Stephen_King">Stephen King</a>, a book that has been mentioned a few times by people I usually interview for my weekly <a class="reference external" href="http://castalio.info/">podcast</a> as something that is both inspiring and has had a major impact on their lives and careers. After the third or forth time someone mentioned I finally broke down and got myself a copy at the local bookstore.</p>
143. <p>I have to say that, so far, I am completely blown away by this book! I can totally see why everyone else recommended it as something that people should add to their BTR (Books To Read) list! First of all, the first section of the book, which Stephen King calls his 'C.V.' (and not his memories or auto biography), covers his early life as a child, his experiences and struggles (there are quite a few passages that will most likely get you to laugh out loud) growing up with his mom and older brother, Dan. This section, roughly speaking around 100 pages or so, are so easy to relate to that you can probably be done with them in about 2 hours no matter what your reading pace is. I am always captivated to learn how someone 'came to be', the real 'behind the scenes' if you will, of how someone started out their lives and the paths they took to get to where they are now.</p>
144. <p>The next sections talk about what any aspiring writer should add to their 'toolbox' and it covers many interesting topics and suggestions which, if you really think about it, makes a ton of sense. This is where I am in the book right now, and though it isn't as captivating as the first section, it should still appeal to anyone looking for solid advice on how to become a better writer in my humble opinion.</p>
145. <p>Though I one day do aspire to become a published writer (fiction most likely), and I am enjoying this book that I'm having a real hard time putting it down, the reason why I chose to write about it is related to a piece of advice that Stephen King shares with the reader about the habit of reading.</p>
146. <p>Stephen King claims that, to become a better writer one must at least obey the following rules:</p>
147. <ul class="simple">
148. <li>Read every day!</li>
149. <li>Write every day!</li>
150. </ul>
151. <p>It is by reading a lot (something that should come naturally to anyone who reads every day) that one learns new vocabulary words, different styles of prose, how to structure ideas into paragraphs and rhythm. He says that it doesn't matter if you read in 'tiny sips' or in huge 'swallows', but as long as you continue to read every day, you'll develop a great and, in his opinion, required habit for becoming a better writer. Obviously, based on his two rules you'd need to write every day too, and if you're one of us who is toying with the idea of becoming a writer one day (or want to become a better writer), I too highly recommend that you give this book a shot! I know, I know, I have not finished it yet but still... I <strong>highly</strong> recommend it!</p>
152. <p>Back to the habit of reading and the purpose of this post, I remember back in 2008 my own 'struggle' to 'find the time' to read non technical books. You know, reading for fun? Back then I was doing a lot of reading, but mostly it consisted of blog posts and articles recommended by my RSS feeds, and since I was very much involved with a lot of different open source projects, I mostly read about GNOME, KDE, Ubuntu and Python. Just the thought of reading a book that did not cover any of these topics gave me a feeling of uneasiness and I couldn't picture myself dedicating time, precious time, to reading 'for fun.' But eventually I realized that I needed to add a bit more variety to my reading experience and that sitting in front of my computer during my lunch break would not help me with this at all. There were too many distractions to lure me away from any book I may be trying to read.</p>
153. <p>I started out by picking up a book that everyone around me had mentioned many times as being 'wicked cool' and 'couldn't put it down' kind of book. Back then I worked at a startup and most of the engineers around me were much younger than me and at one point or another most of them were into 'the new Harry Potter' book. I confess that I felt judgmental and couldn't fathom the idea of reading a 'kid book' but since I was trying to create a new habit and since my previous attempts had failed miserably, I figured that something drastic was just what the doctor would have recommended. One day after work, before driving back home, I stopped by the public library and picked up <a class="reference external" href="https://www.goodreads.com/book/show/3.Harry_Potter_and_the_Sorcerer_s_Stone">Harry Potter and the Sorcerer's Stone</a>.</p>
154. <p>Next day at work when I took my lunch break, I locked my laptop and went downstairs to a quiet corner of the building's lobby. I picked a nice, comfortable seat with a lot of natural sun light and view of the main entrance and started reading... or at least I thought I did. Whenever I started to read a paragraph, someone would open the door at the main entrance to the building either on their way in or out, and with them went my focus and my mind would start wandering. Eventually I'd catch myself and back to the book my eyes went, only to be disrupted by the next person opening the door. Needless to say, experiment 'Get More Reading Done' was an utter failure!</p>
155. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/NWP8BppWK3Q" width="1"/></div>
156.    </content>
157.    <updated>2017-06-27T04:00:00Z</updated>
158.    <published>2017-06-27T04:00:00Z</published>
159.    <category term="books"/>
160.    <category term="reading"/>
161.    <category term="writing"/>
162.    <category term="stephen king"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/on-reading-and-writing.html</feedburner:origLink>
163.    <author>
164.      <name>Og Maciel</name>
165.    </author>
166.    <source>
167.      <id>https://omaciel.github.io/</id>
168.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
169.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
170.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
171.      <title>Journal of an Open Sourcee</title>
172.      <updated>2017-07-03T04:00:00Z</updated>
173.    </source>
174.  </entry>
175.  
176.  <entry>
177.    <id>http://societyserver.org/mbaehr/everlasting-life-through-cyberspace</id>
178.    <link href="http://societyserver.org/mbaehr/everlasting-life-through-cyberspace" rel="alternate" type="text/html"/>
179.    <title>Everlasting Life Through Cyberspace</title>
180.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
181. <p>
182. The idea has been brought up a few times, that we would upload our minds into a
183. computer and in this way would be able to live forever.
184. </p>
185.  
186. <p>
187. How would that look like?
188. </p>
189.  
190. <p>
191. At it's base, every uploaded mind would represent a program with access to data
192. storage and computing resources. These programs can interact with each other
193. not unlike programs on the internet today. For example like in a virtual
194. reality game world. (Second Life, etc)
195. </p>
196.  
197. <p>
198. In uploaded form we would manipulate our environment through other programs,
199. that we create ourselves or that others create for us. There might be a market
200. to trade these programs and its products.
201. </p>
202.  
203. <p>
204. Now, anything that is programmable will have bugs and is exploitable, therefore
205. it will be necessary to protect against such attacks. Much like we use
206. encryption today to keep things private, encryption and self protection will
207. play a large role in such a cyberworld.
208. </p>
209.  
210. <p>
211. Unlike today where we can rely on physical protection, healtcare, etc to
212. support us, in cyberspace, all protection comes in form of programs, and that
213. means instead of relying on others to act in our behalf in order to pretect us,
214. every one of us will be able to get a copy of a protection program that we then
215. will be able to control by ourselves. It's all bits and bytes, so there is no
216. reason to assume that we would not be able to have full control over our
217. environment.
218. </p>
219.  
220. <p>
221. We could build cyberspace without these protections, but it is inconceivable
222. that anyone would accept a world where their own well being is not ensured.
223. Either from the outside, or from the inside. But if everyone is uploaded, then
224. there is no more outside, and therefore all protection must come from the
225. inside, through programs. And since even now, most people are not skilled
226. programmers, and that is unlikely to change much in the future, it is hard to
227. imagine that people would willingly enter a world where their life depends on
228. their programming skills. No, people must be able to trust that no harm will
229. come to them in this new world where they otherwise would not have the skill to
230. protect themselves.
231. </p>
232.  
233. <p>
234. The reason we feel safe in this world is because we agreed to a set of laws
235. which we enforce, and for the most part, crimes are visible and can be
236. persecuted. People who live in places where this is not the case don't feel
237. safe, and noone would willingly leave their save home to move to such an area.
238. </p>
239.  
240. <p>
241. In a cyberworld, such safety can only be achieved by making crime impossible to
242. begin with, because given enough resources, a computer program can do damage
243. without leaving a trace.
244. </p>
245.  
246. <p>
247. This has a few severe implications.
248. </p>
249.  
250. <p>
251. If real crime is impossible and we further have full control over our own
252. protection, controlling what data we receive that could possibly offend us,
253. then effectively we can no longer be hurt. There is no physical pain anyways,
254. and any virtual pain we could just switch off.
255. </p>
256.  
257. <p>
258. If we can not be hurt, the corollary is that we can not really hurt anyone.
259. We can not do anything that has any negative consequences on anyone else.
260. </p>
261.  
262. <p>
263. We can not even steal someones computing resources, or rather we probably could
264. but there would be no point because even if computing resources are unevenly
265. distributed, it would not matter.
266. </p>
267.  
268. <p>
269. There is no sense of time, since any sense of time is simulated and can be
270. controlled. So if we were trying to build something that takes lots of
271. time, we could adjust our sense of time so that we would not have to feel the
272. wait for the computation to complete. With that in mind, stealing resources
273. to make computation faster would become meaningless.
274. </p>
275.  
276. <p>
277. And if we could take all resources from someone, then that would effectively
278. kill them as their program could no longer run. It would be frozen in storage.
279. Allowing this could start a war of attrition that would end with one person
280. controlling everyone else and everyone fearing for their life. It just doesn't
281. make sense to allow that.
282. </p>
283.  
284. <p>
285. In other words we no longer have freedom to do evil. Or more drastically, we no
286. longer have complete free will. Free will implies the ability to chose evil.
287. Without that choice free will is limited.
288. </p>
289.  
290. <h3>In summary life in cyberspace has the following attributes:</h3>
291.  
292. <ul>
293. <li>
294. We will all live there eternally (well, as long as the computer keeps running).
295. </li>
296.  
297. <li>
298. There is no sense of time.
299. </li>
300.  
301. <li>
302. We will keep our sense of identity.
303. </li>
304.  
305. <li>
306. We will be able to interact with every human ever uploaded.
307. </li>
308.  
309. <li>
310. We will continue to advance and develop.
311. </li>
312.  
313. <li>
314. There is no power to do evil.
315. </li>
316.  
317. <li>
318. We will be able to affect the physical world, and the physical world will affect us.
319. </li>
320. </ul>
321.  
322.  
323. <h3>Here is how cyberspace looks like from the outside:</h3>
324.  
325.  
326. <ul>
327. <li>
328. When a person is uploaded, its physical body ceases to function and decays.
329. </li>
330.  
331. <li>
332. Everyone can be uploaded, there is no specific requirements or conditions
333. that would prevent anyone from being uploaded.
334. </li>
335.  
336. <li>
337. We are assuming that we will be able to communicate with those in cyberspace,
338. but imagine how it would look like if we could not communicate with an
339. uploaded person. We would then actually not be able to tell if they
340. successfully uploaded or not. We would in fact not even be able to tell
341. whether cyberspace exists at all, and we would have to take a leap of faith
342. that it is real.
343. </li>
344. </ul>
345.  
346. <h3>Conclusion:</h3>
347.  
348. <p>
349. While discussing this article, a lot of arguments were made about the details
350. of how cyberspace would look like. In particular it was questioned that there
351. would be no pain. Most commenters could not imagine that we'd want a painfree life.
352. </p>
353.  
354. <p>
355. That is fine. These particular details are not important. There are many ways
356. we can imagine how cyberspace could look like.  What is important is this:
357. </p>
358.  
359. <p>
360. These attributes of cyberspace as described here, are all attributes of life
361. after death as described at least by the Baha'i Faith, and possibly other
362. religions.
363. </p>
364.  
365. <p>
366. This is significant not because of the attributes themselves, but because this
367. means that given todays grasp of technology, at least <em>this version of
368. cyberspace looks indistinguishable from life after death</em>.
369. </p>
370.  
371. <p>
372. Now, if we are unable to distinguish cyberspace from life after death, then how
373. would we know which one we are dealing with? If it is possible that cyberspace
374. looks like life after death, isn't it equally possible that life after death
375. looks like cyberspace? Is it possible that they are one and the same?
376. </p>
377.  
378. <p>
379. Why do we want to upload into cyberspace? Because we want eternal life free
380. from bodily limitations? Isn't this something that religions have promised us
381. for millenia?
382. </p>
383.  
384. <p>
385. If that is the case, wouldn't we be trying to reinvent something that maybe
386. already exists?
387. </p>
388.  
389. <p>
390. So maybe, cyberspace already exists, and death is just the upload process?
391. Maybe we are simply not yet advanced enough to perceive or understand our life
392. beyond the point of upload from the outside?
393. </p>
394.  
395. <p>
396. Maybe we just need to evolve further before we are able to communicate with
397. those who are uploaded?
398. </p></div>
399.    </content>
400.    <updated>2017-05-06T15:25:02Z</updated>
401.    <category term="steam"/>
402.    <category term="documents"/>
403.    <author>
404.      <name>Martin Baehr</name>
405.      <email>mbaehr@community.gotpike.org</email>
406.    </author>
407.    <source>
408.      <id>http://societyserver.org/mbaehr</id>
409.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
410.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
411.      <title>DevLog</title>
412.      <updated>2017-07-30T20:40:04Z</updated>
413.    </source>
414.  </entry>
415.  
416.  <entry>
417.    <id>http://societyserver.org/mbaehr/everlasting-live-through-cyberspace</id>
418.    <link href="http://societyserver.org/mbaehr/everlasting-live-through-cyberspace" rel="alternate" type="text/html"/>
419.    <title>everlasting live through cyberspace</title>
420.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
421. <p>
422. The idea has been brought up a few times, that we would upload our minds into a
423. computer and in this way would be able to live forever.
424. </p>
425.  
426. <p>
427. How would that look like?
428. </p>
429.  
430. <p>
431. At it's base, every uploaded mind would represent a program with access to data
432. storage and computing resources. These programs can interact with each other
433. not unlike programs on the internet today. For example like in a virtual
434. reality game world. (Second Life, etc)
435. </p>
436.  
437. <p>
438. In uploaded form we would manipulate our environment through other programs,
439. that we create ourselves or that others create for us. There might be a market
440. to trade these programs and its products.
441. </p>
442.  
443. <p>
444. Now, anything that is programmable will have bugs and is exploitable, therefore
445. it will be necessary to protect against such attacks. Much like we use
446. encryption today to keep things private, encryption and self protection will
447. play a large role in such a cyberworld.
448. </p>
449.  
450. <p>
451. Unlike today where we can rely on physical protection, healtcare, etc to
452. support us, in cyberspace, all protection comes in form of programs, and that
453. means instead of relying on others to act in our behalf in order to pretect us,
454. every one of us will be able to get a copy of a protection program that we then
455. will be able to control by ourselves. It's all bits and bytes, so there is no
456. reason to assume that we would not be able to have full control over our
457. environment.
458. </p>
459.  
460. <p>
461. We could build cyberspace without these protections, but it is inconceivable
462. that anyone would accept a world where their own well being is not ensured.
463. Either from the outside, or from the inside. But if everyone is uploaded, then
464. there is no more outside, and therefore all protection must come from the
465. inside, through programs. And since even now, most people are not skilled
466. programmers, and that is unlikely to change much in the future, it is hard to
467. imagine that people would willingly enter a world where their life depends on
468. their programming skills. No, people must be able to trust that no harm will
469. come to them in this new world where they otherwise would not have the skill to
470. protect themselves.
471. </p>
472.  
473. <p>
474. The reason we feel safe in this world is because we agreed to a set of laws
475. which we enforce, and for the most part, crimes are visible and can be
476. persecuted. People who live in places where this is not the case don't feel
477. safe, and noone would willingly leave their save home to move to such an area.
478. </p>
479.  
480. <p>
481. In a cyberworld, such safety can only be achieved by making crime impossible to
482. begin with, because given enough resources, a computer program can do damage
483. without leaving a trace.
484. </p>
485.  
486. <p>
487. This has a few severe implications.
488. </p>
489.  
490. <p>
491. If real crime is impossible and we further have full control over our own
492. protection, controlling what data we receive that could possibly offend us,
493. then effectively we can no longer be hurt. There is no physical pain anyways,
494. and any virtual pain we could just switch of.
495. </p>
496.  
497. <p>
498. If we can not be hurt, the corollary is that we can not really hurt anyone.
499. We can not do anything that has any negative consequences on anyone else.
500. </p>
501.  
502. <p>
503. We can not even steal someones computing resources, or rather we probably could
504. but there would be no point because even if computing resources are unevenly
505. distributed, it would not matter.
506. </p>
507.  
508. <p>
509. There is no sense of time, since any sense of time is simulated and can be
510. controlled. So if we were trying to build something that takes lots of
511. time, we could adjust our sense of time so that we would not have to feel the
512. wait for the computation to complete. With that in mind, stealing resources
513. to make computation faster would become meaningless.
514. </p>
515.  
516. <p>
517. And if we could take all resources from someone, then that would effectively
518. kill them as their program could no longer run. It would be frozen in storage.
519. Allowing this could start a war of attrition that would end with one person
520. controlling everyone else and everyone fearing for their life. It just doesn't
521. make sense to allow that.
522. </p>
523.  
524. <p>
525. In other words we no longer have freedom to do evil. Or more drastically, we no
526. longer have complete free will. Free will implies the ability to chose evil.
527. Without that choice free will is limited.
528. </p>
529.  
530. <h3>In summary life in cyberspace has the following attributes:</h3>
531.  
532. <ul>
533. <li>
534. We will all live there eternally (well, as long as the computer keeps running).
535. </li>
536.  
537. <li>
538. There is no sense of time.
539. </li>
540.  
541. <li>
542. We will keep our sense of identity.
543. </li>
544.  
545. <li>
546. We will be able to interact with every human ever uploaded.
547. </li>
548.  
549. <li>
550. We will continue to advance and develop.
551. </li>
552.  
553. <li>
554. There is no power to do evil.
555. </li>
556.  
557. <li>
558. We will be able to affect the physical world, and the physical world will affect us.
559. </li>
560. </ul>
561.  
562.  
563. <h3>Here is how cyberspace looks like from the outside:</h3>
564.  
565.  
566. <ul>
567. <li>
568. When a person is uploaded, its physical body ceases to function and decays.
569. </li>
570.  
571. <li>
572. Everyone can be uploaded, there is no specific requirements or conditions
573. that would prevent anyone from being uploaded.
574. </li>
575.  
576. <li>
577. We are assuming that we will be able to communicate with those in cyberspace,
578. but imagine how it would look like if we could not communicate with an
579. uploaded person. We would then actually not be able to tell if they
580. successfully uploaded or not. We would in fact not even be able to tell
581. whether cyberspace exists at all, and we would have to take a leap of faith
582. that it is real.
583. </li>
584. </ul>
585.  
586. <p>
587. These attributes, are all attributes of life after death as described at least
588. by the baha'i faith, and possibly other religions.
589. </p>
590.  
591. <p>
592. So maybe, cyberspace already exists, and death is just the upload process?
593. Maybe we are simply not yet advanced enough to perceive or understand our life
594. beyond the point of upload from the outside?
595. </p>
596.  
597. <p>
598. Maybe we just need to evolve further before we are able to communicate with
599. those who are uploaded?
600. </p></div>
601.    </content>
602.    <updated>2017-05-06T04:06:33Z</updated>
603.    <category term="steam"/>
604.    <category term="documents"/>
605.    <author>
606.      <name>Martin Baehr</name>
607.      <email>mbaehr@community.gotpike.org</email>
608.    </author>
609.    <source>
610.      <id>http://societyserver.org/mbaehr</id>
611.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
612.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
613.      <title>DevLog</title>
614.      <updated>2017-05-06T04:10:03Z</updated>
615.    </source>
616.  </entry>
617.  
618.  <entry>
619.    <id>http://societyserver.org/mbaehr/Everlasting-Life-Through-Cyberspace</id>
620.    <link href="http://societyserver.org/mbaehr/Everlasting-Life-Through-Cyberspace" rel="alternate" type="text/html"/>
621.    <title>Everlasting Live Through Cyberspace</title>
622.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
623. <p>
624. The idea has been brought up a few times, that we would upload our minds into a
625. computer and in this way would be able to live forever.
626. </p>
627.  
628. <p>
629. How would that look like?
630. </p>
631.  
632. <p>
633. At it's base, every uploaded mind would represent a program with access to data
634. storage and computing resources. These programs can interact with each other
635. not unlike programs on the internet today. For example like in a virtual
636. reality game world. (Second Life, etc)
637. </p>
638.  
639. <p>
640. In uploaded form we would manipulate our environment through other programs,
641. that we create ourselves or that others create for us. There might be a market
642. to trade these programs and its products.
643. </p>
644.  
645. <p>
646. Now, anything that is programmable will have bugs and is exploitable, therefore
647. it will be necessary to protect against such attacks. Much like we use
648. encryption today to keep things private, encryption and self protection will
649. play a large role in such a cyberworld.
650. </p>
651.  
652. <p>
653. Unlike today where we can rely on physical protection, healtcare, etc to
654. support us, in cyberspace, all protection comes in form of programs, and that
655. means instead of relying on others to act in our behalf in order to pretect us,
656. every one of us will be able to get a copy of a protection program that we then
657. will be able to control by ourselves. It's all bits and bytes, so there is no
658. reason to assume that we would not be able to have full control over our
659. environment.
660. </p>
661.  
662. <p>
663. We could build cyberspace without these protections, but it is inconceivable
664. that anyone would accept a world where their own well being is not ensured.
665. Either from the outside, or from the inside. But if everyone is uploaded, then
666. there is no more outside, and therefore all protection must come from the
667. inside, through programs. And since even now, most people are not skilled
668. programmers, and that is unlikely to change much in the future, it is hard to
669. imagine that people would willingly enter a world where their life depends on
670. their programming skills. No, people must be able to trust that no harm will
671. come to them in this new world where they otherwise would not have the skill to
672. protect themselves.
673. </p>
674.  
675. <p>
676. The reason we feel safe in this world is because we agreed to a set of laws
677. which we enforce, and for the most part, crimes are visible and can be
678. persecuted. People who live in places where this is not the case don't feel
679. safe, and noone would willingly leave their save home to move to such an area.
680. </p>
681.  
682. <p>
683. In a cyberworld, such safety can only be achieved by making crime impossible to
684. begin with, because given enough resources, a computer program can do damage
685. without leaving a trace.
686. </p>
687.  
688. <p>
689. This has a few severe implications.
690. </p>
691.  
692. <p>
693. If real crime is impossible and we further have full control over our own
694. protection, controlling what data we receive that could possibly offend us,
695. then effectively we can no longer be hurt. There is no physical pain anyways,
696. and any virtual pain we could just switch of.
697. </p>
698.  
699. <p>
700. If we can not be hurt, the corollary is that we can not really hurt anyone.
701. We can not do anything that has any negative consequences on anyone else.
702. </p>
703.  
704. <p>
705. We can not even steal someones computing resources, or rather we probably could
706. but there would be no point because even if computing resources are unevenly
707. distributed, it would not matter.
708. </p>
709.  
710. <p>
711. There is no sense of time, since any sense of time is simulated and can be
712. controlled. So if we were trying to build something that takes lots of
713. time, we could adjust our sense of time so that we would not have to feel the
714. wait for the computation to complete. With that in mind, stealing resources
715. to make computation faster would become meaningless.
716. </p>
717.  
718. <p>
719. And if we could take all resources from someone, then that would effectively
720. kill them as their program could no longer run. It would be frozen in storage.
721. Allowing this could start a war of attrition that would end with one person
722. controlling everyone else and everyone fearing for their life. It just doesn't
723. make sense to allow that.
724. </p>
725.  
726. <p>
727. In other words we no longer have freedom to do evil. Or more drastically, we no
728. longer have complete free will. Free will implies the ability to chose evil.
729. Without that choice free will is limited.
730. </p>
731.  
732. <h3>In summary life in cyberspace has the following attributes:</h3>
733.  
734. <ul>
735. <li>
736. We will all live there eternally (well, as long as the computer keeps running).
737. </li>
738.  
739. <li>
740. There is no sense of time.
741. </li>
742.  
743. <li>
744. We will keep our sense of identity.
745. </li>
746.  
747. <li>
748. We will be able to interact with every human ever uploaded.
749. </li>
750.  
751. <li>
752. We will continue to advance and develop.
753. </li>
754.  
755. <li>
756. There is no power to do evil.
757. </li>
758.  
759. <li>
760. We will be able to affect the physical world, and the physical world will affect us.
761. </li>
762. </ul>
763.  
764.  
765. <h3>Here is how cyberspace looks like from the outside:</h3>
766.  
767.  
768. <ul>
769. <li>
770. When a person is uploaded, its physical body ceases to function and decays.
771. </li>
772.  
773. <li>
774. Everyone can be uploaded, there is no specific requirements or conditions
775. that would prevent anyone from being uploaded.
776. </li>
777.  
778. <li>
779. We are assuming that we will be able to communicate with those in cyberspace,
780. but imagine how it would look like if we could not communicate with an
781. uploaded person. We would then actually not be able to tell if they
782. successfully uploaded or not. We would in fact not even be able to tell
783. whether cyberspace exists at all, and we would have to take a leap of faith
784. that it is real.
785. </li>
786. </ul>
787.  
788. <p>
789. These attributes, are all attributes of life after death as described at least
790. by the baha'i faith, and possibly other religions.
791. </p>
792.  
793. <p>
794. So maybe, cyberspace already exists, and death is just the upload process?
795. Maybe we are simply not yet advanced enough to perceive or understand our life
796. beyond the point of upload from the outside?
797. </p>
798.  
799. <p>
800. Maybe we just need to evolve further before we are able to communicate with
801. those who are uploaded?
802. </p></div>
803.    </content>
804.    <updated>2017-05-06T04:06:33Z</updated>
805.    <category term="steam"/>
806.    <category term="documents"/>
807.    <author>
808.      <name>Martin Baehr</name>
809.      <email>mbaehr@community.gotpike.org</email>
810.    </author>
811.    <source>
812.      <id>http://societyserver.org/mbaehr</id>
813.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
814.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
815.      <title>DevLog</title>
816.      <updated>2017-05-06T04:20:02Z</updated>
817.    </source>
818.  </entry>
819.  
820.  <entry>
821.    <id>tag:omaciel.github.io,2016-09-13:podcasts-ive-been-listening-to-lately.html</id>
822.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/KcslXuKdUMo/podcasts-ive-been-listening-to-lately.html" rel="alternate" type="text/html"/>
823.    <title>Podcasts I've Been Listening To Lately</title>
824.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
825. <img alt="Podcasts" src="https://omaciel.fedorapeople.org/podcast-image.jpg"/>
826. </div>
827. <p>For someone who has run his own <a class="reference external" href="http://castalio.info/">podcast</a> for several years (albeit
828. not generating a lot of content lately), it took me quite some time to
829. actually start <em>listening</em> to podcasts myself. Ironic, I know, but I
830. guess the main reason behind this was because I was always reading
831. code at work and eventually, no matter how hard I tried, I just
832. couldn't pay attention to what was being said! No matter how
833. interesting the topic being discussed was or how engaging the hosts
834. (or hosts) were, my brain would be so focused on reading code that
835. everything else just turned into white noise.</p>
836. <p>Well, fast forward a couple of years and I still am reading code
837. (though not as much as I used to due to a new role), and I still have
838. a hard time listening to podcast while at work... so I decided to only
839. listen to them when I was <strong>not</strong> working. Simple, right? But it took
840. me a while to change that for some reason.</p>
841. <p>Anyhow, I now listen to podcasts while driving (which I don't really
842. do a lot of since I work from home 99.99% of the time) or when I go
843. for walks, and after a while I have started following a handful of
844. them which are now part of my weekly routine:</p>
845. <ul class="simple">
846. <li><a class="reference external" href="http://bookriot.com/listen/shows/allthebooks">All The Books</a> which provide me with an up to date list of
847. suggestions for what books to read next. They're pretty regular with
848. their episodes, so I can always count on listening about new books
849. pretty much every week.</li>
850. <li><a class="reference external" href="http://bookriot.com/listen/shows/thepodcast">Book Riot</a> for another dose of more news about books!</li>
851. <li><a class="reference external" href="http://hacktheentrepreneur.com/">Hack the Entrepreneur</a> to keep up with people who are making
852. something about what they are passionate about.</li>
853. <li><a class="reference external" href="https://howwegettonext.com/tagged/wonderland-podcast">Wonderland Podcast</a> which I only started listening to a few weeks
854. back but it has turned into one of my favorite.</li>
855. <li><a class="reference external" href="https://soundcloud.com/science-vs">Science Vs</a> another new addition to my list, with entertaining
856. takes at interesting topics such as 'the G-spot', 'Fracking', 'Gun
857. Control' and 'Organic Food'.</li>
858. </ul>
859. <p>Today I was introduced to <a class="reference external" href="http://www.npr.org/podcasts/510307/invisibilia">Invisibilia</a> and though I only listened to
860. the first 10 minutes (I was giving the link during working hours, so
861. no go for me), I'm already very interested and will follow it.</p>
862. <p>I do have other podcasts that I am still subscribed to, but these
863. listed here are the ones that I am still following every episode.
864. Maybe if I had to drive to work every day or went for walks more
865. often, maybe then I would listen to more podcasts? Trust me though, I
866. rather continue listening to only a small set of them than drive to
867. work every day. Don't get me wrong, I <strong>love</strong> going to work, but
868. that's 2 hours/day of my life that I rather spend at home :)</p>
869. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/KcslXuKdUMo" width="1"/></div>
870.    </content>
871.    <updated>2016-09-13T04:00:00Z</updated>
872.    <published>2016-09-13T04:00:00Z</published>
873.    <category term="podcasts"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/podcasts-ive-been-listening-to-lately.html</feedburner:origLink>
874.    <author>
875.      <name>Og Maciel</name>
876.    </author>
877.    <source>
878.      <id>https://omaciel.github.io/</id>
879.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
880.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
881.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
882.      <title>Journal of an Open Sourcee</title>
883.      <updated>2017-07-03T04:00:00Z</updated>
884.    </source>
885.  </entry>
886.  
887.  <entry>
888.    <id>tag:omaciel.github.io,2015-12-31:end-of-year-2015.html</id>
889.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/_O822pDZQ8Y/end-of-year-2015.html" rel="alternate" type="text/html"/>
890.    <title>End of Year - 2015</title>
891.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
892. <img alt="Review of 2015" src="https://omaciel.fedorapeople.org/bookshelf.jpeg"/>
893. </div>
894. <p>Another year has gone by and I guess it is time to review the things I
895. set out to do and grade myself on how well (or poorly) I fared. Here
896. are some of my goals for 2015:</p>
897. <div class="section" id="read-70-books">
898. <h2>Read 70 Books</h2>
899. <p>Grade: <strong>PASS</strong></p>
900. <p>Even though I had a very, very busy year at work, with many releases
901. of <strong>Red Hat Satellite 5</strong> and <strong>Red Hat Satellite 6</strong> shipped to our
902. customers, I managed to surpass my goal of reading 70 books, finishing
903. the year with a whopping <strong>79</strong> books read! You can see the books I
904. read here: <a class="reference external" href="https://www.goodreads.com/user/year_in_books/2015/12048315">Year in Books</a></p>
905. <p>This year I also spent a good chunk of my time looking at old, used
906. books, and my personal book collection increased considerably. At one
907. point I had so many piles of books lying around the house that I had
908. to buy 4 new book cases to store them. At first I wanted to have them
909. custom made, but the estimates I got from 3-4 different people were
910. way out of my budget. In the end I went with 4 <a class="reference external" href="http://www.ikea.com/us/en/catalog/products/40279788/#/40263848">Billy Bookcases</a> from
911. Ikea, which cost me about 10 times less!</p>
912. <p>If you want to see what I'm reading or want to recommend a book which
913. you think I might enjoy reading, please feel free to add me on
914. <a class="reference external" href="https://www.goodreads.com/omaciel">GoodReads</a>.</p>
915. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/_O822pDZQ8Y" width="1"/></div></div>
916.    </content>
917.    <updated>2015-12-31T05:00:00Z</updated>
918.    <published>2015-12-31T05:00:00Z</published>
919.    <category term="brno"/>
920.    <category term="czech republic"/>
921.    <category term="israel"/>
922.    <category term="2015"/>
923.    <category term="manager"/>
924.    <category term="books"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/end-of-year-2015.html</feedburner:origLink>
925.    <author>
926.      <name>Og Maciel</name>
927.    </author>
928.    <source>
929.      <id>https://omaciel.github.io/</id>
930.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
931.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
932.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
933.      <title>Journal of an Open Sourcee</title>
934.      <updated>2017-07-03T04:00:00Z</updated>
935.    </source>
936.  </entry>
937.  
938.  <entry>
939.    <id>tag:omaciel.github.io,2015-10-06:books-september-2015.html</id>
940.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/r1r9HGxHqK4/books-september-2015.html" rel="alternate" type="text/html"/>
941.    <title>Books - September 2015</title>
942.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
943. <img alt="Books - September 2015" src="https://omaciel.fedorapeople.org/book_review.png"/>
944. </div>
945. <div class="section" id="read">
946. <h2>Read</h2>
947. <ul class="simple">
948. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Selected+Short+Stories">Selected Short Stories</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Franz+Kafka">Franz Kafka</a> (<a class="reference external" href="https://www.goodreads.com/review/show/1378432779">review</a>)</li>
949. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Sense+and+Sensibility">Sense and Sensibility</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Jane+Austen">Jane Austen</a> (<a class="reference external" href="https://www.goodreads.com/review/show/1392989148">review</a>)</li>
950. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=A+Long+Way+Down">A Long Way Down</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Nick+Hornby">Nick Hornby</a> (<a class="reference external" href="https://www.goodreads.com/review/show/1359387724">review</a>)</li>
951. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Buddha,+Vol.+1:+Kapilavastu">Buddha, Vol. 1: Kapilavastu</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Osamu+Tezuka">Osamu Tezuka</a> (<a class="reference external" href="https://www.goodreads.com/review/show/1384819166">review</a>)</li>
952. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Water+Knife">The Water Knife</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Paolo+Bacigalupi">Paolo Bacigalupi</a> (<a class="reference external" href="https://www.goodreads.com/review/show/1386713795">review</a>)</li>
953. </ul>
954. </div>
955. <div class="section" id="reading">
956. <h2>Reading</h2>
957. <ul class="simple">
958. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Billy+Budd+and+Other+Stories">Billy Budd and Other Stories</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Herman+Melville">Herman Melville</a></li>
959. </ul>
960. </div>
961. <div class="section" id="gift">
962. <h2>Gift</h2>
963. <ul class="simple">
964. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Auto+da+Compadecida">Auto da ...</a></li></ul></div><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/r1r9HGxHqK4" width="1"/></div>
965.    </content>
966.    <updated>2015-10-06T04:00:00Z</updated>
967.    <published>2015-10-06T04:00:00Z</published>
968.    <category term="Rubem Fonseca"/>
969.    <category term="Saul Bellow"/>
970.    <category term="Osamu Tezuka"/>
971.    <category term="Herman Melville"/>
972.    <category term="Jane Austen"/>
973.    <category term="Clarice Lispector"/>
974.    <category term="Gilberto Freire"/>
975.    <category term="Franz Kafka"/>
976.    <category term="Jose de Alencar"/>
977.    <category term="Paolo Bacigalupi"/>
978.    <category term="William Faulkner"/>
979.    <category term="Jose Saramago"/>
980.    <category term="Joaquim Manuel de Macedo"/>
981.    <category term="Leo Tolstoy"/>
982.    <category term="Dias Gomes"/>
983.    <category term="Machado de Assis"/>
984.    <category term="Nick Hornby"/>
985.    <category term="Ariano Suassuma"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books-september-2015.html</feedburner:origLink>
986.    <author>
987.      <name>Og Maciel</name>
988.    </author>
989.    <source>
990.      <id>https://omaciel.github.io/</id>
991.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
992.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
993.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
994.      <title>Journal of an Open Sourcee</title>
995.      <updated>2017-07-03T04:00:00Z</updated>
996.    </source>
997.  </entry>
998.  
999.  <entry>
1000.    <id>tag:omaciel.github.io,2015-08-31:books-august-2015.html</id>
1001.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/CPd7hVOZgnk/books-august-2015.html" rel="alternate" type="text/html"/>
1002.    <title>Books - August 2015</title>
1003.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
1004. <img alt="Books - August 2015" src="https://omaciel.fedorapeople.org/book_review.png"/>
1005. </div>
1006. <p>This <strong>August 2015</strong> I took a break from work and spent about 6 days
1007. enjoying some R&R down the North Carolina shore with my family. I
1008. managed to get through some of the books that were waiting for a long
1009. time for me to get to them, as well as try some new authors.</p>
1010. <div class="section" id="read">
1011. <h2>Read</h2>
1012. <ul>
1013. <li><p class="first"><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Sentinel">The Sentinel</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Arthur+C.+Clarke">Arthur C. Clarke</a></p>
1014. <p>I forgot where I read about how the short story "The Sentinel" was the inspiration for "2001: A Space Odyssey", but being that I have always considered the latter a great book and movie, I managed to grab a copy of the anthology "The Sentinel" just so that I could read the short story by the same name and see what else Arthur C. Clarke "had to offer." Interestingly enough (to me), most if not all the other short stories included in this collection could easily be published today and still feel just as futuristic as they probably were back when they were first published! This was yet another one of the books that I read by the beach this Summer and though it didn't blow me away, it was still a very relaxing read.</p>
1015. </li>
1016. <li><p class="first"><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=A+Princess+of+Mars">A Princess of Mars</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Edgar+Rice+Burroughs">Edgar Rice Burroughs</a></p>
1017. <p>This last June I got from my family for my birthday "John Carter of Mars" containing the complete series and I was just itching for a good opportunity to start reading it. That chance came up this week as I started reading some of Melville's short stories and found that I needed a bit of a "break". First off, I have never read Edgar Rice Burroughs before but I do have a copy of "Tarzan of the Apes" also awaiting for a chance, so I had an idea about what to expect from his style. Sure enough, reading "A Princess of Mars" felt like a taking a trip down memory's lane, back when it was easy to tell who the good and the bad guys were, and there was always a damsel in distress somewhere waiting to be rescued. I have to confess that it took me a few chapters to get re-acclimated with this style, but once I got into it, it was easy reading, which is exactly what I was looking for any how.</p>
1018. <p>John Carter, the main character, shows all the expected, cliché virtues one would expect from a "hero" but one thing that bothered me a bit was the language he used to describe those who were different from him (which was mostly everyone in the story, since they were all Martians) and the way he treated them. It felt a bit abusive and even a but racist? I don't know if someone could get away with writing in the same style today, but then again I remembered that back then people were not as politically correct as we are today... or maybe I was reading too much into it? Anyhow, it was a fun read and I think I will try to add the next 4 books of the series in the coming months so that I can hopefully get a better opinion formed about the author.</p>
1019. </li>
1020. </ul>
1021. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/CPd7hVOZgnk" width="1"/></div></div>
1022.    </content>
1023.    <updated>2015-08-31T04:00:00Z</updated>
1024.    <published>2015-08-31T04:00:00Z</published>
1025.    <category term="Edgar Allan Poe"/>
1026.    <category term="Marcel Proust"/>
1027.    <category term="Franz Kafka"/>
1028.    <category term="Nikolai Gogol"/>
1029.    <category term="Bram Stoker"/>
1030.    <category term="William Golding"/>
1031.    <category term="Arthur C. Clarke"/>
1032.    <category term="Ray Bradbury"/>
1033.    <category term="Herman Melville"/>
1034.    <category term="Jane Austen"/>
1035.    <category term="Edgar Rice Burroughs"/>
1036.    <category term="Graciliano Ramos"/>
1037.    <category term="Stieg Larsson"/>
1038.    <category term="Shirley Jackson"/>
1039.    <category term="Nick Hornby"/>
1040.    <category term="Neil Gaiman"/>
1041.    <category term="Robert M. Pirsig"/>
1042.    <category term="John Steinbeck"/>
1043.    <category term="Flannery O'Connor"/>
1044.    <category term="Henry James"/>
1045.    <category term="Saul Bellow"/>
1046.    <category term="Lewis Carrol"/>
1047.    <category term="Dan Brown"/>
1048.    <category term="Milan Kundera"/>
1049.    <category term="Alexandre Dumas"/>
1050.    <category term="Henry Miller"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books-august-2015.html</feedburner:origLink>
1051.    <author>
1052.      <name>Og Maciel</name>
1053.    </author>
1054.    <source>
1055.      <id>https://omaciel.github.io/</id>
1056.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
1057.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
1058.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
1059.      <title>Journal of an Open Sourcee</title>
1060.      <updated>2017-07-03T04:00:00Z</updated>
1061.    </source>
1062.  </entry>
1063.  
1064.  <entry>
1065.    <id>http://societyserver.org/mbaehr/hiring-pike-programmers</id>
1066.    <link href="http://societyserver.org/mbaehr/hiring-pike-programmers" rel="alternate" type="text/html"/>
1067.    <title>Hiring Pike Programmers</title>
1068.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1069. <p>
1070. Once in a while i have someone reject to work with me because they don't know
1071. Pike.  What they are really saying is, that they are not willing to learn
1072. something new.
1073. </p>
1074.  
1075. <p>
1076. If you are a decent programmer, then learning a new programming language is not
1077. hard.  Technology changes all the time, and every year you'll learn new
1078. frameworks and tools.  That's part of your work.  So why shy away from learning
1079. a new language?
1080. </p>
1081.  
1082. <p>
1083. If you can't bring yourself to learn a new language then i suspect you'll also
1084. have a hard time learning anything else.  So actually i should thank you by
1085. refusing the job because of that.
1086. </p>
1087.  
1088. <h5>
1089. You say: learning a new language is hard.
1090. </h5>
1091.  
1092. <p>
1093. If you believe that, you haven't tried enough.  Sure, if you pick some of the
1094. more unusual languages like Haskell, it may be hard (but i don't know, i have
1095. not tried learning Haskell yet) and in general, learning your second language
1096. is probably the hardest (because the first language you learn, everything is
1097. new and you expect it to be hard, but with the second language maybe you fear
1098. it is as dificult as the first one, and you don't want to go through that
1099. again), also learning a new syntax may take some getting used to.
1100. </p>
1101.  
1102. <p>
1103. But all of these hurdles are measured in days.
1104. </p>
1105.  
1106. <p>
1107. Pike in particular has a syntax very close to C and Java. (that is, operations
1108. that are the same in C, Java and Pike also use the same syntax, with very few
1109. exceptions).  This makes the syntax also similar to Javascript, PHP, and the
1110. many other languages with a C-inspired syntax.  Picking that up should not be
1111. hard.
1112. </p>
1113.  
1114. <p>
1115. The rest is learning the Pike libraries and figuring out what makes Pike tick.
1116. You should have that down within a few weeks.
1117. </p>
1118.  
1119. <p>
1120. This is the same for pretty much any other language you might start to learn.
1121. </p>
1122.  
1123. <p>
1124. I am talking from experience here.  I'll give you a few examples:
1125. </p>
1126.  
1127. <p>
1128. At my first fulltime job i was hired for my Pike experience.  As a junior
1129. programmer who hadn't finished univeristy yet, i didn't really have any work
1130. history.  But i did have a number of Pike modules for the Roxen
1131. webapplicationserver that i could show off.
1132. </p>
1133.  
1134. <p>
1135. At the same time a university graduate was hired, who had not even seen Pike
1136. before joining the team.  Within a few weeks she was as productive as the rest
1137. of us, and having finished her studies she arguably knew more about programming
1138. and could explain more about Pike than i could.
1139. </p>
1140.  
1141. <p>
1142. At another job a few years later one of my managers who had just recently
1143. joined the company fell in love with Pike, and when he left he built his own
1144. company using Pike as the main development language.  This guy was not even a
1145. programmer.
1146. </p>
1147.  
1148. <p>
1149. When i came to china, my first job was for a python programmer.  I had learned
1150. python by then, but i had no practical experiece whatsoever.  I was allowed to
1151. do the programming tests in Pike (they had an automated testsuite, which of
1152. course could not handle Pike, so in my case the answers were reviewed manually.
1153. They had no problems reviewing their tests in a language they had never seen
1154. before.  That's how good they were).  One of the tests i did in python, and i
1155. passed and got the job.  I was productive from the start.
1156. </p>
1158. <p>
1159. A few years ago i hired 3 chinese students to work for me.  Since this was the
1160. first time i hired anyone, i was not sure how learning a new language would go
1161. down, on the first day, possibly their first experiene working with a foreigner
1162. too.  So the first project i gave them was in Java.  It was a Java client for
1163. the sTeam server.  Two of the students left after the summer holidays were
1164. over, but one stayed on, and his next project was in Pike.  Also for the sTeam
1165. server, so he could reuse his knowledge of the APIs that he learned during the
1166. Java project, but he did have to learn the language itself.  He was productive
1167. within a few days.
1168. </p>
1170. <p>
1171. Last year i was hired to help with a PHP project, using the Laravel framework.
1172. I had never really written PHP code before, but the framework was not so different
1173. from others (eg Django) so that i was productive immideately.  And i ended up
1174. fixing other peoples code too.
1175. </p>
1176.  
1177. <p>
1178. This summer, i was working with 3 students for Google Summer Of Code.  One
1179. student worked on the sTeam server, and had to learn Pike for that.  He did it
1180. during the get-to-know period and started churning out code from the first day
1181. of the coding-period.
1182. </p>
1184. <p>
1185. Another student picked a smalltalk project.  She learned smalltalk as soon as
1186. she picked the project, joined the pharo-smalltalk community and became a
1187. recognized contributor to the pharo 4.0 release.  All before her proposal for
1188. the GSOC project was even accepted.
1189. </p>
1191. <p>
1192. Convinced yet?
1193. </p>
1195. <h5>
1196. You say: Noone else uses Pike. It won't help me get a job.
1197. </h5>
1199. <p>
1200. That is probably true. But it is becoming less true as time goes by.
1201. </p>
1203. <p>
1204. One of the problems with hiring is that, just as you believe learning a new
1205. language is hard, so do the hiring managers, and thus they search only for
1206. programmers that already know the language that they will need to use.
1207. </p>
1208.  
1209. <p>
1210. In the Pike community too.  I was the only Pike programmer available who liked
1211. moving countries, and so i had my pick for jobs in the USA, in Germany, in New
1212. Zealand, in Latvia.  Thanks to Pike i got around.  Try that with a popular language.
1213. </p>
1214.  
1215. <p>
1216. Fortunately, this is changing.  Like my first China job, more companies
1217. recognizing the ability to learn as more important than a particular language.
1218. For them it won't matter which programming languages you learned, as long as
1219. you can demonstrate your learning skill.  In fact, learning an unknown language
1220. will let you stand out as someone serious about learning programming languages.
1221. </p>
1222.  
1223. <p>
1224. Learning new languages will also increase your confidence in your ability.  For
1225. that PHP job i was never asked how much PHP experience i had. I did make clear
1226. that i had no experience with Laravel, which is something they could not expect
1227. from everyone, even if they had plenty of PHP experiece. But i had experience
1228. with similar frameworks, and i was confident that i could pick up what i needed
1229. quickly.  And i proved it.
1230.  
1231. </p>
1232.  
1233. <p>
1234. When i am hiring programmers myself, i definetly don't care which languages they know.
1235. All i care is that they know at least two languages.  These people have at
1236. least gotten over the second language hump, and learning a third language will
1237. be a breeze.  Whether it's Pike or any other language.
1238. </p>
1239.  
1240. <p>
1241. </p>
1242.  
1243. <p>
1244. Stop telling me that you can't learn a new programming language.  You can!
1245. Because if you couldn't, you would not qualify as a programmer to begin with.
1246. At least, i would not hire you.
1247. </p></div>
1248.    </content>
1249.    <updated>2015-08-24T17:47:51Z</updated>
1250.    <category term="steam"/>
1251.    <category term="documents"/>
1252.    <author>
1253.      <name>Martin Baehr</name>
1254.      <email>mbaehr@community.gotpike.org</email>
1255.    </author>
1256.    <source>
1257.      <id>http://societyserver.org/mbaehr</id>
1258.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1259.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1260.      <title>DevLog</title>
1261.      <updated>2017-07-30T20:40:04Z</updated>
1262.    </source>
1263.  </entry>
1264.  
1265.  <entry>
1266.    <id>tag:omaciel.github.io,2015-07-29:books-july-2015.html</id>
1267.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/qHI81lr4ZEc/books-july-2015.html" rel="alternate" type="text/html"/>
1268.    <title>Books - July 2015</title>
1269.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
1270. <img alt="Books - July 2015" src="https://omaciel.fedorapeople.org/book_review.png"/>
1271. </div>
1272. <p>This <strong>July 2015</strong> I travelled to the <strong>Red Hat</strong> office in <strong>Brno, Czech Republic</strong> to spend some time with my teammates there, and I managed to get a lot of reading done between long plane rides and being jet lagged for many nights :) So I finally managed to finish up some of the books that had been lingering on my <em>ToDo</em> list and even managed to finally read a few of the books that together make up the <strong>Chronicles of Narnia</strong>, since I had never read them as a kid.</p>
1273. <div class="section" id="read">
1274. <h2>Read</h2>
1275. <ul class="simple">
1276. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Armada">Armada</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Ernest+Cline">Ernest Cline</a></li>
1277. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Memoirs+of+Sherlock+Holmes">The Memoirs of Sherlock Holmes</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Arthur+Conan+Doyle">Arthur Conan Doyle</a></li>
1278. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Horse+and+His+Boy">The Horse and His Boy</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=C.+S.+Lewis">C. S. Lewis</a></li>
1279. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Magician's+Nephew">The Magician's Nephew</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=C.+S.+Lewis">C. S. Lewis</a></li>
1280. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=All+Quiet+on+the+Western+Front">All Quiet on the Western Front</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Erich+Maria+Remarque">Erich Maria Remarque</a></li>
1281. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Managing+Humans:+Biting+and+Humorous+Tales+of+a+Software+Engineering+Manager">Managing Humans: Biting and Humorous Tales of a Software Engineering Manager</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Michael+Lopp">Michael Lopp</a></li>
1282. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Cryptonomicon">Cryptonomicon</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Neal+Stephenson">Neal Stephenson</a></li>
1283. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+October+Country">The October Country</a> by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Ray+Bradbury">Ray Bradbury</a></li>
1284. <li><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Lion,+the+Witch+and+the+Wardrobe">The Lion, the Witch and the Wardrobe</a> por <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=C.+S.+Lewis">C. S. Lewis</a></li>
1285. </ul>
1286. <p>Out of all the books I read this month, I feel that <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=All+Quiet+on+the+Western+Front">All Quiet on the Western Front</a> and <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+October+Country">The October Country</a> were the ones I enjoyed reading the most, closely followed by <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Cryptonomicon">Cryptonomicon</a>, which took me a while to get through. The other books, with the exception of <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+Memoirs+of+Sherlock+Holmes">The Memoirs of Sherlock Holmes</a>, helped me pass the time when I only wanted to be entertained.</p>
1287. <p><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=All+Quiet+on+the+Western+Front">All Quiet on the Western Front</a> takes the prize for being one of the best books I have ever read! I felt that the way <strong>WWI</strong> was presented through the eyes of the main character was a great way to represent all the pain, angst and suffering that all sides of conflict went through, without catering for any particular side or having an agenda. <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Erich+Maria+Remarque">Erich Maria Remarque</a>'s style had me some times breathless, some times with a knot on the pit of my stomach I as 'endured' the many life changing events that took place in the book. Is this an action-packed book about WWI? Will it read like a thriller? In my opinion, even though there are many chapters with gory details about killings and battles, the answer is a very bland 'maybe'. I think that the real 'star' of this book is its philosophical view of the war and how the main characters, all around 19-20 years of age, learn to deal with its life lasting effects.</p>
1288. <p>Now, I have been a huge fan of <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Ray+Bradbury">Ray Bradbury</a> for a while now, and when I got <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=The+October+Country">The October Country</a> for my birthday last month, I just knew that it would be time well spent reading it. For those of you who are more acquainted his science fiction works, this book will surprise you as it shows you a bit of  his 'darker' side. All of the short stories included in this collection deal with death, mysterious apparitions, inexplicable endings and are sure to spook you a little bit.</p>
1289. <p><a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Cryptonomicon">Cryptonomicon</a> was at times slow, some other times funny and, especially toward the end, a very entertaining book. Weighing in at a hefty 1000 pages (depending on the edition you have, plus/minus 50 odd pages), this book covers two different periods in the lives of a number of different characters, past (around <strong>WWII</strong>) and present, all different threads eventually leading to a great finale. Alternating between past and present, the story takes us to the early days of how <strong>cryptology</strong> was 'officially invented' and used during the war, and how many of the events that took place back then were affecting the lives of some of the direct descendants of the main characters in our present day. As you go through the back and forth you start to gather bits and pieces of information that eventually connects all the dots of an interesting puzzle. It definitely requires a long term commitment to go though it, but it was enjoyable and, as I mention before, it made me laugh at many places.</p>
1290. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/qHI81lr4ZEc" width="1"/></div></div>
1291.    </content>
1292.    <updated>2015-07-29T04:00:00Z</updated>
1293.    <published>2015-07-29T04:00:00Z</published>
1294.    <category term="Azar Nafisi"/>
1295.    <category term="Junot D&#xED;az"/>
1296.    <category term="Ernest Cline"/>
1297.    <category term="Arthur Conan Doyle"/>
1298.    <category term="Luciano Ramalho"/>
1299.    <category term="Harper Lee"/>
1300.    <category term="J. J. Abrams"/>
1301.    <category term="Ray Bradbury"/>
1302.    <category term="C. S. Lewis"/>
1303.    <category term="Neal Stephenson"/>
1304.    <category term="Raymond Chandler"/>
1305.    <category term="Mario Vargas Llosa"/>
1306.    <category term="Michael Lopp"/>
1307.    <category term="Erich Maria Remarque"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books-july-2015.html</feedburner:origLink>
1308.    <author>
1309.      <name>Og Maciel</name>
1310.    </author>
1311.    <source>
1312.      <id>https://omaciel.github.io/</id>
1313.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
1314.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
1315.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
1316.      <title>Journal of an Open Sourcee</title>
1317.      <updated>2017-07-03T04:00:00Z</updated>
1318.    </source>
1319.  </entry>
1320.  
1321.  <entry>
1322.    <id>tag:omaciel.github.io,2015-06-30:books-june-2015.html</id>
1323.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/8vW3gl-a-Ds/books-june-2015.html" rel="alternate" type="text/html"/>
1324.    <title>Books - June 2015</title>
1325.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure align-left" style="width: 40%;">
1326. <img alt="Books - June 2015" src="https://omaciel.fedorapeople.org/book_review.png"/>
1327. </div>
1328. <p>Those of you who know me know that I am a huge book reader and spend most of my free time reading several books at the same time. One could say that reading is one of my passions, and having wasted so many years after high school completely ignoring this passion (in exchange for spending most of my time trying to learn about <strong>Linux</strong>, get an education, a job and, let's be frank, chasing after girls), I decided that something had to be done about it, and starting around 2008 I 'forced' myself to dedicate at least one solid hour of reading <strong>for fun</strong> every day.</p>
1329. <p>I find it funny to say that I had to <strong>force</strong> myself, but this statement is very much true. Being so used to spending all of my time sitting in front of a computer and getting flooded with information every single minute of the day (IRC, Twitter, Facebook, commit emails, RSS feeds, etc), I found it difficult to 'unplug' and spend time doing nothing but focusing on only one thing. I was so used to multitasking and being constantly bombarded with lots of information that sitting quietly and reading didn't feel very productive to me... sad but true.</p>
1330. <p>Anyhow, after several 'agonizing' months of getting up from my desk and making a point of turning off my cel phone and finding a quiet place somewhere in the building (or at home during the weekends), I finally got into the habit of reading for pleasure. I actually looked forward to these reading periods (imagine that, huh?) and eventually I realized that if I skipped  this 'ritual' even one day, my days felt like they got longer and I felt stressed out and irritable for the remaining of the day. Reading became not only a good habit but my mechanism for relaxing and recharging my energies during the day!</p>
1331. <p>Well, this passion and appetite for reading has only gotten bigger, and with time I have to say that it has become a pretty big part of who I am today! In a way I am happy that it took me this long to get back into the habit of reading... I mean, I feel that getting older was an important part of preparing myself so that I could really appreciate <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=John+Steinbeck">John Steinbeck</a>, <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Ray+Bradbury">Ray Bradbury</a> and the likes of them! Would I have truly appreciated <strong>The Grapes of Wrath</strong> when I was younger? Perhaps... but it took me around 40 years to get to it and I'm happy that when it did I was able to appreciate this amazing piece of art!</p>
1332. <p>These last few months I decided that I wanted to start tracking all the books that I read, buy or receive as a gift every month (see my reading progress on <a class="reference external" href="https://www.goodreads.com/user/show/12048315-og-maciel">GoodReads</a> and add me as a friend), and jot down some of my impressions and motives for reading or buying them. Those familiar with <a class="reference external" href="https://www.goodreads.com/search?utf8=%E2%9C%93&amp;query=Nick+Hornby">Nick Hornby</a> will probably associate this post (and hopefully others that will surely come) with the work he has done writing for the <a class="reference external" href="http://www.believermag.com/">Believer Magazine</a> ... and this would be correct. My intention is not to copy his style or anything like that, but I thought that the format he chose to report on his own reading 'adventures' would fit in quite nicely with what I wanted to get across to my readers... and I'm sticking with the format as long as it works for me :)</p>
1333. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/8vW3gl-a-Ds" width="1"/></div>
1334.    </content>
1335.    <updated>2015-06-30T04:00:00Z</updated>
1336.    <published>2015-06-30T04:00:00Z</published>
1337.    <category term="Anton Chekhov"/>
1338.    <category term="Arthur Conan Doyle"/>
1339.    <category term="Luciano Ramalho"/>
1340.    <category term="Henry David Thoreau"/>
1341.    <category term="Marcel Proust"/>
1342.    <category term="Fyodor Dostoyevsky"/>
1343.    <category term="Sophocles"/>
1344.    <category term="Ray Bradbury"/>
1345.    <category term="Herman Melville"/>
1346.    <category term="Robert M. Pirsig"/>
1347.    <category term="J. J. Abrams"/>
1348.    <category term="Neal Stephenson"/>
1349.    <category term="Jim Whitehurst"/>
1350.    <category term="Graciliano Ramos"/>
1351.    <category term="Machado de Assis"/>
1352.    <category term="Nick Hornby"/>
1353.    <category term="Edgar Rice Burroughs"/>
1354.    <category term="Isaac Asimov"/>
1355.    <category term="Flannery O'Connor"/>
1356.    <category term="Jack London"/>
1357.    <category term="John Steinbeck"/>
1358.    <category term="Howard Mittelmark"/>
1359.    <category term="Michael Kelahan"/>
1360.    <category term="John Cheever"/>
1361.    <category term="Camus"/>
1362.    <category term="Jorge Amado"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books-june-2015.html</feedburner:origLink>
1363.    <author>
1364.      <name>Og Maciel</name>
1365.    </author>
1366.    <source>
1367.      <id>https://omaciel.github.io/</id>
1368.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
1369.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
1370.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
1371.      <title>Journal of an Open Sourcee</title>
1372.      <updated>2017-07-03T04:00:00Z</updated>
1373.    </source>
1374.  </entry>
1375.  
1376.  <entry>
1377.    <id>tag:blogger.com,1999:blog-3136133058831511247.post-5953345307091969989</id>
1378.    <link href="http://marktmisc.blogspot.com/feeds/5953345307091969989/comments/default" rel="replies" type="application/atom+xml"/>
1379.    <link href="http://www.blogger.com/comment.g?blogID=3136133058831511247&amp;postID=5953345307091969989" rel="replies" type="text/html"/>
1380.    <link href="http://www.blogger.com/feeds/3136133058831511247/posts/default/5953345307091969989" rel="edit" type="application/atom+xml"/>
1381.    <link href="http://www.blogger.com/feeds/3136133058831511247/posts/default/5953345307091969989" rel="self" type="application/atom+xml"/>
1382.    <link href="http://marktmisc.blogspot.com/2015/05/goodby-foresight.html" rel="alternate" type="text/html"/>
1383.    <title>Goodby Foresight</title>
1384.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Little more than a year ago I posted about the bright future of foresight linux.<br/>Well it looks like this won't happen any more.<br/>Yesterday Michael announced our decision to bury (or at least it feels like this) foresight linux.<br/>I've been involved in foresightlinux for ~ 10 years and it's hard when such a long period ends. I will miss foresight and the people that formed it.<br/>Special Thanks to Ken Vandine who started that whole thing 10+ years ago.<br/>Here is the announcement:<br/><br/><span>The Foresight Linux Council has determined that there has</span><br/><span>been insufficient volunteer activity to sustain meaningful new</span><br/><span>development of Foresight Linux. Faced with the need either to</span><br/><span>update the project's physical infrastructure or cease operations,</span><br/><span>we find no compelling reason to update the infrastructure.</span><br/><br/><span>Therefore, around the end of May, the following will be shut down:</span><br/><span>* Software repositories (Foresight Linux and legacy rBuilder Online</span><br/><span>  repositories)</span><br/><span>* JIRA and Confluence servers</span><br/><span>* Shared development infrastructure</span><br/><span>* Mailing lists, including these lists</span><br/><br/><span>The<span class="Apple-converted-space"> </span></span><a href="http://foresightlinux.org/" target="_blank">foresightlinux.org</a><span><span class="Apple-converted-space"> </span>domain will remain as an informal "alumni</span><br/><span>association" for an indefinite amount of time, along with the</span><br/><span>project IRC channels for as long as they are in use.</span><br/><br/><span>Volunteers to host read-only copies of the JIRA/Confluence</span><br/><span>and/or mailing list archives should respond to</span><br/><a href="mailto:foresight-devel@lists.foresightlinux.org">foresight-devel (at) lists.foresightlinux.org</a><span><span class="Apple-converted-space"> </span>in the next few days,</span><br/><span>while the lists are still operational.</span><br/><br/><span>Hosting the repositories in read-only mode would be non-trivial;</span><br/><span>requiring approximately 2.5TB of storage; simply moving the data</span><br/><span>would be a substantial task. Do not assume that the repository</span><br/><span>contents will be retained.</span><br/><br/><span>The Foresight Linux Council would like to extend our thanks to the</span><br/><span>Software Freedom Conservancy, our corporate home, for their support</span><br/><span>of Foresight Linux and of software freedom generally. We would also</span><br/><span>like to thank SAS Institute for providing physical infrastructure and</span><br/><span>hosting for the past two and a half years, as well as for offering</span><br/><span>to refresh the infrastructure. This decision to retire Foresight</span><br/><span>Linux was entirely the council's.</span><br/><br/><span>To those of us who have been a part of this community for up</span><br/><span>to ten years, this feels a little like a death. If you wish to</span><br/><span>celebrate the life of this project, please discuss soon on the</span><br/><a href="mailto:foresight-devel@lists.foresightlinux.org">foresight-devel (at) lists.foresightlinux.org</a><span><span class="Apple-converted-space"> </span>list or on IRC on the</span><br/><a href="http://freenode.net/" target="_blank">freenode.net</a><span><span class="Apple-converted-space"> </span>#foresight-devel channel when and how to do so.</span><br/><br/><span>On behalf of the Foresight Linux Council,</span><br/><br/><span>Michael K Johnson</span></div>
1385.    </content>
1386.    <updated>2015-05-13T05:48:34Z</updated>
1387.    <published>2015-05-13T05:48:00Z</published>
1388.    <author>
1389.      <name>Mark Trompell</name>
1390.      <email>noreply@blogger.com</email>
1391.      <uri>https://plus.google.com/107105581234887980823</uri>
1392.    </author>
1393.    <source>
1394.      <id>tag:blogger.com,1999:blog-3136133058831511247</id>
1395.      <category term="foresight"/>
1396.      <category term="xfce"/>
1397.      <category term="whaawmp"/>
1398.      <category term="fosdem"/>
1399.      <author>
1400.        <name>Mark Trompell</name>
1401.        <email>noreply@blogger.com</email>
1402.        <uri>https://plus.google.com/107105581234887980823</uri>
1403.      </author>
1404.      <link href="http://marktmisc.blogspot.com/feeds/posts/default" rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml"/>
1405.      <link href="http://www.blogger.com/feeds/3136133058831511247/posts/default" rel="self" type="application/atom+xml"/>
1406.      <link href="http://marktmisc.blogspot.com/" rel="alternate" type="text/html"/>
1407.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
1408.      <title>Nothing new under the sun</title>
1409.      <updated>2017-08-03T04:19:49Z</updated>
1410.    </source>
1411.  </entry>
1412.  
1413.  <entry>
1414.    <id>http://societyserver.org/mbaehr/training/building-an-api-with-zinc-rest-in-pharo-smalltalk</id>
1415.    <link href="http://societyserver.org/mbaehr/training/building-an-api-with-zinc-rest-in-pharo-smalltalk" rel="alternate" type="text/html"/>
1416.    <title>Building an API with Zinc-REST in Pharo Smalltalk</title>
1417.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1418. <p>
1419. In this session we are going to build a simple RESTful API using the Zinc-REST package.</p>
1420. <p>
1421. The base image is again Moose, now the latest build of Moose 5.1
1422. </p>
1423. <p>
1424. You may watch <a href="http://societyserver.org/scripts/Using-the-FileSystem-class-in-Pharo-Smalltalk">part one</a>, <a href="http://societyserver.org/scripts/Serving-files-through-FileSystem-in-Pharo-Smalltalk">part two</a> and <a href="http://societyserver.org/scripts/a-static-webapplication-hosted-on-pharo-smalltalk">part three</a> of this series if you are interested to find out what lead to this point. They are however not needed to be able to follow this session.
1425. </p>
1426. <video height="240" src="/mbaehr/training/Zinc-REST-Screencast-1.webm" width="320"><!-- SAX: Tag video invalid
1427. -->
1428. </video></div>
1429.    </content>
1430.    <updated>2015-02-28T17:23:13Z</updated>
1431.    <category term="steam"/>
1432.    <category term="documents"/>
1433.    <author>
1434.      <name>Martin Baehr</name>
1435.      <email>mbaehr@community.gotpike.org</email>
1436.    </author>
1437.    <source>
1438.      <id>http://societyserver.org/mbaehr</id>
1439.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1440.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1441.      <title>DevLog</title>
1442.      <updated>2017-07-30T20:40:04Z</updated>
1443.    </source>
1444.  </entry>
1445.  
1446.  <entry>
1447.    <id>http://societyserver.org/mbaehr/training/a-static-webapplication-hosted-on-pharo-smalltalk</id>
1448.    <link href="http://societyserver.org/mbaehr/training/a-static-webapplication-hosted-on-pharo-smalltalk" rel="alternate" type="text/html"/>
1449.    <title>A static webapplication hosted on Pharo Smalltalk</title>
1450.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1451. <p>
1452. For part three of our workshop series we start from scratch, and build a small website that hosts nothing but static files from a  memory FileSystem.</p>
1453. <p>
1454. We are also going to explore the new development tools that are built in the <a href="http://www.moosetechnology.org/">Moose</a> project
1455. </p>
1456. <p>
1457. You may watch <a href="http://societyserver.org/scripts/Using-the-FileSystem-class-in-Pharo-Smalltalk">the first</a> and <a href="http://societyserver.org/scripts/Serving-files-through-FileSystem-in-Pharo-Smalltalk">second parts</a> of this series, or you may jump right in here.
1458. </p>
1459. <video height="240" src="/mbaehr/training/User-Role-Manager-Screencast-1.webm" width="320"><!-- SAX: Tag video invalid
1460. -->
1461. </video>
1462.  
1463. <p>In the <a href="http://societyserver.org/scripts/building-an-api-with-zinc-rest-in-pharo-smalltalk">next session</a> we are going to build the RESTful API to make this application functional</p></div>
1464.    </content>
1465.    <updated>2015-02-28T17:20:34Z</updated>
1466.    <category term="steam"/>
1467.    <category term="documents"/>
1468.    <author>
1469.      <name>Martin Baehr</name>
1470.      <email>mbaehr@community.gotpike.org</email>
1471.    </author>
1472.    <source>
1473.      <id>http://societyserver.org/mbaehr</id>
1474.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1475.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1476.      <title>DevLog</title>
1477.      <updated>2017-07-30T20:40:04Z</updated>
1478.    </source>
1479.  </entry>
1480.  
1481.  <entry>
1482.    <id>http://societyserver.org/mbaehr/training/Serving-files-through-FileSystem-in-Pharo-Smalltalk</id>
1483.    <link href="http://societyserver.org/mbaehr/training/Serving-files-through-FileSystem-in-Pharo-Smalltalk" rel="alternate" type="text/html"/>
1484.    <title>Serving files through FileSystem in Pharo Smalltalk</title>
1485.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1486. <p>In the second part of this series we transform our website to serve all content as files from a FileSystem object.</p>
1487. <p>If you haven't yet, take a look at <a href="http://societyserver.org/scripts/Using-the-FileSystem-class-in-Pharo-Smalltalk">part 1</a></p>
1488. <p>
1489. <video height="240" src="/mbaehr/training/pharo-FileSystem-part-2.webm" width="320"><!-- SAX: Tag video invalid
1490. -->
1491. </video>
1492. </p>
1493. <p>In the <a href="http://societyserver.org/scripts/a-static-webapplication-hosted-on-pharo-smalltalk">next session</a> we will serve an actual web-application</p>
1494. <!-- SAX: Unexpected end tag : p
1495. --></div>
1496.    </content>
1497.    <updated>2015-02-13T08:41:12Z</updated>
1498.    <category term="steam"/>
1499.    <category term="documents"/>
1500.    <author>
1501.      <name>Martin Baehr</name>
1502.      <email>mbaehr@community.gotpike.org</email>
1503.    </author>
1504.    <source>
1505.      <id>http://societyserver.org/mbaehr</id>
1506.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1507.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1508.      <title>DevLog</title>
1509.      <updated>2017-07-30T20:40:04Z</updated>
1510.    </source>
1511.  </entry>
1512.  
1513.  <entry>
1514.    <id>http://societyserver.org/mbaehr/training/Using-the-FileSystem-class-in-Pharo-Smalltalk</id>
1515.    <link href="http://societyserver.org/mbaehr/training/Using-the-FileSystem-class-in-Pharo-Smalltalk" rel="alternate" type="text/html"/>
1516.    <title>Using the FileSystem class in Pharo Smalltalk</title>
1517.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1518. <p>I am learning how to build a <a href="http://labs.fossasia.org/posts/smalltalk-REST-api.html">website with a RESTful API</a> in <a href="http://pharo.org/">Pharo</a> Smalltalk. This project started during Google Code-In as a set of tasks for students to work on. A handful of students were interested and picked up tasks to learn Pharo.</p>
1519.  
1520. <p>Now that Google Code-In is over, the students are interested to continue learning and so i am running workshops with them, where we explore the tools needed to build this server.</p>
1521.  
1522. <p>The first workshop was held last week on sunday the 25th, and the next one will be on saturday the 31st of Jnauary. from 2pm to 6pm chinese time, that is 7am to 11am CET or 6am to 10am UTC.
1523.  We will meet on freenode irc in the channels #fossasia and #pharo.</p>
1524.  
1525. <p>A part of website consists of static files. To simplify development and deployment, we want to serve those files from the smalltalk image. One way to hold several documents inside an image is using a memory FileSystem.  The FileSystem class is described in the book "<a href="http://rmod.lille.inria.fr/pbe2/">Deep into Pharo</a>" in chapter 3.</p>
1526.  
1527. <p>In the first workshop we try to use the FileSystem class in a sample application. We use the tutorial "<a href="http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/">Building and deploying your first web app with Pharo</a>" as a starting point, and adapt the code to store images in a FileSystem object.</p>
1528.  
1529. <p>If you want to follow along, please first complete the <a href="http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/">tutorial</a> and then watch the screencast below to continue:</p>
1530.  
1531. <p><video height="240" src="/mbaehr/training/pharo-FileSystem-part-1.webm" width="320"><!-- SAX: Tag video invalid
1532. -->
1533. </video> </p>
1534.  
1535. <p>In the <a href="http://societyserver.org/scripts/Serving-files-through-FileSystem-in-Pharo-Smalltalk">next session</a> we will convert the rest of the website to using our FileSystem object.</p></div>
1536.    </content>
1537.    <updated>2015-02-03T05:41:51Z</updated>
1538.    <category term="steam"/>
1539.    <category term="documents"/>
1540.    <author>
1541.      <name>Martin Baehr</name>
1542.      <email>mbaehr@community.gotpike.org</email>
1543.    </author>
1544.    <source>
1545.      <id>http://societyserver.org/mbaehr</id>
1546.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1547.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1548.      <title>DevLog</title>
1549.      <updated>2017-07-30T20:40:04Z</updated>
1550.    </source>
1551.  </entry>
1552.  
1553.  <entry>
1554.    <id>http://societyserver.org/mbaehr/the-community-calendar-project-at-google-code-in</id>
1555.    <link href="http://societyserver.org/mbaehr/the-community-calendar-project-at-google-code-in" rel="alternate" type="text/html"/>
1556.    <title>the community calendar project at google code in</title>
1557.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1558. <p>For the community-calendar project in total, 11 tasks were proposed, of which 7 got completed:</p>
1559.  
1560. <ul>
1561. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5242785342947328">Style the event list for the community-calendar project</a> (angular.js, coffeescript, html, css)</li>
1562. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5305646886944768">Add an event submission form to the community-calendar project</a> (angular.js, coffeescript, html, css)</li>
1563. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5831267048226816">explore and document the API used by the community-calendar</a> (coffeescript, REST, pike)</li>
1564. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5864190791122944">testing the community-calendar REST API</a> (javascript, REST, testing)</li>
1565. </ul>
1566.  
1567. <p>Not so much work got done on the code itself, but we now have some documentation of the API as well as the start of a testing framework to help keep the API stable.</p>
1568.  
1569. <p>As a sideproject, these tasks were designed to explore the ember.js framework. the calendar-widget, going to be embedded into different websites was a good target because we now can offer both versions for embedding.</p>
1570. <ul>
1571. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5528286918606848">rewrite the community-calendar with ember.js or another framework</a> (javascript, coffeescript, angular.js, ember.js)</li>
1572. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5910835612352512">explore how to create a complex component with ember.js</a> (javascript, ember.js)</li>
1573. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/6429977570443264">compare angular.js and ember.js by using the community calendar as an example</a> (angular.js, ember.js, javascript, coffeescript)</li>
1574. </ul>
1575.  
1576. <p>For ember.js the student, samarjeet wrote about the work in his weblog. An initial comparison: <a href="http://sharpcoderock.blogspot.in/2015/01/comparing-community-calendar.html">Comparing the community-calendar</a><br/>
1577. <a href="http://sharpcoderock.blogspot.de/2015/01/creating-ember-components.html">Creating Ember Components</a> turned out to be more dificult, and we had to enlist outside help to solve it.<br/>
1578. Finally, a deeper comparison of <a href="http://sharpcoderock.blogspot.in/2015/01/angularjs-vs-emberjs.html">Angular.js vs. Ember.js</a></p>
1579.  
1580. <p>This leaves us with 4 tasks that were not worked on</p>
1581. <ul>
1582. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5270724960845824">continue to explore and document the API used by the community-calendar</a> (coffeescript, REST, pike)</li>
1583. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5791175759888384">make the community-calendar widget embeddable into an angular.js website</a> (angular.js, javascript, coffeescript)</li>
1584. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5868277184069632">make event submission work in the community-calendar project</a> (angular.js, coffeescript, REST)</li>
1585. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5209409017872384">Add a calendar widget to the community-calendar project</a> (angular.js, coffeescript, html, css)</li>
1586. </ul></div>
1587.    </content>
1588.    <updated>2015-01-31T09:19:07Z</updated>
1589.    <category term="steam"/>
1590.    <category term="documents"/>
1591.    <author>
1592.      <name>Martin Baehr</name>
1593.      <email>mbaehr@community.gotpike.org</email>
1594.    </author>
1595.    <source>
1596.      <id>http://societyserver.org/mbaehr</id>
1597.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1598.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1599.      <title>DevLog</title>
1600.      <updated>2017-07-30T20:40:04Z</updated>
1601.    </source>
1602.  </entry>
1603.  
1604.  <entry>
1605.    <id>http://societyserver.org/mbaehr/csdn-interview</id>
1606.    <link href="http://societyserver.org/mbaehr/csdn-interview" rel="alternate" type="text/html"/>
1607.    <title>csdn interview</title>
1608.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1609. <p>I have been interviewed by <a href="http://www.csdn.net">CSDN</a>. The interview has been <a href="http://code.csdn.net/news/2823665">published today in chinese</a>.
1610. </p>
1611. <p>
1612. The original english answers as i sent them are below:</p>
1613.  
1614. <p>
1615.  </p><h3>1. Could you introduce yourself to us first?</h3>
1616.  
1617. <p>
1618.    I am using and developing Free Software and Open Source for more than 20
1619.    years.  I am a contributor to the Pike programming language, the Foresight
1620.    Linux distribution and several other Free Software Projects.  I co-edited a
1621.    book on Pike and organized developer conferences. I am also a mentor at
1622.    FOSSASIA. Throughout my career I focused on developing and advocating Free
1623.    Software. I have lived and worked in several countries around our planet
1624.    Earth.  I came to china in 2008.  I am currently the CTO at eKita, a startup
1625.    in Bangkok, and the General Manager at Realsoftservice, a Linux service firm
1626.    in Beijing where i offer software development, training and internships. I
1627.    live in Beijing with my family.
1628. </p>
1629.  
1630. <h3>2. Compared with your own country, what attracts you most in China or Beijing?</h3>
1631.  
1632. <p>
1633.    China (and Asia in general) has a different culture from western countries.
1634.    Learning chinese culture allows me to look at situations from a different
1635.    perspective.
1636. </p>
1637. <p>
1638.    I believe that all the world should be united into one country. And in order
1639.    to do that we need to understand the different parts of the world, what
1640.    everyone can contribute to this world, and what unifies us.
1641. </p>
1642. <p>
1643.    China is a large part of this world, and also not much is known about
1644.    china outside of it. The only way to learn about china is to be here.
1645. </p>
1646. <p>
1647.    China is also huge. I like to travel, and china allows me to travel long
1648.    distances to places that are very different from each other without having to
1649.    cross any borders.
1650. </p>
1651.  
1652. <h3>3. What is your role in BLUG? Could you describe the important development milestones of BLUG?</h3>
1653.  
1654. <p>
1655.    I am acting as the secretary. That means i help to arrange meetings and events for the group.
1656. </p>
1657. <p>
1658.    I joined the BLUG in 2008 and i am not familiar with the history before.
1659.    One important event before i joined was the 2007 Software Freedom Day which
1660.    was chosen as the best SFD event for that year.
1661. </p>
1662. <p>
1663.    At the time, when i joined, the BLUG had monthly meetings, frequent quan'r
1664.    dinners and BLUG Tuesday events. We also had a group aiming to build a
1665.    quadcopter and a library. Active members were both foreigners and chinese.
1666. </p>
1667. <p>
1668.    In summer 2008 an intern at Exoweb where i worked at the time, together with me
1669.    initiated a hackaton event called "Coding For Fun". I then continued hosting
1670.    the event by myself as part of the BLUG. When i left Beijing other BLUG members
1671.    continued hosting the event.
1672. </p>
1673. <p>
1674.    When I came back to Beijing some active members had left. I took over the
1675.    management of the group in 2013, when most active members had left. At that
1676.    time active participation was very low.  I continued running the monthly
1677.    meetings and Coding For Fun events. In Autumn we re-started BLUG Tuesday and
1678.    used it to test new meeting locations. That way we found our current meeting
1679.    place.
1680. </p>
1681. <p>
1682.    We slowly regained new active members, most of them chinese.
1683. </p>
1684.  
1685. <h3>4. What kind of difficulties have BLUG encountered in the process of development， and how to solve them?</h3>
1686.  
1687. <p>
1688.    The main difficulty we have is finding good locations for the meeting and
1689.    Coding For Fun events. It is still an unsolved problem. We don't have
1690.    sponsors to pay for using locations, so we rely on offers for places we can use
1691.    for free.
1692. </p>
1693.  
1694. <h3>5. What are the daily activities in BLUG? Do you (or BLUG) have any interactions with other communities?</h3>
1695.  
1696. <p>
1697.    I am trying to visit and keep relations with every group that i can find in Beijing.
1698.    I am regularly participating at events from the Beijing Open Party, Ruby,
1699.    Python, Angular.js meetups. Barcamp and more.
1700. </p>
1701. <p>
1702.    Most of these groups have Linux users, but as i am a programmer, many groups
1703.    are interesting to me personally too.
1704. </p>
1705. <p>
1706.    We also work with other groups to organize events, for example the Software
1707.    Freedom Day. or we support conferences like GNOME.asia and FUDcon or the
1708.    OpenSUSE summit, all of which had volunteers who are BLUG members.
1709. </p>
1710. <p>
1711.    We also participated at Google Code-In with FOSSASIA.
1712. </p>
1713.  
1714. <h3>6. Have you ever attended open source activities in other countries or regions?</h3>
1715. <h3>What are the differences between other countries and China in Open-source activities?</h3>
1716.  
1717. <p>
1718.    Every place and every country i have lived in, i participate in the local activities.
1719.    These vary in size and regularity. In some cases my visit was the motivation for
1720.    a group to have more meetings. In most groups the meeting involved some form of
1721.    topic presentation and discussion. But sometimes it was just going out for dinner.
1722.    Really not much different from china.
1723. </p>
1724.  
1725. <h3>7. From your personal point of view, could you share with us some tips on how to manage one open source community successfully?</h3>
1726.  
1727. <p>
1728.    Well, there are different kinds of communities, for example those that revolve
1729.    around a particular software project where all members in some form contribute
1730.    to that software project. The contributions to such projects are often
1731.    motivated by the contributors own needs.  The main goal for community
1732.    managers is to get active contributors to the project.
1733. </p>
1734. <p>
1735.    Other communities are more loose where people just share a common ideal, but
1736.    actually may contribute to different projects.
1737. </p>
1738. <p>
1739.    The BLUG is of the latter kind. People contribute to the BLUG more out of a
1740.    desire to serve the community than out of a personal need. And many do not
1741.    contribute to the BLUG directly.
1742. </p>
1743. <p>
1744.    The goal of the BLUG is to provide a venue for Free Software contributors and
1745.    users to share and meet like-minded people.
1746.    Most Free Software Communities are spread all over the world, whereas groups
1747.    like the BLUG are very local.
1748. </p>
1749. <p>
1750.    To manage a local group, i believe persistence would be the most important aspect.
1751.    If the group has meetings, they should be regular, so that new people can
1752.    easily find out when and where the meetings happen. Then it takes a while for
1753.    the word to spread, and attendance to grow. Keep holding the meetings, even if
1754.    only two or three people join. Then keep advertising the group and invite new
1755.    people. Eventually more will join and come back regularly.
1756. </p>
1757.  
1758. <h3>8. Could you introduce us some active and outstanding members in BLUG?</h3>
1759.  
1760. <p>
1761.    It is difficult to praise the contributions of some people without unjustly
1762.    leaving out others. Moreover i don't even know all the contributions of every member.
1763.    Some members don't come to the meeting often but they are very active elsewhere
1764.    in the Free Software and Open Source Community. This is one of the things that
1765.    tends to be miss-understood about the Free Software community.
1766. </p>
1767. <p>
1768.    Some people worry if they release their work with a Free Software license, then
1769.    others can take advantage of it without giving anything back. But we don't know
1770.    if those users are not active somewhere else making contributions to our
1771.    society in other ways.
1772. </p>
1773. <p>
1774.    This is after all what i believe is the purpose of our life.
1775.    All Men have been created to carry forward an ever-advancing civilization.
1776.    (人人生æ?¥æ˜¯ä¸ºäº†æŽ¨åŠ¨æ–‡æ˜Žä¸?断进步的)
1777. </p>
1778.  
1779. <h3>9. GNU project founder Richard Stallman came to China in May, 2014, did you have a meet with him?</h3>
1780. <h3>And what do you think about the Free Software campaign leaded by Richard Stallman since 1980th?</h3>
1781.  
1782. <p>
1783.    I have met richard stallman a few times before, but never had much direct
1784.    interaction with him. This year he joined us for a BLUG Dinner. As for his
1785.    campaign, i fully support the idea of Free Software. I believe that all
1786.    knowledge should be shared, and everyone should have the opportunity to use all
1787.    of the worlds knowledge in their work. To fulfill the purpose of life we should
1788.    all use our work to contribute to society. And allowing others to use and
1789.    modify our software is a great and very easy way of doing that.
1790. </p>
1791.  
1792. <h3>10. The last one, could you reveal to us the BLUG's future development plan, and what kind of activity will be organized in the future days?</h3>
1793.  
1794. <p>
1795.    Future plans of the BLUG depend on its members. For now my goal is to get more
1796.    active members, people who help to host events, give talks, or help contribute
1797.    to our website. The BLUG website is very old and in dire need of an upgrade.
1798.    but it is difficult to do if we want to keep all the data.
1799. </p>
1800. <p>
1801.    I am also trying to work on a community calendar where we can share all events
1802. </p>
1803. <!-- SAX: Unexpected end tag : p
1804. --></div>
1805.    </content>
1806.    <updated>2015-01-29T08:13:08Z</updated>
1807.    <category term="steam"/>
1808.    <category term="documents"/>
1809.    <author>
1810.      <name>Martin Baehr</name>
1811.      <email>mbaehr@community.gotpike.org</email>
1812.    </author>
1813.    <source>
1814.      <id>http://societyserver.org/mbaehr</id>
1815.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1816.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1817.      <title>DevLog</title>
1818.      <updated>2017-07-30T20:40:04Z</updated>
1819.    </source>
1820.  </entry>
1821.  
1822.  <entry>
1823.    <id>http://societyserver.org/mbaehr/learning-smalltalk-with-Google-Code-In</id>
1824.    <link href="http://societyserver.org/mbaehr/learning-smalltalk-with-Google-Code-In" rel="alternate" type="text/html"/>
1825.    <title>learning smalltalk with Google Code In</title>
1826.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
1827. <p>
1828. For years i have been meaning to learn smalltalk. my first exploration started about 10 years ago while teaching two children to make a game with squeak. Then i worked through a tutorial about making a simple game. Unfortunately it didn't capture my interest. So the my attempts to learn smalltalk were stalled as i searched for a project that i could do with it.
1829. </p>
1830.  
1831. <p>
1832. Why do i want to learn smalltalk? Because it is the first object-oriented language. Many of the OO concepts were invented in smalltalk. There is also the concept of working in an image that not only contains my code but also a full IDE which is used to update my code at runtime. Updating code at runtime is a concept that has been with me for more than 20 years now, ever since i started programming MUDs in LPC and writing modules for the Spinner/Roxen webserver in Pike. Pike allows recompiling classes at runtime. Any new instances will be made from the new class, while old instances remain as is. If the compilation fails, the class is not replaced and the old class continues to work. This way it is possible to make changes on a live server without restarting and disrupting ongoing requests. A decade later i discovered sTeam, the platform that also drives this very website. It takes this process even further: sTeam persists code and objects in a database. While in Roxen objects live as long as it takes to process a request, in sTeam objects are permanent, much like in a smalltalk image. sTeam then adds the capability to update live objects with new class implementations. The image concept of smalltalk is therefore already very familiar, and the major difference is smalltalk's GUI.
1833. </p>
1834.  
1835. <p>
1836. Recently a friend asked me what it would take to build a text search application for the Baha'i writings in chinese. There is one for english and other western languages, but not for chinese, and it does not run on mobile devices. It is also not Free Software, so i can't use it as a base to improve. But i didn't really want to take on a new project either so i just filed the idea for the time being.
1837. </p>
1838.  
1839. <p>
1840. One of my customers is managing access to several internal resources through htaccess and htpasswd. Because they have many interns who need to have access to some of these, and because they are now spread over multiple servers, it is becoming more and more cumbersome to manage them manually via these files. It also does not help that a salt module which we could use to help depends on apache helpers, which we can not install because apache conflicts with nginx which we are using. So i started exploring alternatives. One such alternative is a different way for nginx to verify access. It can make a request to an external service which then grants or rejects access depending on the resource and credentials. This could be implemented as a webservice with a webinterface to manage the users. I looked for some existing applications that would get me part of the way but i found nothing suitable.
1841. </p>
1842.  
1843. <p>
1844. <strong>Enter Google Code-In:</strong> FOSSASIA invited the BLUG to join them as mentors.
1845. </p>
1846.  
1847. <p>
1848. At first i put up tasks for the community-calendar project, but then i realized that this was an opportunity to explore new ideas. Figuring that teaching is the best way to learn i put up those project ideas as tasks for the students. I could ask students to learn and explore, and finally work on those projects. I would pick the technology and guide the students through a sequence of tasks to acquire the skills needed to implement the actual applications. This was my chance to get back into smalltalk. Since code-In targets middle and highschool students, it is quite unlikely that any of them already know smalltalk, or have even heared about it. so in a way this will introduce a few students to smalltalk. I picked pharo because i feel it is going in the right direction trying to improve itself and also adding things like commandline support.
1849. </p>
1850.  
1851. <p>
1852. The desktop application was straight-forward: find out how to embed text-documents in the image and make them searchable.
1853. </p><ul>
1854. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5902940472606720">create a text reader prototype</a> (completed)</li>
1855. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5904045940146176">add search and categories</a></li>
1856. </ul>
1857. <!-- SAX: Unexpected end tag : p
1858. -->
1859.  
1860. <p>The web application took more exploration. I wanted to do it with a RESTful api and a javascript frontend. Again, the frontend was easy to define: create a user management interface. For the backend, the question was which webframework to use? AIDA/web has builtin user management and REST style url support by default. Seaside includes a REST module, but both are strong on generating html which i am not interested in. Then there is iliad, which appears more lightweight. Eventually i figured i could just let the students explore each, and i created a task for each tutorial that i could find:
1861. </p><ul>
1862. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5786620192096256">seaside part 1</a> (<a href="https://iamikram.wordpress.com/2014/12/25/my-experience-with-seaside-framework-on-pharo-smalltalk/">completed</a>)
1863.    <a href="https://www.google-melange.com/gci/task/view/google/gci2014/5822893606830080">part 2</a> (<a href="https://iamikram.wordpress.com/2014/12/31/going-deep-with-seaside-and-pharo-d/">completed</a>)
1864.       <a href="https://www.google-melange.com/gci/task/view/google/gci2014/5007750153109504">part 3</a></li>
1865. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5884354588835840">seaside</a> (alternate tutorial)</li>
1866. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5858171612561408">aida/web</a> (<a href="http://awblog.blog.com/2014/12/21/hello-world-creating-a-simple-webpage-with-the-aidaweb-framework-on-pharo-smalltalk/">done</a>)
1867.   (<a href="https://www.google-melange.com/gci/task/view/google/gci2014/5897100306939904">reopened</a>)</li>
1868. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5888240192061440">iliad</a> (<a href="http://awblog.blog.com/2014/12/22/hello-world-creating-a-simple-webpage-with-the-iliad-framework-on-pharo-smalltalk/">done</a>)
1869.   (<a href="https://www.google-melange.com/gci/task/view/google/gci2014/5844083767508992">reopened</a>)</li>
1870. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5291284432420864">tide</a></li>
1871. </ul>
1872. (some of these i repeated because the student who did the them first time didn't pick up the follow-up tasks.)
1873. <!-- SAX: Unexpected end tag : p
1874. -->
1875.  
1876.  
1877. <p>Finally i discovered that Zinc, the HTTP server used by most frameworks is powerful enough to build a RESTful API without all the templating extras that the above frameworks provide. I also discovered teapot, a microframework that might be useful.
1878. </p><ul>
1879. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5906919541702656">zinc</a></li>
1880. </ul>
1881. <!-- SAX: Unexpected end tag : p
1882. -->
1883.  
1884.  
1885. <p>Once the students are familiar with the smalltalk environment, they can move on to the next steps:
1886. </p><ul>
1887. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5814729360539648">learn how to serve static files</a></li>
1888. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5880541949722624">create the RESTful API</a></li>
1889. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5046486547038208">create the whole user-management application</a></li>
1890. </ul>
1891. <!-- SAX: Unexpected end tag : p
1892. -->
1893.  
1894. <p>Of course there are also tasks for the front-end
1895. </p><ul>
1896. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5905960371486720">create the frontend</a> (completed)</li>
1897. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5240815429353472">make it work with the REST backend</a></li>
1898. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/6472822016704512">learn amber</a> (a href="https://github.com/amroto/Amber-Tutorial"&gt;completed<!-- SAX: Unexpected end tag : a
1899. -->
1900. </li>
1901. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5825641580593152">rewrite the front-end in amber</a></li>
1902. </ul>
1903. <!-- SAX: Unexpected end tag : p
1904. -->
1905.  
1906. <p>Related is also this task about a file editor, which i believe should make it easier to edit static assets like html and css pages from within the image:
1907. </p><ul>
1908. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5231805040951296">create a file-editor</a></li>
1909. </ul>
1910. <!-- SAX: Unexpected end tag : p
1911. --></div>
1912.    </content>
1913.    <updated>2015-01-01T15:18:53Z</updated>
1914.    <category term="steam"/>
1915.    <category term="documents"/>
1916.    <author>
1917.      <name>Martin Baehr</name>
1918.      <email>mbaehr@community.gotpike.org</email>
1919.    </author>
1920.    <source>
1921.      <id>http://societyserver.org/mbaehr</id>
1922.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
1923.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
1924.      <title>DevLog</title>
1925.      <updated>2017-07-30T20:40:04Z</updated>
1926.    </source>
1927.  </entry>
1928.  
1929.  <entry>
1930.    <id>tag:omaciel.github.io,2014-12-31:2014-in-book-covers.html</id>
1931.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/rT_17o_RWLU/2014-in-book-covers.html" rel="alternate" type="text/html"/>
1932.    <title>2014 in Book Covers</title>
1933.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>For my last post of 2014 I wanted to show, with pictures, the books I
1934. read and spent so much time with this year.</p>
1935. <p>Back in January of 2014 I set out to read 30 books as part of my
1936. <a class="reference external" href="https://www.goodreads.com/challenges/1914-2014-reading-challenge">Reading
1937. Challenge</a>.
1938. I wanted to focus on reading Brazilian authors early on as I felt that I
1939. really needed to learn more about Brazilian literature and this time,
1940. read books for fun and not because I was told to back when I was much
1941. younger.</p>
1942. <div class="figure">
1943. <img alt="books 1" src="http://c1.staticflickr.com/9/8561/15972365217_fa019a4c47_n.jpg"/>
1944. </div>
1945. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/rT_17o_RWLU" width="1"/></div>
1946.    </content>
1947.    <updated>2014-12-31T18:26:00Z</updated>
1948.    <published>2014-12-31T18:26:00Z</published>
1949.    <category term="books"/>
1950.    <category term="goodreads"/>
1951.    <category term="2014"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/2014-in-book-covers.html</feedburner:origLink>
1952.    <author>
1953.      <name>Og Maciel</name>
1954.    </author>
1955.    <source>
1956.      <id>https://omaciel.github.io/</id>
1957.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
1958.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
1959.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
1960.      <title>Journal of an Open Sourcee</title>
1961.      <updated>2017-07-03T04:00:00Z</updated>
1962.    </source>
1963.  </entry>
1964.  
1965.  <entry xml:lang="en-us">
1966.    <id>https://omaciel.github.io/books/goodreads/2014/2014/12/31/year-in-book-covers</id>
1967.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/RJtsWezn4jk/year-in-book-covers.html" rel="alternate" type="text/html"/>
1968.    <title>2014 in Book Covers</title>
1969.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>For my last post of 2014 I wanted to show, with pictures, the books I
1970. read and spent so much time with this year.</p>
1971.  
1972. <p>Back in January of 2014 I set out to read 30 books as part of my
1973. <a href="https://www.goodreads.com/challenges/1914-2014-reading-challenge">Reading Challenge</a>. I wanted to focus on reading Brazilian
1974. authors early on as I felt that I really needed to learn more about
1975. Brazilian literature and this time, read books for fun and not because
1976. I was told to back when I was much younger.</p>
1977.  
1978. <p><img alt="books 1" src="http://c1.staticflickr.com/9/8561/15972365217_fa019a4c47_n.jpg"/></p>
1979.  
1980. <p>I took advantage that <strong>UNC</strong> has a vast books collection with a very
1981. decent section on Brazilian authors and I was able to read some really
1982. awesome books by <a href="https://www.goodreads.com/author/show/3376364.Erico_Verissimo">Erico Verissimo</a>,
1983. <a href="https://www.goodreads.com/author/show/191653.Joaquim_Manuel_de_Macedo">Joaquim Manuel de Macedo</a>, <a href="https://www.goodreads.com/author/show/540628.Jos_de_Alencar">José de Alencar</a>,
1984. <a href="https://www.goodreads.com/author/show/52683.Jorge_Amado">Jorge Amado</a> and <a href="https://www.goodreads.com/author/show/22458.Machado_de_Assis">Machado de Assis</a>! I also fell in
1985. love with these authors and the fact that it took me a couple of
1986. decades to truly appreciate them doesn’t bother me at all, since I
1987. believe that it took me this long to reach the right maturity level…
1988. in other words, I was not ready for them yet until this year.</p>
1989.  
1990. <p><img alt="books 2" src="http://c2.staticflickr.com/8/7536/16132335406_f5bdfa631b_n.jpg"/></p>
1991.  
1992. <p>I also fell in love with <a href="https://www.goodreads.com/author/show/585.John_Steinbeck">John Steinbeck</a> and
1993. <a href="https://www.goodreads.com/author/show/1630.Ray_Bradbury">Ray Bradbury</a>, and I think that <a href="https://www.goodreads.com/book/show/18114322-the-grapes-of-wrath">Grapes of Wrath</a>
1994. and <a href="https://www.goodreads.com/book/show/50033.Dandelion_Wine">Dandelion Wine</a> are two of the best books I have ever
1995. read!</p>
1996.  
1997. <p>Lastly, 2014 was also the year I started reading short stories (to sample
1998. different authors and see what they ‘have to offer’), and I highly
1999. recommend the short stories of <a href="https://www.goodreads.com/author/show/22694.Flannery_O_Connor">Flannery O’Connor</a>,
2000. <a href="https://www.goodreads.com/author/show/7464.John_Cheever">John Cheever</a>, <a href="https://www.goodreads.com/author/show/158635.Simon_Rich">Simon Rich</a>, and
2001. <a href="https://www.goodreads.com/author/show/13450.Gabriel_Garc_a_M_rquez">Gabriel Garcí­a Márquez</a>.</p>
2002.  
2003. <p><img alt="books 3" src="http://c2.staticflickr.com/8/7526/16132335446_ecd062b9bd_n.jpg"/></p>
2004.  
2005. <p>In 2015 I plan to continue reading more Brazilian authors and
2006. exploring different authors and genres! I may even re-read
2007. <a href="https://www.goodreads.com/book/show/33.The_Lord_of_the_Rings">The Lord of the Rings</a> again. :)</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/RJtsWezn4jk" width="1"/></div>
2008.    </summary>
2009.    <updated>2014-12-31T13:26:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books/goodreads/2014/2014/12/31/year-in-book-covers.html</feedburner:origLink>
2010.    <author>
2011.      <name>Og Maciel</name>
2012.      <email>omaciel@ogmaciel.com</email>
2013.    </author>
2014.    <source>
2015.      <id>https://omaciel.github.io/</id>
2016.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2017.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
2018.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2019.      <title>Journal of An Open Sourcee</title>
2020.      <updated>2014-12-31T19:14:08Z</updated>
2021.    </source>
2022.  </entry>
2023.  
2024.  <entry>
2025.    <id>http://societyserver.org/mbaehr/leaning-smalltalk-through-Google-Code-In</id>
2026.    <link href="http://societyserver.org/mbaehr/leaning-smalltalk-through-Google-Code-In" rel="alternate" type="text/html"/>
2027.    <title>leaning smalltalk through Google Code In</title>
2028.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
2029. <p>
2030. For years i have been meaning to learn smalltalk. my first exploration started about 10 years ago while teaching two children to make a game with squeak. Then i worked through a tutorial about making a simple game. Unfortunately it didn't capture my interest. So the my attempts to learn smalltalk were stalled as i searched for a project that i could do with it.
2031. </p>
2032.  
2033. <p>
2034. Why do i want to learn smalltalk? Because it is the first object-oriented language. Many of the OO concepts were invented in smalltalk. There is also the concept of working in an image that not only contains my code but also a full IDE which is used to update my code at runtime. Updating code at runtime is a concept that has been with me for more than 20 years now, ever since i started programming MUDs in LPC and writing modules for the Spinner/Roxen webserver.
2035. </p>
2036.  
2037. <p>
2038. Recently a friend asked me what it would take to build a text search application for the Baha'i writings in chinese. There is one for english and other western languages, but not for chinese, and it does not run on mobile devices. It is also not Free Software, so i can't use it as a base to improve. But i didn't really want to take on a new project either so i just filed the idea for the time being.
2039. </p>
2040.  
2041. <p>
2042. One of my customers is managing access to several internal resources through htaccess and htpasswd. Because they have many interns who need to have access to some of these, and because they are now spread over multiple servers, it is becoming more and more cumbersome to manage them manually via these files. It also does not help that a salt module which we could use to help depends on apache helpers, which we can not install because apache conflicts with nginx which we are using. So i started exploring alternatives. One such alternative is a different way for nginx to verify access. It can make a request to an external service which then grants or rejects access depending on the resource and credentials. This could be implemented as a webservice with a webinterface to manage the users. I looked for some existing applications that would get me part of the way but i found nothing suitable.
2043. </p>
2044.  
2045. <p>
2046. <strong>Enter Google Code-In:</strong> FOSSASIA invited the BLUG to join them as mentors.
2047. </p>
2048.  
2049. <p>
2050. At first i put up tasks for the community-calendar project, but then i realized that this was an opportunity to explore new ideas. Figuring that teaching is the best way to learn i put up those project ideas as tasks for the students. I could ask students to learn and explore, and finally work on those projects. I would pick the technology and guide the students through a sequence of tasks to acquire the skills needed to implement the actual applications. This was my chance to get back into smalltalk. Since code-In targets middle and highschool students, it is quite unlikely that any of them already know smalltalk, or have even heared about it. so in a way this will introduce a few students to smalltalk. I picked pharo because i feel it is going in the right direction trying to improve itself and also adding things like commandline support.
2051. </p>
2052.  
2053. <p>
2054. The desktop application was straight-forward: find out how to embed text-documents in the image and make them searchable.
2055. </p><ul>
2056. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5902940472606720">create a text reader</a></li>
2057. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5904045940146176">add search and categories</a></li>
2058. </ul>
2059. <!-- SAX: Unexpected end tag : p
2060. -->
2061.  
2062. <p>The web application took more exploration. I wanted to do it with a RESTful api and a javascript frontend. Again, the frontend was easy to define: create a user management interface. For the backend, the question was which webframework to use? AIDA/web has builtin user management and REST style url support by default. Seaside includes a REST module, but both are strong on generating html which i am not interested in. Then there is iliad, which appears more lightweight. Eventually i figured i could just let the students explore each, and i created a task for each tutorial that i could find:
2063. </p><ul>
2064. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5786620192096256">seaside part 1</a>  and <a href="http://www.google-melange.com/gci/task/view/google/gci2014/5822893606830080">part 2</a></li>
2065. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5884354588835840">seaside</a> (alternate tutorial)</li>
2066. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5858171612561408">aida/web</a> (<a href="https://www.google-melange.com/gci/task/view/google/gci2014/5897100306939904">repeat</a>)</li>
2067. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5888240192061440">iliad</a> (<a href="https://www.google-melange.com/gci/task/view/google/gci2014/5844083767508992">repeat</a>)</li>
2068. <li><a href="http://www.google-melange.com/gci/task/view/google/gci2014/5291284432420864">tide</a></li>
2069. </ul>
2070. (some of these i repeated because the student who did the them first time didn't pick up the follow-up tasks.)
2071. <!-- SAX: Unexpected end tag : p
2072. -->
2073.  
2074.  
2075. <p>Finally i discovered that Zinc, the HTTP server used by most frameworks is powerful enough to build a RESTful API without all the templating extras that the above frameworks provide. I also discovered teapot, a microframework that might be useful.
2076. </p><ul>
2077. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5906919541702656">zinc</a></li>
2078. </ul>
2079. <!-- SAX: Unexpected end tag : p
2080. -->
2081.  
2082.  
2083. <p>Once the students are familiar with the smalltalk environment, they can move on to the next steps:
2084. </p><ul>
2085. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5814729360539648">learn how to serve static files</a></li>
2086. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5880541949722624">create the RESTful API</a></li>
2087. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5046486547038208">create the whole user-management application</a></li>
2088. </ul>
2089. <!-- SAX: Unexpected end tag : p
2090. -->
2091.  
2092. <p>Of course there are also tasks for the front-end
2093. </p><ul>
2094. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5905960371486720">create the frontend</a></li>
2095. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5240815429353472">make it work with the REST backend</a></li>
2096. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/6472822016704512">learn amber</a></li>
2097. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5825641580593152">rewrite the front-end in amber</a></li>
2098. </ul>
2099. <!-- SAX: Unexpected end tag : p
2100. -->
2101.  
2102. <p>Related is also this task about a file editor, which i believe should make it easier to edit static assets like html and css pages from within the image:
2103. </p><ul>
2104. <li><a href="https://www.google-melange.com/gci/task/view/google/gci2014/5231805040951296">create a file-editor</a></li>
2105. </ul>
2106. <!-- SAX: Unexpected end tag : p
2107. --></div>
2108.    </content>
2109.    <updated>2014-12-31T06:11:01Z</updated>
2110.    <category term="steam"/>
2111.    <category term="documents"/>
2112.    <author>
2113.      <name>Martin Baehr</name>
2114.      <email>mbaehr@community.gotpike.org</email>
2115.    </author>
2116.    <source>
2117.      <id>http://societyserver.org/mbaehr</id>
2118.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
2119.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
2120.      <title>DevLog</title>
2121.      <updated>2014-12-31T06:20:03Z</updated>
2122.    </source>
2123.  </entry>
2124.  
2125.  <entry>
2126.    <id>http://societyserver.org/mbaehr/Google-Code-In-with-FOSSASIA</id>
2127.    <link href="http://societyserver.org/mbaehr/Google-Code-In-with-FOSSASIA" rel="alternate" type="text/html"/>
2128.    <title>Google Code In with FOSSASIA</title>
2129.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><!-- sTeam link consistency and HTML extension parser - modified document view !-->
2130. <p>FOSSASIA is a mentor organization at Google Code-In, and the Beijing GNU/Linux User Group has been invited to join them as mentors.
2131. </p><p>
2132. Two of us joined and created tasks for our projects.
2133. </p><p>
2134. At first i created tasks for our community-calendar project, but then i took the opportunity to get students to work on new projects that i had been hoping to do. For a long time i wanted to learn smalltalk, but i lacked good project ideas. This changed recently, as a friend asked me about a text search application, and one of my customers needed a better solution than htpasswd to manage users for nginx. I decided that both could be done in smalltalk.
2135. </p><p>
2136. So i created tasks for three new projects: A text search application to run on the desktop, and one on mobile, and a user-management web-application. For the desktop and the web-application i stipulated pharo smalltalk as the implementation platform. For good measure i also threw in my idealist for sup, a reimplementation of the frontend for this weblog in angular.js, a t-shirt design for the BLUG, packaging pike, and exploration of the meetup.com api. I also proposed a new structure of the files for the fossasia api, and helped mentor a few tasks relating to getting chinese communities added to the api.
2137. </p><p>
2138. </p><ul>
2139. <li>community-calendar (7 tasks)</li>
2140. <li>desktop text search application (2 tasks)</li>
2141. <li>mobile text search application (2 tasks)</li>
2142. <li>user-management web-application (12 tasks)</li>
2143. <li>sup ideas (more than 50 ideas, create tasks as needed)</li>
2144. <li>fossasia (1 task)</li>
2145. <li>sTeam weblog ui (1 task)</li>
2146. <li>blug t-shirt (1 task)</li>
2147. <li>amber (2 tasks)</li>
2148. <li>file-editor (1 task)</li>
2149. <li>packaging pike (1 task)</li>
2150. <li>meetup.com api (3 tasks)</li>
2151. </ul>
2152. new tasks will be added as needed, when i get another idea for improvements on one of the projects, or if i feel a task needs to be redone.
2153. <!-- SAX: Unexpected end tag : p
2154. --></div>
2155.    </content>
2156.    <updated>2014-12-31T03:53:36Z</updated>
2157.    <category term="steam"/>
2158.    <category term="documents"/>
2159.    <author>
2160.      <name>Martin Baehr</name>
2161.      <email>mbaehr@community.gotpike.org</email>
2162.    </author>
2163.    <source>
2164.      <id>http://societyserver.org/mbaehr</id>
2165.      <link href="http://societyserver.org/mbaehr" rel="alternate" type="text/html"/>
2166.      <link href="http://societyserver.org/scripts/rss.pike?feed=/mbaehr/" rel="self" type="application/rss+xml"/>
2167.      <title>DevLog</title>
2168.      <updated>2017-07-30T20:40:04Z</updated>
2169.    </source>
2170.  </entry>
2171.  
2172.  <entry xml:lang="en-US">
2173.    <id>https://www.foresightlinux.se/?p=1705</id>
2174.    <link href="https://www.foresightlinux.se/updated-google-chrome/" rel="alternate" type="text/html"/>
2175.    <title>Updated Google-chrome</title>
2176.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Maybe you are using google-chrome-stable in Foresight-c7. Then you might be using the contrib repository. To get the latest, you need to change the repository to grab it from foresighters instead.   I have ... <a class="readmore" href="https://www.foresightlinux.se/updated-google-chrome/"/></div>
2177.    </summary>
2178.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Maybe you are using google-chrome-stable in Foresight-c7. Then you might be using the contrib repository. To get the latest, you need to change the repository to grab it from foresighters instead.</p>
2179. <p> </p>
2180. <p>I have updated the wiki to use foresighters repo instead, read more <a href="http://wiki.foresightlinux.se/index.php?title=Google-chrome-stable" target="_blank">here</a>.</p></div>
2181.    </content>
2182.    <updated>2014-12-22T21:01:12Z</updated>
2183.    <category term="Blog"/>
2184.    <category term="Linux"/>
2185.    <category term="News"/>
2186.    <author>
2187.      <name>Tomas Forsman</name>
2188.    </author>
2189.    <source>
2190.      <id>https://www.foresightlinux.se</id>
2191.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2192.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2193.      <subtitle>Where it all begins</subtitle>
2194.      <title>Blog – Foresight Linux</title>
2195.      <updated>2016-01-21T09:20:12Z</updated>
2196.    </source>
2197.  </entry>
2198.  
2199.  <entry>
2200.    <id>tag:omaciel.github.io,2014-12-05:three-years-and-counting.html</id>
2201.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/nzpRatJKxX8/three-years-and-counting.html" rel="alternate" type="text/html"/>
2202.    <title>Three Years and Counting!</title>
2203.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Making a quick pit stop to mark this milestone in my professional
2204. career: today is my 3-year anniversary at Red Hat! Time has certainly
2205. flown by and I really cannot believe that it has been three years since
2206. I joined this company.</p>
2207. <p>I know it is sort of cliche to say "I can not believe that it has been
2208. this long..." and so on and so forth, but it is so true. Back then I
2209. joined a relatively new project with very high ambitions, and the first
2210. few months had me swimming way out in the deepest part of the pool,
2211. trying to learn all 'Red Hat-things' and <strong>Clojure</strong> for the existing
2212. automation framework (now we are fully using <strong>Python</strong>).</p>
2213. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/nzpRatJKxX8" width="1"/></div>
2214.    </content>
2215.    <updated>2014-12-05T15:49:00Z</updated>
2216.    <published>2014-12-05T15:49:00Z</published>
2217.    <category term="work"/>
2218.    <category term="redhat"/>
2219.    <category term="anniversary"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/three-years-and-counting.html</feedburner:origLink>
2220.    <author>
2221.      <name>Og Maciel</name>
2222.    </author>
2223.    <source>
2224.      <id>https://omaciel.github.io/</id>
2225.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2226.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
2227.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2228.      <title>Journal of an Open Sourcee</title>
2229.      <updated>2017-07-03T04:00:00Z</updated>
2230.    </source>
2231.  </entry>
2232.  
2233.  <entry xml:lang="en-us">
2234.    <id>https://omaciel.github.io/work/redhat/anniversary/2014/12/05/red-hat-three-years</id>
2235.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/ols4jtUHLnY/red-hat-three-years.html" rel="alternate" type="text/html"/>
2236.    <title>Three Years and Counting!</title>
2237.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Making a quick pit stop to mark this milestone in my professional
2238. career: today is my 3-year anniversary at Red Hat! Time has certainly
2239. flown by and I really cannot believe that it has been three years
2240. since I joined this company.</p>
2241.  
2242. <p>I know it is sort of cliche to say “I can not believe that it has been
2243. this long…” and so on and so forth, but it is so true. Back then I
2244. joined a relatively new project with very high ambitions, and the
2245. first few months had me swimming way out in the deepest part
2246. of the pool, trying to learn all ‘Red Hat-things’ and <strong>Clojure</strong> for
2247. the existing automation framework (now we are fully using <strong>Python</strong>).</p>
2248.  
2249. <p>I did a lot of swimming for sure, and through the next months, through
2250. many long days and weekends and hard work, tears and sweat (you know,
2251. your typical life for a <strong>Quality Engineer</strong> worth his/her salt), I
2252. succeeded in adding <strong>and</strong> wearing many types of hats, going from a
2253. <strong>Senior Quality Engineer</strong>, to a <strong>Supervisor</strong> of the team, to
2254. eventually becoming the <strong>Manager</strong> for a couple of teams, spread over
2255. 4 different countries. Am I bragging? Maaaybe a little bit :) but my
2256. point is really to highlight a major key factor that made this rapid
2257. ascension path possible: Red Hat’s work philosophy and culture of
2258. rewarding those who work hard and truly embrace the company! Sure, I
2259. worked really hard, but I have worked just as hard before in previous
2260. places and gotten nowhere really fast! Being recognized and rewarded
2261. for your hard work is something new to me, and I owe a great debt of
2262. gratitude to those who took the time to acknowledge my efforts and
2263. allowed me room to grow within this company!</p>
2264.  
2265. <p>The best part of being a Red Hatter for 3 years? Being surrounded by
2266. an enormous pool of talented, exciting people who not only enjoy what
2267. they do, but are always willing to teach you something new, and/or to
2268. drop what they’re working on to lend you a helping hand! There is not
2269. a single day that I don’t learn something new, and thankfully I don’t
2270. see any sign of this trend stopping :) Have I mentioned that I
2271. <strong>love</strong> my teammates too? What a great bunch of guys!!! Getting up
2272. early in the morning and walking to my home office (yeah, they let me
2273. work remotely too) day in, day out, is never a drag because I just
2274. know that there are new things to learn and new adventures and
2275. ‘achievements to unlock’ right around the corner.</p>
2276.  
2277. <p><strong>I am Red Hat!!!</strong></p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/ols4jtUHLnY" width="1"/></div>
2278.    </summary>
2279.    <updated>2014-12-05T10:49:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/work/redhat/anniversary/2014/12/05/red-hat-three-years.html</feedburner:origLink>
2280.    <author>
2281.      <name>Og Maciel</name>
2282.      <email>omaciel@ogmaciel.com</email>
2283.    </author>
2284.    <source>
2285.      <id>https://omaciel.github.io/</id>
2286.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2287.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
2288.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2289.      <title>Journal of An Open Sourcee</title>
2290.      <updated>2014-12-31T19:14:08Z</updated>
2291.    </source>
2292.  </entry>
2293.  
2294.  <entry xml:lang="en-US">
2295.    <id>https://www.foresightlinux.se/?p=1701</id>
2296.    <link href="https://www.foresightlinux.se/dropbox-available/" rel="alternate" type="text/html"/>
2297.    <title>Dropbox available</title>
2298.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Many users uses dropbox in their smartphones and want to be able to sync from the computer too. Been added in FLR repo. Read more about dropbox in our wiki site here. Dropbox is ... <a class="readmore" href="https://www.foresightlinux.se/dropbox-available/"/></div>
2299.    </summary>
2300.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Many users uses dropbox in their smartphones and want to be able to sync from the computer too. Been added in <a href="http://wiki.foresightlinux.se/index.php?title=FLR" target="_blank">FLR</a> repo. Read more about dropbox in our wiki site <a href="http://wiki.foresightlinux.se/index.php?title=Dropbox" target="_blank">here</a>.</p>
2301. <blockquote><p>Dropbox is a free service that lets you bring your photos, docs, and videos anywhere and share them easily. Never email yourself a file again!</p></blockquote></div>
2302.    </content>
2303.    <updated>2014-12-01T09:55:58Z</updated>
2304.    <category term="Blog"/>
2305.    <category term="Linux"/>
2306.    <category term="News"/>
2307.    <author>
2308.      <name>Tomas Forsman</name>
2309.    </author>
2310.    <source>
2311.      <id>https://www.foresightlinux.se</id>
2312.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2313.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2314.      <subtitle>Where it all begins</subtitle>
2315.      <title>Blog – Foresight Linux</title>
2316.      <updated>2016-01-21T09:20:12Z</updated>
2317.    </source>
2318.  </entry>
2319.  
2320.  <entry xml:lang="en-US">
2321.    <id>https://www.foresightlinux.se/?p=1696</id>
2322.    <link href="https://www.foresightlinux.se/new-packages-available/" rel="alternate" type="text/html"/>
2323.    <title>New packages available</title>
2324.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">We have added few packages that might come in handy. They are added in the wiki. Virtualbox – Always fun to play around with different things in a virtual system. Android-tools – Needed to ... <a class="readmore" href="https://www.foresightlinux.se/new-packages-available/"/></div>
2325.    </summary>
2326.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>We have added few packages that might come in handy. They are added in the wiki.</p>
2327. <p><a href="http://wiki.foresightlinux.se/index.php?title=Virtualbox" target="_blank">Virtualbox</a> – Always fun to play around with different things in a virtual system.</p>
2328. <p><a href="http://wiki.foresightlinux.se/index.php?title=Android-tools" target="_blank">Android-tools</a> – Needed to get fastboot and adb into your system.</p>
2329. <p><a href="http://wiki.foresightlinux.se/index.php?title=Deja-dup" target="_blank">Deja-dup</a> – Probably want to make some backups.</p>
2330. <p><a href="http://wiki.foresightlinux.se/index.php?title=Chromium" target="_blank">Chromium</a> – Open Source web browser.</p>
2331. <p> </p>
2332. <p> </p></div>
2333.    </content>
2334.    <updated>2014-11-28T12:19:57Z</updated>
2335.    <category term="Blog"/>
2336.    <category term="Linux"/>
2337.    <category term="News"/>
2338.    <author>
2339.      <name>Tomas Forsman</name>
2340.    </author>
2341.    <source>
2342.      <id>https://www.foresightlinux.se</id>
2343.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2344.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2345.      <subtitle>Where it all begins</subtitle>
2346.      <title>Blog – Foresight Linux</title>
2347.      <updated>2016-01-21T09:20:12Z</updated>
2348.    </source>
2349.  </entry>
2350.  
2351.  <entry xml:lang="en-US">
2352.    <id>https://www.foresightlinux.se/?p=1693</id>
2353.    <link href="https://www.foresightlinux.se/enable-contrib-and-epel7-repository-in-your-system/" rel="alternate" type="text/html"/>
2354.    <title>Enable Contrib and Epel7 repository in your system</title>
2355.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">If you have already installed or planning to install in the near future, you need to enable atleast 2 repository to get hold of more packages. Contrib and Epel repository. It will give you ... <a class="readmore" href="https://www.foresightlinux.se/enable-contrib-and-epel7-repository-in-your-system/"/></div>
2356.    </summary>
2357.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>If you have already installed or planning to install in the near future, you need to enable atleast 2 repository to get hold of more packages. Contrib and Epel repository.</p>
2358. <p>It will give you more packages to be able to install from conary.</p>
2359. <p>Read more at: <a href="http://wiki.foresightlinux.se/index.php?title=Repositories" target="_blank">Repository</a></p>
2360. <p>Those will be enabled as default later, when installation notes and installation guides gets updated. So if you already installed conary with centos, then make sure to enable them.</p>
2361. <p> </p></div>
2362.    </content>
2363.    <updated>2014-11-27T20:01:17Z</updated>
2364.    <category term="Blog"/>
2365.    <category term="Linux"/>
2366.    <category term="News"/>
2367.    <author>
2368.      <name>Tomas Forsman</name>
2369.    </author>
2370.    <source>
2371.      <id>https://www.foresightlinux.se</id>
2372.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2373.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2374.      <subtitle>Where it all begins</subtitle>
2375.      <title>Blog – Foresight Linux</title>
2376.      <updated>2016-01-21T09:20:12Z</updated>
2377.    </source>
2378.  </entry>
2379.  
2380.  <entry xml:lang="en-US">
2381.    <id>https://www.foresightlinux.se/?p=1690</id>
2382.    <link href="https://www.foresightlinux.se/make-foresight-to-ask-continue-with-update-yn/" rel="alternate" type="text/html"/>
2383.    <title>Make Foresight to ask continue with update? [Y/n]</title>
2384.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">From scratch, you won’t get the question when installing/updating/removing applications. That need to be enabled in your system. It will assume you want to do the action and do it. To make it ask ... <a class="readmore" href="https://www.foresightlinux.se/make-foresight-to-ask-continue-with-update-yn/"/></div>
2385.    </summary>
2386.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>From scratch, you won’t get the question when installing/updating/removing applications. That need to be enabled in your system. It will assume you want to do the action and do it. To make it ask first, you need to open a file and add a setting for it. To do it, follow this guide:</p>
2387. <pre class="brush: text; gutter: false; first-line: 1">sudo gedit /etc/conaryrc</pre>
2388. <p>Add this line on a new row:</p>
2389. <pre class="brush: text; gutter: false; first-line: 1">interactive True</pre>
2390. <p>Save the file, now it will ask like you see below.</p>
2391. <p> </p>
2392. [tforsman@tforsman ~]$ sudo conary install chromium<br/>
2393. [sudo] password for tforsman:<br/>
2394. The following updates will be performed:<br/>
2395. Install chromium(:rpm)=39.0.2171.65_1.el7.centos-1-1<br/>
2396. continue with update? [Y/n]
2397. <p> </p></div>
2398.    </content>
2399.    <updated>2014-11-24T09:22:52Z</updated>
2400.    <category term="Blog"/>
2401.    <category term="Linux"/>
2402.    <category term="News"/>
2403.    <author>
2404.      <name>Tomas Forsman</name>
2405.    </author>
2406.    <source>
2407.      <id>https://www.foresightlinux.se</id>
2408.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2409.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2410.      <subtitle>Where it all begins</subtitle>
2411.      <title>Blog – Foresight Linux</title>
2412.      <updated>2016-01-21T09:20:12Z</updated>
2413.    </source>
2414.  </entry>
2415.  
2416.  <entry xml:lang="en-US">
2417.    <id>https://www.foresightlinux.se/?p=1685</id>
2418.    <link href="https://www.foresightlinux.se/possible-to-download-recipes-foresighters-repo/" rel="alternate" type="text/html"/>
2419.    <title>Possible to download recipes – Foresighters repo</title>
2420.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">Iv’e been busy to find a way for users to see what’s been added to foresighters repo and able to download the recipe for the package. And now it’s possible. First, you can see ... <a class="readmore" href="https://www.foresightlinux.se/possible-to-download-recipes-foresighters-repo/"/></div>
2421.    </summary>
2422.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Iv’e been busy to find a way for users to see what’s been added to foresighters repo and able to download the recipe for the package. And now it’s possible.</p>
2423. <p>First, you can see latest added recipes in the widget on the right side and browse all recipes here: <a href="https://www.foresightlinux.se/flr-recipes/" target="_blank">https://www.foresightlinux.se/flr-recipes/</a></p>
2424. <p>Don’t forget to look at <a href="https://www.foresightlinux.se/videos/" target="_blank">Videos</a> section, as Iv’e been planning to make some videos in the near future.</p>
2425. <p>Wondered how Foresight Linux 7 looks like? Take a look at the video below.</p>
2426. <p><span class="embed-youtube" style="text-align: center; display: block;"/></p></div>
2427.    </content>
2428.    <updated>2014-11-23T21:29:15Z</updated>
2429.    <category term="Blog"/>
2430.    <category term="Linux"/>
2431.    <category term="News"/>
2432.    <category term="Videos"/>
2433.    <category term="Foresighters"/>
2434.    <author>
2435.      <name>Tomas Forsman</name>
2436.    </author>
2437.    <source>
2438.      <id>https://www.foresightlinux.se</id>
2439.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2440.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2441.      <subtitle>Where it all begins</subtitle>
2442.      <title>Blog – Foresight Linux</title>
2443.      <updated>2016-01-21T09:20:12Z</updated>
2444.    </source>
2445.  </entry>
2446.  
2447.  <entry xml:lang="en-US">
2448.    <id>http://www.foresightlinux.org/?p=1110</id>
2449.    <link href="http://www.foresightlinux.org/uncategorized/foresight-based-on-centos-7/" rel="alternate" type="text/html"/>
2450.    <title>Foresight – Based on Centos 7</title>
2451.    <summary>Foresight Linux will be based on Centos 7. We will have a stable core and maintained for years.We will have whole centos main repository available and whole epel 7. We will have own repository for additional packages and packages that we need to tweak, for fitting into foresight and make it unique. There is already […]</summary>
2452.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Foresight Linux will be based on Centos 7. We will have a stable core and maintained for years.We will have whole centos main repository available and whole <a href="https://fedoraproject.org/wiki/EPEL" target="_blank">epel 7</a>. We will have own repository for additional packages and packages that we need to tweak, for fitting into foresight and make it unique.</p>
2453. <p>There is already a way to install it and use conary as package manager. read more at: <a href="http://wiki.foresightlinux.se/index.php?title=Installation" target="_blank">http://wiki.foresightlinux.se/index.php?title=Installation</a></p>
2454. <p><span style="color: #ff0000;">Remember, this is a early beta stage. </span></p>
2455. <p>We already have whole main repository from centos and fully updated. We also have epel repository, but not built with deep closed checks. That means if you install filezilla or similar, you might need to add missing packages on your own. Or it will tell you that you are missing libraries, that filezilla needs. No huge issue at the moment, it will be fixed in near future.</p>
2456. <p>We will write more about foresight, when we are starting to get somewhere. If you need any help, easiest to get help is from <a href="http://wiki.foresightlinux.se/index.php?title=Irc" target="_blank">irc</a> or <a href="http://wiki.foresightlinux.se/index.php?title=Mailinglist" target="_blank">mailinglist</a>.</p></div>
2457.    </content>
2458.    <updated>2014-11-22T20:52:01Z</updated>
2459.    <category term="news"/>
2460.    <category term="Uncategorized"/>
2461.    <author>
2462.      <name>Tomas Forsman</name>
2463.    </author>
2464.    <source>
2465.      <id>http://www.foresightlinux.org</id>
2466.      <link href="http://www.foresightlinux.org/feed/" rel="self" type="application/atom+xml"/>
2467.      <link href="http://www.foresightlinux.org" rel="alternate" type="text/html"/>
2468.      <subtitle>Because your distro should be cool!</subtitle>
2469.      <title>Foresight Linux</title>
2470.      <updated>2014-11-22T21:00:14Z</updated>
2471.    </source>
2472.  </entry>
2473.  
2474.  <entry>
2475.    <id>tag:omaciel.github.io,2014-09-21:books.html</id>
2476.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/5pLDHoTkAGU/books.html" rel="alternate" type="text/html"/>
2477.    <title>Books</title>
2478.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Woke up this morning and, as usual, sat down to read the <strong>Books</strong>
2479. section of <strong>The New York Times</strong> while drinking my coffee. This has
2480. become sort of a 'tradition' for me and because of it I have been able
2481. to learn about many interesting books, some of which I would not have
2482. found out on my own. I also 'blame' this activity to turning my
2483. nightstand into a mini-library on its own.</p>
2484. <p>Currently I have the following books waiting for me:</p>
2485. <ul class="simple">
2486. <li><a class="reference external" href="https://www.goodreads.com/book/show/19651089-the-oxford-book-of-latin-american-short-stories?ac=1">The Oxford Book of Latin American Short
2487. Stories</a></li>
2488. <li><a class="reference external" href="https://www.goodreads.com/book/show/7841455-the-new-yorker-stories?ac=1">The New Yorker
2489. Stories</a></li>
2490. <li><a class="reference external" href="https://www.goodreads.com/book/show/252981.The_Collected_Tales_of_Nikolai_Gogol?ac=1">The Collected Tales of Nikolai
2491. Gogol</a></li>
2492. <li><a class="reference external" href="https://www.goodreads.com/book/show/130440.Doctor_Zhivago?from_search=true">Doctor
2493. Zhivago</a></li>
2494. <li><a class="reference external" href="https://www.goodreads.com/book/show/13055592-redshirts?ac=1">Redshirts</a></li>
2495. <li><a class="reference external" href="https://www.goodreads.com/book/show/11012.Dubliners?ac=1">Dubliners</a></li>
2496. <li><a class="reference external" href="https://www.goodreads.com/book/show/90192.The_House_of_the_Seven_Gables?ac=1">The House of Seven
2497. Gables</a></li>
2498. <li><a class="reference external" href="http://feeds.feedburner.com/Lolita">Lolita</a></li>
2499. </ul>
2500. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/5pLDHoTkAGU" width="1"/></div>
2501.    </content>
2502.    <updated>2014-09-21T16:07:00Z</updated>
2503.    <published>2014-09-21T16:07:00Z</published>
2504.    <category term="books"/>
2505.    <category term="life"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books.html</feedburner:origLink>
2506.    <author>
2507.      <name>Og Maciel</name>
2508.    </author>
2509.    <source>
2510.      <id>https://omaciel.github.io/</id>
2511.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2512.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
2513.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2514.      <title>Journal of an Open Sourcee</title>
2515.      <updated>2017-07-03T04:00:00Z</updated>
2516.    </source>
2517.  </entry>
2518.  
2519.  <entry xml:lang="en-us">
2520.    <id>https://omaciel.github.io/books/life/2014/09/21/books</id>
2521.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/3ZYwXVBbZAw/books.html" rel="alternate" type="text/html"/>
2522.    <title>Books</title>
2523.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Woke up this morning and, as usual, sat down to read the <strong>Books</strong> section of <strong>The New York Times</strong> while drinking my coffee. This has become sort of a ‘tradition’ for me and because of it I have been able to learn about many interesting books, some of which I would not have found out on my own. I also ‘blame’ this activity to turning my nightstand into a mini-library on its own.</p>
2524.  
2525. <p>Currently I have the following books waiting for me:</p>
2526.  
2527. <ul>
2528.  <li><a href="https://www.goodreads.com/book/show/19651089-the-oxford-book-of-latin-american-short-stories?ac=1">The Oxford Book of Latin American Short Stories</a></li>
2529.  <li><a href="https://www.goodreads.com/book/show/7841455-the-new-yorker-stories?ac=1">The New Yorker Stories</a></li>
2530.  <li><a href="https://www.goodreads.com/book/show/252981.The_Collected_Tales_of_Nikolai_Gogol?ac=1">The Collected Tales of Nikolai Gogol</a></li>
2531.  <li><a href="https://www.goodreads.com/book/show/130440.Doctor_Zhivago?from_search=true">Doctor Zhivago</a></li>
2532.  <li><a href="https://www.goodreads.com/book/show/13055592-redshirts?ac=1">Redshirts</a></li>
2533.  <li><a href="https://www.goodreads.com/book/show/11012.Dubliners?ac=1">Dubliners</a></li>
2534.  <li><a href="https://www.goodreads.com/book/show/90192.The_House_of_the_Seven_Gables?ac=1">The House of Seven Gables</a></li>
2535.  <li><a href="http://feeds.feedburner.com/Lolita">Lolita</a></li>
2536. </ul>
2537.  
2538. <p>Anyhow, while drinking my coffee this morning I realized just how much I enjoy reading and (what I like to call) catching up with all the books I either read when I was younger but took for granted or finally getting to those books that have been so patiently waiting for me to get to them. And now, whenever I’m not working or with my kids, you can bet your bottom dollar that you’ll find me somewhere outside (when the mosquitos are not buzzing about the yard) or cozily nestled with a book (or two) somewhere quiet around the house.</p>
2539.  
2540. <p><a href="https://www.flickr.com/photos/ogmaciel/15123814448" title="Book Queue by Og Maciel, on Flickr"><img alt="Book Queue" height="240" src="https://farm4.staticflickr.com/3838/15123814448_b2477f97b0_m.jpg" width="180"/></a></p>
2541.  
2542. <p>But to the point of this story, today I realized that, if I could go back in time (which reminds me, I should probably add “<a href="https://www.goodreads.com/book/show/2493.The_Time_Machine?ac=1">The Time Machine</a>” to my list) to the days when I was looking to buy a house, I would have done two things differently:</p>
2543.  
2544. <ol>
2545.  <li>wire the entire house so that every room would have a couple of ethernet ports;</li>
2546.  <li>chosen a house with a large-ish room and add wall-to-wall bookcases, like you see in those movies where a well-off person takes their guests into their private libraries for tea and biscuits;</li>
2547. </ol>
2548.  
2549. <p>I realize that I can’t change the past, and I also realize that perhaps it is a good thing that I took my book reading for granted during my high school and university years… I don’t think I would have enjoyed reading “<a href="https://www.goodreads.com/book/show/50033.Dandelion_Wine?ac=1">Dandelion Wine</a>” or “<a href="https://www.goodreads.com/book/show/14942.Mrs_Dalloway?from_search=true">Mrs. Dalloway</a>” as much back then as I when I finally did. I guess reading books is very much like the process of making good wines… with age and experience, the reader, not the book, develops the maturity and ability to properly savor a good story.</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/3ZYwXVBbZAw" width="1"/></div>
2550.    </summary>
2551.    <updated>2014-09-21T12:07:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/books/life/2014/09/21/books.html</feedburner:origLink>
2552.    <author>
2553.      <name>Og Maciel</name>
2554.      <email>omaciel@ogmaciel.com</email>
2555.    </author>
2556.    <source>
2557.      <id>https://omaciel.github.io/</id>
2558.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2559.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
2560.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2561.      <title>Journal of An Open Sourcee</title>
2562.      <updated>2014-12-31T19:14:08Z</updated>
2563.    </source>
2564.  </entry>
2565.  
2566.  <entry xml:lang="en-US">
2567.    <id>http://www.foresightlinux.org/?p=1107</id>
2568.    <link href="http://www.foresightlinux.org/uncategorized/how-to-install-foresight-3/" rel="alternate" type="text/html"/>
2569.    <title>How to install Foresight 3</title>
2570.    <summary>We have written down how you can install Foresight 3 and get cinnamon or openbox as desktop. (more desktop env will come) Read all about it here: http://wiki.foresightlinux.se/index.php?title=Installation About the issue: exceptions.ImportError: libpopt.so.0: cannot open shared object file: No such file or directory That error is probably gone, but has the information there, just in […]</summary>
2571.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>We have written down how you can install Foresight 3 and get cinnamon or openbox as desktop. (more desktop env will come)</p>
2572. <p>Read all about it here:</p>
2573. <p><a href="http://wiki.foresightlinux.se/index.php?title=Installation">http://wiki.foresightlinux.se/index.php?title=Installation</a></p>
2574. <p>About the issue: exceptions.ImportError: libpopt.so.0: cannot open shared object file: No such file or directory</p>
2575. <p>That error is probably gone, but has the information there, just in case.</p>
2576. <p>We know that conary updateall or conary update *** doesn’t work for the moment, because the groups are out of sync. But will be fixed later.</p>
2577. <p>Leave a comment if you wonder anything.</p>
2578. <p>Note: The old wiki is located here: <a href="http://www.foresightlinux.se/wiki-en">http://www.foresightlinux.se/wiki-en</a></p>
2579. <p>The new wiki will live here: <a href="http://wiki.foresightlinux.se">http://wiki.foresightlinux.se</a></p>
2580. <p> </p>
2581. <p>Remember, these wiki’s are unofficial ones. But worth mention.</p></div>
2582.    </content>
2583.    <updated>2014-09-06T06:46:59Z</updated>
2584.    <category term="Developing"/>
2585.    <category term="news"/>
2586.    <category term="Uncategorized"/>
2587.    <author>
2588.      <name>Tomas Forsman</name>
2589.    </author>
2590.    <source>
2591.      <id>http://www.foresightlinux.org</id>
2592.      <link href="http://www.foresightlinux.org/feed/" rel="self" type="application/atom+xml"/>
2593.      <link href="http://www.foresightlinux.org" rel="alternate" type="text/html"/>
2594.      <subtitle>Because your distro should be cool!</subtitle>
2595.      <title>Foresight Linux</title>
2596.      <updated>2014-11-22T21:00:14Z</updated>
2597.    </source>
2598.  </entry>
2599.  
2600.  <entry>
2601.    <id>tag:omaciel.github.io,2014-07-12:the-end-for-pylyglot.html</id>
2602.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/U7qJSk5gpGs/the-end-for-pylyglot.html" rel="alternate" type="text/html"/>
2603.    <title>The End For Pylyglot</title>
2604.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="section" id="background">
2605. <h2>Background</h2>
2606. <p>It was around 2005 when I started doing translations for Free and
2607. Open-Source Software. Back then I was warmly welcomed to the Ubuntu
2608. family and quickly learned all there was to know about using their
2609. Rosetta online tool to translate and/or review existing translations for
2610. the Brazilian Portuguese language. I spent so much time doing it, even
2611. during working hours, that eventually I sort of "made a name for myself"
2612. and made my way up to the upper layers of the Ubuntu Community echelon.</p>
2613. <p>Then I "graduated" and started doing translations for the upstream
2614. projects, such as GNOME, Xfce, LXDE, and Openbox. I took on more
2615. responsabilities, learned to use Git and make commits for myself as well
2616. as for other contributors, and strived to unify all Brazilian Portuguese
2617. translations across as many different projects as possible. Many
2618. discussions were had, (literally) hundreds of hours were spent going
2619. though also hundreds of thoundands of translations for hundreds of
2620. different applications, none of it bringing me any monetary of financial
2621. advantage, but all done for the simple pleasure of knowing that I was
2622. helping make FOSS applications "speak" Brazilian Portuguese.</p>
2623. <img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/U7qJSk5gpGs" width="1"/></div></div>
2624.    </content>
2625.    <updated>2014-07-12T15:20:00Z</updated>
2626.    <published>2014-07-12T15:20:00Z</published>
2627.    <category term="translations"/>
2628.    <category term="life"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/the-end-for-pylyglot.html</feedburner:origLink>
2629.    <author>
2630.      <name>Og Maciel</name>
2631.    </author>
2632.    <source>
2633.      <id>https://omaciel.github.io/</id>
2634.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2635.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
2636.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2637.      <title>Journal of an Open Sourcee</title>
2638.      <updated>2017-07-03T04:00:00Z</updated>
2639.    </source>
2640.  </entry>
2641.  
2642.  <entry xml:lang="en-us">
2643.    <id>https://omaciel.github.io/translations/life/2014/07/12/end-of-pylyglot</id>
2644.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/zDbkbWqli3M/end-of-pylyglot.html" rel="alternate" type="text/html"/>
2645.    <title>The End For Pylyglot</title>
2646.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><h2 id="background">Background</h2>
2647.  
2648. <p>It was around 2005 when I started doing translations for Free and
2649. Open-Source Software. Back then I was warmly welcomed to the Ubuntu
2650. family and quickly learned all there was to know about using their
2651. Rosetta online tool to translate and/or review existing translations
2652. for the Brazilian Portuguese language. I spent so much time doing it,
2653. even during working hours, that eventually I sort of “made a name for
2654. myself” and made my way up to the upper layers of the Ubuntu Community
2655. echelon.</p>
2656.  
2657. <p>Then I “graduated” and started doing translations for the upstream
2658. projects, such as GNOME, Xfce, LXDE, and Openbox. I took on more
2659. responsabilities, learned to use Git and make commits for myself as
2660. well as for other contributors, and strived to unify all Brazilian
2661. Portuguese translations across as many different projects as possible.
2662. Many discussions were had, (literally) hundreds of hours were spent
2663. going though also hundreds of thoundands of translations for hundreds
2664. of different applications, none of it bringing me any monetary of
2665. financial advantage, but all done for the simple pleasure of knowing
2666. that I was helping make FOSS applications “speak” Brazilian
2667. Portuguese.</p>
2668.  
2669. <p>I certainly learned a lot though the experience of working on these
2670. many projects… some times I made mistakes, other times I “fought”
2671. alone to make sure that standards and procedures were complied with.
2672. All in all, looking back I only have one regret: not being nominated
2673. to become the leader for the Brazilian GNOME translation team.</p>
2674.  
2675. <p>Having handled 50% of the translations for one of the GNOME releases
2676. (the other 50% was handled by a good friend, Vladimir Melo while the
2677. leader did nothing to help) and spent much time making sure that the
2678. release would go out the door 100% translated, I really thought I’d be
2679. nominated to become the next leader. Not that I felt that I needed a
2680. ‘title’ to show off to other people, but in a way I wanted to feel
2681. that my peers acknowledged my hard work and commitment to the project.</p>
2682.  
2683. <p>Seeing other people, even people with no previous experience, being
2684. nominated by the current leader to replace him was a slap in the face.
2685. It really hurt me… but I made sure to be supportive and continue to
2686. work just as hard. I guess you could say that I lived and breathed
2687. translations, my passion not knowing any limits or knowing when to
2688. stop…</p>
2689.  
2690. <p>But stop I eventually did, several years ago, when I realized how hard
2691. it was to land a job that would allow me to support my family (back
2692. then I had 2 small kids) and continue to do the thing I cared the
2693. most. I confess that I even went through a series of job interviews
2694. for the translation role that Jono Bacon, Canonical’s former community
2695. manager, was trying to hire, but in the end things didn’t work out the
2696. way I wanted. I also flirted with another similar role at MeeGo but
2697. since they wanted me to move to the West Coast I decided not to pursue
2698. it (I also had fallen in love with my then current job).</p>
2699.  
2700. <h2 id="pylyglot">Pylyglot</h2>
2701.  
2702. <p>As a way to keep myself somewhat still involved with the translation
2703. communities and at the same time learn a bit more about the Django
2704. framework, I then created <a href="http://www.pylyglot.org">Pylyglot</a>, “a web based glossary
2705. compedium for Free and Open Source Software translators heavily
2706. inspired on the Open-tran.eu web site… with the objective to
2707. ‘provide a concise, yet comprehensive compilation of a body of
2708. knowledge’ for translators derived from existing Free and Open Source
2709. Software translations.”</p>
2710.  
2711. <p><img alt="Pylyglot" src="http://feeds.feedburner.com/images/pylyglot.png" title="Pylyglot"/></p>
2712.  
2713. <p>I have been running this service on my own and paying for the cost of
2714. domain registration and database costs out of my own pocket for a
2715. while now, and I now find myself facing the dilema of renewing the
2716. domain registration and keep Pylyglot alive for another year… or
2717. retire it and end once and for all my relationship with FOSS
2718. translations.</p>
2719.  
2720. <p>Having spent the last couple of months thinking about it, I have now
2721. arrived at the conclusion that it is time to let this chapter of my
2722. life rest. Though the US$140/year that I won’t be spending won’t make
2723. me any richer, I don’t foresee myself either maintaining or spending
2724. any time improving the project. So this July 21st, 2014 Pylyglot will
2725. close its doors and cease to exist in its current form.</p>
2726.  
2727. <p>To those who knew about Pylyglot and used it and, hopefuly, found it
2728. to be useful, my sincere thanks for using it. To those who supported
2729. my idea and the project itself, whether by submitting code patches,
2730. building the web site or just giving me moral support, thank you!</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/zDbkbWqli3M" width="1"/></div>
2731.    </summary>
2732.    <updated>2014-07-12T11:20:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/translations/life/2014/07/12/end-of-pylyglot.html</feedburner:origLink>
2733.    <author>
2734.      <name>Og Maciel</name>
2735.      <email>omaciel@ogmaciel.com</email>
2736.    </author>
2737.    <source>
2738.      <id>https://omaciel.github.io/</id>
2739.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2740.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
2741.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2742.      <title>Journal of An Open Sourcee</title>
2743.      <updated>2014-12-31T19:14:08Z</updated>
2744.    </source>
2745.  </entry>
2746.  
2747.  <entry>
2748.    <id>tag:omaciel.github.io,2014-06-30:fauxfactory-030.html</id>
2749.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/1aTk1l1xzho/fauxfactory-030.html" rel="alternate" type="text/html"/>
2750.    <title>FauxFactory 0.3.0</title>
2751.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Took some time from my vacation and released <strong>FauxFactory 0.3.0</strong> to
2752. make it <strong>Python 3</strong> compatible and to add a new <strong>generate_utf8</strong>
2753. method (plus some nice tweaks and code clean up).</p>
2754. <p>As always, the package is available on
2755. <a class="reference external" href="https://pypi.python.org/pypi/fauxfactory/">Pypi</a> and can be
2756. installed via <strong>pip install fauxfactory</strong>.</p>
2757. <p>If ...</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/1aTk1l1xzho" width="1"/></div>
2758.    </content>
2759.    <updated>2014-06-30T23:00:00Z</updated>
2760.    <published>2014-06-30T23:00:00Z</published>
2761.    <category term="python"/>
2762.    <category term="testing"/>
2763.    <category term="qe"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/fauxfactory-030.html</feedburner:origLink>
2764.    <author>
2765.      <name>Og Maciel</name>
2766.    </author>
2767.    <source>
2768.      <id>https://omaciel.github.io/</id>
2769.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2770.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
2771.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2772.      <title>Journal of an Open Sourcee</title>
2773.      <updated>2017-07-03T04:00:00Z</updated>
2774.    </source>
2775.  </entry>
2776.  
2777.  <entry xml:lang="en-us">
2778.    <id>https://omaciel.github.io/python/testing/qe/2014/06/30/fauxfactory-0-3-0</id>
2779.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/4qT1KTIr3cQ/fauxfactory-0-3-0.html" rel="alternate" type="text/html"/>
2780.    <title>FauxFactory 0.3.0</title>
2781.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Took some time from my vacation and released <strong>FauxFactory 0.3.0</strong> to
2782. make it <strong>Python 3</strong> compatible and to add a new <strong>generate_utf8</strong>
2783. method (plus some nice tweaks and code clean up).</p>
2784.  
2785. <p>As always, the package is available on <a href="https://pypi.python.org/pypi/fauxfactory/">Pypi</a> and can be installed via
2786. <strong>pip install fauxfactory</strong>.</p>
2787.  
2788. <p>If you have any constructive feedback, suggestions, or file a bug
2789. report or feature request, please use the <a href="https://github.com/omaciel/fauxfactory">Github</a> page.</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/4qT1KTIr3cQ" width="1"/></div>
2790.    </summary>
2791.    <updated>2014-06-30T19:00:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/python/testing/qe/2014/06/30/fauxfactory-0-3-0.html</feedburner:origLink>
2792.    <author>
2793.      <name>Og Maciel</name>
2794.      <email>omaciel@ogmaciel.com</email>
2795.    </author>
2796.    <source>
2797.      <id>https://omaciel.github.io/</id>
2798.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
2799.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
2800.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
2801.      <title>Journal of An Open Sourcee</title>
2802.      <updated>2014-12-31T19:14:08Z</updated>
2803.    </source>
2804.  </entry>
2805.  
2806.  <entry xml:lang="en-US">
2807.    <id>https://www.foresightlinux.se/?p=1565</id>
2808.    <link href="https://www.foresightlinux.se/tips-huge-discount-on-linux-steam-games/" rel="alternate" type="text/html"/>
2809.    <title>Tips – Huge discount on Linux steam games</title>
2810.    <summary>When summer arrives, many games sites starts to sell out cheap games. We have found several games that works perfectly on Linux. All games comes from  Green Man Gaming and needs steam. Left 4 Dead Bundle This pack contains: Left 4 Dead Left 4 Dead 2 £22.99 £5.74    Half Life Complete   This pack contains: […]</summary>
2811.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>When summer arrives, many games sites starts to sell out cheap games. We have found several games that works perfectly on Linux.</p>
2812. <p>All games comes from  Green Man Gaming and needs steam.</p>
2813. <h2><a href="http://www.greenmangaming.com/?gmgr=doyaxido" target="_blank">Left 4 Dead Bundle</a></h2>
2814. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/l4d.jpg"><img alt="l4d" class="aligncenter size-full wp-image-166" height="346" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/l4d.jpg" width="296"/></a></p>
2815. <p>This pack contains:</p>
2816. <ul>
2817. <li>Left 4 Dead</li>
2818. <li>Left 4 Dead 2</li>
2819. </ul>
2820. <p><del>£22.99</del> <span style="font-weight: bold;"><span style="color: #ff0000;">£5.74</span></span></p>
2821. <p> </p>
2822. <h2> <a href="http://www.greenmangaming.com/?gmgr=doyaxido" target="_blank">Half Life Complete</a></h2>
2823. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/thumbnail-half-life-complete_boxart_tall-296x346.jpg"><img alt="thumbnail-half-life-complete_boxart_tall-296x346" class="aligncenter size-full wp-image-168" height="346" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/thumbnail-half-life-complete_boxart_tall-296x346.jpg" width="296"/></a></p>
2824. <p> </p>
2825. <p>This pack contains:</p>
2826. <ul>
2827. <li>Team Fortress Classic</li>
2828. <li>Half-Life: Opposing Force</li>
2829. <li>Half-Life</li>
2830. <li>Half-Life: Blue Shift</li>
2831. <li>Half-Life 2</li>
2832. <li>Half-Life: Source</li>
2833. <li>Half-Life 2: Deathmatch</li>
2834. <li>Half-Life 2: Lost Coast</li>
2835. <li>Half-Life 2: Episode One</li>
2836. <li>Half-Life 2: Episode Two</li>
2837. </ul>
2838. <p><del>£26.99</del> <span style="color: #ff0000;"><span style="font-weight: bold;">£6.74</span></span></p>
2839. <p> </p>
2840. <h2><a href="http://www.greenmangaming.com/?gmgr=doyaxido" target="_blank">Valve Complete Pack</a></h2>
2841. <p>(This pack contains few games that only works on win though)</p>
2842. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/thumbnail-valve-complete-pack_boxart_tall-296x346.jpg"><img alt="thumbnail-valve-complete-pack_boxart_tall-296x346" class="aligncenter size-full wp-image-169" height="346" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/thumbnail-valve-complete-pack_boxart_tall-296x346.jpg" width="296"/></a></p>
2843. <p>This pack contains:</p>
2844. <ul>
2845. <li>Counter-Strike</li>
2846. <li>Team Fortress Classic</li>
2847. <li>Day of Defeat</li>
2848. <li>Deathmatch Classic</li>
2849. <li>Half-Life: Opposing Force</li>
2850. <li>Ricochet</li>
2851. <li>Half-Life</li>
2852. <li>Counter-Strike: Condition Zero</li>
2853. <li>Half-Life: Blue Shift</li>
2854. <li>Half-Life 2</li>
2855. <li>Counter-Strike: Source</li>
2856. <li>Half-Life: Source</li>
2857. <li>Day of Defeat: Source</li>
2858. <li>Half-Life 2: Deathmatch</li>
2859. <li>Half-Life 2: Lost Coast</li>
2860. <li>Half-Life 2: Episode One</li>
2861. <li>Half-Life Deathmatch: Source</li>
2862. <li>Left 4 Dead</li>
2863. <li>Half-Life 2: Episode Two</li>
2864. <li>Team Fortress 2</li>
2865. <li>Portal</li>
2866. <li>Left 4 Dead 2</li>
2867. <li>Portal 2</li>
2868. <li>Counter-Strike: Global Offensive</li>
2869. </ul>
2870. <p><del> £49.99</del> <span style="color: #ff0000;"><span style="font-weight: bold;">£16.99</span></span></p>
2871. <h2/>
2872. <h2><span style="color: #333333;">voucher</span><span style="color: #333333;"> code</span></h2>
2873. <p><span style="color: #333333;">You can also make these deals even more extreme by abusing the below <span style="font-weight: bold;">15% voucher</span> code:</span></p>
2874. <div style="color: #333333;">
2875. <div><span style="font-weight: bold;">ENCORE-IFDSAL-E15OFF</span></div>
2876. <div/>
2877. <div>Code comes from <a href="http://blog.playfire.com/2014/06/international-federation-of-deals_14.html" target="_blank">GMG blog</a></div>
2878. <p> </p>
2879. </div></div>
2880.    </content>
2881.    <updated>2014-06-14T15:08:09Z</updated>
2882.    <category term="Blog"/>
2883.    <category term="Games"/>
2884.    <author>
2885.      <name>Tomas Forsman</name>
2886.    </author>
2887.    <source>
2888.      <id>https://www.foresightlinux.se</id>
2889.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2890.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2891.      <subtitle>Where it all begins</subtitle>
2892.      <title>Blog</title>
2893.      <updated>2014-08-30T02:00:10Z</updated>
2894.    </source>
2895.  </entry>
2896.  
2897.  <entry xml:lang="en-US">
2898.    <id>https://www.foresightlinux.se/?p=1561</id>
2899.    <link href="https://www.foresightlinux.se/hard-to-install-and-use-bumblebee-in-foresight/" rel="alternate" type="text/html"/>
2900.    <title>Hard to install and use bumblebee in Foresight?</title>
2901.    <summary>someone told me once that users thought it was hard to install and use bumblebee for Nvidia optimus cards in Foresight. So we listened and took care of it. Now you only need to run two commands in terminal and reboot, and you are done. No need to edit files or similar. Read all about […]</summary>
2902.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/bumblebee3banner.jpg"><img alt="bumblebee foresight" class="aligncenter size-full wp-image-1562" height="245" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/bumblebee3banner.jpg" width="824"/></a></p>
2903. <p>someone told me once that users thought it was hard to install and use bumblebee for Nvidia optimus cards in Foresight.</p>
2904. <p>So we listened and took care of it.</p>
2905. <p>Now you only need to run two commands in terminal and reboot, and you are done. No need to edit files or similar.</p>
2906. <p>Read all about how you install it here: <a href="http://wiki.foresightlinux.se/index.php?title=Bumblebee" target="_blank">Bumblebee</a></p>
2907. <p>There is probably no easier way to install it somewhere else either. Sure you can bake in so you run one command to make 2 things. But we believe that you can handle 2 commands  :)</p></div>
2908.    </content>
2909.    <updated>2014-06-11T16:26:41Z</updated>
2910.    <category term="Blog"/>
2911.    <category term="bumblebee"/>
2912.    <author>
2913.      <name>Tomas Forsman</name>
2914.    </author>
2915.    <source>
2916.      <id>https://www.foresightlinux.se</id>
2917.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2918.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2919.      <subtitle>Where it all begins</subtitle>
2920.      <title>Blog</title>
2921.      <updated>2014-08-30T02:00:10Z</updated>
2922.    </source>
2923.  </entry>
2924.  
2925.  <entry xml:lang="en-US">
2926.    <id>https://www.foresightlinux.se/?p=1551</id>
2927.    <link href="https://www.foresightlinux.se/howto-adblock-midori-browser/" rel="alternate" type="text/html"/>
2928.    <title>HOWTO – adblock midori browser</title>
2929.    <summary>adblock midori It’s time to learn how to add and activate Advertisement Blocker in midori browser. Open up Preferences from the menu Go to Extensions tab and choose Advertisement Blocker Click on configure icon on the right side   Activate EasyPrivacy and Easylist. Also possible to go those sites and add even more blocklists. But these […]</summary>
2930.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><h2><strong>adblock midori</strong></h2>
2931. <p>It’s time to learn how to add and activate Advertisement Blocker in midori browser. Open up Preferences from the menu <a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/midori.png"><img alt="midori" class="aligncenter size-full wp-image-1552" height="534" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/midori.png" width="344"/></a> Go to Extensions tab and choose Advertisement Blocker</p>
2932. <figure class="wp-caption aligncenter" id="attachment_1553" style="width: 611px;"><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences-for-Midori.png"><img alt="Advertisement blocker" class="size-full wp-image-1553" height="374" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences-for-Midori.png" width="611"/></a>Advertisement blocker</figure>
2933. <p>Click on configure icon on the right side <a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Configure-Advertisement-filters.png"><img alt="adblock midori" class="aligncenter size-full wp-image-1554" height="382" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Configure-Advertisement-filters.png" width="430"/></a>   Activate EasyPrivacy and Easylist. Also possible to go those sites and add even more blocklists. But these two should be enough to block most of the common ads. Restart midori browser and you will see less ads from now on. Everytime you start midori, it will look for updates for the blocklist. Now you have a working adblock midori.</p></div>
2934.    </content>
2935.    <updated>2014-06-11T07:39:17Z</updated>
2936.    <category term="Blog"/>
2937.    <category term="adblock midori"/>
2938.    <category term="howto"/>
2939.    <author>
2940.      <name>Tomas Forsman</name>
2941.    </author>
2942.    <source>
2943.      <id>https://www.foresightlinux.se</id>
2944.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2945.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2946.      <subtitle>Where it all begins</subtitle>
2947.      <title>Blog</title>
2948.      <updated>2014-08-30T02:00:10Z</updated>
2949.    </source>
2950.  </entry>
2951.  
2952.  <entry xml:lang="en-US">
2953.    <id>https://www.foresightlinux.se/?p=1536</id>
2954.    <link href="https://www.foresightlinux.se/updating-menus-getting-started/" rel="alternate" type="text/html"/>
2955.    <title>Updating menus + Getting started</title>
2956.    <summary>I’m currently fixing the menu and added Getting started. Hopefully it will become easier to navigate for newcomers and easier to find help when it’s needed. As always, got some complaints or suggestions, feel free to leave a comment about it.</summary>
2957.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I’m currently fixing the menu and added <a href="https://www.foresightlinux.se/getting-started/" target="_blank">Getting started</a>. Hopefully it will become easier to navigate for newcomers and easier to find help when it’s needed.</p>
2958. <p>As always, got some complaints or suggestions, feel free to leave a comment about it.</p></div>
2959.    </content>
2960.    <updated>2014-06-08T11:15:27Z</updated>
2961.    <category term="Blog"/>
2962.    <category term="News"/>
2963.    <author>
2964.      <name>Tomas Forsman</name>
2965.    </author>
2966.    <source>
2967.      <id>https://www.foresightlinux.se</id>
2968.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
2969.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
2970.      <subtitle>Where it all begins</subtitle>
2971.      <title>Blog</title>
2972.      <updated>2014-08-30T02:00:10Z</updated>
2973.    </source>
2974.  </entry>
2975.  
2976.  <entry xml:lang="en-US">
2977.    <id>https://www.foresightlinux.se/?p=1517</id>
2978.    <link href="https://www.foresightlinux.se/setup-the-perfect-foresight-linux/" rel="alternate" type="text/html"/>
2979.    <title>Setup the perfect Foresight Linux</title>
2980.    <summary>Perfect Foresight Linux I will show you how to get the latest stuff in your Foresight Linux. As for now, we can call it a perfect Foresight Linux. We will erase these applications: Evolution Firefox (will be installed again) OpenOffice Gedit Gcalctool Transmission Totem Gnome-do (+ do-plugins) We will install these applications: Firefox claws-mail LibreOffice […]</summary>
2981.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><h2><em><strong>Perfect Foresight Linux</strong></em></h2>
2982. <p>I will show you how to get the latest stuff in your Foresight Linux.</p>
2983. <p>As for now, we can call it a <em><strong>perfect Foresight Linux</strong></em>.</p>
2984. <h3>We will erase these applications:</h3>
2985. <p><span style="color: #ff0000;">Evolution</span><br/>
2986. <span style="color: #ff0000;"> Firefox (will be installed again)</span><br/>
2987. <span style="color: #ff0000;"> OpenOffice</span><br/>
2988. <span style="color: #ff0000;"> Gedit</span><br/>
2989. <span style="color: #ff0000;"> Gcalctool</span><br/>
2990. <span style="color: #ff0000;"> Transmission</span><br/>
2991. <span style="color: #ff0000;"> Totem</span><br/>
2992. <span style="color: #ff0000;"> Gnome-do (+ do-plugins)</span></p>
2993. <h3>We will install these applications:</h3>
2994. <p><a href="http://www.mozilla.org/en-US/firefox/new/" target="_blank">Firefox</a><br/>
2995. <a href="http://www.claws-mail.org/" target="_blank">claws-mail</a><br/>
2996. <a href="http://www.libreoffice.org/" target="_blank">LibreOffice</a><br/>
2997. <a href="http://mooedit.sourceforge.net/" target="_blank">medit</a><br/>
2998. <a href="http://galculator.sourceforge.net/" target="_blank">galculator</a><br/>
2999. <a href="http://www.qbittorrent.org/" target="_blank">qbittorrent</a><br/>
3000. <a href="http://www.videolan.org/vlc/" target="_blank">vlc</a> (+<a href="http://git.videolan.org/?p=npapi-vlc.git;a=summary" target="_blank">firefox plugin</a>)</p>
3001. <h2>Why?</h2>
3002. <p>You will get newer applications and they have more features than the applications we are removing. The system will feel more updated and will be alot more updated. And you can call it for the perfect foresight linux.</p>
3003. <h3>A bit of explanation</h3>
3004. <p><strong>Firefox &gt; Firefox</strong><br/>
3005. Just changing to a newer firefox that’s not available in fl:2-devel label.</p>
3006. <p><strong>Evolution &gt; Claws-mail</strong><br/>
3007. Evolution is useful, but many bugs have been spotted and fixed in newer versions. as we are still using gnome2, then we can change application instead.<br/>
3008. Don’t forget to look at: <a href="https://www.foresightlinux.se/howto-setup-claws-mail-the-best-way/">HOWTO – Setup Claws-mail the best way</a></p>
3009. <p><strong>OpenOffice &gt; LibreOffice</strong><br/>
3010. To get more recent version and use LibreOffice instead.</p>
3011. <p><strong> Gedit &gt; Medit</strong><br/>
3012. Medit is heavily customized and can either make it very thin or very powerful. Also remembers the documents you had opened before.</p>
3013. <p><strong> Galctool &gt; Galculator</strong><br/>
3014. Get a fresh calculator instead.</p>
3015. <p><strong>Transmission &gt; Qbittorrent</strong><br/>
3016. A nicer layout and more updated torrent application.</p>
3017. <p><strong> Totem &gt; Vlc</strong><br/>
3018. Vlc can handle alot more and more popoular than totem. Also easier to find help if needed. Also we will use vlc as playback for some videos in firefox.</p>
3019. <h2>Let’s get started</h2>
3020. <p>We are asuming you are using gnome and fl:2-devel label. Make sure you are using latest updated system, or npapi-vlc won’t be available and you end up with a error that it doesn’t exist. So we start to make sure we are updated.</p>
3021. <pre class="brush: text; gutter: false; first-line: 1">sudo conary updateall</pre>
3022. <p>To find out if you are using fl:2-qa or fl:2-devel label, open terminal and write:</p>
3023. <pre class="brush: text; gutter: false; first-line: 1">conary q group-gnome-dist --labels</pre>
3024. <p>Now you can see if it has fl:2-qa or fl:2-devel in the line.</p>
3025. <pre class="brush: bash; gutter: false; first-line: 1">[tforsman@localhost ~]$ conary q group-gnome-dist --labels
3026. group-gnome-dist=foresight.rpath.org@fl:2-devel/2.5.5+2014.06.02-0.1-2[~!gcc.core]
3027. [tforsman@localhost ~]$</pre>
3028. <p>If you need to change to development label, <a href="http://wiki.foresightlinux.se/index.php?title=Switch_from_stable_to_devel_system" target="_blank">read this</a>.</p>
3029. <p>Now we will edit your <a href="http://wiki.foresightlinux.se/index.php?title=System-model" target="_blank">system-model </a>file.</p>
3030. <p>Let’s start with open the file,</p>
3031. <pre class="brush: text; gutter: false; first-line: 1">sudo gedit /etc/conary/system-model</pre>
3032. <h3>How the file should look like</h3>
3033. <p>I added a file here to see how it should look like: <a href="http://wiki.foresightlinux.se/images/c/c5/System-model.txt" target="_blank">system-model</a></p>
3034. <p><span style="color: #ff0000;">If you run 32bit system</span>, change the name of firefox-64 to firefox-32 instead.</p>
3035. <p>Save your system-model file and close it. You shouldn’t change anything above the comments line that starts with #</p>
3036. <p>Now update your system.</p>
3037. <pre class="brush: text; gutter: false; first-line: 1">sudo conary updateall</pre>
3038. <p>All done. Now you got a bit more updated system with common applications you probably use. So now you have a perfect foresight linux system <img alt=":)" class="wp-smiley" src="http://www.foresightlinux.se/wp-includes/images/smilies/icon_smile.gif"/> </p>
3039. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot.png"><img alt="perfect foresight linux" class="size-full wp-image-1515" height="719" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot.png" width="1262"/></a></p>
3040. <p> </p>
3041. <p>Also some users doesn’t like banshee. You might want to do something with that one.</p>
3042. <pre class="brush: text; gutter: false; first-line: 1">sudo conary erase banshee banshee-community-extensions</pre>
3043. <p>Then install something smaller.</p>
3044. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install guayadeque</pre>
3045. <p>Homepage: <a href="http://guayadeque.org/" target="_blank">Guayadeque</a></p>
3046. <h3/>
3047. <h3>Additional applications</h3>
3048. <p>Maybe you need some more applications to get going.</p>
3049. <p><a href="http://wiki.foresightlinux.se/index.php?title=Wine" target="_blank">Wine</a> – To install windows applications.<br/>
3050. <a href="http://wiki.foresightlinux.se/index.php?title=Dropbox" target="_blank">Dropbox</a> – A cloud based storage.<br/>
3051. <a href="http://wiki.foresightlinux.se/index.php?title=Teamviewer" target="_blank">Teamviewer</a> – To get help from me? <img alt=":)" class="wp-smiley" src="http://www.foresightlinux.se/wp-includes/images/smilies/icon_smile.gif"/><br/>
3052. <a href="http://wiki.foresightlinux.se/index.php?title=Spotify" target="_blank">Spotify</a> – To play music from an application</p>
3053. <p>To install all of those, open terminal and write:</p>
3054. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install wine wine-gecko dropbox teamviewer spotify</pre>
3055. <p> </p>
3056. <h4>Conclusion</h4>
3057. <p>This is only based on what I think you should do with your Foresight system. So you can exclude some applications, if you want.</p>
3058. <p>But I call my system perfect foresight linux system <img alt=":)" class="wp-smiley" src="http://www.foresightlinux.se/wp-includes/images/smilies/icon_smile.gif"/> </p>
3059. <p>If you feel like I’m missing something. Feel free to comment about it.</p></div>
3060.    </content>
3061.    <updated>2014-06-07T16:35:48Z</updated>
3062.    <category term="Blog"/>
3063.    <category term="perfect foresight linux"/>
3064.    <author>
3065.      <name>Tomas Forsman</name>
3066.    </author>
3067.    <source>
3068.      <id>https://www.foresightlinux.se</id>
3069.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3070.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3071.      <subtitle>Where it all begins</subtitle>
3072.      <title>Blog</title>
3073.      <updated>2014-08-30T02:00:10Z</updated>
3074.    </source>
3075.  </entry>
3076.  
3077.  <entry xml:lang="en-US">
3078.    <id>https://www.foresightlinux.se/?p=1514</id>
3079.    <link href="https://www.foresightlinux.se/libreoffice-4-2-4-is-available-in-foresight-linux/" rel="alternate" type="text/html"/>
3080.    <title>Libreoffice 4.2.4 is available in Foresight Linux</title>
3081.    <summary>Now you can easily install latest stable release of libreoffice 4.2.4 for foresight linux. Better document file formats Round-trip interoperability with Microsoft OOXML, particularly for DOCX, as well as legacy RTF, has also improved considerably. A new import filter for Abiword documents has also been added. A new engine for Calc Massive parallel calculations of […]</summary>
3082.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="panel panel-default">
3083. <div class="panel-heading">
3084. <p>Now you can easily install latest stable release of libreoffice 4.2.4 for foresight linux.</p>
3085. <figure class="wp-caption aligncenter" id="attachment_1515" style="width: 1262px;"><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot.png"><img alt="libreoffice foresight linux" class="size-full wp-image-1515" height="719" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot.png" width="1262"/></a>libreoffice foresight linux</figure>
3086. <h3>Better document file formats</h3>
3087. </div>
3088. <div class="panel-collapse in" id="collapseOne" style="height: auto;">
3089. <div class="panel-body">
3090. <p>Round-trip interoperability with Microsoft OOXML, particularly for DOCX, as well as legacy RTF, has also improved considerably. A new import filter for Abiword documents has also been added.</p>
3091. <div class="panel-heading">
3092. <h3>A new engine for Calc</h3>
3093. </div>
3094. <p>Massive parallel calculations of formula cells using GPU via OpenCL are now possible thanks to our new formular interpreter.</p>
3095. <p><strong>Read more and download at <a href="http://wiki.foresightlinux.se/index.php?title=Libreoffice">wiki.foresightlinux.se</a></strong></p>
3096. </div>
3097. </div>
3098. </div></div>
3099.    </content>
3100.    <updated>2014-06-07T08:30:07Z</updated>
3101.    <category term="Blog"/>
3102.    <category term="News"/>
3103.    <category term="libreoffice foresight linux"/>
3104.    <author>
3105.      <name>Tomas Forsman</name>
3106.    </author>
3107.    <source>
3108.      <id>https://www.foresightlinux.se</id>
3109.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3110.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3111.      <subtitle>Where it all begins</subtitle>
3112.      <title>Blog</title>
3113.      <updated>2014-08-30T02:00:10Z</updated>
3114.    </source>
3115.  </entry>
3116.  
3117.  <entry xml:lang="en-US">
3118.    <id>https://www.foresightlinux.se/?p=1510</id>
3119.    <link href="https://www.foresightlinux.se/last-90-days-of-security-incapsula-for-foresightlinux-se/" rel="alternate" type="text/html"/>
3120.    <title>Last 90 days of security incapsula for foresightlinux.se</title>
3121.    <summary>Incapsula is doing what it should do + more. I’m very pleased with incapsula and what it really do for foresightlinux.se Based on 90 days, we can clearly see that bad bots and comments are the worst problems out there. But it grabs them and keeping foresightlinux.se free from bad comments and hacking attempts. You […]</summary>
3122.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><a href="http://www.incapsula.com/" target="_blank">Incapsula</a> is doing what it should do + more. I’m very pleased with incapsula and what it really do for foresightlinux.se</p>
3123. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-1.png"><img alt="incapsula" class="aligncenter size-full wp-image-1511" height="243" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-1.png" width="881"/></a></p>
3124. <p>Based on 90 days, we can clearly see that bad bots and comments are the worst problems out there. But it grabs them and keeping foresightlinux.se free from bad comments and hacking attempts.</p>
3125. <p>You probably think it’s based on a few attempts only.</p>
3126. <h2>26 May – 2 June</h2>
3127. <p>If we only look under period <strong><span style="font-size: small; line-height: 18px; color: #276eae; font-family: Arial,Helvetica,sans-serif;">May. 26 ,2014 – Jun. 2 ,2014</span></strong></p>
3128. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-4.png"><img alt="Screenshot-4" class="aligncenter size-full wp-image-1512" height="284" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-4.png" width="560"/></a></p>
3129. <p>As you can see, it’s alot of attempts every day. And last week it was a drop of 67%. So we are talking about 70+ comment spammer that incapsula blocks.</p>
3130. <p>If it wasn’t for <strong>incapsula</strong>, I probably would have given up running this site.</p></div>
3131.    </content>
3132.    <updated>2014-06-06T20:03:20Z</updated>
3133.    <category term="Blog"/>
3134.    <category term="incapsula"/>
3135.    <author>
3136.      <name>Tomas Forsman</name>
3137.    </author>
3138.    <source>
3139.      <id>https://www.foresightlinux.se</id>
3140.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3141.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3142.      <subtitle>Where it all begins</subtitle>
3143.      <title>Blog</title>
3144.      <updated>2014-08-30T02:00:10Z</updated>
3145.    </source>
3146.  </entry>
3147.  
3148.  <entry xml:lang="en-US">
3149.    <id>https://www.foresightlinux.se/?p=1506</id>
3150.    <link href="https://www.foresightlinux.se/huge-discount-on-watch-dogs-pc-game-uplay/" rel="alternate" type="text/html"/>
3151.    <title>Huge discount on Watch dogs – pc game uplay</title>
3152.    <summary>Watch Dogs Now available for $39.84 for a uplay key.  -41% from original prize.   Product Description All it takes is the swipe of a finger. We connect with friends. We buy the latest gadgets and gear. We find out what’s happening in the world. But with that same simple swipe, we cast an increasingly […]</summary>
3153.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><h2><a href="http://www.g2play.net/category/6612/watch-dogs-uplay-key/?___store=g2play_net_english&amp;acc=1srfh" target="_blank">Watch Dogs</a></h2>
3154. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/watch-dogs-G2P_3.jpg"><img alt="Watch dogs" class="aligncenter size-full wp-image-1507" height="120" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/watch-dogs-G2P_3.jpg" width="173"/></a></p>
3155. <p>Now available for <span style="color: #ff0000;">$39.84</span> for a uplay key.  -41% from original prize.</p>
3156. <p> </p>
3157. <h2 style="text-align: justify;">Product Description</h2>
3158. <hr/>
3159. <p style="text-align: justify;">All it takes is the swipe of a finger. We connect with friends. We buy the latest gadgets and gear. We find out what’s happening in the world. But with that same simple swipe, we cast an increasingly expansive shadow. With each connection, we leave a digital trail that tracks our every move and milestone, our every like and dislike. And it’s not just people. Today, all major cities are networked. Urban infrastructures are monitored and controlled by complex operating systems.</p>
3160. <p>In Watch_Dogs, this system is called the Central Operating System (ctOS) – and it controls almost every piece of the city’s technology and holds key information on all of the city’s residents.</p>
3161. <p>You play as Aiden Pearce, a brilliant hacker and former thug, whose criminal past led to a violent family tragedy. Now on the hunt for those who hurt your family, you’ll be able to monitor and hack all who surround you by manipulating everything connected to the city’s network. Access omnipresent security cameras, download personal information to locate a target, control traffic lights and public transportation to stop the enemy…and more.</p>
3162. <p>Use the city of Chicago as your ultimate weapon and exact your own style of revenge.</p>
3163. <h2 style="text-align: justify;">Features</h2>
3164. <hr/>
3165. <div class="content" style="margin-left: 15px; text-align: justify;"><strong>HACK THE CITY</strong></div>
3166. <div class="content" style="margin-left: 15px; text-align: justify;">Watch_Dogs takes place in a fully simulated living city where, using your smartphone, you have real-time control over the city’s infrastructure. Trap your enemy in a 30-car pileup by manipulating the traffic lights. Stop a train, and then board it to evade the authorities. Narrowly escape capture by quickly raising a drawbridge. Anything connected to the city’s ctOS can become your weapon.</div>
3167. <div class="content" style="margin-left: 15px; text-align: justify;">
3168. <p><strong>STREET JUSTICE</strong><br/>
3169. Living in inner city Chicago where violence is best answered by violence, you have the skills to take the fight to the streets. Take down enemies by delivering devastating blows with your baton, or experience a shoot-out like never before with a physics simulation that rivals anything in the shooter category. Overall, you will have access to more than 30 traditional weapons.</p>
3170. <p><strong>HIGH OCTANE</strong><br/>
3171. With help from Ubisoft Reflections, the acclaimed studio behind the award-winning Driver series, Watch_Dogs offers a stable bursting with horsepower. Get behind the wheel of more than 65 vehicles, each with state-of-art physics and handling, and explore the massive city while completing missions.</p>
3172. <p><strong>EVERYTHING IS UNDER CONTROL</strong><br/>
3173. Disrupt, the all-new game engine dedicated to Watch_Dogs, uses advanced processing and graphics to deliver a stunning visual and an incredibly realistic experience. Disrupt gives you the power to affect the story, the city and the life of the population with your choices creating a ripple effect throughout the city.</p>
3174. <p><strong>DYNAMIC NAVIGATION</strong><br/>
3175. Watch_Dogs gives you the ability to not only use the city’s ctOS to your advantage, but the streets as well. In real-world Chicago, cut through one of the buildings or climb to the rooftops to catch your target.</p>
3176. <p> </p>
3177. <p> </p>
3178. </div>
3179. <h2 style="text-align: justify;">System Requirements</h2>
3180. <hr/>
3181. <p><strong>Minimum</strong></p>
3182. <ul>
3183. <li>Supported OS: Windows Vista SP2 64bit, Windows 7 SP1 64bit, Windows 8 64bit</li>
3184. <li>Processor: Intel Core 2 Quad Q8400 @ 2.66Ghz or AMD Phenom II X4 940 @ 3.0Ghz</li>
3185. <li>RAM: 6 GB</li>
3186. <li>Video Card: 1024 VRAM DirectX 11 with Shader Model 5.0 (see supported list)</li>
3187. <li>Sound Card: DirectX 9 compatible Sound Card</li>
3188. <li>This product supports 64-bit operating systems ONLY</li>
3189. </ul>
3190. <p><strong> </strong></p>
3191. <p><strong>Recommended</strong></p>
3192. <ul>
3193. <li>Processor: Core i7 3770 @ 3.5Ghz or AMD FX-8350 @ 4.0Ghz</li>
3194. <li>RAM: 8 GB</li>
3195. <li>Video Card: 2048 VRAM DirectX 11 with Shader Model 5.0 or higher (see supported list)</li>
3196. <li>Sound Card: Surround Sound 5.1 capable sound card</li>
3197. <li>Supported Video Cards at Time of Release: nVidia GeForce GTX460 or better, GT500, GT600, GT700 series, AMD Radeon HD5850 or better, HD6000, HD7000, R7 and R9 series, Intel® Iris™ Pro HD 5200</li>
3198. </ul>
3199. <p> </p>
3200. <p>Conclusion</p>
3201. <p>So this is a huge prize drop from original prize. A huge discount with another word for <strong>Watch dogs</strong>.</p></div>
3202.    </content>
3203.    <updated>2014-06-06T10:19:48Z</updated>
3204.    <category term="Action"/>
3205.    <category term="Blog"/>
3206.    <category term="Games"/>
3207.    <category term="watch dogs"/>
3208.    <author>
3209.      <name>Tomas Forsman</name>
3210.    </author>
3211.    <source>
3212.      <id>https://www.foresightlinux.se</id>
3213.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3214.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3215.      <subtitle>Where it all begins</subtitle>
3216.      <title>Blog</title>
3217.      <updated>2014-08-30T02:00:10Z</updated>
3218.    </source>
3219.  </entry>
3220.  
3221.  <entry xml:lang="en-US">
3222.    <id>https://www.foresightlinux.se/?p=1498</id>
3223.    <link href="https://www.foresightlinux.se/howto-setup-claws-mail-the-best-way/" rel="alternate" type="text/html"/>
3224.    <title>HOWTO – Setup Claws-mail the best way</title>
3225.    <summary>When you install claws-mail, you will only see text messages for all mails you have and will get. You need to load a plugin that will let you show mails as they were excpected. This is how it looks like from beginning Open Configuration inside claws-mail, choose Plugins Click on load and find fancy.so file. […]</summary>
3226.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>When you install <strong>claws-mail</strong>, you will only see text messages for all mails you have and will get. You need to load a plugin that will let you show mails as they were excpected.</p>
3227. <p>This is how it looks like from beginning</p>
3228. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-FREE-tee-with-Sniper-Elite-3-LEGO-Batman-3-WWE-2K15-more.png"><img alt="Screenshot-FREE tee with Sniper Elite 3 | LEGO Batman 3 | WWE 2K15 &amp; more" class="aligncenter wp-image-1499 size-large" height="249" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-FREE-tee-with-Sniper-Elite-3-LEGO-Batman-3-WWE-2K15-more-1024x538.png" width="474"/></a></p>
3229. <p>Open Configuration inside claws-mail, choose Plugins</p>
3230. <p>Click on load and find fancy.so file.</p>
3231. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Plugins.png"><img alt="Screenshot-Plugins" class="aligncenter size-full wp-image-1500" height="327" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Plugins.png" width="427"/></a></p>
3232. <p>Then click on Close. Open Configuration again, click on Preferences, find Message View and click on Text options.</p>
3233. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences.png"><img alt="claws-mail" class="aligncenter size-full wp-image-1501" height="577" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences.png" width="710"/></a></p>
3234. <p>Make sure you choose “Select the HTML part of Multipart/alternative messages.</p>
3235. <p>Then in same preferences, go to Plugins and highlight Fancy.</p>
3236. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences-1.png"><img alt="Screenshot-Preferences-1" class="aligncenter size-full wp-image-1502" height="577" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-Preferences-1.png" width="710"/></a></p>
3237. <p>There you can choose to “Enable loading of remote content and Display images.</p>
3238. <p>Then click on Apply and Ok.</p>
3239. <p>Now your mails will look normal again.</p>
3240. <p><a href="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-FREE-tee-with-Sniper-Elite-3-LEGO-Batman-3-WWE-2K15-more-1.png"><img alt="Screenshot-FREE tee with Sniper Elite 3 | LEGO Batman 3 | WWE 2K15 &amp; more-1" class="aligncenter size-full wp-image-1503" height="718" src="https://www.foresightlinux.se/wp-content/uploads/2014/06/Screenshot-FREE-tee-with-Sniper-Elite-3-LEGO-Batman-3-WWE-2K15-more-1.png" width="1366"/></a></p>
3241. <p>This is the same mail as the first image in this post.</p>
3242. <p>So now you got a great mail application and the mails look sane.</p>
3243. <p>To install it in Foresight, open terminal and write:</p>
3244. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install claws-mail</pre>
3245. <p>I also recommend to load bogofilter and Notification from plugins. As bogofilter will help you against spam and notification will notify you with a popup window.</p></div>
3246.    </content>
3247.    <updated>2014-06-03T15:53:57Z</updated>
3248.    <category term="Blog"/>
3249.    <category term="claws mail"/>
3250.    <category term="howto"/>
3251.    <author>
3252.      <name>Tomas Forsman</name>
3253.    </author>
3254.    <source>
3255.      <id>https://www.foresightlinux.se</id>
3256.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3257.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3258.      <subtitle>Where it all begins</subtitle>
3259.      <title>Blog</title>
3260.      <updated>2014-08-30T02:00:10Z</updated>
3261.    </source>
3262.  </entry>
3263.  
3264.  <entry xml:lang="en-US">
3265.    <id>https://www.foresightlinux.se/?p=1496</id>
3266.    <link href="https://www.foresightlinux.se/different-ways-to-get-help-with-foresight/" rel="alternate" type="text/html"/>
3267.    <title>Different ways to get help with Foresight</title>
3268.    <summary>There are few ways to get help with Foresight and get help with various issues you might hit.   JIRA – Official bug tracker The problem can be that some users never knows when a issue is reported, if you don’t visit the tracker or subscribe on new entries.   Irc – Realtime chatting A […]</summary>
3269.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>There are few ways to get help with Foresight and get help with various issues you might hit.</p>
3270. <p> </p>
3271. <ul>
3272. <li><a href="http://issues.foresightlinux.org/jira/secure/Dashboard.jspa" target="_blank">JIRA</a> – Official bug tracker</li>
3273. </ul>
3274. <p>The problem can be that some users never knows when a issue is reported, if you don’t visit the tracker or subscribe on new entries.</p>
3275. <p> </p>
3276. <ul>
3277. <li><a href="http://wiki.foresightlinux.se/index.php?title=Irc" target="_blank">Irc</a> – Realtime chatting</li>
3278. </ul>
3279. <p>A great way to get help right away, but also depends on users are there and awake.</p>
3280. <p> </p>
3281. <ul>
3282. <li><a href="http://ask.foresightlinux.se/" target="_blank">Ask Foresight</a> – Ask a question and get an answer</li>
3283. </ul>
3284. <p>Still kinda new way to get help. But works real fine and also visible in more places and users can see that someone asked something. Easy to follow from RSS feed too.</p>
3285. <p> </p>
3286. <ul>
3287. <li><a href="https://plus.google.com/u/0/communities/114787519646243782914" target="_blank">Google+</a> – A community group.</li>
3288. </ul>
3289. <p>Probably the easiest way to get help, as it probably sends a notification to users that have “notify on” inside that group.</p>
3290. <p> </p>
3291. <ul>
3292. <li><a href="http://www.foresightlinux.se/forum/" target="_blank">Forum</a> – Unofficial forum</li>
3293. </ul>
3294. <p>Those who still want to use forum and write all kinds of stuff.</p>
3295. <p> </p>
3296. <p><a href="http://wiki.foresightlinux.se/index.php?title=Mailinglist" target="_blank">Mailinglist</a> – E-mail to our mailinglists</p>
3297. <p>Some users might want to send a mail instead. Harder to follow for users that doesn’t subscribe on it though.</p>
3298. <p> </p>
3299. <p>We always recommend Jira in first place, but you can also post that link from Jira in ask foresight or G+ to get users to notify about it.</p>
3300. <p>Common questions, we recommend ask foresight, G+ or Forum.</p>
3301. <p>We usually test packages and talks about development in irc. Mostly in devel channel. We use mailinglist for keep on track on ongoing development.</p>
3302. <p><strong>Fastest way</strong> to get help, use G+ or ask foresight for non critical issues.</p>
3303. <p>I might be wrong in some stuff here, but this is my personal feeling about ways to get help and how fast we notice about the problem/issue.</p></div>
3304.    </content>
3305.    <updated>2014-06-03T11:24:01Z</updated>
3306.    <category term="Blog"/>
3307.    <category term="help with foresight"/>
3308.    <author>
3309.      <name>Tomas Forsman</name>
3310.    </author>
3311.    <source>
3312.      <id>https://www.foresightlinux.se</id>
3313.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3314.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3315.      <subtitle>Where it all begins</subtitle>
3316.      <title>Blog</title>
3317.      <updated>2014-06-14T15:00:14Z</updated>
3318.    </source>
3319.  </entry>
3320.  
3321.  <entry xml:lang="en-US">
3322.    <id>https://www.foresightlinux.se/?p=1493</id>
3323.    <link href="https://www.foresightlinux.se/latest-firefox-versions-available/" rel="alternate" type="text/html"/>
3324.    <title>Latest Firefox versions available</title>
3325.    <summary>I’ve been building Firefox 29.0.1 and 30.0b8 in foresighters repo. To install any of them,  open terminal and write: 32bit sudo conary install firefox-32=foresighters.rpath.org@fl:2-devel or for beta sudo conary install firefox-beta-32=foresighters.rpath.org@fl:2-devel 64bit sudo conary install firefox-64=foresighters.rpath.org@fl:2-devel or for beta sudo conary install firefox-beta-64=foresighters.rpath.org@fl:2-devel</summary>
3326.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>I’ve been building Firefox 29.0.1 and 30.0b8 in foresighters repo.</p>
3327. <p>To install any of them,  open terminal and write:</p>
3328. <h2>32bit</h2>
3329. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install firefox-32=foresighters.rpath.org@fl:2-devel</pre>
3330. <p>or for beta</p>
3331. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install firefox-beta-32=foresighters.rpath.org@fl:2-devel</pre>
3332. <h2>64bit</h2>
3333. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install firefox-64=foresighters.rpath.org@fl:2-devel</pre>
3334. <p>or for beta</p>
3335. <pre class="brush: text; gutter: false; first-line: 1">sudo conary install firefox-beta-64=foresighters.rpath.org@fl:2-devel</pre></div>
3336.    </content>
3337.    <updated>2014-05-29T14:59:33Z</updated>
3338.    <category term="Blog"/>
3339.    <category term="Commits"/>
3340.    <category term="Linux"/>
3341.    <author>
3342.      <name>Tomas Forsman</name>
3343.    </author>
3344.    <source>
3345.      <id>https://www.foresightlinux.se</id>
3346.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3347.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3348.      <subtitle>Where it all begins</subtitle>
3349.      <title>Blog</title>
3350.      <updated>2014-06-11T16:20:10Z</updated>
3351.    </source>
3352.  </entry>
3353.  
3354.  <entry>
3355.    <id>tag:omaciel.github.io,2014-05-28:twenty-three-years.html</id>
3356.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/Wa77ZfQ2O5M/twenty-three-years.html" rel="alternate" type="text/html"/>
3357.    <title>Twenty Three Years</title>
3358.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>My parents were eagerly awaiting our arrival on an early Spring morning,
3359. and when our plane finally landed after the almost 10 1/2 hours flight
3360. and we made our way to the luggage claim area, the reunion was filled
3361. with a lot of hugging, laughter and a huge sigh ...</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/Wa77ZfQ2O5M" width="1"/></div>
3362.    </content>
3363.    <updated>2014-05-28T22:32:00Z</updated>
3364.    <published>2014-05-28T22:32:00Z</published>
3365.    <category term="family"/>
3366.    <category term="life"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/twenty-three-years.html</feedburner:origLink>
3367.    <author>
3368.      <name>Og Maciel</name>
3369.    </author>
3370.    <source>
3371.      <id>https://omaciel.github.io/</id>
3372.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
3373.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
3374.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
3375.      <title>Journal of an Open Sourcee</title>
3376.      <updated>2017-07-03T04:00:00Z</updated>
3377.    </source>
3378.  </entry>
3379.  
3380.  <entry xml:lang="en-us">
3381.    <id>https://omaciel.github.io/family/life/2014/05/28/twenty-three-years-in-america</id>
3382.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/rIxf9I_zPGg/twenty-three-years-in-america.html" rel="alternate" type="text/html"/>
3383.    <title>Twenty Three Years</title>
3384.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>My parents were eagerly awaiting our arrival on an early Spring
3385. morning, and when our plane finally landed after the almost 10 1/2
3386. hours flight and we made our way to the luggage claim area, the
3387. reunion was filled with a lot of hugging, laughter and a huge sigh of
3388. relief. For someone who had spent most of their entire lives in a
3389. small and sleepy town in the East coast of <strong>Brazil</strong>, waking up and
3390. finding yourself at <strong>JFK Airport</strong> was nothing short of a major event! I
3391. had never seen so many people of so many different races and speaking
3392. so many different dialects in my entire life, all 16 years of them!
3393. Everywhere I looked, everything was so different from what I was used
3394. to… even signs (so many of them) were in a different language!
3395. Eventually we grabbed our luggage and made our way to the parking lot
3396. looking for our car.</p>
3397.  
3398. <p>Before my sister and I left Brazil, I had the very hard task of giving
3399. away all of my possessions and only bringing the very bare minimal to
3400. start “a new life”. I was still going through my mid-teenager years,
3401. so I had to give away all of my favorite music LPs, books, childhood
3402. toys, and all the mementos I had collected through the years. This may
3403. not be such a big deal to you, but I have always been very attached
3404. to the things people give me, specially if they were given by someone
3405. I really cared. Seeing the things that represented so many people and
3406. moments of my life slowly drifting away filled me with a great feeling
3407. of personal loss. This feeling would stay with me for the next couple
3408. of years as I tried to adjust to my new adopted country. I was a
3409. stranger in a different land, where nobody knew me and I did not know
3410. anyone.</p>
3411.  
3412. <p>It’s been <strong>23 years</strong> since this event took place, and I’m still here
3413. in the “Land of the Free”. Through the years I have survived High
3414. School, graduated with a Bachelors in Science from an university in
3415. Upstate New York, married (another immigrant from another country who
3416. you shall meet soon), moved a couple of times, and now find myself
3417. raising three young girls in <strong>North Carolina</strong>, the <strong>first Maciel
3418. generation</strong> of our families to be born outside our countries! Our
3419. similarities and differences, however, go beyond only the generation
3420. gap!</p>
3421.  
3422. <p>You see, contrary to a lot of the “stereotypical” immigrant families,
3423. we have completely immersed ourselves into the <strong>Americal way of life
3424. and culture</strong>, with a dash of our childhood cultures sprinkled here
3425. and there to add a little diversity to the mix. My wife and I stopped
3426. observing the holidays from our countries of origin a long time ago,
3427. specially those with no corresponding holidays here. We share a lot of
3428. the things that we learned growing up with our kids, but always in a
3429. nostalgic, almost didactic sort of way. We speak a mix of <strong>Brazilian
3430. Portuguese-Mexican Spanish-New Jersey English</strong> at home and try our
3431. best not to force our children to learn either language in particular.
3432. As it stands now, our kids’ primary language is English and even
3433. though I still make a habit of speaking in Brazilian Portuguese to
3434. them, their vocabulary consists of several words that they only say
3435. either in Spanish or Portuguese, like the word “daddy”. My wife’s
3436. vocabulary has also gone through a very interesting transformation,
3437. and <strong>she now speaks more Portuguese than Spanish</strong> when talking to
3438. our kids. Maybe it is because she was very young when she moved to New
3439. York in the early 1990s and never really got a lot of exposure to the
3440. Spanish language growing up in a different country.</p>
3441.  
3442. <p>All I can say is that <strong>I call North Carolina home</strong>, I vote during
3443. elections, I always get emotional when hearing the American Anthem,
3444. and together with my wife I raise the next generation of the Maciel
3445. family! Maybe they will take some of our culture and teach it to their
3446. own kids one day… maybe one day they may even learn to speak
3447. Portuguese or Spanish… maybe they won’t, and that is ok by me. We
3448. don’t even force them to follow the same religion our parents (and
3449. their parents) taught us growing up, prefering that they make that
3450. decision on their own, when and if they’re ever interested in doing
3451. so. We want them to be able to choose their own paths and make
3452. educated decisions about every aspect of their lives without any
3453. pressure or guilt.</p>
3454.  
3455. <p>I’m an <strong>American-Brazilian</strong>, my wife is <strong>American-Mexican</strong> and our kids
3456. are Americans with a touch of Brazilian and Mexican pride and culture.
3457. Together we form the <strong>New American Family</strong>!</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/rIxf9I_zPGg" width="1"/></div>
3458.    </summary>
3459.    <updated>2014-05-28T18:32:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/family/life/2014/05/28/twenty-three-years-in-america.html</feedburner:origLink>
3460.    <author>
3461.      <name>Og Maciel</name>
3462.      <email>omaciel@ogmaciel.com</email>
3463.    </author>
3464.    <source>
3465.      <id>https://omaciel.github.io/</id>
3466.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
3467.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
3468.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
3469.      <title>Journal of An Open Sourcee</title>
3470.      <updated>2014-12-31T19:14:08Z</updated>
3471.    </source>
3472.  </entry>
3473.  
3474.  <entry xml:lang="en-US">
3475.    <id>https://www.foresightlinux.se/?p=1490</id>
3476.    <link href="https://www.foresightlinux.se/launch-jar-files-using-nautilus/" rel="alternate" type="text/html"/>
3477.    <title>How to launch .jar files using nautilus</title>
3478.    <summary>This is not nautilus specific issue and will work in more tools (like other file manager, xdg-open in cli etc) Create a run-jar.desktop in your ~/.local/share/applications/ directory with the following content: [DesktopEntry] Encoding=UTF-8 Type=Application Exec=java -jar %f Icon=java Name=run-jar Name[zh_CN]=run-jar Comment=Run the jar file Comment[zh_CN]=运行 JAR 文件 Now when you open the file’s property dialog and go to open with […]</summary>
3479.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p style="color: #4b4b4b;">This is not nautilus specific issue and will work in more tools (like other file manager, xdg-open in cli etc)</p>
3480. <p style="color: #4b4b4b;">Create a <span style="font-weight: bold;">run-jar.desktop</span> in your <span style="font-weight: bold;"><em><code style="color: #dd1144;">~/.local/share/applications/</code></em></span> directory with the following content:</p>
3481. <pre class="prettyprint"><code style="color: inherit;"><span class="pun" style="color: #666600;">[</span><span class="typ" style="color: #660066;">Desktop</span><span class="typ" style="color: #660066;">Entry</span><span class="pun" style="color: #666600;">]
3482. </span><span class="typ" style="color: #660066;">Encoding</span><span class="pun" style="color: #666600;">=</span><span class="pln" style="color: #000000;">UTF</span><span class="pun" style="color: #666600;">-</span><span class="lit" style="color: #006666;">8
3483. </span><span class="typ" style="color: #660066;">Type</span><span class="pun" style="color: #666600;">=</span><span class="typ" style="color: #660066;">Application
3484.  
3485. </span><span class="typ" style="color: #660066;">Exec</span><span class="pun" style="color: #666600;">=</span><span class="pln" style="color: #000000;">java </span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">jar </span><span class="pun" style="color: #666600;">%</span><span class="pln" style="color: #000000;">f
3486. </span><span class="typ" style="color: #660066;">Icon</span><span class="pun" style="color: #666600;">=</span><span class="pln" style="color: #000000;">java
3487.  
3488. </span><span class="typ" style="color: #660066;">Name</span><span class="pun" style="color: #666600;">=</span><span class="pln" style="color: #000000;">run</span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">jar
3489. </span><span class="typ" style="color: #660066;">Name</span><span class="pun" style="color: #666600;">[</span><span class="pln" style="color: #000000;">zh_CN</span><span class="pun" style="color: #666600;">]=</span><span class="pln" style="color: #000000;">run</span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">jar
3490. </span><span class="typ" style="color: #660066;">Comment</span><span class="pun" style="color: #666600;">=</span><span class="typ" style="color: #660066;">Run</span><span class="pln" style="color: #000000;"> the jar file
3491. </span><span class="typ" style="color: #660066;">Comment</span><span class="pun" style="color: #666600;">[</span><span class="pln" style="color: #000000;">zh_CN</span><span class="pun" style="color: #666600;">]=运行</span><span class="pln" style="color: #000000;"> JAR </span><span class="pun" style="color: #666600;">文件</span></code></pre>
3492. <p style="color: #4b4b4b;">Now when you open the file’s property dialog and go to open with tab, you can see run-jar mentioned in ‘show more app’.</p>
3493. <p style="color: #4b4b4b;">To make run-jar the default action, use nautilus ‘set default’ button or the type the following command in a terminal:</p>
3494. <pre class="prettyprint"><code style="color: inherit;"><span class="pln" style="color: #000000;">xdg</span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">mime query </span><span class="kwd" style="color: #000000;">default</span><span class="pln" style="color: #000000;"> application</span><span class="pun" style="color: #666600;">/</span><span class="pln" style="color: #000000;">x</span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">java</span><span class="pun" style="color: #666600;">-</span><span class="pln" style="color: #000000;">archive</span></code></pre>
3495. <p style="color: #4b4b4b;">The mime type can be found with the command:</p>
3496. <pre class="prettyprint"><span style="color: #000000;">xdg-mime query filetype my_shiny_app.jar</span></pre>
3497. <p><code style="color: inherit;"><span class="pln" style="color: #000000;"> </span></code></p>
3498. <p>There is other ways to do it too, like creating a nautilus script. But this feels like a better way though.</p></div>
3499.    </content>
3500.    <updated>2014-05-21T19:52:43Z</updated>
3501.    <category term="Blog"/>
3502.    <category term="Linux"/>
3503.    <category term="jar files"/>
3504.    <author>
3505.      <name>Tomas Forsman</name>
3506.    </author>
3507.    <source>
3508.      <id>https://www.foresightlinux.se</id>
3509.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3510.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3511.      <subtitle>Where it all begins</subtitle>
3512.      <title>Blog</title>
3513.      <updated>2014-06-08T16:20:54Z</updated>
3514.    </source>
3515.  </entry>
3516.  
3517.  <entry xml:lang="en-US">
3518.    <id>https://www.foresightlinux.se/?p=1487</id>
3519.    <link href="https://www.foresightlinux.se/difference-akmod-kmod/" rel="alternate" type="text/html"/>
3520.    <title>The difference between an ‘akmod’ and ‘kmod’</title>
3521.    <summary>  A ‘kmod’ (kernel driver module) is the pre-compiled, low-level software interface between the kernel and a driver. It gets loaded (into RAM) and merged into the running kernel. Linux kmods are specific to one and only one kernel, and will not work (nor even load) for any other kernel. Advantages: Pre-Compiled – no need […]</summary>
3522.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p> </p>
3523. <p>A<strong> ‘kmod’</strong> (kernel driver module) is the pre-compiled, low-level software interface between the kernel and a driver. It gets loaded (into RAM) and merged into the running kernel. Linux kmods are specific to one and only one kernel, and will not work (nor even load) for any other kernel.</p>
3524. <p><strong>Advantages:</strong> Pre-Compiled – no need to fool around with compiling, compilers, *-devel packages and other associated overhead.</p>
3525. <p><strong>Disadvantages:</strong> updating and re-booting into a new kernel without updating the kmod(s) will result in loss of functionality and inherent delays in updating kmods after kernel updates.</p>
3526. <p><strong>akmods</strong> (similar to dkms) is a solution to the problem of some kernel modules depending on specific versions of a kernel. As you start your computer, the akmod system will check if there are any missing kmods and if so, rebuild a new kmod for you. Akmods have more overhead than regular kmod packages as they require a few development tools such as gcc and automake in order to be able to build new kmods locally. If you think you’d like to try akmods, simply replace kmod with akmod</p>
3527. <p>With akmod you don’t have to worry about kernel updates as it recreates the driver for the new kernel on boot. With kmod you have to wait until a matching kmod is available before installing the kernel update.</p>
3528. <p><strong>Advantages:</strong> obvious.</p>
3529. <p><strong>Disadvantages:</strong> HDD space required for compilers and *-devel packages; unforseen/uncorrectable driver problems that cannot be resolved by the automatic tools.</p></div>
3530.    </content>
3531.    <updated>2014-05-21T19:03:46Z</updated>
3532.    <category term="Blog"/>
3533.    <category term="Linux"/>
3534.    <category term="akmod"/>
3535.    <author>
3536.      <name>Tomas Forsman</name>
3537.    </author>
3538.    <source>
3539.      <id>https://www.foresightlinux.se</id>
3540.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3541.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3542.      <subtitle>Where it all begins</subtitle>
3543.      <title>Blog</title>
3544.      <updated>2014-06-08T16:20:53Z</updated>
3545.    </source>
3546.  </entry>
3547.  
3548.  <entry xml:lang="en-US">
3549.    <id>https://www.foresightlinux.se/?p=1482</id>
3550.    <link href="https://www.foresightlinux.se/anyone-interested-get-updates-fl2-devel/" rel="alternate" type="text/html"/>
3551.    <title>Anyone interested to get updates for FL:2-devel ?</title>
3552.    <summary>Hello all Foresight users. I wonder if anyone is interested to still get some updates to current fl:2-devel repo? If so, leave a tiny comment and will put in some time to update some regular packages in near future. As we all waiting for F20, so we are not sure how many users are left […]</summary>
3553.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Hello all Foresight users.</p>
3554. <p>I wonder if anyone is interested to still get some updates to current fl:2-devel repo? If so, leave a tiny comment and will put in some time to update some regular packages in near future.</p>
3555. <p>As we all waiting for F20, so we are not sure how many users are left with latest Foresight today…..</p></div>
3556.    </content>
3557.    <updated>2014-05-19T15:44:41Z</updated>
3558.    <category term="Blog"/>
3559.    <category term="Linux"/>
3560.    <category term="fl 2 devel"/>
3561.    <author>
3562.      <name>Tomas Forsman</name>
3563.    </author>
3564.    <source>
3565.      <id>https://www.foresightlinux.se</id>
3566.      <link href="http://www.foresightlinux.se/category/blog/feed/" rel="self" type="application/atom+xml"/>
3567.      <link href="https://www.foresightlinux.se" rel="alternate" type="text/html"/>
3568.      <subtitle>Where it all begins</subtitle>
3569.      <title>Blog</title>
3570.      <updated>2014-06-08T11:10:52Z</updated>
3571.    </source>
3572.  </entry>
3573.  
3574.  <entry>
3575.    <id>tag:omaciel.github.io,2014-05-09:fauxfactory-021.html</id>
3576.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/VohMtM8X64k/fauxfactory-021.html" rel="alternate" type="text/html"/>
3577.    <title>FauxFactory 0.2.1</title>
3578.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><div class="figure">
3579. <img alt="paper bag release" src="https://farm4.staticflickr.com/3373/3204502310_f8025dbd75_m.jpg"/>
3580. </div>
3581. <p>Short on its heels, today I'm releasing <strong>FauxFactory 0.2.1</strong> to fix a
3582. <a class="reference external" href="http://catb.org/jargon/html/B/brown-paper-bag-bug.html">brown paper bag
3583. bug</a> I
3584. encountered last night before going to bed.</p>
3585. <p>Basically, the new "Lorem Ipsum" generator was not honoring the
3586. <strong>words</strong> parameter if you asked for a string longer than 70 characters.
3587. I ...</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/VohMtM8X64k" width="1"/></div>
3588.    </content>
3589.    <updated>2014-05-09T21:00:00Z</updated>
3590.    <published>2014-05-09T21:00:00Z</published>
3591.    <category term="python"/>
3592.    <category term="testing"/>
3593.    <category term="qe"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/fauxfactory-021.html</feedburner:origLink>
3594.    <author>
3595.      <name>Og Maciel</name>
3596.    </author>
3597.    <source>
3598.      <id>https://omaciel.github.io/</id>
3599.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
3600.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
3601.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
3602.      <title>Journal of an Open Sourcee</title>
3603.      <updated>2017-07-03T04:00:00Z</updated>
3604.    </source>
3605.  </entry>
3606.  
3607.  <entry xml:lang="en-us">
3608.    <id>https://omaciel.github.io/python/testing/qe/2014/05/09/brown-paper-bag-release</id>
3609.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/6xWeMs-KQWo/brown-paper-bag-release.html" rel="alternate" type="text/html"/>
3610.    <title>FauxFactory 0.2.1</title>
3611.    <summary type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p><img alt="paper bag release" src="https://farm4.staticflickr.com/3373/3204502310_f8025dbd75_m.jpg"/></p>
3612.  
3613. <p>Short on its heels, today I’m releasing <strong>FauxFactory 0.2.1</strong> to fix a
3614. <a href="http://catb.org/jargon/html/B/brown-paper-bag-bug.html">brown paper bag bug</a> I encountered last night before
3615. going to bed.</p>
3616.  
3617. <p>Basically, the new “Lorem Ipsum” generator was not honoring the
3618. <strong>words</strong> parameter if you asked for a string longer than 70
3619. characters. I have fixed the issue as well as added a new test to make
3620. sure that the generator does the right thing.</p>
3621.  
3622. <p>The package is available on <a href="https://pypi.python.org/pypi/fauxfactory/0.2.0">Pypi</a> (sadly the page is <strong>still</strong>
3623. not rendering correctly… suggestions welcome) and can be installed via
3624. <strong>pip install fauxfactory</strong>.</p>
3625.  
3626. <p>If you have any constructive feedback, suggestions, or file a bug
3627. report or feature request, please use the <a href="https://github.com/omaciel/fauxfactory">Github</a> page.</p>
3628.  
3629. <p><em>Image: <strong>Cry</strong> by <a href="https://secure.flickr.com/photos/privatenobby/">LLewleyn Williams a.k.a. SCUD</a>, some rights reserved</em>.</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/6xWeMs-KQWo" width="1"/></div>
3630.    </summary>
3631.    <updated>2014-05-09T17:00:00Z</updated><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/python/testing/qe/2014/05/09/brown-paper-bag-release.html</feedburner:origLink>
3632.    <author>
3633.      <name>Og Maciel</name>
3634.      <email>omaciel@ogmaciel.com</email>
3635.    </author>
3636.    <source>
3637.      <id>https://omaciel.github.io/</id>
3638.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
3639.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/rss+xml"/>
3640.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
3641.      <title>Journal of An Open Sourcee</title>
3642.      <updated>2014-12-31T19:14:08Z</updated>
3643.    </source>
3644.  </entry>
3645.  
3646.  <entry>
3647.    <id>tag:omaciel.github.io,2014-05-08:fauxfactory-020.html</id>
3648.    <link href="http://feedproxy.google.com/~r/JournalOfAnOpenSourcee/~3/C-NnMv0aIMM/fauxfactory-020.html" rel="alternate" type="text/html"/>
3649.    <title>FauxFactory 0.2.0</title>
3650.    <content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml"><p>Today I'm releasing <strong>FauxFactory 0.2.0</strong> with a new feature, a "Lorem
3651. Ipsum" generator. I confess that I did not look around for any existing
3652. implementation in python out there and just started writing code. My
3653. idea was to create a method that would:</p>
3654. <p>Return a "Lorem Ipsum ...</p><img alt="" height="1" src="http://feeds.feedburner.com/~r/JournalOfAnOpenSourcee/~4/C-NnMv0aIMM" width="1"/></div>
3655.    </content>
3656.    <updated>2014-05-08T23:12:00Z</updated>
3657.    <published>2014-05-08T23:12:00Z</published>
3658.    <category term="python"/>
3659.    <category term="testing"/>
3660.    <category term="qe"/><feedburner:origLink xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">https://omaciel.github.io/fauxfactory-020.html</feedburner:origLink>
3661.    <author>
3662.      <name>Og Maciel</name>
3663.    </author>
3664.    <source>
3665.      <id>https://omaciel.github.io/</id>
3666.      <link href="https://omaciel.github.io/" rel="alternate" type="text/html"/>
3667.      <link href="http://feeds.feedburner.com/JournalOfAnOpenSourcee" rel="self" type="application/atom+xml"/>
3668.      <link href="http://pubsubhubbub.appspot.com/" rel="hub" type="text/html"/>
3669.      <title>Journal of an Open Sourcee</title>
3670.      <updated>2017-07-03T04:00:00Z</updated>
3671.    </source>
3672.  </entry>
3673. </feed>
3674.