<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Peter for sharing your thoughts. I agree that a fresh start would also be beneficial here, which I did notice when I edited the current Trac wiki this morning :-)<div><br></div><div>So basically a choice to make would be github pages or github wiki (or both) if we decide to "migrate" what we have.</div><div><br></div><div>I agree with you that github pages would be a good replacement for all we have now (wiki, prose docs, website), and I would prefer to have one system over 2 (pages and wiki).</div><div><br></div><div>It would be interesting to see how many / how often community members have edited the current Trac wiki as opposed to OL devs. My gut feeling is that it has been mostly edited by OL devs anyway.</div><div><br></div><div>All your other suggestions make perfect sense to me as well.</div><div><br></div><div>Best regards,</div><div>Bart</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>-- <br>Bart van den Eijnden<br>OpenGeo - <a href="http://opengeo.org/">http://opengeo.org</a><br>Expert service straight from the developers.</div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On May 23, 2012, at 1:00 PM, Peter Robins wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 23 May 2012 09:52, Bart van den Eijnden <<a href="mailto:bartvde@opengeo.org">bartvde@opengeo.org</a>> wrote:<br><blockquote type="cite">Also, one thing I'd like to discuss for the future is if we have plans to<br></blockquote><blockquote type="cite">migrate the Trac Wiki to the github Wiki. I would be in favor of this.<br></blockquote><br>the same point you made before about many of the tickets being<br>out-of-date also applies to the wiki. As with tickets, I would suggest<br>starting again.<br><br>Some other suggestions:<br><br>- use github pages (<a href="http://openlayers.github.com">openlayers.github.com</a>) rather than wiki. Wiki has<br>advantage that anyone can edit at any time, but that is also a<br>disadvantage, as there's no opportunity for others to discuss proposed<br>changes. With Github pages, you would submit pull requests as with<br>code changes, which enables discussion (though it does add to the<br>workload of core developers). An additional advantage is that you can<br>include any css/js with github pages that you can't with wiki.<br><br>- merge what is currently in <a href="http://docs.openlayers.org">docs.openlayers.org</a> with this new wiki<br>replacement. I don't see the advantage of having this in a separate<br>place, generated by entirely different software, as at present.<br><br>- make it a rule that pull requests for code changes should also<br>include updates to docs where relevant<br><br>- set up a separate repo for v3, and use the issue tracker there for<br>discussion of proposed new/changed/improved functionality - i.e.<br>separate out issues that won't be addressed in v2. In fact, if there's<br>a serious intention to get moving with v3, it might be better to<br>concentrate documentation effort on that rather than v2.<br><br>I too can help out with docs content.<br>_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>http://lists.osgeo.org/mailman/listinfo/openlayers-dev<br></div></blockquote></div><br></div></body></html>