<html>
<head>
</head>
<body style="margin-right: 4px; font-style: normal; font-weight: normal; font-size: 10pt; margin-top: 4px; margin-left: 4px; margin-bottom: 1px; line-height: normal; font-family: Tahoma; font-variant: normal">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Dean,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Excellent on the project offer. What timeline are you anticipating? I'm thinking it may take some time to get certain pieces into place and agreed on by everyone, which I think is mostly desirable for everyone's benefit in the long run.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">The process may move along slightly slower than in the recent past as well for obvious reasons. But I think building the process out around an actual project will be a good one overall.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br><br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> "DEAN ANDERSON" <ANDERSON.DEAN@co.polk.or.us> wrote:<br> </p>
<table style="margin-right: 0; margin-left: 15px; margin-top: 0; font-size: 1em; margin-bottom: 0" bgcolor="#f3f3f3" border="0">
<tr>
<td>
<div style="padding-left: 7px; border-left: solid 1px #050505">
<div>
<p style="margin-bottom: 0; margin-top: 0">
Bob </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
  </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
Yes I think this summarizes our discussions in Oregon as well.  A few issues that need to be addressed in the process. </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
  </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
1. Process to enhance core software. </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
2. Process to standardize share extensions. </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
3. Expand/standardize technical developer documentation. </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
  </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
We (Oregon Consortium) would be happy to put forth our upcoming "Phase 2" development project as way to test the process. </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
  </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
  </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
Dean Anderson </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
IT Director </p>
</div>
<div>
<p style="margin-bottom: 0; margin-top: 0">
Polk County<br><br>>>> "Bob Basques" <Bob.Basques@ci.stpaul.mn.us> 3/2/2011 7:08 AM >>><br> </p>
</div>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">All,</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I'm starting a new thread here to start up a discussion related to implementing some sort of governance model for GeoMoose.  Believe it or not, the project has gotten to where it is in a fairly fractured fashion.   There have been champions of the product from different perspectives along the way as well, developers, salesman, usability (myself), and flexibilty among others.  Each of these capabilities champions have pushed the product to where it is today in a very informal collaborative environment.  </font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I believe we're collectively at a point where the next level of operations needs to be implemented and some formality to some tasks need to be implemented.  Roadmap and feature items need to be recorded and prioritized, as well as vetting of these additions, how will they affect the product moving forward, should they be core or add-on (plugin) constructs, etc.   A capabilitites proposal and voting system needs to be implemented in some fashion as well.  I'm not suggesting jumping straight to a overly strict process, but a process does need to be described for each of these tasks inorder not to fracture resources and development aims.  Some of these topics have already been addressed on the list and some still need to be discussed further.</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">In general, I'm asking here, is it fair to assume that we're all in agreement with the above listed organizational points needed to be put more formally into place?   Yes+ or No- to  further discussing moving the GeoMoose project to a more structured one.</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">If you are on this list, you can vote.</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Thanks</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Bob Basques</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">City of Saint Paul</font> </p>
<p style="margin-bottom: 0; margin-top: 0">
<br>
</p>
</div>
</td>
</tr>
</table>
</body>
</html>