Git-Url: 
http://git.frugalware.org/gitweb/gitweb.cgi?p=homepage-ng.git;a=commitdiff;h=4ccbb1744e2ddcbfef17457d52bfa7a1a86c2d94

commit 4ccbb1744e2ddcbfef17457d52bfa7a1a86c2d94
Author: Russell Dickenson (phayz) <[email protected]>
Date:   Mon Apr 6 22:27:25 2009 +1000

Newsletter issue 42

new file:   images/interviews/vmiklos_house2.jpg
new file:   weeklynews/issue42.html
modified:   xml/news.xml

diff --git a/frugalware/images/interviews/vmiklos_house2.jpg 
b/frugalware/images/interviews/vmiklos_house2.jpg
new file mode 100644
index 0000000..7e198ec
Binary files /dev/null and b/frugalware/images/interviews/vmiklos_house2.jpg 
differ
diff --git a/frugalware/weeklynews/issue42.html 
b/frugalware/weeklynews/issue42.html
new file mode 100755
index 0000000..6f422b8
--- /dev/null
+++ b/frugalware/weeklynews/issue42.html
@@ -0,0 +1,400 @@
+<p><h2>Frugalware Linux Newsletter - Issue 42</h2></p>
+
+<p><h2>...to inform...to educate...to entertain</h2></p>
+
+<p>There are 10 types of people in the world - those who understand binary and
+those who don't. - <em>A geek</em></p>
+
+
+<h2>Welcome</h2>
+
+<p>The newsletter's aim is to keep you up to date with what's happened recently
+in the world of the Linux distribution 'Frugalware'.</p>
+
+<p>Features of this issue include:
+    <ul>
+        <li>To infinity...and beyond</li>
+        <li>Will the <em>real</em> Cedric(k) please stand up?</li>
+        <li>Frugalware's developers are people too - VMiklos</li>
+        <li>Tips and tricks - Unlucky in love?</li>
+        <li>Focus On Package(s) - lsof</li>
+    </ul>
+</p>
+
+
+<h2>Events</h2>
+
+<p>Here's a selection of events which have occurred since the previous
+newsletter:</p>
+
+<ul>
+    <li>
+        <h3>To infinity...and beyond</h3>
+        <p>26 March 2009, VMiklos announced the codename for the next 
Frugalware
+        release - 1.1 -  "Getorin".  It's exciting to try and guess what might
+        be included in the next release.</p>
+    </li>
+    <li>
+        <h3>Will the <em>real</em> Cedric(k) please stand up?</h3>
+        <p>In an event that was sure to happen at some point, we have a
+        developer and contributor with very similar first names - Cedrick
+        Hannier and Cédric Archambeau.  The following options have been 
proposed
+        to avoid any confusion between the two Cedric(k)s:</p>
+        <ul>
+        <li>Each Cedric(k) could wear a name tag, with their full name clearly
+        marked.  Of course someone has already pointed out that this is a 
stupid
+        option because unless you live in France, they'd be so far away that 
you
+        couldn't read the name tag;</li>
+        <li>One of the Cedric(k)s could change their name.  This is perhaps the
+        simplest option, but neither Cedric(k) seems to like the idea;</li>
+        <li>Each developer or contributor could be assigned a unique,
+        sequential number.  This has already been discussed amongst the
+        development team, but no-one could agree on if the numbering should
+        start from 0 or 1.</li>
+        </ul>
+        <p>I hope we can come up with a solution by the next newsletter.</p>
+    </li>
+    <li>
+        <h3>Gnome 2.26</h3>
+        <p>On 25 March 2009, Bouleetbil made available - via the 'current'
+        repo packages for Gnome 2.26.  Thanks to him for his hard work.  Gnome
+        consists of a lot of packages and it's a difficult and time consuming
+        job to get it all done.</p>
+    </li>
+</ul>
+
+
+<h2>Updates</h2>
+
+<p>Here is a selection of packages which have been updated since the previous
+newsletter:</p>
+
+<table border=1 cellpadding=5 cellspacing=0 width=80%>
+<tr>
+    <th width=10%>Package</th>
+    <th width=50%>Description</th>
+    <th width=10%>Upgrade Version</th>
+    <th width=50%>Comments</th>
+
+</tr>
+<tr>
+    <td>dokuwiki</td>
+    <td>DokuWiki wiki</td>
+    <td>2009_02_14-1</td>
+    <td>New package</td>
+</tr>
+<tr>
+    <td>firefox</td>
+    <td>Firefox web browser</td>
+    <td>3.0.8-1</td>
+    <td>Version bump</td>
+</tr>
+<tr>
+    <td>gnome-do</td>
+    <td>A powerful, remote control for GNOME</td>
+    <td>0.8.1-1</td>
+    <td>Version bump</td>
+</tr>
+<tr>
+    <td>gtg</td>
+    <td>Getting Things Gnome, simple personal organizer</td>
+    <td>0.1-1</td>
+    <td>New package</td>
+</tr>
+<tr>
+    <td>gfpm</td>
+    <td>Graphical Frugalware package manager</td>
+    <td>1.2.2-1</td>
+    <td>Version bump</td>
+</tr>
+<tr>
+    <td>vala</td>
+    <td>Vala is a prgramming language that aims to bring modern programming
+    language features to GNOME developers</td>
+    <td>0.6.0-1</td>
+    <td>Version bump</td>
+</tr>
+<tr>
+    <td>firefox-autohide</td>
+    <td>Gives you total control over your fullscreen mode.</td>
+    <td>1.5.0-1</td>
+    <td>Version bump</td>
+</tr>
+<tr>
+    <td>gtk+2-engines-murrine</td>
+    <td>Murrine is a fast and modern looking GTK+2 engine.</td>
+    <td>0.90.0-1</td>
+    <td>Version bump. Use Finclude gnome as murrine is now a gnome project.
+    Removed outdated theme(s).</td>
+</tr>
+</table>
+
+
+<h2>Frugalware's developers are people too - VMiklos</h2>
+
+<p>In this issue we have a very special interview with VMiklos, the founder of
+Frugalware Linux.  I thought it would be interesting to have him look back on
+the past 5 years and to the future.</p>
+
+<dl>
+    <dt><strong>What were your goals when you started the Frugalware project?
+    </strong></dt>
+        <dd><p>I had to search back, I could only remember that there were
+        three goals. Here they are:</p></dd>
+        <ul>
+            <li>A fast package manager, written in C (versus Slackware's
+            pkgtool which was slow and was written in bash);</li>
+            <li>I18n support (Slackware's setup was not localised);</li>
+            <li>Smooth upgrades between stable releases (at that time there
+            was no slapt-get and upgrades were a PITA);</li>
+        </ul></dd>
+<br>
+    <dt><strong>Do you think you've achieved any of these goals?</strong></dt>
+
+        <dd><p>Sure:</p>
+        <ul>
+            <li>The original problem with slow package removals were never the
+            case with pacman;</li>
+            <li>I18n support is everywhere, we have 10 localised projects on
+            Pootle;</li>
+            <li>We recently introduced upgrade HOWTO, so the change between
+            stable versions is pretty smooth. Actually it must be, since most
+            of the devs administer multiple Frugalware machines. :)</li></dd>
+        </ul>
+<br>
+    <dt><strong>Have your goals changed and if so, how?</strong></dt>
+
+        <dd><p>We always reach goals and accordingly set new ones. I remember
+        a fast installer was a goal before 0.3, a tool like repoman (to make
+        installing blobs like opera or skype easy) was something users wanted,
+        the automatic package builder was a collection of scripts we really
+        loved when it was introduced, etc. I remember the first time the
+        installer supported the WPA encryption via wireless and we were quite
+        happy. :)</p>
+
+        <p>Anyway we have implicitly reached some goals, like trying to be
+        nice to users, respecting users' decisions, having a fully documented
+        and as-open-as-possible infrastructure, and this seems to be unchanged
+        during several releases. (Yes, I stole this list from LGee, as he
+        collected this stuff floating around. :) )</p></dd>
+
+    <dt><strong>Do you plan a career in IT and if so, do you think your work on
+    Frugalware will help you?</strong></dt>
+
+        <dd><p>I already work part-time and have already solved many problems
+        at work which would not have been possible without Frugalware. Random
+        example: we have used Git and Pootle for a long time and when we wanted
+        to give it a try at work, I was able to help with that, since I already
+        know them quite well.</p></dd>
+
+    <dt><strong>In what areas would you like to see Frugalware improved?
+    </strong></dt>
+        <dd><p>On the one hand, Frugalware is already in the shape I think an
+        ideal distribution should look be, so I don't think we will radically
+        change anything in the near future.</p>
+
+        <p>On the other hand, we have many smaller targets, for example smaller
+        packages (lzma support), better error handling in the installer, 
etc.</p></dd>
+
+        <dt><strong>Do you have all the support you would like, or do you want
+        more developers and contributors?</strong></dt>
+
+        <dd><p>Currently I maintain 670 packages. This is way too much. I
+        think in an ideal world a developer should maintain about 100-200
+        packages. So more developers would be nice, though I think we're moving
+        in that direction, we got 4 new developers in 2008, and we already
+        have two new developers this year as well.</p></dd>
+
+    <dt><strong>Can you give a summary of your experience over the past 5 
years?
+    </strong></dt>
+
+        <dd><p>Lots of funny and instructive stories. :) Other than that,
+        running The Perfect distro on my boxes really makes me pleased (and I
+        do not mean bug-free, there are bugs, but all the concepts are the way
+        I like it), and I have met numerous great developers and users here.
+        </p></dd>
+
+    <dt><strong>Do you see Frugalware having a long life?</strong></dt>
+
+        <dd><p>I really don't see what could stop us. :) Also a few of us
+        (devels) are more-or-less paid to work on Frugalware (maintain
+        installed systems) and so we have the ability to use it in a
+        production environment which is yet another reason not to stop
+        development.</p></dd>
+
+    <dt><strong>Do you think Frugalware would continue if you left the project?
+    </strong></dt>
+
+        <dd><p>Frugalware is my pet, and during the past 5 years, I got a lot
+        of practice in doing project leadership stuff (resolving personal
+        conflicts, release-engineering, etc.), so in case somebody else would
+        want to do it, it would take a while to hand him everything over. But
+        ideally everything is documented and I think it's possible that one
+        day we meet somebody who has more time or better skills than me, and
+        I won't hesitate to step back in that case. I'm already proud of what
+        we have achieved with this great team.</p></dd>
+
+    <dt><strong>What's the view from your front door?</strong></dt>
+
+        <dd><p>I'm sure I provided a photo of the view from my front door in
+        issue 16. Since the view changes from season to season though, here's
+        the current view. <img src="vmiklos_house2.jpg" alt="View from VMiklos
+        front door"/></p></dd>
+</dl>
+
+
+<h2>Getting To Know You</h2>
+
+<p>In this section of the newsletter, we get to know Frugalware Linux a little
+at a time.  This is not meant to replace the official documentation but instead
+make it easier to read.  This should suit those those people who, like me, have
+short attention spans.  :)</p>
+
+<h3>What's going on?</h3>
+
+<p>One of the best ways of finding out what's happening with Frugalware is to
+subscribe to one or more of the mailing lists. Here you can read the
+discussions behind the various decisions that are made regarding Frugalware.
+There's also a mailing list which announces the security fixes as they are
+released. Review the mailing lists available
+<a href="http://frugalware.org/mailman/listinfo";>here</a> and subscribe to
+those that interest you.</p>
+
+
+<h2>Tips and tricks</h2>
+
+<p><b>Disclaimer</b> - Be aware that the hints &amp; tips provided here have 
NOT
+been tested and so come with no warranty.</p>
+
+<ul>
+    <li>
+        <h3>Free Linux Magazine</h3>
+
+        <p><a href="http://www.linux-magazine.com";>Linux Magazine</a> is 
available for
+        free in PDF format. Parts of each issue are available a few weeks
+        after the issue was available in printed form, and the remaining
+        articles are added until the complete issue is available, usually 4
+        months after it was available in printed form. Linux Magazine is an
+        excellent magazine which covers a broad range of Linux-related topics
+        and has articles which suit people from newbie to experienced Linux
+        users.</p>
+    </li>
+    <li>
+        <h3>Unlucky in love?</h3>
+        <p>If you find that you're unlucky in love, it just might be you that's
+        the problem. Some people aren't attracted to geeks but don't worry,
+        because here's <strong>one</strong> way to improve your chances of
+        finding "true love". Find people that are much geekier than you and,
+        when the person to whom you're attracted sees you with them, you'll
+        actually appear normal and so more attractive! The key to success is
+        finding the right people. The type of people that you need to look
+        for:</p>
+        <ul>
+            <li>Use vi, Emacs or - even better - <strong>both</strong>;</li>
+            <li>Wear a binary watch and are proud to do so;</li>
+            <li>Calculate their age according to the Unix epoch.</li>
+        </ul>
+        <p>You don't have to actually like these people; it's good enough to
+        pretend. At the right moment, provoke a discussion about which is the
+        best editor - vi or Emacs.  You must appear utterly confused, or this
+        technique will fail. Remember that you must <strong>NOT</strong>
+        contribute to the discussion.</p>
+        <p>Good luck and "May the Force be with you".</p>
+    </li>
+</ul>
+
+<p>This section relies on your contributions! If have some tips and tricks that
+you would like to be shown in the newsletter, <em>please</em> post them on the
+forums.</p>
+
+
+<h2>Focus On Package(s)</h2>
+
+<h3>lsof</h3>
+
+<p>"Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open 
Files,
+and it does just that. It lists information about any files that are open by
+processes currently running on the system. It can also list communications open
+by each process."</p>
+
+<p>lsof is more useful than you might first think because, in UNIX, everything
+is a file. It's extremely useful, for example, when you know some process has a
+file open but it's not obvious just which process has it open. For some great
+examples of what it can be used for, refer to
+<a href="http://dmiessler.com/study/lsof/";>this page</a>.
+</p>
+
+
+<h2>Bug fixes</h2>
+
+<p>The following table gives you a overview of activity on bugs and feature
+requests as at 6 April 2009. In each cell of the table is a link to a detailed
+list of the relevant bugs or feature requests.</p>
+
+<table border=1 cellpadding=5 cellspacing=0>
+<tr>
+    <th>Activity</th>
+    <th>Bugs</th>
+    <th>Feature<br>Requests</th>
+</tr>
+<tr>
+    <td>Open</td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type[]=1&sev[]=&pri[]=&due[]=&reported[]=&cat[]=&status[]=open&percent[]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index";>211</a></td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type[]=2&sev[]=&pri[]=&due[]=&reported[]=&cat[]=&status[]=open&percent[]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index";>223</a></td>
+</tr>
+<tr>
+    <td>Opened since the last newsletter</td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type[]=1&sev[]=&pri[]=&due[]=&reported[]=&cat[]=&status[]=open&percent[]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=2009-03-23&openedto=&closedfrom=&closedto=&do=index";>18</a></td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type[]=2&sev[]=&pri[]=&due[]=&reported[]=&cat[]=&status[]=open&percent[]=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=2009-03-23&openedto=&closedfrom=&closedto=&do=index";>1</a></td>
+</tr>
+<tr>
+    <td>Closed since the previous newsletter</td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type%5B%5D=1&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=closed&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=2009-03-23&closedto=&do=index";>12</a></td>
+    <td><a 
href="http://bugs.frugalware.org/index.php?string=&project=1&type%5B%5D=2&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=closed&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=2009-03-23&closedto=&do=index";>0</a></td>
+</tr>
+</table>
+
+
+<h2>Security announcements</h2>
+
+<p><b>Remember</b> - According to the normal support arrangements for
+Frugalware, the release of 1.0 ("Anacreon") means that no further security or 
bug
+fixes will be released for Frugalware 0.9 ("Solaria") or earlier releases.</p>
+
+<p>Here is a list of <a href="/security">security issues</a> which have been
+discovered and fixed in the 1.0 release since the previous newsletter.</p>
+
+<table border=1 cellpadding=5 
cellspacing=0><tr></tr><th>FSA</th><th>Package</th>
+    <th>FSA Description</th><th>Upgrade To</th></tr>
+<tr><td>FSA589</td><td>drupal6-cck</td><td>A security issue has been reported
+in the CCK Field Privacy module for Drupal, which can be exploited by malicious
+people to bypass certain security restrictions</td>
+<td>drupal6-cck-6.x_2.2-1anacreon1</td></tr>
+</table>
+
+
+<h2>About the newsletter</h2>
+
+<h3>Author</h3>
+<p>The Frugalware newsletter is written and edited by Russell Dickenson (AKA
+phayz). Credit for the Frugalware distribution goes to the development 
team.</p>
+
+<h3>Translations</h3>
+<p>The newsletter is currently translated into French and Danish. The <a
+href="http://frugalware-fr.tuxfamily.org/forums/index.php?board=34.0";>French
+translation</a> is provided by the French Frugalware community. The <a
+href="http://frugalware.dk/?cat=5";>Danish translation</a> is provided by the
+Danish Frugalware community. Thanks to all those involved in providing and
+hosting these translations.</p>
+
+<h3>Release</h3>
+<p>To allow time for review and corrections, each newsletter is written ahead 
of
+its release date. Therefore it may not mention events which occurred in the few
+days before its release - e.g. security fixes. To be sure that you've got the
+very latest information on these topics, go to the appropriate page of the
+Frugalware web site.</p>
+
+<h3>Feedback</h3>
+<p>If you have feedback about the Frugalware newsletter - whether good or bad -
+please provide it via the forums. Your feedback is valuable because we want the
+newsletter to meet the needs of Frugalware's users.</p>
diff --git a/frugalware/xml/news.xml b/frugalware/xml/news.xml
index c7069d6..d975437 100644
--- a/frugalware/xml/news.xml
+++ b/frugalware/xml/news.xml
@@ -22,6 +22,26 @@ Example: Mon, 07 Aug 2006 12:34:56 -0600 -->

<news>
<post>
+        <id>132</id>
+        <title>Frugalware Newsletter Issue 42</title>
+        <date>Mon, 06 Apr 2009 22:12:36 +1000</date>
+        <author>phayz</author>
+        <hidden>0</hidden>
+        <content><![CDATA[
+            The newsletter's aim is to keep you up to date with what's 
happened recently in the world of Frugalware.<br />
+            Features of this issue include:
+            <ul>
+                <li>To infinity...and beyond</li>
+                <li>Will the <em>real</em> Cedric(k) please stand up?</li>
+                <li>Frugalware's developers are people too - VMiklos</li>
+                <li>Tips and tricks - Unlucky in love?</li>
+                <li>Focus On Package(s) - lsof</li>
+            </ul>
+            You can read it <a href="/newsletter/42">here</a>. We hope you 
like it!
+            ]]>
+        </content>
+    </post>
+    <post>
<id>131</id>
<title>Solaria: End of life</title>
<date>Wed, 25 Mar 2009 23:36:55 +0100</date>
_______________________________________________
Frugalware-git mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-git

Reply via email to