<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Times New Roman Bold";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p.Contract1Level, li.Contract1Level, div.Contract1Level
{margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.5in;
text-indent:-.5in;
mso-list:l0 level1 lfo3;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Contract2Level, li.Contract2Level, div.Contract2Level
{margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.5in;
text-indent:-.5in;
mso-list:l0 level2 lfo3;
font-size:11.0pt;
font-family:"Times New Roman";}
p.Contract3Style, li.Contract3Style, div.Contract3Style
{margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.5in;
text-indent:-.5in;
mso-list:l0 level3 lfo3;
font-size:11.0pt;
font-family:"Times New Roman";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:36785278;
mso-list-template-ids:-656662344;}
@list l0:level1
{mso-level-style-link:"Contract 1 Level";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.5in;
mso-ansi-font-size:11.0pt;
mso-bidi-font-size:11.0pt;
font-family:"Times New Roman Bold";
mso-ansi-font-weight:bold;
mso-ansi-font-style:normal;}
@list l0:level2
{mso-level-style-link:"Contract 2 Level";
mso-level-text:"%1\.%2";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level3
{mso-level-style-link:"Contract 3 Style";
mso-level-text:"%1\.%2\.%3";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level4
{mso-level-text:"%1\.%2\.%3\.%4";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.5in;}
@list l0:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5";
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.75in;}
@list l0:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.75in;}
@list l0:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
@list l0:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
@list l0:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-1.0in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Yes, Markus, that does clarify it. Thank you.
We can have a discussion of whether we want to use some sort of digital
signing mechanism for key votes (annual member meeting comes to mind). I don’t
think it is necessary to add anything to the bylaws on this, but I agree it is
useful to consider this in the future.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>-Rich<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Markus Neteler
[mailto:neteler.osgeo@gmail.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, February 26, 2006
1:06 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">board@board.osgeo.org</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [OSGeo-Board] Bylaws
posted</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>Hi Rich,<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>On 2/23/06, <b><span style='font-weight:bold'>Rich
Steele</span></b> <<a href="mailto:Rich.Steele@autodesk.com">Rich.Steele@autodesk.com</a>>
wrote:</span></font></span><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>...<br>
"article IV: sec 4.2, second paragraph. Does it make sense to<br>
add/suggest digitally signed messages via GnuPG? I would at least<br>
recommend the use of GnuPG."<br>
<br>
Is encryption really required for notices? The purpose of this
section <br>
is simply to ensure that a person receives actual notice of a scheduled<br>
meeting. The law permits sending an email to suffice as notice so
long<br>
as the recipient has consented and provided a specific email address. <br>
Can you explain why you would recommend GnuPG in this situation? I'm<br>
not sure I understand.<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<br>
In general, there are two modes:<br>
1. encryption of messages (think hiding, doesn't apply here)<br>
2. digital signing (think ensuring that the mail really originated from the
sender,<br>
message is *not* encrypted)<br>
<br>
I thought of (2) to ensure that the sender is really the sender. This is done
by<br>
a pair of public/private key,<br>
<br>
GnuPG, because it's a free implementation for both (1) and (2), see<br>
<a href="http://en.wikipedia.org/wiki/Gnupg">http://en.wikipedia.org/wiki/Gnupg</a>
. There are plugins for most email<br>
software packages available.<br>
<br>
The correct term to refer to will be OpenPGP, see<br>
<a href="http://en.wikipedia.org/wiki/OpenPGP">http://en.wikipedia.org/wiki/OpenPGP</a><br>
<br>
Of course the dissemination of info isn't that complicated,<br>
I meant in fact to digitally sign votes etc. which are sent over<br>
email.<br>
<br>
Two days ago, I had only 5 min to hack down my comments in <br>
a break, now I am back home. I hope this clarifies my comment <br>
(somewhat). <br>
<br>
Markus<o:p></o:p></span></font></p>
</div>
</div>
</div>
</div>
</body>
</html>