<div>
Thinking:
</div><div><br></div><div>It is something we look for - but it is something we look for before accepting a project into incubation is it not (see http://www.osgeo.org/incubator/process/application.html).</div><div><br></div><div>Still adding a section (at the top!) called "open" would be good.</div><div><br></div><div>Rather than go back and forth on email I have added the section and invite your review.</div><div><br></div>
<div><div>Additional comments in line.</div><div><br></div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">- To be honest I do not understand why committee requirements are<span><div><div><div>grouped under a "Community" top-level section that falls outside the </div><div>checklist section... is this intended or a mistake?</div></div></div></span></blockquote><div><br></div><div>It is intended; it is not part of the basic checklist required for graduation. We could rename the section as "OSGeo Participation" if you like … </div><div><br></div><div>Basically the incubation committee is not acting as an enforcer for other committees; instead we open the door to the foundation after checking the project has an open source license and is not otherwise embarissing in public.</div><div><br></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">section be called "other committee requirements" or something like that?<span><div><div><div> Shouldn't this</div><div>And also let's make it clear whether those requirements from other </div><div>committees are part of the graduation checklist or not (since this group </div><div>falls outside the "= Checklist =" grouping it's not clear whether they </div><div>are hard requirements or not).</div></div></div></span></blockquote><div>So yes this is very much intentional; it was hard in previous version of this checklist to separate out what was needed form what was an invitation.</div><div> </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">- With respect to the "Community" sub-section itself, I'd be tempted to<span><div><div><div>change that title to be a second-level like the others (i.e. == </div><div>Community ==) and make it fit in the master checklist, and then add a </div><div>checklist item "Project has demonstrated that it has an open and </div><div>active/healthy users and developers community."</div><div><br></div><div>Sorry for the late feedback...</div></div></div></span></blockquote><div>It is okay; can you review the page quickly? I will make sure I am on IRC if you want to talk things over.</div><div><br></div><div>Jody </div><div><br>
</div>