<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I am always trying to improve my English and look op the words and
expressions they didn't teach us at our (Dutch) school. Wikipedia says
(<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Pinky_swear">http://en.wikipedia.org/wiki/Pinky_swear</a>): <br>
<br>
"Traditionally, the pinky swear is considered binding and tantamount to
a <a href="http://en.wikipedia.org/wiki/Handshake" title="Handshake">handshake</a>
in terms of sealing a deal. The pinky swear originally indicated that
the person who breaks the promise must cut off their pinky finger.<sup
id="cite_ref-1" class="reference"><a
href="http://en.wikipedia.org/wiki/Pinky_swear#cite_note-1"><span>[</span>2<span>]</span></a></sup>
In modern times, pinky swearing is a more informal way of sealing a
promise. It is most common among school-age children and close friends.
The pinky swear signifies a promise that cannot be broken or
counteracted by the <a
href="http://en.wikipedia.org/wiki/Crossed_fingers"
title="Crossed
fingers">crossing of fingers</a> or other such
trickery.<sup id="cite_ref-2" class="reference"><a
href="http://en.wikipedia.org/wiki/Pinky_swear#cite_note-2"><span>[</span>3<span>]</span></a></sup>
The Pinky Swear can be broken if all parties agree. Pinky promises are
also only valid if all parties agree prior to interlocking pinkies. If
it is broken without the consent of the other parties, that person is
able to kill the promise breaker. A pinky swear can however be broken
if the majority of candidates chose to break it."<br>
<br>
I propose that these guidelines be added to the commiter guidelines in
RFC 7.1, corrected for spelling of course :-).<br>
<br>
<a class="moz-txt-link-freetext" href="http://mapserver.org/development/rfc/ms-rfc-7.1.html">http://mapserver.org/development/rfc/ms-rfc-7.1.html</a><br>
<br>
Jan<br>
<br>
On 22-2-2010 15:02, Dan Little wrote:
<blockquote cite="mid:601119.73165.qm@web51403.mail.re2.yahoo.com"
type="cite">
<pre wrap="">Upon approval, I will comply with RFC 7.1. Promise/Pinky-Swear.
----- Original Message ----
</pre>
<blockquote type="cite">
<pre wrap="">From: thomas bonfort <a class="moz-txt-link-rfc2396E" href="mailto:thomas.bonfort@gmail.com"><thomas.bonfort@gmail.com></a>
To: Frank Warmerdam <a class="moz-txt-link-rfc2396E" href="mailto:warmerdam@pobox.com"><warmerdam@pobox.com></a>
Cc: MapServer Dev Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:mapserver-dev@lists.osgeo.org"><mapserver-dev@lists.osgeo.org></a>
Sent: Sun, February 21, 2010 10:53:20 PM
Subject: Re: [mapserver-dev] Motion: Commit rights for Dan Little
+1
--
thomas
On Sun, Feb 21, 2010 at 22:55, Frank Warmerdam wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Howard Butler wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
All,
I would like to propose granting commit rights to Dan Little. He has been
dropping patches in tickets and on the mailing list for a bit, and he has
attended both the Toronto and New York sprints and contributed significantly
in both. He has an interest in things like SVG symbol rendering, variable
binding for the database drivers, and potentially some MapScript cleanups as
he runs into issues. Commit rights will lower the friction to allow him to
keep making more significant and useful contributions to the project.
/me starts with a +1
</pre>
</blockquote>
<pre wrap="">
+1 Frank
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam,
<a class="moz-txt-link-abbreviated" href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</a>
light and sound - activate the windows | <a class="moz-txt-link-freetext" href="http://pobox.com/~warmerdam">http://pobox.com/~warmerdam</a>
and watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
mapserver-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
mapserver-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
mapserver-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a>
</pre>
</blockquote>
</body>
</html>