[OpenLayers-Dev] Github or Trac?
Bart van den Eijnden
bartvde at opengeo.org
Wed May 23 08:22:38 EDT 2012
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 :-)
So basically a choice to make would be github pages or github wiki (or both) if we decide to "migrate" what we have.
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).
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.
All your other suggestions make perfect sense to me as well.
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On May 23, 2012, at 1:00 PM, Peter Robins wrote:
> On 23 May 2012 09:52, Bart van den Eijnden <bartvde at opengeo.org> wrote:
>> Also, one thing I'd like to discuss for the future is if we have plans to
>> migrate the Trac Wiki to the github Wiki. I would be in favor of this.
> the same point you made before about many of the tickets being
> out-of-date also applies to the wiki. As with tickets, I would suggest
> starting again.
> Some other suggestions:
> - use github pages (openlayers.github.com) rather than wiki. Wiki has
> advantage that anyone can edit at any time, but that is also a
> disadvantage, as there's no opportunity for others to discuss proposed
> changes. With Github pages, you would submit pull requests as with
> code changes, which enables discussion (though it does add to the
> workload of core developers). An additional advantage is that you can
> include any css/js with github pages that you can't with wiki.
> - merge what is currently in docs.openlayers.org with this new wiki
> replacement. I don't see the advantage of having this in a separate
> place, generated by entirely different software, as at present.
> - make it a rule that pull requests for code changes should also
> include updates to docs where relevant
> - set up a separate repo for v3, and use the issue tracker there for
> discussion of proposed new/changed/improved functionality - i.e.
> separate out issues that won't be addressed in v2. In fact, if there's
> a serious intention to get moving with v3, it might be better to
> concentrate documentation effort on that rather than v2.
> I too can help out with docs content.
> Dev mailing list
> Dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dev