Hi David<div><br></div><div>Could I suggest that you address this message to the QGIS Users mailing list? The community-team list is used to organise community related work such as writing the user manuals, web site etc. You can subscribe to the users list here:</div>
<div><br></div><div><a href="http://lists.osgeo.org/mailman/listinfo/qgis-user">http://lists.osgeo.org/mailman/listinfo/qgis-user</a></div><div><br></div><div>Regards</div><div><br></div><div>Tim<br><br><div class="gmail_quote">
On Wed, Mar 6, 2013 at 1:04 AM, David Saeger <span dir="ltr"><<a href="mailto:saegeritup@gmail.com" target="_blank">saegeritup@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>After attending a wonderful conference on Federal Applications of
OS Geo software I am re motivated to approach completing a VPAT for
QGIS. My estimation of the importance of doing so was reinforced after
hearing some knowledgeable friends of the OS Geo community who work in
the federal environment bemoan how hard it is to get software approved
and specifically point to the Section 508 compliance/VPAT (or lack therof) as a reason why. <br><br></div><div>What is a VPAT?: <br><div><font color="#000000" face="sans-serif"><span style="line-height:19.2px">Here is a general guidelines for Section 508 compliance:</span></font></div>
<div><font color="#000000" face="sans-serif"><span style="line-height:19.2px"><a href="http://www.uspto.gov/about/offices/cio/section508/14e.jsp" target="_blank">http://www.uspto.gov/about/offices/cio/section508/14e.jsp</a></span></font></div>
<br></div><div>
<br>After my first go at this, there are a items VPAT that I am unable
to answer. It occurs to me that it would be great to use the mechanics
of a platform like stack-exchange to track the discussion and answers to
some of the questions posed by the VPAT and as an experiment I posted
one of the questions I had here: <a href="http://gis.stackexchange.com/questions/53454/qgis-vpat-section-1194-21c" target="_blank">http://gis.stackexchange.com/questions/53454/qgis-vpat-section-1194-21c</a><br>
<br></div><div>The only thing I have received so far is a comment
telling me that the userbase of this forum is oriented toward a crowd
who may not be suited to answering these types of questions. I agree
that it is a bit of an unusual type of question to ask on that forum. I
think however, that utilizing a forum like stackexchange to help develop
the VPAT would be a great example of how OS projects can get these
types of regulatory documents filled out in a transparent and efficient
way. I also think that it is possible that some of the questions on the
VPAT might benefit from input from a wider audience than exists on the
QGIS dev list serve. <br>
<br></div><div>Any thoughts? Should I just post my questions here? Do
any of you have suggestions for a better venue? Any of y'all want to
take a crack at the item I listed on stackexchange? <br><br></div><div>Thanks,<br>
<br></div><div>-David<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><br><br><br><br>-- <br>David Saeger<br>305.984.5539
</font></span></div>
<br>_______________________________________________<br>
Qgis-community-team mailing list<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Tim Sutton - QGIS Project Steering Committee Member (Release Manager)<br>==============================================<br>Visit <a href="http://linfiniti.com" target="_blank">http://linfiniti.com</a> to find out about:<br>
* QGIS programming services<br> * GeoDjango web development<br> * FOSS Consulting Services<br>Skype: timlinux Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a><br>==============================================
</div>