<div>This discussion is moving along at a great rate; could we capture the "answers" in a wiki page as they are sorted out? I am really keen to get through this promptly; and we can ask for any feedback in Monday's incubation meeting.</div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><blockquote type="cite"><div><div> In any case, our docs are "open". I think OSGeo's main concern is preventing things like (past versions of) numpy that had free code, but no docs, unless you paid.</div></div></blockquote></div></div></span>So at least you and I think that we should license our docs under our <span>existing code license. In all cases, they are certainly 'open'.</span></blockquote><div>If you have this sorted; I am interested in writing down what is in place today. We can always hunt down someone with more experience if we need guidance on where to go tomorrow.</div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><blockquote type="cite"><div><div>Is the #geomoose IRC room archived somewhere?</div></div></blockquote></div></div></span>No. I have some logs locally on various computers but have made no<span><div><div><div>attempt to really log it. If the channel is active, we could ask Gary</div><div>Sherman to send his bot and post the archives as he kindly does for</div><div>some other OSGeo Projects.</div></div></div></span></blockquote><div>We post the geotools logs to a blog or something whenever we have a formal IRC meeting.</div><div>Indeed the most popular way to end a meeting was to offer to post the logs.</div><div><br></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><blockquote type="cite"><div><blockquote type="cite"><div><blockquote type="cite"><div><div> The project follows a documented testing process.</div><div> Ideally, this includes both automated and manual testing</div></div></blockquote><div><br></div><div>More than Incubation, this could really help us. I have some mediocre</div><div>ideas on this (like bash/curl/diff/etc to make autotests), if others</div><div>have good ideas, I'd be interested in pursuing that.</div></div></blockquote><div><br></div><div>The "hard" part is what I'd really like to automatically test is the JavaScript part across multiple browsers. Is there such a thing as a build-bot for a browser based app?</div></div></blockquote></div></div></span></blockquote><div>Consider focusing on what you do for testing today?</div><div><br></div><div>Minimal:</div><div>- Make an experimental release (often called release candidate) and ask the community to test for a week. if they don't complain loud enough publish it as the release.</div><div><br></div><div>Manual:</div><div>- a couple of sample data sets are put through their paces manually. Often this is a good approach if you have training material, or installation guides to start from.</div><div><br></div><div>Maximal:</div><div>- conformance tests provided by a third part (example OGC "Cite" tests available for several of their web services; and possibly some clients)</div>