<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2enclosuresfull.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-6177317444519479825</atom:id><lastBuildDate>Wed, 30 May 2012 10:58:12 +0000</lastBuildDate><category>flash</category><category>tools</category><category>stadies</category><category>news</category><category>lunux</category><category>free</category><category>void</category><category>robot</category><category>SIP</category><category>new</category><category>hosting</category><category>association</category><category>VPN</category><category>impress</category><category>AI</category><category>Kbase</category><category>nginx</category><category>spam</category><category>embedded technology</category><category>LUG</category><category>Libre software</category><category>virtual</category><category>defects</category><category>open source commitment</category><category>facebook</category><category>packages</category><category>system</category><category>SSH</category><category>coud</category><category>academy</category><category>java</category><category>CAD</category><category>schedules</category><category>private data</category><category>success</category><category>computer scientists</category><category>faq</category><category>government</category><category>philosophy</category><category>testimonial</category><category>pdf</category><category>GPL</category><category>anonymous</category><category>desktop</category><category>Scrum</category><category>network</category><category>ubuntu</category><category>Computation</category><category>google</category><category>Data centers</category><category>technology</category><category>Informatics Technologies</category><category>nasa</category><category>Matlab</category><category>efficiency</category><category>system admin</category><category>iso</category><category>usa</category><category>online classes</category><category>protocols</category><category>GNU</category><category>command</category><category>anonymous-os</category><category>advocacy</category><category>high performance computing</category><category>visualisation</category><category>Libre</category><category>technologie</category><category>shell</category><category>systems</category><category>spyware</category><category>statement</category><category>mirror oslm</category><category>open standards</category><category>ICT</category><category>learning</category><category>repository</category><category>activist</category><category>DOE</category><category>annonce</category><category>cloud computing</category><category>computer science lebanon</category><category>writer</category><category>Software Development</category><category>distributed computing</category><category>file system</category><category>opinions</category><category>Open Source</category><category>networks</category><category>Octave</category><category>apache Microsoft</category><category>wireless</category><category>unix</category><category>touch-free</category><category>dedicated</category><category>foundation</category><category>kernel</category><category>foss</category><category>communications</category><category>alternatives</category><category>In-Vehicle Infotainment</category><category>management</category><category>replication</category><category>mobile</category><category>openid</category><category>Open Source Lebanon</category><category>libreoffice</category><category>courses</category><category>installation</category><category>web</category><category>web hosting</category><category>social collaboration</category><category>CAM</category><category>google appengine</category><category>Floss</category><category>projects</category><category>dvd</category><category>freedom</category><category>phone</category><category>fsf</category><category>Military</category><category>iphone</category><category>GIT</category><category>top</category><category>AGI</category><category>supercomputing</category><category>i-truc</category><category>future</category><category>business</category><category>scientists</category><category>mysql</category><category>security</category><category>xoom</category><category>sourceforge</category><category>OCW</category><category>groups</category><category>réseaux</category><category>language</category><category>cloud</category><category>bash</category><category>multimedia</category><category>automobile</category><category>gant</category><category>stallman</category><category>MITx</category><category>logiciels libre</category><category>Development</category><category>chalenge</category><category>android</category><category>tutorials</category><category>transparency</category><category>software</category><category>ACTA</category><category>base</category><category>Asteriks</category><category>coding</category><category>calc</category><category>quality</category><category>technews</category><category>revenue</category><category>campain</category><category>computing</category><category>users</category><category>media</category><category>PCAST</category><category>technologies</category><category>workflow</category><category>apple</category><category>network admin</category><category>mirror</category><category>piracy</category><category>document foundation</category><category>social</category><category>doocracy</category><category>autocad</category><category>arab</category><category>help</category><category>softaware</category><category>b2g</category><category>social networking</category><category>developers</category><category>commands</category><category>agile</category><category>Mozilla</category><category>consulting</category><category>functional</category><category>internet</category><category>script</category><category>IP PBX</category><category>debian</category><category>parallel</category><category>windows</category><category>open</category><category>citation analyze</category><category>motorola</category><category>mint</category><category>apache</category><category>linux</category><category>computer science</category><category>repositories</category><category>branching</category><category>cvs</category><category>openstack</category><category>OSGi</category><category>platform</category><category>guide</category><category>office</category><category>research</category><category>opposing Microsoft</category><category>programming</category><category>objects</category><category>voip</category><category>careers</category><category>entreprise</category><category>samsung</category><category>OSLM</category><category>MIT</category><category>Supercomputer</category><category>source</category><category>free software</category><category>jobs</category><category>fslm</category><category>raise</category><category>call</category><category>shared</category><category>Emergency Aid</category><category>healthcare</category><category>entertainment</category><category>data</category><category>lebanon</category><category>metadata</category><category>informations</category><title>Free Libre Open Source Lebanese Movement</title><description>Free software is simply software that respects our freedom — our freedom to learn and understand the software we are using. Free software is designed to free the user from restrictions put in place by proprietary software, and so using free software lets you join a global community of people who are making the political and ethical assertion of our rights to learn and to share what we learn with others.</description><link>http://oslm.cofares.net/</link><managingEditor>noreply@blogger.com (Pascal Emile Farès)</managingEditor><generator>Blogger</generator><openSearch:totalResults>222</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/oslm" /><feedburner:info uri="oslm" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><creativeCommons:license>http://creativecommons.org/licenses/by/3.0/</creativeCommons:license><feedburner:emailServiceId>oslm</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5906082296948458816</guid><pubDate>Wed, 30 May 2012 10:50:00 +0000</pubDate><atom:updated>2012-05-30T13:58:12.539+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">CAD</category><category domain="http://www.blogger.com/atom/ns#">autocad</category><title>Cad for linux (clone or near AutoCad)</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
&lt;div dir="ltr" style="background-color: white; color: #333333; font-family: Arial; font-size: 14px; line-height: 22px;" trbidi="on"&gt;
&lt;div style="text-align: justify;"&gt;
Autocad is not ported on Linux but some apps exist.&lt;/div&gt;
&lt;div style="text-align: justify;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div style="text-align: justify;"&gt;
Computer-aided design (CAD) is the use of computer technology for the process of design and design-documentation.&amp;nbsp;But are there any good free CAD apps for Linux? Strangely, that is one of the questions we often receive in our mail. We will try to list not just the free CAD apps here, but also the non-free ones that works well under Linux(in no particular order).&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-n-PuS-Gt_RU/Tdz9DURGdoI/AAAAAAAACG4/2g3MnyzAKmA/s1600/bricscad.jpeg" imageanchor="1" style="color: #5588aa; margin-left: 1em; margin-right: 1em;"&gt;&lt;img alt="Top CAD Apps for Linux" border="0" height="301" src="http://4.bp.blogspot.com/-n-PuS-Gt_RU/Tdz9DURGdoI/AAAAAAAACG4/2g3MnyzAKmA/s400/bricscad.jpeg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;a href="http://www.blogger.com/blogger.g?blogID=6177317444519479825" name="more"&gt;&lt;/a&gt;&lt;br /&gt;
&lt;div style="text-align: justify;"&gt;
&lt;b&gt;Bricscad&lt;/b&gt;&amp;nbsp;is a CAD package developed by Bricsys, originally built using the IntelliCAD engine. We have featured Bricscad before in our featured listing of&amp;nbsp;&lt;a href="http://www.techdrivein.com/2011/05/10-commercial-apps-for-linux-that-i.html" style="color: #2970a6; text-decoration: none;"&gt;top commercial apps for Linux&lt;/a&gt;. Bricscad is among the few commercially supported CAD packages which runs on Linux. Bricscad is capable of most contemporary AutoCAD functionalities.&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.bricsys.com/en_INTL/bricscad/index.jsp" style="color: #2970a6; text-decoration: none;"&gt;Download Bricscad for Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div style="text-align: justify;"&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-sONC-i9L99I/Tj-8pzslSWI/AAAAAAAACZE/zQmOKPBB09M/s1600/qcad_for_linux.png" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="GPLed QCad" border="0" height="313" src="http://2.bp.blogspot.com/-sONC-i9L99I/Tj-8pzslSWI/AAAAAAAACZE/zQmOKPBB09M/s400/qcad_for_linux.png" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;QCad&lt;/b&gt;&amp;nbsp;is a CAD software package for 2D design and drafting. QCad professional edition is the non-free version with options for limited-time free trial. There is also a community edition of QCad which is licensed under GPL. You can download QCad community edition for free.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.qcad.org/qcad_downloads.html" style="color: #2970a6; text-decoration: none;"&gt;Download QCad Professional and Community Editions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;span class="Apple-style-span" style="color: #0000ee;"&gt;&lt;u&gt;"&lt;/u&gt;&lt;/span&gt;&lt;a href="http://1.bp.blogspot.com/-48mN79HxnPc/Tj_BYdNuVQI/AAAAAAAACZI/cgKtzcM27Tc/s1600/freecad.jpg" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="freeCAD" border="0" height="235" src="http://1.bp.blogspot.com/-48mN79HxnPc/Tj_BYdNuVQI/AAAAAAAACZI/cgKtzcM27Tc/s400/freecad.jpg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;FreeCAD&lt;/b&gt;&amp;nbsp;is a free and Open Source 3D CAD/CAE program, based on OpenCascade, QT and Python. It features key concepts like macro recording, workbenches, ability to run as server and dynamically loadable application extensions. Windows, Mac and Linux versions available.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://sourceforge.net/projects/free-cad/" style="color: #2970a6; text-decoration: none;"&gt;Download FreeCAD for Windows, Mac and Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-KTC2-wzf7-E/Tj_Dt8TCjII/AAAAAAAACZM/6mj-_MP43X8/s1600/varicad.jpg" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="variCAD for Linux" border="0" height="301" src="http://1.bp.blogspot.com/-KTC2-wzf7-E/Tj_Dt8TCjII/AAAAAAAACZM/6mj-_MP43X8/s400/varicad.jpg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;VariCAD&lt;/b&gt;&amp;nbsp;is 3D/2D CAD program primarily meant for mechanical engineering design. VariCAD provides support for parameters and geometric constraints, tools for shells, pipelines, sheet metal unbending and crash tests, assembly support, mechanical part and symbol libraries, calculations, bills of materials, and more. VariCAD is a non-free, proprietary application with packages for Windows and Linux readily available.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.varicad.com/en/home/online-store/" style="color: #2970a6; text-decoration: none;"&gt;Buy VariCAD for Linux from VariCAD Online Store&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-cwz7r8e33C8/Tj_I93VEWmI/AAAAAAAACZQ/ECMZZj2uKQE/s1600/opencascade_CAD.jpg" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img border="0" height="300" src="http://2.bp.blogspot.com/-cwz7r8e33C8/Tj_I93VEWmI/AAAAAAAACZQ/ECMZZj2uKQE/s400/opencascade_CAD.jpg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;Open CASCADE Technology&lt;/b&gt;&amp;nbsp;is a software development platform for 3D surface and solid modeling, visualization, data exchange and rapid application development. Open CASCADE Technology is available for free download and is licensed under&amp;nbsp;Open CASCADE Technology Public License which the developer claims to be 'LGPL-like with certain differences'. The Debian project considers the license to meet the Debian Free Software Guidelines and has accepted Open CASCADE into its main archive.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.opencascade.org/getocc/download/" style="color: #2970a6; text-decoration: none;"&gt;Download&amp;nbsp;Open CASCADE Technology for Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-Powi6ow1XMs/Tj_KnvawVzI/AAAAAAAACZU/mNoVsMX6XTo/s1600/cycas_CAD.jpg" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="cycas 3D CAD" border="0" height="331" src="http://4.bp.blogspot.com/-Powi6ow1XMs/Tj_KnvawVzI/AAAAAAAACZU/mNoVsMX6XTo/s400/cycas_CAD.jpg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;b&gt;CYCAS&lt;/b&gt;&amp;nbsp;is a 2D/3D CAD application for Windows and Linux which offers special elements and techniques for architectural design apart from normal CAD techniques. CYCAS enables intuitive and uncomplicated handling of 2D and 3D elements. It is non-free and proprietary.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.cycas.de/down.php?s=en#top" style="color: #2970a6; text-decoration: none;"&gt;Download CYCAS for Windows, Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-PiaKiU-61dI/Tj_PnAoeI9I/AAAAAAAACZY/jVWZVDZ-YBY/s1600/Cityeninge_3D_CAD.jpg" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="cityengine" border="0" height="232" src="http://3.bp.blogspot.com/-PiaKiU-61dI/Tj_PnAoeI9I/AAAAAAAACZY/jVWZVDZ-YBY/s400/Cityeninge_3D_CAD.jpg" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;CityEngine&lt;/b&gt;&amp;nbsp;is a 3D modeling application specialized in the generation of three dimensional urban environments&lt;b&gt;.&amp;nbsp;&lt;/b&gt;Key features of CityEngine include GIS/CAD Data Support, Dynamic City Layouts, Street Networks Patterns, Map-Controlled City Modeling, Industry-Standard 3D Formats and more. CityEngine is non-free and is available for Windows, Mac and Linux.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.procedural.com/purchase/commercial-solutions.html" style="color: #2970a6; text-decoration: none;"&gt;Download CityEngine for Windows, Mac and Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-48s_qZvOhz0/Tj_V3zxoPoI/AAAAAAAACZc/on-eIYEZWnI/s1600/CAD_Linux.png" imageanchor="1" style="color: #2970a6; margin-left: 1em; margin-right: 1em; text-decoration: none;"&gt;&lt;img alt="BRL-CAD" border="0" height="250" src="http://1.bp.blogspot.com/-48s_qZvOhz0/Tj_V3zxoPoI/AAAAAAAACZc/on-eIYEZWnI/s400/CAD_Linux.png" style="border-bottom-style: none; border-bottom-width: 0px; border-color: initial; border-image: initial; border-left-style: none; border-left-width: 0px; border-right-style: none; border-right-width: 0px; border-top-style: none; border-top-width: 0px; border-width: initial; padding-bottom: 2px; padding-left: 2px; padding-right: 2px; padding-top: 2px;" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;b&gt;BRL-CAD&lt;/b&gt;&amp;nbsp;is a cross-platform open source solid modeling system that includes interactive geometry editing, high-performance ray-tracing for rendering and geometric analysis, image and signal-processing tools, a system performance analysis benchmark suite, libraries for robust geometric representation, with more than 20 years of active development. BRL-CAD is free to download and is available for almost all platforms out there.&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://brlcad.org/d/download" style="color: #2970a6; text-decoration: none;"&gt;Download BRL-CAD for Windows, Mac, Linux, Solaris etc.&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
&lt;b&gt;Edit: 3 Other CAD Apps for Linux Recommended by Our Readers&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.3ds.com/products/draftsight/download-draftsight/" style="color: #2970a6; text-decoration: none;"&gt;Draftsight&lt;/a&gt;&amp;nbsp;- It was a really big mistake from our part for not including Draftsight in the first place. DraftSight is a free 2D CAD product developed by Dassault Systèmes. DraftSight lets users to create, edit and view DWG, DXF files easily. Specific packages for Ubuntu, Fedora, Mandriva and Suse available for free download.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://librecad.org/cms/home.html" style="color: #2970a6; text-decoration: none;"&gt;LibreCAD&lt;/a&gt;&amp;nbsp;is the free and Open Source personal CAD application for Windows, Mac and Linux.&amp;nbsp;LibreCAD is among the very few truly community driven CAD app for Linux.&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.graebert.com/en/cad/ares/99" style="color: #2970a6; text-decoration: none;"&gt;ARES Commander Edition for Linux&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5906082296948458816?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0RLvGkF6eU7K-zwNsCrj1b2LsRo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0RLvGkF6eU7K-zwNsCrj1b2LsRo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0RLvGkF6eU7K-zwNsCrj1b2LsRo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0RLvGkF6eU7K-zwNsCrj1b2LsRo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/RF02qk25nVs" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/RF02qk25nVs/cad-for-linux-clone-or-near-autocad.html</link><author>noreply@blogger.com (Pascal Fares)</author><media:thumbnail url="http://4.bp.blogspot.com/-n-PuS-Gt_RU/Tdz9DURGdoI/AAAAAAAACG4/2g3MnyzAKmA/s72-c/bricscad.jpeg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/cad-for-linux-clone-or-near-autocad.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-4695760817744631262</guid><pubDate>Sun, 27 May 2012 18:38:00 +0000</pubDate><atom:updated>2012-05-27T21:38:45.854+03:00</atom:updated><title>'Father of the Internet' Warns Web Freedom Is Under Attack</title><description>&lt;p&gt;&lt;br&gt;  The Hill&lt;br&gt;  (05/21/12) Andrew Feinberg&lt;/p&gt;  &lt;p&gt; Governments around the world are trying to use intellectual property and cybersecurity issues to control the Internet, says Google vice president and chief Internet evangelist Vint Cerf. &amp;quot;Political structures ... are often scared by the possibility that the general public might figure out that they don&amp;#39;t want them in power,&amp;quot; Cerf says. He speculates that the International Telecommunications Union will likely become the global Internet cop, and expects the group to try to lock in mandatory intellectual property protections as a backdoor for easy Web surveillance. The public should view even good-faith efforts at Internet policymaking skeptically because balancing freedom and security &amp;quot;isn&amp;#39;t something that government alone is going to figure out,&amp;quot; Cerf says. He is concerned about the U.S. Cybersecurity and Intelligence Protection Act passed by the House, because it does not offer enough limits on how information about cyberthreats would be used. Still, Cerf expresses optimism that resourceful engineers will find a way around hostile government attempts to restrict access.&lt;/p&gt;    &lt;p&gt;View Full Article&lt;br&gt;  &lt;a href="http://thehill.com/blogs/hillicon-valley/technology/228561-father-of-the-internet-warns-web-freedom-is-under-attack"&gt;http://thehill.com/blogs/hillicon-valley/technology/228561-father-of-the-internet-warns-web-freedom-is-under-attack&lt;/a&gt;&lt;br&gt;    &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-4695760817744631262?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/cxmX_7QVOdUIQ7VxEizhzSbNkI0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/cxmX_7QVOdUIQ7VxEizhzSbNkI0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/cxmX_7QVOdUIQ7VxEizhzSbNkI0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/cxmX_7QVOdUIQ7VxEizhzSbNkI0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/ScE_bY7G09M" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/ScE_bY7G09M/father-of-internet-warns-web-freedom-is.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/father-of-internet-warns-web-freedom-is.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-3509957748222578041</guid><pubDate>Fri, 25 May 2012 16:45:00 +0000</pubDate><atom:updated>2012-05-25T19:45:43.538+03:00</atom:updated><title>Why Wall Street hate open source?</title><description>&lt;p&gt;&lt;a href="http://www.thestreet.mobi/story/11547866/1/why-wall-street-hates-open-source.html"&gt;http://www.thestreet.mobi/story/11547866/1/why-wall-street-hates-open-source.html&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-3509957748222578041?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/OWxYC-RS9RxBNdRknd8I63gZNpc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OWxYC-RS9RxBNdRknd8I63gZNpc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/OWxYC-RS9RxBNdRknd8I63gZNpc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/OWxYC-RS9RxBNdRknd8I63gZNpc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/KX5QzeDnck4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/KX5QzeDnck4/why-wall-street-hate-open-source.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/why-wall-street-hate-open-source.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-9132862120916192178</guid><pubDate>Fri, 25 May 2012 16:39:00 +0000</pubDate><atom:updated>2012-05-25T19:39:37.344+03:00</atom:updated><title>[Ma3bar Announcement] "Linux Essentials Certification" exam at UOB - June 5, 2012 - Free of charge</title><description>&lt;p&gt;&lt;br&gt;  &amp;quot;Linux Essentials Certification&amp;quot; exam at UOB - June 5, 2012 - Free of charge&lt;br&gt;  Free Linux Essentials Certification Exam&lt;br&gt;  University of Balamand,&lt;br&gt;  Al-Kurah, Lebanon&lt;br&gt;  Tuesday June 5, 2012 - 9:30 AM&lt;br&gt;  (Registration is open until 8:00 PM June 1, 2012)&lt;br&gt;   &lt;br&gt;  (Beirut, Lebanon: April 19, 2012) The Linux Professional Institute - Middle East (LPI-ME: &lt;a href="http://www.lpime.org"&gt;www.lpime.org&lt;/a&gt;), issued a call for volunteers to participate in the first &amp;quot;beta&amp;quot; exams for the Linux Professionals Institute&amp;#39;s (LPI: &lt;a href="http://www.lpi.org"&gt;www.lpi.org&lt;/a&gt;) &amp;quot;Linux Essentials&amp;quot; program.&lt;/p&gt;    &lt;p&gt;"Linux Essentials" is an innovative new program measuring foundational knowledge in Linux and Open Source Software and will be publicly released in June 2012.  &amp;quot;Beta&amp;quot; exams are offered free to volunteers who wish to assist LPI in its exam development process for the &amp;quot;Linux Essentials&amp;quot; program.&lt;/p&gt;    &lt;p&gt;During the month of May and early June, there will be various sessions for volunteers to take &amp;quot;beta&amp;quot; exams which are offered free of charge.  This volunteer effort will enable LPI to measure the &amp;quot;Linux Essentials&amp;quot; exam for quality, accuracy and relevancy.  All interested individuals who do not hold an existing Linux certification are invited to participate--however seating is limited to ten per session.&lt;/p&gt;    &lt;p&gt;Successful candidates who pass the exam will be awarded a &amp;quot;Linux Essentials Certificate of Achievement&amp;quot;.  Alternatively candidates may choose to have their exam results deleted from their registration record. Final exam scores for the volunteer &amp;quot;beta&amp;quot; exams will be available in late June 2012.&lt;/p&gt;    &lt;p&gt;Each &amp;quot;beta&amp;quot; session is for ninety minutes and consists of sixty questions. To participate exam volunteers must obtain an LPI ID at &lt;a href="https://cs.lpi.org/caf/Xamman/register"&gt;https://cs.lpi.org/caf/Xamman/register&lt;/a&gt; and register in advance for the Linux Essentials &amp;quot;beta&amp;quot; exam with their focal point.&lt;/p&gt;    &lt;p&gt;Targeted at new technology users, the "Linux Essentials" program is set to be adopted by schools, universities, educational authorities, training centers and others commencing June 2012.&lt;/p&gt;  &lt;p&gt;The Linux Professional Institute is globally supported by the IT industry, enterprise customers, community professionals, government entities and the educational community. LPI&amp;#39;s certification program is supported by an affiliate network spanning five continents and is distributed worldwide in multiple languages at more than 7,000 testing locations. Since 1999, LPI has delivered over 300,000 exams and 100,000 LPIC certifications around the world.&lt;/p&gt;    &lt;p&gt; &lt;br&gt;  Overview of the Exam&lt;/p&gt;  &lt;p&gt;To secure the Certificate of Achievement in Linux Essentials, you should be able to demonstrate a(n):&lt;/p&gt;  &lt;p&gt;Understands the basic concepts of processes, programs and the components of an Operating System.&lt;br&gt;  Has a basic knowledge of computer hardware&lt;br&gt;  Demonstrates a knowledge of Open Source Applications in the Workplace as they relate to Closed Source equivalents.&lt;br&gt;  Understands navigation systems on a Linux Desktop and where to go for help.&lt;br&gt;  Has a rudimentary ability to work on the command line and with files.&lt;br&gt;  Can use a basic command line editor.&lt;br&gt;  Detailed exam objectives and coverage are available at &lt;a href="http://www.lpi.org/linux-certifications/introductory-programs/linux-essentials"&gt;www.lpi.org/linux-certifications/introductory-programs/linux-essentials&lt;/a&gt;&lt;br&gt;     &lt;br&gt;  Registration form&lt;br&gt;   &lt;br&gt;  Reserve your seat in the exam on June 5 at the University of Balamand by filling and submitting the form below. For further inquiries, please contact us at &lt;a href="mailto:info@ma3bar.org"&gt;info@ma3bar.org&lt;/a&gt;&lt;br&gt;   &lt;br&gt;  Registration is open until 8:00 PM June 1, 2012&lt;br&gt;  Ma3bar Announcement&lt;/p&gt;  &lt;p&gt;Unsubscribe from this newsletter&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-9132862120916192178?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ofXJSWsoVxYJ4vRaFIfH0tf5JZg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ofXJSWsoVxYJ4vRaFIfH0tf5JZg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ofXJSWsoVxYJ4vRaFIfH0tf5JZg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ofXJSWsoVxYJ4vRaFIfH0tf5JZg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/lwS-KfmYUBY" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/lwS-KfmYUBY/ma3bar-announcement-linux-essentials.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/ma3bar-announcement-linux-essentials.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-6757004606735993045</guid><pubDate>Sat, 19 May 2012 11:26:00 +0000</pubDate><atom:updated>2012-05-19T14:26:42.939+03:00</atom:updated><title>Fwd: GNU/Linux LPIC-1 Training Workshop - July 2012 @ AUST Beirut</title><description>&lt;p class="mobile-photo"&gt;&lt;a href="http://1.bp.blogspot.com/-SyzKO0mVVaA/T7eDc23kWtI/AAAAAAAADs8/Jx2hZ7GKAR0/s1600/WorkshopBanner_v02s-702945.jpg"&gt;&lt;img src="http://1.bp.blogspot.com/-SyzKO0mVVaA/T7eDc23kWtI/AAAAAAAADs8/Jx2hZ7GKAR0/s320/WorkshopBanner_v02s-702945.jpg"  border="0" alt="" id="BLOGGER_PHOTO_ID_5744204381522516690" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;  &lt;p&gt;Registration NOW OPEN&lt;/p&gt;  &lt;p&gt;Registration form available at &lt;a href="http://ma3bar.org/?q=en/node/170"&gt;http://ma3bar.org/?q=en/node/170&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;LPI-101 – July 3 – 6, 2012&lt;/p&gt;  &lt;p&gt;LPI-102 – July 9 – 12, 2012&lt;/p&gt;  &lt;p&gt;In collaboration with LPI, the Linux Professional Institute, Ma3bar, the Arab Support Center for Free &amp;amp; Open Source Software, and the IEEE Computer Society – Lebanon Chapter, The Department of Computer Science at the American University of Science and Technology – AUST announces a GNU/Linux Training Workshop on the campus of AUST, Ashrafieh, Beirut, Lebanon. This workshop covers two courses, LPI-101 and LPI-102, which lead to the LPIC-1 renown certification.&lt;/p&gt;    &lt;p&gt;Purpose&lt;/p&gt;  &lt;p&gt;As part of Ma3bar&amp;#39;s mission to promote Free Software in Arab societies, this Training workshop is a fourth of a series of GNU/Linux training workshops that aim to increase the level of competence in Free Software environments.&lt;/p&gt;    &lt;p&gt;LPIC-1 – Junior Level Linux Professional&lt;/p&gt;  &lt;p&gt;LPIC-1 is the first IT certification program to be professionally accredited by National Commission For Certifying Agencies (NCCA). It requires passing both exams of LPI-101 and LPI-102. To pass this level, someone should be able to:&lt;/p&gt;    &lt;p&gt;- Work at the GNU/Linux command line&lt;/p&gt;  &lt;p&gt;- Perform easy maintenance tasks: help out users, add users to a larger system, backup &amp;amp; restore, shutdown &amp;amp; reboot&lt;/p&gt;  &lt;p&gt;- Install and configure a workstation (including X) and connect it to a LAN, or a stand-alone PC to the Internet.&lt;/p&gt;  &lt;p&gt;LPI-101 – July 3 – 6, 2012&lt;br&gt;        (4 sessions, 2:00–8:00 PM)&lt;/p&gt;  &lt;p&gt;This course covers basic skills for the GNU/Linux professional that are common to major distributions of GNU/Linux.&lt;/p&gt;  &lt;p&gt;Topics include:&lt;/p&gt;  &lt;p&gt;- System Architecture&lt;br&gt;  - Determine and configure hardware settings&lt;br&gt;  - Boot the system&lt;br&gt;  - Change run-levels and shutdown or reboot system&lt;br&gt;  - GNU/Linux Installation and Package Management&lt;br&gt;  - Design hard disk layout&lt;br&gt;  - Install a boot manager&lt;br&gt;  - Manage shared libraries&lt;br&gt;  - Use Debian package management&lt;br&gt;  - Use RPM and YUM package management&lt;br&gt;  - GNU and Unix Commands&lt;br&gt;  - Work on the command line&lt;br&gt;  - Process text streams using filters&lt;br&gt;  - Perform basic file management&lt;br&gt;  - Use streams, pipes and redirects&lt;br&gt;  - Create, monitor and kill processes&lt;br&gt;  - Modify process execution priorities&lt;br&gt;  - Search text files using regular expressions&lt;br&gt;  - Perform basic file editing operations using vi&lt;br&gt;  - Devices, Linux Filesystems, Filesystem Hierarchy Standard&lt;br&gt;  - Create partitions and filesystems&lt;br&gt;  - Maintain the integrity of filesystems&lt;br&gt;  - Control mounting and unmounting of filesystems&lt;br&gt;  - Manage disk quotas&lt;br&gt;  - Manage file permissions and ownership&lt;br&gt;  - Create and change hard and symbolic links&lt;br&gt;  - Find system files and place files in the correct location&lt;/p&gt;  &lt;p&gt;LPI-102 – July 9-12, 2012&lt;br&gt;        (4 sessions, 2:00–8:00 PM)&lt;/p&gt;  &lt;p&gt;This course covers basic &amp;amp; more advanced skills for the GNU/Linux professional that are common to major distributions of GNU/Linux.&lt;/p&gt;  &lt;p&gt;Topics include:&lt;/p&gt;  &lt;p&gt;- Shells, Scripting and Data Management&lt;br&gt;  - Customize and use the shell environment&lt;br&gt;  - Customize or write simple scripts&lt;br&gt;  - SQL data management&lt;br&gt;  - User Interfaces and Desktops&lt;br&gt;  - Install and configure X11&lt;br&gt;  - Setup a display manager&lt;br&gt;  - Accessibility&lt;br&gt;  - Administrative Tasks&lt;br&gt;  - Manage user and group accounts and related system files&lt;br&gt;  - Automate system administration tasks by scheduling jobs&lt;br&gt;  - Localization and internationalization&lt;br&gt;  - Essential System Services&lt;br&gt;  - Maintain system time&lt;br&gt;  - System logging- Mail Transfer Agent (MTA) basics&lt;br&gt;  - Manage printers and printing&lt;br&gt;  - Networking Fundamentals&lt;br&gt;  - Fundamentals of internet protocols&lt;br&gt;  - Basic network configuration&lt;br&gt;  - Basic network troubleshooting&lt;br&gt;  - Configure client side DNS&lt;br&gt;  - Security&lt;br&gt;  - Perform security administration tasks&lt;br&gt;  - Setup host security- Securing data with encryption&lt;/p&gt;  &lt;p&gt;LPIC-1 certification exams&lt;/p&gt;  &lt;p&gt;LPIC-1 certification requires passing both exams 101 and 102. These two exams can be taken anytime at any LPI certified exam center. It is recommended that trainees consider taking the exams at least two weeks after the workshop in order to have adequate time to prepare, practice and review. More information about the exams will be provided during the workshop.&lt;/p&gt;    &lt;p&gt; &lt;br&gt;  Who should attend&lt;/p&gt;  &lt;p&gt;- Beginner users in GNU/Linux environments who want to gain further technical skills&lt;/p&gt;  &lt;p&gt;- Users of GNU/Linux who want to start building basic skills in system administration and configuration&lt;/p&gt;  &lt;p&gt;- Computer professionals, fresh graduates, or students in graduate schools who want to become certified GNU/Linux professionals&lt;/p&gt;  &lt;p&gt;Registration&lt;/p&gt;  &lt;p&gt;Registration is open until June 22, 2012. Early bird registration fees apply on or before June 2, 2012. Registration is confirmed only upon filling the on-line application form at &lt;a href="http://ma3bar.org/?q=en/node/170"&gt;http://ma3bar.org/?q=en/node/170&lt;/a&gt; and receiving the full payment.&lt;/p&gt;    &lt;p&gt;Travel &amp;amp; Accommodation&lt;/p&gt;  &lt;p&gt;For participants coming from neighboring Arab countries, assistance and special rates on travel and accommodation will be arranged. Please contact &lt;a href="mailto:gnulinux@ma3bar.org"&gt;gnulinux@ma3bar.org&lt;/a&gt; for further details.&lt;/p&gt;    &lt;p&gt;What you get&lt;/p&gt;  &lt;p&gt;- Student material and study aid kit, including Approved Training Material – ATM, presentations, labs, electronic material, practice exams, and LPI portal access&lt;/p&gt;  &lt;p&gt;- Certificate of attendance&lt;/p&gt;  &lt;p&gt;- 90% certification success rate&lt;/p&gt;  &lt;p&gt;Cost Matrix&lt;/p&gt;  &lt;p&gt;LPI-101 (IEEE student member rate) *&lt;br&gt;  LPI-102 (IEEE student member rate) * §&lt;br&gt;  LPI-101 (student rate) §&lt;br&gt;  LPI-102 (student** rate) §&lt;br&gt;  LPI-101 (IEEE member professional rate) †&lt;br&gt;  LPI-102 (IEEE member professional rate) †&lt;br&gt;  LPI-101 (professional rate)&lt;br&gt;  LPI-102 (professional rate)&lt;br&gt;  LPI-101 (group professional rate) ‡&lt;br&gt;  LPI-102 (group professional rate) ‡&lt;/p&gt;  &lt;p&gt;Early bird rate&lt;/p&gt;  &lt;p&gt;USD 400&lt;br&gt;  USD 400&lt;br&gt;  USD 450&lt;br&gt;  USD 450&lt;br&gt;  USD 750&lt;br&gt;  USD 750&lt;br&gt;  USD 900&lt;br&gt;  USD 900&lt;br&gt;  USD 800&lt;br&gt;  USD 800&lt;br&gt;   &lt;/p&gt;  &lt;p&gt;Full rate&lt;/p&gt;  &lt;p&gt;USD    450&lt;br&gt;  USD    450&lt;br&gt;  USD    500&lt;br&gt;  USD    500&lt;br&gt;  USD    850&lt;br&gt;  USD    850&lt;br&gt;  USD 1,000&lt;br&gt;  USD 1,000&lt;br&gt;  USD    900&lt;br&gt;  USD    900&lt;br&gt;   &lt;/p&gt;  &lt;p&gt;* a valid IEEE student membership card for 2012 is required.&lt;br&gt;  § an eligible student must have a valid student ID from an accredited Institution of higher education, and should be less than 25 years of age.&lt;br&gt;  † an eligible group consists of two or more persons delegated by an organization&lt;br&gt;  ‡ a valid IEEE membership card for 2012 is required.&lt;/p&gt;  &lt;p&gt; &lt;br&gt;  Contact us&lt;/p&gt;  &lt;p&gt;For more information, please contact:&lt;/p&gt;  &lt;p&gt;Dr. Aziz M. Barbar&lt;br&gt;  Chair, IEEE Computer Chapter, Lebanon&lt;br&gt;  Chairperson, Department of Computer Science&lt;br&gt;  AUST - American University of Science &amp;amp; Technology&lt;br&gt;  Alfred Naccash Avenue – Ashrafieh&lt;br&gt;  P.O. Box: 16-6452 Beirut 1100-2130, Lebanon&lt;br&gt;  Tel : +961 (0)1 218 716, Ext. 311&lt;br&gt;  Fax: +961 (0)1 339 302&lt;br&gt;  email: &lt;a href="mailto:gnulinux@ma3bar.org"&gt;gnulinux@ma3bar.org&lt;/a&gt;&lt;br&gt;  web: &lt;a href="http://ma3bar.org/gnulinux/"&gt;http://ma3bar.org/gnulinux/&lt;/a&gt;&lt;/p&gt;  &lt;p&gt;________________________________&lt;br&gt;  You are receiving this message because you are registered to this mailing list at &lt;a href="http://ma3bar.org"&gt;ma3bar.org&lt;/a&gt;. We respect your privacy and hold your communication preferences in the highest regard. If you have any suggestions or questions about the &lt;a href="http://ma3bar.org"&gt;ma3bar.org&lt;/a&gt; e-mail subscriptions, of if you wish to unsubscribe from this list, please contact us at: &lt;a href="mailto:info@ma3bar.org"&gt;info@ma3bar.org&lt;/a&gt;&lt;/p&gt;    &lt;p&gt; &lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-6757004606735993045?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/6v23J-FzU08myxPzRcqbT1Q7IMQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6v23J-FzU08myxPzRcqbT1Q7IMQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/6v23J-FzU08myxPzRcqbT1Q7IMQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/6v23J-FzU08myxPzRcqbT1Q7IMQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/8p-m1lKllUc" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/8p-m1lKllUc/fwd-gnulinux-lpic-1-training-workshop.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><media:thumbnail url="http://1.bp.blogspot.com/-SyzKO0mVVaA/T7eDc23kWtI/AAAAAAAADs8/Jx2hZ7GKAR0/s72-c/WorkshopBanner_v02s-702945.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/fwd-gnulinux-lpic-1-training-workshop.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-646425192994714133</guid><pubDate>Sat, 19 May 2012 10:34:00 +0000</pubDate><atom:updated>2012-05-19T13:34:29.298+03:00</atom:updated><title>LPIC-1 GNU/Linux Workshop, July 2012</title><description>&lt;p&gt;&lt;a href="http://ma3bar.org/gnulinux"&gt;http://ma3bar.org/gnulinux&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-646425192994714133?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/NsJMgj4lEwhFawkppbiGeZF00k4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/NsJMgj4lEwhFawkppbiGeZF00k4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/NsJMgj4lEwhFawkppbiGeZF00k4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/NsJMgj4lEwhFawkppbiGeZF00k4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/uNBOzt6tjeA" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/uNBOzt6tjeA/lpic-1-gnulinux-workshop-july-2012.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/lpic-1-gnulinux-workshop-july-2012.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-6888510175763933895</guid><pubDate>Fri, 18 May 2012 19:12:00 +0000</pubDate><atom:updated>2012-05-18T22:12:24.111+03:00</atom:updated><title>Open Source Startup Inktank Sets Gaze On Ubuntu | The VAR Guy</title><description>&lt;p&gt;&lt;a href="http://www.thevarguy.com/2012/05/15/open-source-startup-inktank-sets-gaze-on-ubuntu-server/"&gt;http://www.thevarguy.com/2012/05/15/open-source-startup-inktank-sets-gaze-on-ubuntu-server/&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-6888510175763933895?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/1t0JZEy8IgFcp7MXEbkB3x3AUrU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1t0JZEy8IgFcp7MXEbkB3x3AUrU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/1t0JZEy8IgFcp7MXEbkB3x3AUrU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1t0JZEy8IgFcp7MXEbkB3x3AUrU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/WU-2IVXS6d4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/WU-2IVXS6d4/open-source-startup-inktank-sets-gaze.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/open-source-startup-inktank-sets-gaze.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-3793357301315953374</guid><pubDate>Sun, 13 May 2012 15:20:00 +0000</pubDate><atom:updated>2012-05-13T18:20:05.394+03:00</atom:updated><title>iText (R) - Free / Open Source PDF Library for Java and C#</title><description>&lt;p&gt;&lt;a href="http://itextpdf.com/index.php"&gt;http://itextpdf.com/index.php&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-3793357301315953374?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/uhB1taw5jNbYuwzM5B9QY4r5-eM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/uhB1taw5jNbYuwzM5B9QY4r5-eM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/uhB1taw5jNbYuwzM5B9QY4r5-eM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/uhB1taw5jNbYuwzM5B9QY4r5-eM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/g58FfJwTJ7U" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/g58FfJwTJ7U/itext-r-free-open-source-pdf-library.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/itext-r-free-open-source-pdf-library.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-8579857060903577215</guid><pubDate>Sat, 12 May 2012 08:21:00 +0000</pubDate><atom:updated>2012-05-12T11:21:54.676+03:00</atom:updated><title>Bringing Open, User-Centric Cloud Infrastructure to Research Communities</title><description>&lt;p&gt;Communities CORDIS News&lt;br&gt;  (05/04/12) &lt;/p&gt;  &lt;p&gt; European researchers working on the VENUS-C project have developed an open, scalable, and user-centered cloud computing infrastructure, highlighting an attempt to implement a user-centric approach to the cloud. Cloud computing empowers researchers &amp;quot;in a number of different ways, enabling them not only to do better science by accelerating discovery but also new science they could not have done before,&amp;quot; says VENUS-C project director Andrea Manieri. The new infrastructure integrates easily with users&amp;#39; working environments and provides on-demand access to cloud resources as and when needed. &amp;quot;Our approach to the interoperability layer tackles current challenges with our users firmly in mind,&amp;quot; Manieri says. The researchers used the VENUS-C infrastructure on Microsoft&amp;#39;s Windows Azure platform to run BLAST, a data-intensive tool used by biologists to find regions of local similarity in amino-acid sequences of different proteins. The VENUS-C infrastructure made the experiment cost less than 600 euros and take just a week to process the data that normally would have taken more than year. &amp;quot;The advantage of using VENUS-C BLAST compared with renting cloud resources and deploying high-performance computing or high-throughput versions of BLAST is that deployment efforts are minimized and client impact is also minimal, since users don&amp;amp;#8217;t have to log-in on a different machine,&amp;quot; says VENUS-C&amp;#39;s Ignacio Blanquer.&lt;/p&gt;    &lt;p&gt;View Full Article&lt;br&gt;  &lt;a href="http://cordis.europa.eu/fetch?CALLER=OFFR_TM_EN&amp;amp;amp;ACTION=D&amp;amp;amp;DOC=2&amp;amp;amp;CAT=OFFR&amp;amp;amp;QUERY=01372c12290d:268c:2205a860&amp;amp;amp;RCN=8520"&gt;http://cordis.europa.eu/fetch?CALLER=OFFR_TM_EN&amp;amp;amp;ACTION=D&amp;amp;amp;DOC=2&amp;amp;amp;CAT=OFFR&amp;amp;amp;QUERY=01372c12290d:268c:2205a860&amp;amp;amp;RCN=8520&lt;/a&gt;&lt;/p&gt;    &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-8579857060903577215?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Z-00Na8pcC_1HyIeauqFtflQfu4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Z-00Na8pcC_1HyIeauqFtflQfu4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Z-00Na8pcC_1HyIeauqFtflQfu4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Z-00Na8pcC_1HyIeauqFtflQfu4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/oEE99l0Ez8w" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/oEE99l0Ez8w/bringing-open-user-centric-cloud.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/bringing-open-user-centric-cloud.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5678598265862771166</guid><pubDate>Sat, 12 May 2012 08:20:00 +0000</pubDate><atom:updated>2012-05-12T11:20:03.483+03:00</atom:updated><title>Google Gets License for Driverless Car</title><description>&lt;p&gt;&lt;br&gt;  InformationWeek&lt;br&gt;  (05/08/12) Thomas Claburn&lt;/p&gt;  &lt;p&gt; Nevada has issued a license that permits Google to test its experimental self-driving cars on state roads. Google, which provided demonstrations of its autonomous cars on state freeways, highways, and roads in Carson City and Las Vegas to Nevada&amp;#39;s Autonomous Review Committee, also received special red license plates bearing an infinity symbol. &amp;quot;We&amp;#39;re excited to receive the first testing license for self-driving vehicles in Nevada,&amp;quot; says a Google representative. &amp;quot;We believe the state&amp;#39;s framework--the first of its kind--will help speed up the delivery of technology that will make driving safer and more enjoyable.&amp;quot; The Nevada Department of Motor Vehicles says automakers also have expressed interest in testing autonomous vehicles in the future. Autonomous vehicle legislation was introduced in the California State Assembly in March, and Arizona, Hawaii, and Florida also are in the process of considering legislation. Meanwhile, Google recently acquired a Federal Communications Commission permit to operate automatic cruise control radar units in the 76.0-77.0 GHz band for driverless car navigation.&lt;/p&gt;    &lt;p&gt;View Full Article&lt;br&gt;  &lt;a href="http://www.informationweek.com/news/government/policy/232901672"&gt;http://www.informationweek.com/news/government/policy/232901672&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5678598265862771166?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/j9FcvEMuiWGw-Qg-xax8Q6v5w_o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/j9FcvEMuiWGw-Qg-xax8Q6v5w_o/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/j9FcvEMuiWGw-Qg-xax8Q6v5w_o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/j9FcvEMuiWGw-Qg-xax8Q6v5w_o/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/Nx3VRujH-VY" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/Nx3VRujH-VY/google-gets-license-for-driverless-car.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/google-gets-license-for-driverless-car.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-7585275603502115324</guid><pubDate>Fri, 11 May 2012 08:37:00 +0000</pubDate><atom:updated>2012-05-11T11:37:27.371+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">GIT</category><category domain="http://www.blogger.com/atom/ns#">branching</category><title>A successful Git branching model</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
&lt;h1 style="background-color: white; clear: left; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; font-size: 40px; letter-spacing: -1px; line-height: 40px; margin-bottom: 26px; margin-left: 0px; margin-right: 0px; margin-top: 26px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;span style="color: #cccccc; font-size: 12px; line-height: 20px; text-align: left;"&gt;Published:&lt;/span&gt;&lt;span style="color: #cccccc; font-size: 12px; line-height: 20px; text-align: left;"&gt;&amp;nbsp;&lt;/span&gt;&lt;span class="reldate" style="color: #888888; font-size: 12px; line-height: 20px; text-align: left;"&gt;January 05, 2010&lt;/span&gt;&lt;/h1&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
In this post the author present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so&amp;nbsp;thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="center" src="http://nvie.com/img/2009/12/Screen-shot-2009-12-24-at-11.32.03.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; display: block; margin-bottom: 0px; margin-left: auto; margin-right: auto; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
It focuses around&amp;nbsp;&lt;a href="http://home.cofares.net/GIT/" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;Git&lt;/a&gt;&amp;nbsp;as the tool for the versioning of all of our source code.&lt;/div&gt;
&lt;h2 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; margin-top: 24px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Why git?&lt;/h2&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
For a thorough discussion on the pros and cons of Git compared to centralized source code control systems,&amp;nbsp;&lt;a href="http://whygitisbetterthanx.com/" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;see&lt;/a&gt;&amp;nbsp;&lt;a href="http://www.looble.com/git-vs-svn-which-is-better/" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;the&lt;/a&gt;&amp;nbsp;&lt;a href="http://git.or.cz/gitwiki/GitSvnComparsion" rel="nofollow" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;web&lt;/a&gt;. There are plenty of flame wars going on there. As a developer, I prefer Git above all other tools around today. Git really changed the way developers think of merging and branching. From the classic&amp;nbsp;&lt;span class="caps"&gt;CVS&lt;/span&gt;/Subversion world I came from, merging/branching has always been considered a bit scary (“beware of merge conflicts, they bite you!”) and something you only do every once in a while.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
But with Git, these actions are extremely cheap and simple, and they are considered one of the core parts of your&amp;nbsp;&lt;em&gt;daily&lt;/em&gt;&amp;nbsp;workflow, really. For example, in&amp;nbsp;&lt;span class="caps"&gt;CVS&lt;/span&gt;/Subversion&amp;nbsp;&lt;a href="http://svnbook.red-bean.com/" rel="nofollow" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;books&lt;/a&gt;, branching and merging is first discussed in the later chapters (for advanced users), while in&amp;nbsp;&lt;a href="http://home.cofares.net/GIT/book/" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;every&lt;/a&gt;&amp;nbsp;&lt;a href="http://pragprog.com/titles/tsgit/pragmatic-version-control-using-git" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;Git&lt;/a&gt;&amp;nbsp;&lt;a href="http://home.cofares.net/GIT/progit/" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;book&lt;/a&gt;, it’s already covered in chapter 3 (basics).&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
As a consequence of its simplicity and repetitive nature, branching and merging are no longer something to be afraid of. Version control tools are supposed to assist in branching/merging more than anything else.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Enough about the tools, let’s head onto the development model. The model that I’m going to present here is essentially no more than a set of procedures that every team member has to follow in order to come to a managed software development process.&lt;/div&gt;
&lt;h2 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; margin-top: 24px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Decentralized but centralized&lt;/h2&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The repository setup that we use and that works well with this branching model, is that with a central “truth” repo. Note that this repo&amp;nbsp;is only&amp;nbsp;&lt;em&gt;considered&lt;/em&gt;&amp;nbsp;to be the central one (since Git is a&amp;nbsp;&lt;span class="caps"&gt;DVCS&lt;/span&gt;, there is no such thing as a central repo at a technical level).&amp;nbsp;We will refer to this repo as&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin&lt;/code&gt;, since this name is familiar to all Git users.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="center" src="http://nvie.com/img/2010/01/centr-decentr.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; display: block; margin-bottom: 0px; margin-left: auto; margin-right: auto; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Each developer pulls and pushes to origin. But besides the centralized push-pull relationships, each developer may also pull changes from other peers to form sub teams. For example, this might be useful to work together with two or more developers on a big new feature, before pushing the work in progress to&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin&lt;/code&gt;&amp;nbsp;prematurely. In the figure above, there are subteams of Alice and Bob, Alice and David, and Clair and David.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Technically, this means nothing more than that Alice has defined a Git remote, named&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;bob&lt;/code&gt;, pointing to Bob’s repository, and vice versa.&lt;/div&gt;
&lt;h2 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; margin-top: 24px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The main branches&lt;/h2&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="right" src="http://nvie.com/img/2009/12/bm002.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; float: right; margin-bottom: 12px; margin-left: 12px; margin-right: 0px; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
At the core, the development model is greatly inspired by existing models out there.&amp;nbsp;The central repo holds two main branches with an infinite lifetime:&lt;/div&gt;
&lt;ul style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; margin-bottom: 20px; margin-left: 0px; margin-right: 0px; margin-top: -12px; text-align: -webkit-auto;"&gt;
&lt;li style="font-size: 15px; line-height: 20px; list-style-type: square;"&gt;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&lt;/li&gt;
&lt;li style="font-size: 15px; line-height: 20px; list-style-type: square;"&gt;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;branch at&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin&lt;/code&gt;&amp;nbsp;should be familiar to every Git user.&amp;nbsp;Parallel to the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;branch, another branch exists called&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
We consider&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin/master&lt;/code&gt;&amp;nbsp;to be the main branch where the source code of&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;HEAD&lt;/code&gt;&amp;nbsp;always reflects a&lt;em&gt;production-ready&lt;/em&gt;&amp;nbsp;state.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
We consider&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin/develop&lt;/code&gt;&amp;nbsp;to be the main branch where the source code of&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;HEAD&lt;/code&gt;&amp;nbsp;always reflects a state with the latest delivered development changes for the next release. Some would call this the “integration branch”. This is where any automatic nightly builds are built from.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
When the source code in the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch reaches a stable point and is ready to be released, all of the changes should be merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;somehow and then tagged with a release number. How this is done in detail will be discussed further on.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Therefore, each time when changes are merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;, this is a new production release&amp;nbsp;&lt;em&gt;by definition&lt;/em&gt;.&amp;nbsp;We tend to be very strict at this, so that theoretically, we could use a Git hook script to automatically build and roll-out our software to our production servers everytime there was a commit on&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;.&lt;/div&gt;
&lt;h2 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; margin-top: 24px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Supporting branches&lt;/h2&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Next to the main branches&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, our development model uses a variety of supporting branches to aid parallel development between team members, ease tracking of features, prepare for production releases and to assist in quickly fixing live production problems. Unlike the main branches, these branches always have a limited life time, since they will be removed eventually.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The different types of branches we may use are:&lt;/div&gt;
&lt;ul style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; margin-bottom: 20px; margin-left: 0px; margin-right: 0px; margin-top: -12px; text-align: -webkit-auto;"&gt;
&lt;li style="font-size: 15px; line-height: 20px; list-style-type: square;"&gt;Feature branches&lt;/li&gt;
&lt;li style="font-size: 15px; line-height: 20px; list-style-type: square;"&gt;Release branches&lt;/li&gt;
&lt;li style="font-size: 15px; line-height: 20px; list-style-type: square;"&gt;Hotfix branches&lt;/li&gt;
&lt;/ul&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Each of these branches have a specific purpose and are bound to strict rules as to which branches may be their originating branch and which branches must be their merge targets. We will walk through them in a minute.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
By no means are these branches “special” from a technical perspective. The branch types are categorized by how we&amp;nbsp;&lt;em&gt;use&lt;/em&gt;&amp;nbsp;them. They are of course plain old Git branches.&lt;/div&gt;
&lt;h3 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Feature branches&lt;/h3&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="right" src="http://nvie.com/img/2009/12/fb.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; float: right; margin-bottom: 12px; margin-left: 12px; margin-right: 0px; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
May branch off from:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&lt;br /&gt;Must merge back into:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&lt;br /&gt;Branch naming convention: anything except&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;,&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;,&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;release-*&lt;/code&gt;, or&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;hotfix-*&lt;/code&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Feature branches (or sometimes called topic branches) are used to develop new features for the upcoming or a distant future release. When starting development of a feature, the target release in which this feature will be incorporated may well be unknown at that point. The essence of a feature branch is that it exists as long as the feature is in development, but will eventually be merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;(to definitely add the new feature to the upcoming release) or discarded (in case of a disappointing experiment).&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Feature branches typically exist in developer repos only, not in&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;origin&lt;/code&gt;.&lt;/div&gt;
&lt;h4 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Creating a feature branch&lt;/h4&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
When starting work on a new feature, branch off from the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch.&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout -b myfeature develop
&lt;span class="go" style="color: #888888;"&gt;Switched to a new branch "myfeature"&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h4 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Incorporating a finished feature on develop&lt;/h4&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Finished features may be merged into the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch definitely add them to the upcoming release:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout develop
&lt;span class="go" style="color: #888888;"&gt;Switched to branch 'develop'&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git merge --no-ff myfeature
&lt;span class="go" style="color: #888888;"&gt;Updating ea1b82a..05e9557&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;(Summary of changes)&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git branch -d myfeature
&lt;span class="go" style="color: #888888;"&gt;Deleted branch myfeature (was 05e9557).&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git push origin develop&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;--no-ff&lt;/code&gt;&amp;nbsp;flag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward. This avoids losing information about the historical existence of a feature branch and groups together all commits that together added the feature. Compare:&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="center" src="http://nvie.com/img/2010/01/merge-without-ff.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; display: block; margin-bottom: 0px; margin-left: auto; margin-right: auto; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
In the latter case, it is impossible to see from the Git history which of the commit objects together have implemented a feature—you would have to manually read all the log messages. Reverting a whole feature (i.e. a group of commits), is a true headache in the latter situation, whereas it is easily done if the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;--no-ff&lt;/code&gt;&amp;nbsp;flag was used.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Yes, it will create a few more (empty) commit objects, but the gain is much bigger that that cost.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Unfortunately, I have not found a way to make&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;--no-ff&lt;/code&gt;&amp;nbsp;the default behaviour of&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;git merge&lt;/code&gt;yet, but it really should be.&lt;/div&gt;
&lt;h3 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Release branches&lt;/h3&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
May branch off from:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&lt;br /&gt;Must merge back into:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&lt;br /&gt;Branch naming convention:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;release-*&lt;/code&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Release branches support preparation of a new production release.&amp;nbsp;They allow for last-minute dotting of i’s and crossing t’s. Furthermore, they allow for minor bug fixes and preparing meta-data for a release (version number, build dates, etc.). By doing all of this work on a release branch, the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch is cleared to receive features for the next big release.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The key moment to branch off a new release branch from&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;is when develop (almost) reflects the desired state of the new release.&amp;nbsp;At least all features that are targeted for the release-to-be-built must be merged in to&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;at this point in time. All features targeted at future releases may not—they must wait until after the release branch is branched off.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
It is exactly at the start of a release branch that the upcoming release gets assigned a version number—not any earlier. Up until that moment, the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch reflected changes for the “next release”, but it is unclear whether that “next release” will eventually become 0.3 or 1.0, until the release branch is started. That decision is made on the start of the release branch and is carried out by the project’s rules on version number bumping.&lt;/div&gt;
&lt;h4 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Creating a release branch&lt;/h4&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Release branches are created from the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch. For example, say version 1.1.5 is the current production release and we have a big release coming up. The state of&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;is ready for the “next release” and we have decided that this will become version 1.2 (rather than 1.1.6 or 2.0). So we branch off and give the release branch a name reflecting the new version number:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout -b release-1.2 develop
&lt;span class="go" style="color: #888888;"&gt;Switched to a new branch "release-1.2"&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; ./bump-version.sh 1.2
&lt;span class="go" style="color: #888888;"&gt;Files modified successfully, version bumped to 1.2.&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git commit -a -m &lt;span class="s2" style="color: #bb8844;"&gt;"Bumped version number to 1.2"&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;[release-1.2 74d9424] Bumped version number to 1.2&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;1 files changed, 1 insertions(+), 1 deletions(-)&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
After creating a new branch and switching to it, we bump the version number. Here,&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;bump-version.sh&lt;/code&gt;&amp;nbsp;is a&amp;nbsp;fictional&amp;nbsp;shell script that changes some files in the working copy to reflect the new version. (This can of course be a manual change—the point being that&amp;nbsp;&lt;em&gt;some&lt;/em&gt;&amp;nbsp;files change.) Then, the bumped version number is committed.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
This new branch may exist there for a while, until the release may be rolled out definitely. During that time, bug fixes may be applied in this branch (rather than on the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;branch). Adding large new features here is strictly prohibited. They must be merged into&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, and therefore, wait for the next big release.&lt;/div&gt;
&lt;h4 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Finishing a release branch&lt;/h4&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
When the state of the release branch is ready to become a real release, some actions need to be carried out. First, the release branch is merged into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;(since every commit on&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;is a new release&amp;nbsp;&lt;em&gt;by definition&lt;/em&gt;, remember). Next, that commit on&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;must be tagged for easy future reference to this historical version. Finally, the changes made on the release branch need to be merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, so that future releases also contain these bug fixes.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The first two steps in Git:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout master
&lt;span class="go" style="color: #888888;"&gt;Switched to branch 'master'&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git merge --no-ff release-1.2
&lt;span class="go" style="color: #888888;"&gt;Merge made by recursive.&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;(Summary of changes)&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git tag -a 1.2&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The release is now done, and tagged for future reference.&lt;br /&gt;&lt;ins style="text-decoration: none;"&gt;&lt;strong&gt;Edit:&lt;/strong&gt;&amp;nbsp;You might as well want to use the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;-s&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;-u &amp;lt;key&amp;gt;&lt;/code&gt;&amp;nbsp;flags to sign your tag cryptographically.&lt;/ins&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
To keep the changes made in the release branch, we need to merge those back into&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, though. In Git:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout develop
&lt;span class="go" style="color: #888888;"&gt;Switched to branch 'develop'&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git merge --no-ff release-1.2
&lt;span class="go" style="color: #888888;"&gt;Merge made by recursive.&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;(Summary of changes)&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
This step may well lead to a merge conflict (probably even, since we have changed the version number). If so, fix it and commit.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Now we are really done and the release branch may be removed, since we don’t need it anymore:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git branch -d release-1.2
&lt;span class="go" style="color: #888888;"&gt;Deleted branch release-1.2 (was ff452fe).&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Hotfix branches&lt;/h3&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;img alt="" class="right" src="http://nvie.com/img/2010/01/hotfix-branches1.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; float: right; margin-bottom: 12px; margin-left: 12px; margin-right: 0px; margin-top: 0px; max-width: 580px;" /&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
May branch off from:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&lt;br /&gt;Must merge back into:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&lt;br /&gt;Branch naming convention:&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;hotfix-*&lt;/code&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Hotfix branches are very much like release branches in that they are also meant to prepare for a new production release, albeit unplanned. They arise from the necessity to act immediately upon an undesired state of a live production version. When a critical bug in a production version must be resolved immediately, a hotfix branch may be branched off from the corresponding tag on the master branch that marks the production version.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The essence is that work of team members (on the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;branch) can continue, while another person is preparing a quick production fix.&lt;/div&gt;
&lt;h4 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Creating the hotfix branch&lt;/h4&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Hotfix branches are created from the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;branch. For example, say version 1.2 is the current production release running live and causing troubles due to a severe bug. But changes on&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;are yet unstable.&amp;nbsp;We may then branch off a hotfix branch and start fixing the problem:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout -b hotfix-1.2.1 master
&lt;span class="go" style="color: #888888;"&gt;Switched to a new branch "hotfix-1.2.1"&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; ./bump-version.sh 1.2.1
&lt;span class="go" style="color: #888888;"&gt;Files modified successfully, version bumped to 1.2.1.&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git commit -a -m &lt;span class="s2" style="color: #bb8844;"&gt;"Bumped version number to 1.2.1"&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;[hotfix-1.2.1 41e61bb] Bumped version number to 1.2.1&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;1 files changed, 1 insertions(+), 1 deletions(-)&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Don’t forget to bump the version number after branching off!&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Then, fix the bug and commit the fix in one or more separate commits.&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git commit -m &lt;span class="s2" style="color: #bb8844;"&gt;"Fixed severe production problem"&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;[hotfix-1.2.1 abbe5d6] Fixed severe production problem&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;5 files changed, 32 insertions(+), 17 deletions(-)&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;strong&gt;Finishing a hotfix branch&lt;/strong&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
When finished, the bugfix needs to be merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;, but also needs to be merged back into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, in order to&amp;nbsp;safeguard&amp;nbsp;that the bugfix is included in the next release as well. This is completely similar to how release branches are finished.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
First, update&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;master&lt;/code&gt;&amp;nbsp;and tag the release.&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout master
&lt;span class="go" style="color: #888888;"&gt;Switched to branch 'master'&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git merge --no-ff hotfix-1.2.1
&lt;span class="go" style="color: #888888;"&gt;Merge made by recursive.&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;(Summary of changes)&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git tag -a 1.2.1&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;ins style="text-decoration: none;"&gt;&lt;strong&gt;Edit:&lt;/strong&gt;&amp;nbsp;You might as well want to use the&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;-s&lt;/code&gt;&amp;nbsp;or&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;-u &amp;lt;key&amp;gt;&lt;/code&gt;&amp;nbsp;flags to sign your tag cryptographically.&lt;/ins&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Next,&amp;nbsp;include the bugfix in&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;, too:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git checkout develop
&lt;span class="go" style="color: #888888;"&gt;Switched to branch 'develop'&lt;/span&gt;
&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git merge --no-ff hotfix-1.2.1
&lt;span class="go" style="color: #888888;"&gt;Merge made by recursive.&lt;/span&gt;
&lt;span class="go" style="color: #888888;"&gt;(Summary of changes)&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
The one exception to the rule here is that,&amp;nbsp;&lt;strong&gt;when a release branch currently exists, the hotfix changes need to be merged into that release branch, instead of&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&lt;/strong&gt;. Back-merging the bugfix into the release branch will eventually result in the bugfix being merged into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;too, when the release branch is finished. (If work in&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;immediately requires this bugfix and cannot wait for the release branch to be finished, you may safely merge the bugfix into&amp;nbsp;&lt;code style="font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt;"&gt;develop&lt;/code&gt;&amp;nbsp;now already as well.)&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Finally, remove the temporary branch:&lt;/div&gt;
&lt;pre style="-webkit-box-shadow: rgb(204, 204, 204) 2px 3px 5px; background-color: #fefef1; border-bottom-color: rgb(247, 166, 0); border-bottom-right-radius: 12px; border-bottom-style: solid; border-bottom-width: 1px; border-image: initial; border-left-color: rgb(247, 166, 0); border-left-style: solid; border-left-width: 5px; border-right-color: rgb(247, 166, 0); border-right-style: solid; border-right-width: 1px; border-top-color: rgb(247, 166, 0); border-top-style: solid; border-top-width: 1px; box-shadow: rgb(204, 204, 204) 2px 3px 5px; color: #222222; display: table; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; line-height: 1.4em; margin-bottom: 20px; margin-left: 20px; margin-right: 20px; margin-top: -10px; overflow-x: hidden; overflow-y: hidden; padding-bottom: 10px; padding-left: 16px; padding-right: 16px; padding-top: 10px; text-align: -webkit-auto;"&gt;&lt;code class="language-console" style="display: block; font-family: 'Droid Sans Mono', 'Courier New', monospace !important; font-size: 9pt; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; max-width: 520px; overflow-x: visible; overflow-y: visible; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;"&gt;&lt;span class="gp" style="color: #555555;"&gt;$&lt;/span&gt; git branch -d hotfix-1.2.1
&lt;span class="go" style="color: #888888;"&gt;Deleted branch hotfix-1.2.1 (was abbe5d6).&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 style="background-color: white; clear: both; color: #333333; font-family: 'Graublau Web', Helvetica, sans-serif; margin-bottom: 12px; margin-left: 0px; margin-right: 0px; margin-top: 24px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Summary&lt;/h2&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
While there is nothing really shocking new to this branching model, the “big picture” figure that this post began with has turned out to be tremendously useful in our projects. It forms an elegant mental model that is easy to comprehend and allows team members to develop a shared understanding of the branching and releasing processes.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
A high-quality&amp;nbsp;&lt;span class="caps"&gt;PDF&lt;/span&gt;&amp;nbsp;version of the figure is provided here. Go ahead and hang it on the wall for quick reference at any time.&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
&lt;ins style="text-decoration: none;"&gt;&lt;strong&gt;Update:&lt;/strong&gt;&amp;nbsp;And for anyone who requested it: here’s the&amp;nbsp;&lt;a href="http://github.com/downloads/nvie/gitflow/Git-branching-model-src.key.zip" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;gitflow-model.src.key&lt;/a&gt;&amp;nbsp;of the main diagram image (Apple Keynote).&lt;/ins&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: center;"&gt;
&lt;a href="http://github.com/downloads/nvie/gitflow/Git-branching-model.pdf" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;&lt;img alt="" src="http://nvie.com/img/pdf.png" style="border-bottom-style: none; border-color: initial; border-image: initial; border-left-style: none; border-right-style: none; border-top-style: none; border-width: initial; max-width: 580px;" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a href="http://github.com/downloads/nvie/gitflow/Git-branching-model.pdf" style="color: #3270ae; text-decoration: none;" target="_blank"&gt;Git-branching-model.pdf&lt;/a&gt;&lt;/div&gt;
&lt;div style="background-color: white; color: #333333; font-family: Georgia, Arial, sans-serif; font-size: 15px; line-height: 20px; margin-bottom: 20px; margin-top: 10px; padding-bottom: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px; text-align: -webkit-auto;"&gt;
Feel free to add your comments!&lt;/div&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-7585275603502115324?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/uLRV_DMYSGzExgN8PF2QSjPMQ6M/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/uLRV_DMYSGzExgN8PF2QSjPMQ6M/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/uLRV_DMYSGzExgN8PF2QSjPMQ6M/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/uLRV_DMYSGzExgN8PF2QSjPMQ6M/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/1NfcpequuNo" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/1NfcpequuNo/successful-git-branching-model.html</link><author>noreply@blogger.com (Pascal Fares)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/successful-git-branching-model.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-973481143659862529</guid><pubDate>Fri, 04 May 2012 18:46:00 +0000</pubDate><atom:updated>2012-05-04T21:46:13.503+03:00</atom:updated><title>Harvard and M.I.T. Team Up to Offer Free Online Courses</title><description>&lt;p&gt;New York Times (05/02/12) Tamar Lewin&lt;/p&gt;  &lt;p&gt; Harvard University and the Massachusetts Institute of Technology (MIT) announced a plan to offer free massively open online courses under their edX partnership. Overseeing edX will be a nonprofit organization that Harvard and MIT will govern equally, and each school has pledged $30 million to the initiative. EdX&amp;#39;s inaugural president will be Anant Agarwal, director of MIT&amp;#39;s Computer Science and Artificial Intelligence Laboratory, while Harvard&amp;#39;s contribution will be supervised by provost Alan M. Garber. University officials say the new online platform would be used to research educational technologies and methods as well as to build a global community of online students. Included in the edX project will be engineering courses and humanities courses, in which crowdsourcing or software may be used to grade essays. Harvard Corporation&amp;#39;s Lawrence S. Bacow says education technology currently lacks &amp;quot;an online platform that gives faculty the capacity to customize the content of their own highly interactive courses.&amp;quot; The edX effort faces competition from similar partnerships between Stanford, Princeton, the University of Pennsylvania, the University of Michigan, and Coursera. The rapid evolution of online education technology is such that those in the new ventures say the courses are still in an experimental stage.&lt;/p&gt;    &lt;p&gt;View Full Article&lt;br&gt;  &lt;a href="http://www.nytimes.com/2012/05/03/education/harvard-and-mit-team-up-to-offer-free-online-courses.html"&gt;http://www.nytimes.com/2012/05/03/education/harvard-and-mit-team-up-to-offer-free-online-courses.html&lt;/a&gt;&lt;/p&gt;    &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-973481143659862529?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/ssFt917Le2LJNxqEc7NeX0fnsu0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ssFt917Le2LJNxqEc7NeX0fnsu0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/ssFt917Le2LJNxqEc7NeX0fnsu0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/ssFt917Le2LJNxqEc7NeX0fnsu0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/ly7pXRIVtw4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/ly7pXRIVtw4/harvard-and-mit-team-up-to-offer-free.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/harvard-and-mit-team-up-to-offer-free.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5356021531268313205</guid><pubDate>Thu, 03 May 2012 12:18:00 +0000</pubDate><atom:updated>2012-05-03T15:18:14.197+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">linux</category><category domain="http://www.blogger.com/atom/ns#">SSH</category><category domain="http://www.blogger.com/atom/ns#">windows</category><title>PuTTY: A Free Telnet/SSH Client</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
PuTTY is a free implementation of Telnet and SSH for Windows and Unix 
platforms, along with an &lt;code&gt;xterm&lt;/code&gt; terminal emulator. It is written and 
maintained primarily by &lt;a href="http://www.pobox.com/~anakin/" rel="nofollow" target="_blank"&gt;Simon Tatham&lt;/a&gt;. 
&lt;br /&gt;
The latest version is beta 0.62. 
&lt;br /&gt;
&lt;b&gt;LEGAL WARNING&lt;/b&gt;: Use of PuTTY, PSCP, PSFTP and Plink is illegal in 
countries where encryption is outlawed. I believe it is legal to use PuTTY, 
PSCP, PSFTP and Plink in England and Wales and in many other countries, but I am 
not a lawyer and so if in doubt you should seek legal advice before downloading 
it. &lt;br /&gt;

&lt;br /&gt;
Use of the Telnet-only binary (PuTTYtel) is unrestricted by any cryptography 
laws. 
&lt;br /&gt;
&lt;h2&gt;
Latest news&lt;/h2&gt;
&lt;br /&gt;
&lt;b&gt;2011-12-10 PuTTY 0.62 released&lt;/b&gt; 
&lt;br /&gt;
PuTTY 0.62 is out, containing only bug fixes from 0.61, in particular a &lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/password-not-wiped.html" rel="nofollow" target="_blank"&gt;security fix&lt;/a&gt; preventing passwords 
from being accidentally retained in memory. 
&lt;br /&gt;
&lt;b&gt;2011-11-27 PuTTY 0.62 pre-release builds available&lt;/b&gt; 
&lt;br /&gt;
PuTTY 0.61 had a few noticeable bugs in it (but nothing security-related), so 
we are planning to make a 0.62 release containing just bug fixes. The Wishlist 
page lists the bugs that will be fixed by the 0.62 release. The Download page 
now contains pre-release snapshots of 0.62, which contain those bug fixes and 
should be otherwise stable. (The usual development snapshots, containing other 
development since 0.61, are also still available.) 
&lt;br /&gt;
&lt;b&gt;2011-07-12 PuTTY 0.61 is released&lt;/b&gt; 
&lt;br /&gt;
PuTTY 0.61 is out, after over four years (sorry!), with new features, bug 
fixes, and compatibility updates for Windows 7 and various SSH server software. 
&lt;br /&gt;
&lt;b&gt;2010-05-17 Google listing confusion&lt;/b&gt; 
&lt;br /&gt;
Several users have pointed out to us recently that the top Google hit for 
"putty" is now not the official PuTTY site but a mirror that used to be listed 
on our Mirrors page. 
&lt;br /&gt;
The official PuTTY web page is still where it has always been: 
&lt;br /&gt;
&lt;div align="center"&gt;
&lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/" rel="nofollow" target="_blank"&gt;http://www.chiark.greenend.org.uk/~sgtatham/putty/&lt;/a&gt;&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/licence.html" rel="nofollow" target="_blank"&gt;Licence conditions&lt;/a&gt; under which you may use PuTTY. 

&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html" rel="nofollow" target="_blank"&gt;The FAQ&lt;/a&gt;. 
&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/docs.html" rel="nofollow" target="_blank"&gt;The documentation&lt;/a&gt;. 
&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html"&gt;Download PuTTY&lt;/a&gt;!&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5356021531268313205?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/2Q7s9oORLS8VvxPDku1RDPW9LXw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2Q7s9oORLS8VvxPDku1RDPW9LXw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/2Q7s9oORLS8VvxPDku1RDPW9LXw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/2Q7s9oORLS8VvxPDku1RDPW9LXw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/XDDlxjBlKY4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/XDDlxjBlKY4/putty-free-telnetssh-client.html</link><author>noreply@blogger.com (Pascal Fares)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/putty-free-telnetssh-client.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-762303088107435764</guid><pubDate>Thu, 03 May 2012 11:39:00 +0000</pubDate><atom:updated>2012-05-03T14:39:08.728+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">mysql</category><category domain="http://www.blogger.com/atom/ns#">replication</category><title>MySQL How to Set Up Replication</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
&lt;div class="titlepage" style="background-color: white; font-family: Helvetica, Arial, sans-serif; font-size: 14px; text-align: -webkit-auto;"&gt;
&lt;h3 class="title" style="background-color: white; font-size: 22px;"&gt;
How to Set Up Replication&lt;/h3&gt;
&lt;/div&gt;
&lt;div class="toc" style="background-color: white; font-family: Helvetica, Arial, sans-serif; font-size: 14px; text-align: -webkit-auto;"&gt;

&lt;dl&gt;&lt;ul style="text-align: left;"&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-masterbaseconfig" style="color: #015a84;"&gt;Setting the Replication Master Configuration&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-slavebaseconfig" style="color: #015a84;"&gt;Setting the Replication Slave Configuration&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-repuser" style="color: #015a84;"&gt;Creating a User for Replication&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-masterstatus" style="color: #015a84;"&gt;Obtaining the Replication Master Binary Log Coordinates&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-mysqldump" style="color: #015a84;"&gt;Creating a Data Snapshot Using&amp;nbsp;&lt;strong class="command" style="background-color: white; color: #990000; font-family: 'Courier New', Courier, fixed, monospace; font-size: 15px; font-style: oblique;"&gt;mysqldump&lt;/strong&gt;&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-rawdata" style="color: #015a84;"&gt;Creating a Data Snapshot Using Raw Data Files&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-newservers" style="color: #015a84;"&gt;Setting Up Replication with New Master and Slaves&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-existingdata" style="color: #015a84;"&gt;Setting Up Replication with Existing Data&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-additionalslaves" style="color: #015a84;"&gt;Introducing Additional Slaves to an Existing Replication Environment&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;dt&gt;&lt;span class="section"&gt;&lt;a href="http://bey.cofares.net/refman-5.5-en.html-chapter/replication.html#replication-howto-slaveinit" style="color: #015a84;"&gt;Setting the Master Configuration on the Slave&lt;/a&gt;&lt;/span&gt;&lt;/dt&gt;
&lt;/ul&gt;
&lt;/dl&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-762303088107435764?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/U-bVSHimwRZiGMeDSZAW7RAWISs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/U-bVSHimwRZiGMeDSZAW7RAWISs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/U-bVSHimwRZiGMeDSZAW7RAWISs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/U-bVSHimwRZiGMeDSZAW7RAWISs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/J9Iqunpiv4o" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/J9Iqunpiv4o/mysql-how-to-set-up-replication.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/mysql-how-to-set-up-replication.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5616504972532601967</guid><pubDate>Mon, 30 Apr 2012 22:41:00 +0000</pubDate><atom:updated>2012-05-02T21:49:28.844+03:00</atom:updated><title>Bringing Open Education to the Mainstream</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;  Campus Technology&lt;br /&gt;  (04/24/12) Jennifer Demski&lt;br /&gt;
Large-scale open education initiatives have the potential to transform the environment of higher education by creating a learning landscape that spreads beyond the walls of the university. However, wide-scale adoption of open education resources remains slow. "There are all of these open ed depositories, but you can't easily mix and match across platforms, let alone search across them," says Rice University professor Richard Baraniuk. He notes that faculty bandwidth is another issue. Rice's OpenStax College initiative was created to help streamline access to open education resources. "We're trying to address the highest impact community college courses, as defined by the total number of students enrolled in a particular course multiplied by the average cost of that course's materials for the student," Baraniuk says. The Web versions of the OpenStax textbooks were built on the Connections XML platform, which enables instructors to add new material to the book, or edit the material in the book. Baraniuk says the platform also is highly accessible for students with disabilities, and all of the content in the books is semantically marked up. "Ultimately we'll be moving from a world of better access and cheaper materials to a world of vastly improved learning outcomes," he says.&lt;br /&gt;
View Full Article&lt;br /&gt;  &lt;a href="http://campustechnology.com/articles/2012/04/24/bringing-open-education-to-the-mainstream.aspx" rel="nofollow" target="_blank"&gt;http://campustechnology.com/articles/2012/04/24/bringing-open-education-to-the-mainstream.aspx&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5616504972532601967?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tfH_Youp-3PRa10l5A1zS4XRPT0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tfH_Youp-3PRa10l5A1zS4XRPT0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tfH_Youp-3PRa10l5A1zS4XRPT0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tfH_Youp-3PRa10l5A1zS4XRPT0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/qdYcv0ABx2U" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/qdYcv0ABx2U/bringing-open-education-to-mainstream.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/05/bringing-open-education-to-mainstream.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-8139179012189380692</guid><pubDate>Sun, 29 Apr 2012 18:25:00 +0000</pubDate><atom:updated>2012-04-30T09:00:59.180+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">VPN</category><category domain="http://www.blogger.com/atom/ns#">SSH</category><title>SSH_VPN - Community Ubuntu Documentation</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;  Very simple VPN with open ssh&lt;br /&gt;
&lt;a href="https://help.ubuntu.com/community/SSH_VPN" rel="nofollow" target="_blank"&gt;https://help.ubuntu.com/community/SSH_VPN&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-8139179012189380692?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/9bvJZNZ4ZG7lydzw6Du9LoQMWZ4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9bvJZNZ4ZG7lydzw6Du9LoQMWZ4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/9bvJZNZ4ZG7lydzw6Du9LoQMWZ4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/9bvJZNZ4ZG7lydzw6Du9LoQMWZ4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/Q8o-yUFHxbU" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/Q8o-yUFHxbU/sshvpn-community-ubuntu-documentation.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/sshvpn-community-ubuntu-documentation.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-1773394359790368436</guid><pubDate>Sun, 29 Apr 2012 14:13:00 +0000</pubDate><atom:updated>2012-05-02T21:50:14.115+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">linux</category><category domain="http://www.blogger.com/atom/ns#">debian</category><category domain="http://www.blogger.com/atom/ns#">ubuntu</category><title>Ubuntu 12.04 LTS , Precise Pangolin , is here</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
Ubuntu just published it's 4th long term support (12.04 LTS Precise Pangolin)&lt;br /&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Here is some MUST HAVE&amp;nbsp;applications&amp;nbsp;for your newly installed Ubuntu:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;span style="text-align: left;"&gt;&lt;b&gt;&lt;i&gt;MyUnity&lt;/i&gt;&lt;/b&gt;&lt;/span&gt;&lt;br /&gt;
&lt;div&gt;
MyUnity is a must have configuration tool for Unity ( change themes, icons, transparency…) : &lt;a href="apt://myunity" rel="nofollow" target="_blank"&gt;install it&lt;/a&gt;&lt;br /&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;b&gt;&lt;i&gt;Medibuntu&lt;/i&gt;&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
The must have repositories. &lt;a href="http://www.unixmen.com/medibuntu-repositories-available-for-ubuntu-12-04-lts-precise-pangolin-ppa/" rel="nofollow" target="_blank"&gt;Medibuntu&lt;/a&gt; is a packaging project dedicated to distributing software that cannot be included in Ubuntu for various reasons, related to geographical variations in      legislation regarding intellectual property, security and other issues. by adding Medibuntu repositories you will be able to install many softwares like Google-Earth , opera ,Win32codecs , divcss, Msfonts.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
Just type &lt;br /&gt;
&lt;blockquote class="tr_bq"&gt;
&lt;strong style="color: #444444; font-family: 'Courier New', Courier, monospace; font-size: 12px; line-height: 18px; text-align: justify; white-space: pre-wrap;"&gt;sudo -E wget --output-document=/etc/apt/sources.list.d/medibuntu.list http://www.medibuntu.org/sources.list.d/$(lsb_release -cs).list &amp;amp;&amp;amp; sudo apt-get --quiet update &amp;amp;&amp;amp; sudo apt-get --yes --quiet --allow-unauthenticated install medibuntu-keyring &amp;amp;&amp;amp; sudo apt-get --quiet update&lt;/strong&gt;&lt;/blockquote&gt;
In a teminal&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;i&gt;Gnome 3 Not Unity!&lt;/i&gt;&lt;/b&gt;&lt;br /&gt;
I you do not like Unity you can go back to Gnome3 &lt;a href="apt://gnome-shell" rel="nofollow" target="_blank"&gt;install gnome 3 for Ubuntu&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;i&gt;VLC2 Media Streaming and player&lt;/i&gt;&lt;/b&gt;&lt;br /&gt;
VLC is the best media player for Linux it play almost everything , he has many features that you can not find in any other media player.&lt;a href="apt://vlc" rel="nofollow" target="_blank"&gt; install VLC&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-1773394359790368436?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/L7ynLe3OlTYI-Nne_OLpQtCvV0s/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/L7ynLe3OlTYI-Nne_OLpQtCvV0s/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/L7ynLe3OlTYI-Nne_OLpQtCvV0s/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/L7ynLe3OlTYI-Nne_OLpQtCvV0s/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/WKN0cDz6pos" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/WKN0cDz6pos/ubuntu-1204-lts-is-here.html</link><author>noreply@blogger.com (Pascal Fares)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/ubuntu-1204-lts-is-here.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-8812398166870854107</guid><pubDate>Sun, 29 Apr 2012 13:55:00 +0000</pubDate><atom:updated>2012-05-02T21:50:29.687+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">SIP</category><title>Jitsi (SIP Communicator) open source remplacement for skype</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
Jitsi (previously SIP Communicator) is an audio/video and chat communicator that supports protocols such as SIP, XMPP/Jabber, AIM/ICQ, Windows Live, Yahoo! and many other useful features.&lt;br /&gt;
&lt;a href="http://jitsi.org/" rel="nofollow" target="_blank"&gt;http://jitsi.org/&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-8812398166870854107?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/753u_-ClG4gKTY7dg-WtifkjrvQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/753u_-ClG4gKTY7dg-WtifkjrvQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/753u_-ClG4gKTY7dg-WtifkjrvQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/753u_-ClG4gKTY7dg-WtifkjrvQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/Ay53IGST8rY" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/Ay53IGST8rY/jitsi-sip-communicator-open-source.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/jitsi-sip-communicator-open-source.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-4146875167328926708</guid><pubDate>Fri, 27 Apr 2012 23:41:00 +0000</pubDate><atom:updated>2012-05-02T21:50:41.941+03:00</atom:updated><title>Voting Information Project Takes Aim at Open Data, Social Media</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
&lt;br /&gt;
Government Technology&lt;br /&gt;
(04/23/12) Wayne Hanson&lt;br /&gt;
The Pew Center on the States and several technology companies recently launched the Voting Information Project (VIP), which enables Foursquare users to receive an "I Voted" badge when they visit their polling places. VIP also provides voters in 37 states with an easier way to find election information via social media and mobile devices. VIP takes state election information and translates it into an open programming format, organizing it into application programming interfaces (APIs). "Right now, we're getting that information from 37 states, and all that information is stored in these feeds--these APIs--so that developers and whoever wants to use that information can create a user-friendly tool out of it," says Pew associate Olivia Doherty. VIP will make election information available on search engines, media sites, get-out-the-vote campaigns, and political party Web sites. In several of the states, including California, Florida, Texas, and Illinois, the counties provide the political data. Doherty hopes that many more local governments will use the tool on their Web sites this year.&lt;br /&gt;
View Full Article&lt;br /&gt;
&lt;a href="http://www.govtech.com/e-government/Voting-Information-Project-Takes-Aim-at-Open-Data-Social-Media.html" rel="nofollow" target="_blank"&gt;http://www.govtech.com/e-government/Voting-Information-Project-Takes-Aim-at-Open-Data-Social-Media.html&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-4146875167328926708?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TGaO_PBoxKh790KIGXyPX0NStZU/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TGaO_PBoxKh790KIGXyPX0NStZU/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TGaO_PBoxKh790KIGXyPX0NStZU/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TGaO_PBoxKh790KIGXyPX0NStZU/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/SZibp8rhLdk" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/SZibp8rhLdk/voting-information-project-takes-aim-at.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/voting-information-project-takes-aim-at.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-1535794982450633337</guid><pubDate>Fri, 27 Apr 2012 20:57:00 +0000</pubDate><atom:updated>2012-05-02T21:50:55.430+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">file system</category><category domain="http://www.blogger.com/atom/ns#">cloud</category><title>XtreemFS - a cloud file system</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
The open source cloud file system &lt;br /&gt;
&lt;a href="http://www.xtreemfs.org/" rel="nofollow" target="_blank"&gt;http://www.xtreemfs.org/&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-1535794982450633337?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/udE0LdobAjpeoWo49eEIZpYM-CY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/udE0LdobAjpeoWo49eEIZpYM-CY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/udE0LdobAjpeoWo49eEIZpYM-CY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/udE0LdobAjpeoWo49eEIZpYM-CY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/zE9VCAIMuz4" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/zE9VCAIMuz4/xtreemfs-cloud-file-system.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/xtreemfs-cloud-file-system.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-8757816404109577420</guid><pubDate>Tue, 24 Apr 2012 00:42:00 +0000</pubDate><atom:updated>2012-04-24T03:42:22.247+03:00</atom:updated><title>Proof-of-Concept Android Trojan Uses Motion Sensor to Determine Tapped Keys</title><description>&lt;p&gt;&lt;br&gt; IDG News Service&lt;br&gt; (04/20/12) Lucian Constantin&lt;/p&gt; &lt;p&gt; Researchers at Pennsylvania State University and IBM have developed TapLogger, a proof-of-concept Android Trojan app that can steal passwords and other sensitive information by using the smartphone&amp;#39;s motion sensors to determine what keys users tap on their touchscreens. The researchers developed TapLogger to demonstrate how data from a smartphone&amp;#39;s accelerometer and orientation sensors can be abused by applications to compromise privacy. The researchers note that accelerometer and orientation sensor data are not protected under Android&amp;#39;s security model, which exposes that data to any application regardless of its permissions on the system. TapLogger functions as an icon-matching game, but has several background components that capture and use data from the motion sensors to infer touchscreen-based user input. After the data is collected, the application builds tap event patterns and uses them to infer user input during targeted operations. &amp;quot;While the applications relying on mobile sensing are booming, the security and privacy issues related to such applications are not well understood yet,&amp;quot; the researchers say.&lt;/p&gt;  &lt;p&gt;View Full Article&lt;br&gt; &lt;a href="http://www.computerworld.com/s/article/9226421/Proof_of_concept_Android_Trojan_uses_motion_sensor_to_determine_tapped_keys"&gt;http://www.computerworld.com/s/article/9226421/Proof_of_concept_Android_Trojan_uses_motion_sensor_to_determine_tapped_keys&lt;/a&gt;&lt;/p&gt;  &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-8757816404109577420?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jucRYnAqVQY8H6ro1LQSXZJoKmM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jucRYnAqVQY8H6ro1LQSXZJoKmM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jucRYnAqVQY8H6ro1LQSXZJoKmM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jucRYnAqVQY8H6ro1LQSXZJoKmM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/wh0ga3-V2n0" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/wh0ga3-V2n0/proof-of-concept-android-trojan-uses.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/proof-of-concept-android-trojan-uses.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-6685850788240919027</guid><pubDate>Sun, 22 Apr 2012 15:40:00 +0000</pubDate><atom:updated>2012-04-22T18:40:34.232+03:00</atom:updated><title>Secret Computer Code Threatens Science</title><description>&lt;p&gt;From ACM TechNews: &lt;br&gt; Secret Computer Code Threatens Science&lt;br&gt; Scientific American&lt;br&gt; (04/13/12) Jeremy Hsu&lt;/p&gt; &lt;p&gt; Although modern science calls for researchers to share their work so that their peers can verify the success or failure of experiments, most researchers still do not share the source code for the software used in their projects. However, a group of researchers is pushing for new standards that require newly published studies to make their source code available. &amp;quot;As computing becomes an ever larger and more important part of research in every field of science, access to the source code used to generate scientific results is going to become more and more critical,&amp;quot; says Harvard University researcher Andrew Morin. Of the 20 most-cited scientific journals in 2010, only three require that computer source code be made available upon publication. The researchers propose that public funding or policy-setting agencies should support the idea of openly sharing source code. In addition, research institutions and universities should use open source software licenses to allow for source-code sharing while protecting the commercial rights to possible innovation spinoffs from research. &amp;quot;The encouraging thing is that all of the proposals we have made have already been implemented by various journals, funding agencies, and research institutions in one form or another,&amp;quot; Morin says.&lt;/p&gt;  &lt;p&gt;View Full Article&lt;br&gt; &lt;a href="http://www.scientificamerican.com/article.cfm?id=secret-computer-code-threatens-science"&gt;http://www.scientificamerican.com/article.cfm?id=secret-computer-code-threatens-science&lt;/a&gt;&lt;/p&gt; &lt;p&gt;Motorola Xoom&lt;br&gt; &lt;a href="http://www.cofares.net"&gt;http://www.cofares.net&lt;/a&gt;&lt;/p&gt; &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-6685850788240919027?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/sxTZTyxNr14dyMflkRLsIUfkEug/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sxTZTyxNr14dyMflkRLsIUfkEug/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/sxTZTyxNr14dyMflkRLsIUfkEug/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sxTZTyxNr14dyMflkRLsIUfkEug/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/wmgEFHGithI" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/wmgEFHGithI/secret-computer-code-threatens-science.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/secret-computer-code-threatens-science.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5146467597857689498</guid><pubDate>Sun, 22 Apr 2012 15:38:00 +0000</pubDate><atom:updated>2012-04-30T09:04:50.902+03:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Open Source</category><title>Open Source Hardware Movement Seeks Legitimacy</title><description>&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;
IDG News Service&lt;br /&gt; (04/17/12) Agam Shah&lt;br /&gt;
A group of technologists recently established the Open Source Hardware Association (OSHA) to promote the creation and sharing of hardware or electronic designs. OSHA aims to foster growth in the open source hardware movement. Open source hardware is similar to open source software because designs can be applied to commercial applications from which companies can make money. "It has many similar principals of open source software, but differs because hardware is a different beast [with] different methods, formats, and issues than software," says OSHA founder Alicia Gibb. She says OSHA will host the annual Open Hardware Summit conference, which will act as a forum for technology professionals to discuss devices, manufacturing, design, business, and law. "We publish all the files needed to improve, make derivatives, or re-manufacture the things built," Gibb says. Many open source hardware projects are based on the Arduino microcontroller, which serves as a prime example of how open source hardware works. The open source hardware movement also has received support from organizations such as the European Organization for Nuclear Research. "Many open source hardware projects will not be the type of thing that are eligible for copyright protection," notes Public Knowledge attorney Michael Weinberg.&lt;br /&gt;
View Full Article&lt;br /&gt; &lt;a href="http://www.networkworld.com/news/2012/041712-open-source-hardware-movement-seeks-258372.html" rel="nofollow" target="_blank"&gt;http://www.networkworld.com/news/2012/041712-open-source-hardware-movement-seeks-258372.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5146467597857689498?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/5icghCHZ2CkQKfEVxeC7RNWVq_0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5icghCHZ2CkQKfEVxeC7RNWVq_0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/5icghCHZ2CkQKfEVxeC7RNWVq_0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5icghCHZ2CkQKfEVxeC7RNWVq_0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/8e6zA5BVCMQ" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/8e6zA5BVCMQ/open-source-hardware-movement-seeks.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/open-source-hardware-movement-seeks.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-5682373815436217917</guid><pubDate>Sat, 21 Apr 2012 17:33:00 +0000</pubDate><atom:updated>2012-04-21T20:33:56.276+03:00</atom:updated><title>NBAndroid: Installation</title><description>&lt;a href="http://www.nbandroid.org/p/installation.html"&gt;NBAndroid: Installation&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-5682373815436217917?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/L_Vj9yji9lAddrCdNesvIWLpuKY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/L_Vj9yji9lAddrCdNesvIWLpuKY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/L_Vj9yji9lAddrCdNesvIWLpuKY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/L_Vj9yji9lAddrCdNesvIWLpuKY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/Uz3tEzV1sgE" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/Uz3tEzV1sgE/nbandroid-installation.html</link><author>noreply@blogger.com (Pascal Fares)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/nbandroid-installation.html</feedburner:origLink></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6177317444519479825.post-174131795572224972</guid><pubDate>Wed, 18 Apr 2012 23:54:00 +0000</pubDate><atom:updated>2012-04-19T02:54:58.372+03:00</atom:updated><title>Programming Project Comes to Primary Schools</title><description>&lt;p&gt;From ACM TechNews: &lt;br&gt; Programming Project Comes to Primary Schools&lt;br&gt; BBC News&lt;br&gt; (04/17/12) &lt;/p&gt; &lt;p&gt; A volunteer project in the United Kingdom is writing session plans for teaching the basics of computer programming to children between the ages of 10 and 11. Called Code Clubs, the sessions will give schoolchildren an opportunity to engage in hands-on tasks such as making games and eventually controlling robots. &amp;quot;The idea is to build things that are really exciting,&amp;quot; says Clare Sutcliffe, who developed the idea for Code Clubs along with Linda Sandvik. Several schools have volunteered to test the session plans. The club sessions will make use of the Massachusetts Institute of Technology&amp;#39;s Scratch tool, which enables youngsters to engage in programming by dragging and dropping code elements instead of typing them. The first 12 sessions should be free for participating schools to run, and the only extra step would be to download and install Scratch on their computers. Volunteers would run the Code Clubs, rather than teachers. Sutcliffe and Sandvik hope to have Code Clubs in 25 percent of British primary schools by 2014. The Code Club would &amp;quot;slot neatly alongside&amp;quot; the changes to the national curriculum that will emphasize programming, Sutcliffe notes.&lt;/p&gt;  &lt;p&gt;View Full Article&lt;br&gt; &lt;a href="http://www.bbc.com/news/technology-17740143"&gt;http://www.bbc.com/news/technology-17740143&lt;/a&gt;&lt;/p&gt; &lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6177317444519479825-174131795572224972?l=oslm.cofares.net' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/86BBJ-b77g0QxJzxa56sf0V4nuA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/86BBJ-b77g0QxJzxa56sf0V4nuA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/86BBJ-b77g0QxJzxa56sf0V4nuA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/86BBJ-b77g0QxJzxa56sf0V4nuA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/oslm/~4/HUamwbqtMfE" height="1" width="1"/&gt;</description><link>http://feedproxy.google.com/~r/oslm/~3/HUamwbqtMfE/programming-project-comes-to-primary.html</link><author>noreply@blogger.com (Pascal Emile Farès)</author><thr:total>0</thr:total><feedburner:origLink>http://oslm.cofares.net/2012/04/programming-project-comes-to-primary.html</feedburner:origLink></item><language>en-us</language><media:rating>nonadult</media:rating></channel></rss>

