<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>NFG's DBMail Blog - community</title>
    <link>http://blog.dbmail.eu/</link>
    <description>You get what you need</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <pubDate>Tue, 19 Jan 2010 09:28:18 GMT</pubDate>

    <image>
        <url>http://blog.dbmail.eu/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: NFG's DBMail Blog - community - You get what you need</title>
        <link>http://blog.dbmail.eu/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>DBMail on twitter</title>
    <link>http://blog.dbmail.eu/archives/11-DBMail-on-twitter.html</link>
            <category>community</category>
    
    <comments>http://blog.dbmail.eu/archives/11-DBMail-on-twitter.html#comments</comments>
    <wfw:comment>http://blog.dbmail.eu/wfwcomment.php?cid=11</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.dbmail.eu/rss.php?version=2.0&amp;type=comments&amp;cid=11</wfw:commentRss>
    

    <author>nospam@example.com (Paul J Stevens)</author>
    <content:encoded>
    &lt;p&gt;
I&#039;ve added a post-receive hook to my GIT repository at git.dbmail.eu so you can stay in touch with dbmail changes via twitter.
&lt;/p&gt;
&lt;p&gt;
You can follow me at http://twitter.com/pjstevns.
&lt;/p&gt;
&lt;p&gt;
The script I&#039;m using is really simple. Some others might also find this useful:
&lt;/p&gt;
&lt;pre&gt;
#!/bin/sh

# copyright Paul Stevens, 2010, paul@nfg.nl
# licence GPLv2
#
# example hook script to send out twitter messages.
# This script will send out messages summarizing new revisions
# introduced by the change received
#
#
# Config
# ------
# hooks.twitterid
#   the username on twitter
# hooks.twitterpw
#   the password on twitter
# hooks.hashtag
#   insert a hashtag at the start of the message
# hooks.hashurl
#   replace hash signs in commit messages with an url. This
#   is used to link hash ids in messages to a bugtracker since
#   they typically refer to a bug-id.
#


GIT_DIR=$(git rev-parse --git-dir 2&gt;/dev/null)
if [ -z &quot;$GIT_DIR&quot; ]; then
	echo &gt;&amp;2 &quot;fatal: post-receive: GIT_DIR not set&quot;
	exit 1
fi
projectdesc=$(sed -ne &#039;1p&#039; &quot;$GIT_DIR/description&quot;)
# Check if the description is unchanged from it&#039;s default, and shorten it to a
# more manageable length if it is
if expr &quot;$projectdesc&quot; : &quot;Unnamed repository.*$&quot; &gt;/dev/null
	then
	projectdesc=&quot;UNNAMED PROJECT&quot;
fi


generate_message()
{
	oldrev=$(git rev-parse $1)
        newrev=$(git rev-parse $2)
	refname=&quot;$3&quot;
	message=`git log --pretty=oneline ${oldrev}..${newrev} $refname|cut -f2- -d&#039; &#039;|sed &#039;s/$/, /g&#039;`
	hashurl=`echo &quot;$hashurl&quot;|sed &#039;s/?/?/&#039;`
	if [ -n &quot;$hashtag&quot; ]; then
		echo -n &quot;#${hashtag} &quot;
	fi
	echo $message|sed -e &quot;s,#,${hashurl},g&quot; -e &#039;s/,$//&#039;
}		

send_twitter()
{
	message=&quot;$@&quot;
	curl --basic --user ${twitterid}:${twitterpw} --data status=&quot;$message&quot; 
		https://twitter.com/statuses/update.xml &gt;/dev/null
}




twitterid=$(git repo-config hooks.twitterid)
twitterpw=$(git repo-config hooks.twitterpw)
hashurl=$(git repo-config hooks.hashurl)
hashtag=$(git repo-config hooks.hashtag)

# --- Main loop
# Allow dual mode: run from the command line just like the update hook, or if
# no arguments are given then run as a hook script
if [ -n &quot;$1&quot; -a -n &quot;$2&quot; -a -n &quot;$3&quot; ]; then
        # Output to the terminal in command line mode - if someone wanted to
        # resend an email; they could redirect the output to sendmail themselves
        generate_message $1 $2 $3
else
        while read oldrev newrev refname
        do
                message=`generate_message $oldrev $newrev $refname`
		send_twitter &quot;$message&quot;
        done
fi
&lt;/pre&gt;

 
    </content:encoded>

    <pubDate>Tue, 19 Jan 2010 10:11:32 +0100</pubDate>
    <guid isPermaLink="false">http://blog.dbmail.eu/archives/11-guid.html</guid>
    <category>git</category>
<category>twitter</category>

</item>
<item>
    <title>re-theming dbmail.org</title>
    <link>http://blog.dbmail.eu/archives/10-re-theming-dbmail.org.html</link>
            <category>community</category>
    
    <comments>http://blog.dbmail.eu/archives/10-re-theming-dbmail.org.html#comments</comments>
    <wfw:comment>http://blog.dbmail.eu/wfwcomment.php?cid=10</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.dbmail.eu/rss.php?version=2.0&amp;type=comments&amp;cid=10</wfw:commentRss>
    

    <author>nospam@example.com (Paul J Stevens)</author>
    <content:encoded>
    &lt;p&gt;The look and functionality of dbmail.org has been a neglected steph-child of abandonment for too long. So I decided to spent
some time revising and redesigning.&lt;/p&gt;

&lt;p&gt;The major goal was offering a more professional impression to first time visitors, and providing a better insight into the dynamic of 
the project as a whole. This is why I made it a portal-style site, showing several small blocks of recent activity concerning code-changes,
news, and yes blog entries like this one.&lt;/p&gt;

&lt;p&gt;I&#039;m not a graphics designer, but I still hope the designers among you won&#039;t be too offended by the lack of gloss and finish. Still, I did utilize one
small trick by applying another project I&#039;ve been buzy working on &lt;a href=&quot;http://webfonts.biz&quot; title=&quot;WebFonts: web fonts made easy&quot;&gt;http://webfonts.biz&lt;/a&gt; - a font-service.&lt;/p&gt;

&lt;p&gt;Hope you like it.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Thu, 07 Jan 2010 11:43:19 +0100</pubDate>
    <guid isPermaLink="false">http://blog.dbmail.eu/archives/10-guid.html</guid>
    
</item>
<item>
    <title>Welcome to my dbmail experience</title>
    <link>http://blog.dbmail.eu/archives/1-Welcome-to-my-dbmail-experience.html</link>
            <category>community</category>
    
    <comments>http://blog.dbmail.eu/archives/1-Welcome-to-my-dbmail-experience.html#comments</comments>
    <wfw:comment>http://blog.dbmail.eu/wfwcomment.php?cid=1</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.dbmail.eu/rss.php?version=2.0&amp;type=comments&amp;cid=1</wfw:commentRss>
    

    <author>nospam@example.com (Paul J Stevens)</author>
    <content:encoded>
    &lt;p&gt;
Here I will come to share what it means for me to work on this little open-source project called dbmail. Hopefully it will be as much of a learning experience to write about it, as it is to work on it.
&lt;/p&gt;
&lt;p&gt;
But first, a disclaimer; Whatever I tell you, don&#039;t take my word for it! Seek confirmation from those you trust. If you want to talk about a specific problem, seek the best specialist you can find.
&lt;/p&gt;
&lt;p&gt;
Dbmail, for me, is about writing code, enjoying the act of creation, learning to love C, dealing with matters of consistency, assurance, and trust. It&#039;s about getting it right. Making mistakes. And being honest about both. 
&lt;/p&gt;
&lt;p&gt;
Communities of trust don&#039;t just happen. They take a lot of effort, affection and rejection. Trust yourself as well as others. Where fear or lack of confidence do not deflect you from pursuing your vision, experience will be your teacher. Perseverance will take us halfway any task. Stick to it, and enjoy the ride. 
&lt;/p&gt; 
    </content:encoded>

    <pubDate>Thu, 15 May 2008 22:44:44 +0200</pubDate>
    <guid isPermaLink="false">http://blog.dbmail.eu/archives/1-guid.html</guid>
    <category>community</category>
<category>vision</category>

</item>

</channel>
</rss>